Introducing Derivation Scenarios

Objective

After completing this lesson, you will be able to describe how to automate master data processes with derivation scenarios

Manage Derivation Scenarios

You can use derivation scenarios to deduce master data based on rules and a defined scope. Derivation scenarios are used during master data processes to ensure data quality, for example in mass processing and consolidation as well as in change requests.

Derivation rules are introduced to derive the value(s) of single or multiple fields. This includes the ability to mark the derived value as a default value. Derivation rules can also create and update dependent entities (for example, create a storage location if a plant is created).

Derivation scenarios are provided to combine derivation rules into executable and manageable units. This facilitates the lifecycle management, configuration, and data maintenance by business users.

With the Define Derivation Scenarios app, you can create and edit derivation scenarios. A derivation scenario consists of one or more derivation rules, which control how target values are determined from source values. The process of defining derivation scenarios and rules is shared collaboratively between different roles.

If you want to reuse your derivation scenarios in another system, you can use the Export Derivation Scenarios and Import Derivation Scenarios apps. The derivation scenarios and rules are validated before you can carry out the export or import steps.

Define Derivation Scenarios

Business users define the structure of a derivation scenario in a user-friendly SAP Fiori UI. With the Define Derivation Scenarios app, you can create and edit derivation scenarios for your product and business partner data. You use derivation scenarios to deduce master data based on rules and a defined scope to ensure data quality. A derivation scenario consists of one or more derivation rules. Use your derivation scenarios in change requests, and mass processing and consolidation.

Use the Define Derivation Scenarios app to perform the following:

Define and edit derivation scenarios, including their details.
Define and edit one or more derivation rules for each derivation scenario, including their details.
Enable rules for execution in master data governance processes.
Navigate to the BRFplus Workbench to define scope expressions and decision tables.

To set up derivation scenarios in an efficient manner, use copy functionality. After copying a derivation scenario, you can adjust the derivation rules.

In the BRFplus Workbench you can define scope expressions and decision tables.

User Roles to Create a Derivation Scenario

Creating a derivation scenario is typically a collaboration between different designated user roles.

User Roles

Derivation Scenario Owner
Ensures that the derivation scenario works as expected by the business process
Implementation Expert
Ensures that the decision logic in BRFplus and any custom logic works as required
Derivation Rule Owner
Ensures that the derivation rules produce the correct values, approves them, and decides when the rules are applied
Data Owner
Enters the values that are derived by rule for the area for which they are responsible
For example, there can be different data owners for different company codes.

Types of Derivation Rules

There are two types of derivation rules available:

Rules for Fields
Rules for Tables

You can use Rules for fields to change data of existing entries. You can use Rules for tables to create new entities (new roles, new customer data, new sales data, and new partner functions).

Derivation Rule Sequence

An important aspect is the sequence of derivation rules, which defines the order in which the derivation rules have to be executed. If you rely on a specific rule for data that is used afterwards, you have to create the relevant rule first. For example, if your company code data relies on customer data, the customer data rule needs to be executed before the company code data rule.

Using Derivation Scenarios

Before you can use Derivation scenarios in change requests, and mass processing and consolidation, you must fulfill some prerequisites.

Prerequisites

You have configured the processing templates for mass processing and consolidation using BC-Sets.
You have configured central governance for change requests using BAdI rule-based worfklow - Call System Method and adapted the rule-based workflow WS60800086.
You have set up at least one derivation scenario that has been approved once.
You have set up at least one derivation rule that has the execution status Enabled.

Note

For more information, refer to the Set Up Central Governance to Use Data Quality Management Derivation Scenarios guide

https://www.sap.com/documents/2022/11/643c8f3a-4e7e-0010-bca6-c68f7e60039b.html.

New Processing Templates for Mass Processing and Consolidation

