Applying Advanced Configurations and Automation

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

Here's the list of the general steps for the data migration process from a project management perspective:

• Create a project plan for all migration-related tasks.
• Cleanse legacy data that will be migrated into SAP Sales Cloud Version 2 to avoid technical errors.
• Automate or manually extract source data from the legacy system, which is the customer's responsibility.
• Enter the cleansed and extracted legacy data into the specified SAP migration templates and create the source files.
• Structure the source data closely to the SAP Sales Cloud Version 2 format using the templates' framework.
• Conduct test imports of the source data. A successful test migration guarantees a safe final cut-over migration.
• Verify the source data by using it in test scenarios.
• Conduct the final import of source data to the production system using the Data Import tool.

Depending on the customer landscape, use standard integrations between SAP Sales Cloud Version 2 and SAP S/4HANA to do data migration. However, migrate only a limited number of standard objects using standard integrations.

These objects are:

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

If you need to import or export objects that standard integrations don't support, use the Data Import and Export Tool.

The Data Import and Export Tool serves the same purpose as the Data Workbench previously available in SAP Sales Cloud.

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

When integration with SAP S/4HANA is unavailable, do data migration manually using the migration templates from the data import and export tool within SAP Sales Cloud Version 2.

• Access a template for each migration entity that supports tool-supported migration.
• Use the preset template structure, which allows a few changes.
• Navigate different tabs within each template that group the data into logical units and offer field definitions used during the template population.
• Upload the data several times after filling in the templates, if needed.

Customization involves changing or extending a product or service to meet specific business needs. Buying a ready-made solution doesn't always match all requirements. It makes products or services more relevant and efficient for businesses.

SAP Sales Cloud Version 2 offers several customization options:

With Validation Rules, Alan implements custom logic that either prevents a save or shows a warning message to users during save, based on specific conditions.

Key users also create their own custom checks or conditions besides the SAP standard checks and validations.

Determination Rules allow key users to assign values to fields based on specific conditions. Use these rules to calculate a specific field value depending on certain conditions.

Administrators either default to a value, propose a value, or mandate a value using determinations.

• With a Post- Hook Determination rule, Alan prevents the user from overwriting default values.
• With a Pre- Hook Determination rule, users overwrite field values.

Create and use External Hooks to activate external functions when you save data into an entity. This means customizing or adding extra functionality to the saving process to meet specific needs, using side-by-side tools such as Kyma, BTP, and other external services.

Alan generates an Autoflow using either the Administrative Console or the quick search.

Here are some important features of Autoflow:

• Automate business processes using AutoFlow by defining event and condition-based rules to trigger actions, such as emails, as administrators do.
• Enable Autoflows for various entities, including Call lists, Appointments, Leads, and more.
• Use a visual canvas-based designer for quick, intuitive setup of Autoflow events, conditions, rules, and notifications.

Autoflows involve the creation of rules that trigger actions to:

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

Structure conditions into groups and include criteria that trigger a workflow action when met. Define several conditions using logical operators AND/OR.

• Define the AND operator using conditions within the same group.
• Use the OR operator to add various conditions. Add a new group for the OR operator so that meeting conditions in one group fulfills the overall condition and triggers the workflow.

Defining an approval involves creating rules that trigger actions, such as asking for approval from responsible users or direct approvers.

The system supports the following features:

• Make sure that you follow business processes with condition-based approvals.
• Use an easy-to-use canvas-based UX to configure event and condition-based rules to trigger approval tasks, simplifying your business processes.
• Employ the visual rules designer to enable quick, intuitive setup of approval rules.

Alan, the administrator responsible for managing the system, needs to set up a new Autoflow rule within SAP Sales Cloud Version 2. This rule creates an information notification whenever someone creates a new Lead with the source Cyclo Clothing in the system and then sends it to Victoria.