Advanced Configurations and Automation

One of Alan's tasks is data migration. The data migration is the process of transferring data between storage types, formats or computer systems.

Below is a list of the general steps for the data migration process from a project management perspective:

• Create a project plan for all tasks related to migration.
• Cleanse the legacy data that will be migrated into SAP Sales Cloud Version 2 to avoid technical errors.
• Extraction of source data from the legacy system can be automated or done manually. It is responsibility of the customer.
• Create the source files by entering the cleansed and extracted legacy data in the migration templates predefined by SAP.
• The templates provide a framework to structure the source data closely to SAP Sales Cloud Version 2 structure.
• Perform test imports of the source data. A successful test migration ensures a safe final cutover migration.
• Verify the source data by using it in test scenarios.
• Perform the final import of source data to the production system using the Data import tool

Depending on the customer landscape, data migration can be performed by leveraging standard integrations between SAP Sales Cloud Version 2 and SAP S/4HANA.

However, only a limited number of standard objects can be migrated using standard integrations.

Usually those objects are:

• Customers
• Organizational Units
• Products and Product Groups
• Registered Products (or Equipment)
• Employees

In case you need to import or export objects not supported by the standard integrations, you can use the Data Import and Export Tool:

The Data Import and Export Tool is the equivalent of the Data Workbench that was previously available in SAP Sales Cloud.

The new release of SAP Sales Cloud Version 2, has several entities supported, covering most of the use cases. 

When the integration with S/4HANA is not available, the data migration will have to be performed manually using the migration templates available from the data import and export tool within SAP Sales Cloud Version 2.

• A template is available for each migration entity that supports tool-supported migration.
• The template structure is predefined and a few changes are possible.
• Each template contains different tabs that group the data into logical units. They also provide field definitions which are used during the population of the templates.
• Once the templates have been filled, administrators can upload the data multiple times if required.

Customization refers to the process of extending or modifying the capabilities of a product or service to meet specific and unique business needs. When an off-the-shelf product or solution is purchased, it may not perfectly align with the specific requirements of a particular business or organization.

Customization allows businesses to tailor the product or service to fit their exact needs, making it more relevant, efficient, and effective for their operations.

SAP Sales Cloud Version 2 offers multiple customization options:

Integrate

SAP Sales Cloud Version 2 can integrate with other solutions (SAP and non-SAP) via different approaches:

• Mashups
• Standard REST APIs
• Event Notifications
• Webhooks

API Discovery

Because SAP Sales Cloud Version 2 uses Low-Code-No-Code composer integration, business users can easily adapt the solution to their needs. The SAP Business Accelerator Hub gives access to hundreds of APIs.

• Low-Code-No-Code Composer Integration
• SAP Business Accelerator Hub

Theming Support

With SAP Sales Cloud Version 2 administrators can customize the UI by applying different UI Themes.

Version 2 offers In-App Extensibility that allows customers and partners to extend the software platform without having to modify the original codebase.

Administrators can add to the base functionality using four different features:

• Extension Fields
• Validation Rules
• Determination Rules
• External Hooks

Extend Standard Features

• Easy to use tools to extend standard delivered applications.
• Key users can create additional fields, and modify field properties'.

Embed Side by Side Apps

• Key users can embed custom modules created in SAP Build in standard UIs using powerful mashup features.
• Certain fields can be passed from SAP Sales Cloud to the external solution.

UI Adaptation

• Key users can customize the UI look and feel using an intuitive adaptation tool.
• Changes performed are applied to all users or certain groups/personas.

Custom Logic

• Simple editor is provided for creating validation and determination rules.
• These can be used to alter the standard application behavior by adding additional checks or logic as part of the business needs.

Language Adaptation

Language adaptation tailors communication to diverse users, aligning with business and linguistic preferences. It enhances comprehension and engagement by customizing content, allowing for the modification of SAP texts, custom messages, and field labels to meet specific business needs.

This practice is crucial for global communication, ensuring information accessibility and improving user experience across various linguistic and cultural backgrounds.

As an administrator, you can translate or alter field labels, codelist descriptions, custom messages, and UI texts for applications.

Extension Fields and Mashups

Extension fields are additional fields that an administrator can add to SAP Sales Cloud Version 2, and they provide the means to store additional data for specific use cases beyond what is natively present in the solution. 

Only some entities are enabled and can be extended with new fields.

Mashups are used to integrate data from SAP's cloud solution with data provided by an online Web service or application. 

• Users can access the content provided by these Web services and applications and use it in their daily work. 
• Mashups can include Web searches, company or industry business information, or online map searches.
• When creating a Mashup, the Description, Name, and URL of the Mashup are required for configuration.

With Validation Rules, Alan can implement a custom logic where they can prevent a save or issue a warning message to users during save, based on certain conditions.

Key users can also create their own custom checks/conditions on top of SAP standard checks/validations.

With Determination Rules, key users can assign value(s) to field(s) based on specific conditions using determination. Use determinations to calculate specific field value based on certain conditions. 

Administrators can either default or propose the value or mandate a certain value using determinations.

• With a Post Hook Determination rule Alan can prevent the user to overwrite default values.
• With a Pre Hook Determination rule, users can overwrite the field values.

You can create and use External Hooks to activate external functions when you save data into an entity. This means you can customize or add extra functionalities to the saving process according to your needs using side-by-side tools such as Kyma, BTP and other external services.

Alan can generate an autoflow by either using the Administrative Console or using the quick search.

Here are some important features of Autoflow:

• Administrators can automate business processes using autoflow by defining event & condition-based rules to trigger actions like email, etc.
• As an administrator, Alan can enable autoflows for various entities including Call lists, Appointments, Leads and more.
• A visual canvas-based designer enables quick and intuitive set-up of autoflow events, condition, rules and notifications.

Autoflows involve the creation of rules which can trigger actions to:

• send event notifications to integrated solutions.
• send in-app notifications to users.
• trigger automatic emails for business objects.

The conditions are structured in groups and include criteria that must be fulfilled if a workflow action must be triggered. More than one condition can be defined using logical operators AND/OR.

• The AND operator can be defined using condition within the same group.
• To add more than one condition, use the OR operator. Add a new group to define the OR operator amongst the workflow conditions such that if conditions in at least one group are met, then the overall condition is considered fulfilled and the workflow rule has been triggered.

Defining an approval involves the creation of rules that can trigger actions such as request for approval to responsible users or direct approvers.

The following features are supported:

• Ensures business processes are followed with condition-based approvals.
• Easy to use canvas-based UX allows configuration of event & condition-based rules to trigger approval tasks to streamline your business processes.
• Visual rules designer enables quick and intuitive set-up of approval rules.