SAP_MM_MAD - SAP: Mass Change Product Data Including MDQ Derivation
SAP_MM_COD - SAP: Consolidate Products Including MDG Derivation
SAP_BP_MAD - SAP: Mass Change Business Partner Data Including MDQ Derivation
SAP_BP_COD - SAP: Consolidate Business Partners Including MDQ Derivation

In consolidation and mass processing, all active derivation scenarios (scenarios with statuses other than Disabled) containing rules that have execution status Enabled are executed in all processes that have a Derivation step.

In central governance, all active derivation scenarios (scenarios with statuses other than Disabled) containing rules that have execution status Enabled are executed in the rule-based workflow of change requests.

Derivation Scenario Status

The lifecycle of a derivation scenario is determined by various statuses, which can be set by different roles, as shown in the figure, Derivation Scenario Status. The status transitions can be restricted by authorizations.

Note

Changing the status is only possible when the scenario is in display mode.

You can set the status Disabled from any status, and you can move the scenario from status Disabled to any other status except New.

You can delete a scenario if it has status New or Disabled.

Note

When you select Prepare Scope Expression or Create Decision Table, the BRFplus artifacts are generated in the background. While the generation is ongoing, the scenario or rule has the status Generation Running, and you cannot change the scenario and the rule. When the generation is complete, the status changes back to To Be Implemented.

Status in detail

The following table provides more information about the individual statuses in the typical process.

Status	Description	Rule Execution
New	The scenario has been created recently. Rules might have been defined, but are not ready for execution yet.	No
To be Implemented	The implementation expert needs to implement the scope expressions. Please note, however, that the scope expressions aren’t activated yet.	Dependent on the rule's execution status
To be Reviewed	The scenario owner needs to check if the scenario fulfills its purpose.	Dependent on the rule's execution status
Approved	The scenario has been verified with regard to business and implementation aspects. The scope expressions are activated.	Dependent on the rule's execution status
Disabled	The rules are not executed.	No

Derivation Rule Status

The lifecycle of a derivation rule is determined by various statuses, as shown in the figure, Derivation Rule Status. The definitions of the individual roles determine who is responsible for setting which status.

Note

Changing the status is only possible when the scenario is in display mode.

You can set the status Disabled from any status, and you can move the rule from status Disabled to any other status except New.

You can delete a rule if it has status New or Disabled.

Note

Status in detail

The following table provides more information about the individual statuses in the typical process:

Status	Description
New	The rule has been created recently.
To be Implemented	The implementation expert needs to prepare and implement the BRFplus artifacts.
To be Reviewed	The scenario owner needs to check if the rule fulfills its purpose.
Ready for Input	The data owner maintains values in the decision table.
To be Approved	The rule owner needs to verify the rule with regard to business and implementation aspects.
Approved	The rule has been verified with regard to business and implementation aspects. The scope expression and the decision table are activated. You can switch on the execution.
Disabled	The rule is not executed.

Import / Export of a Derivation Scenario

Export a Derivation Scenario

With the Export Derivation Scenarios app, you can download derivation scenarios and their rules, which you previously created in the Define Derivation Scenarios app. This is useful if you want to reuse derivation scenarios in another system. You start the export process in the Define Derivation Scenarios app. The selected derivation scenarios and their rules are validated before you can start the export and download the file. Check the validation logs to find and correct any issues, which were found during validation. Use the Import Derivation Scenarios app to upload derivation scenarios to another system. You can use this app to export derivation scenarios for business partners and for products.

Import a Derivation Scenario

With the Import Derivation Scenarios app, you can upload and import derivation scenarios and their rules, which you have previously downloaded using the Export Derivation Scenarios app. The uploaded derivation scenarios and their rules are validated before you can start the import. You can use this app to import derivation scenarios for business partners and for products.

Note

If you want to update a derivation scenario that already exists in the target system, the derivation scenario in the target system needs to be disabled. You can then import the new version of the derivation scenario. The existing derivation scenario will be overwritten.

Note

The imported derivation scenarios are disabled until you manually enable them by approving them.

Next lesson