Introducing Common Features of Consolidation and Mass Processing

Objective

After completing this lesson, you will be able to describe the common features for consolidation and mass processing.

Supported Data Models of Consolidation and Mass Processing

This lesson provides an overview of the data models for MDG on SAP S/4HANA for Consolidation, Mass Processing, and Data Quality Management.

Business Partner Data Model

The figure shows the data model information which is only valid for Master Data Governance on SAP S/4HANA for Consolidation, Mass Processing, and Data Quality Management.

The figure shows the Business Partner Data Model ,which consists of Central Data, Roles, Bank Accounts, Address Details, Relationships, and so on.

ERP Customer Data Model

The figure shows the data model information which is only valid for Master Data Governance on SAP S/4HANA for Consolidation, Mass Processing and Data Quality Management.

The figure shows the ERP Customer Data Model, which consists of General Data, Documents, Classifications, Company Code Data, Sales Area Data, and so on.

ERP Supplier Data Model

The figure shows the data model information which is only valid for Master Data Governance on SAP S/4HANA for Consolidation, Mass Processing, and Data Quality Management.

The figure shows the ERP Supplier Data Model, which consists of General Data, Documents, Classifications, Company Code Data, and Purchasing Organization Data, among others.

Product Data Model

The figure shows the data model information which is only valid for Master Data Governance on SAP S/4HANA for Consolidation, Mass Processing, and Data Quality Management.

The figure shows the Product Data Model, which consists of Basic Data, Descriptions, Dimensions, Documents, Plant Data, and MRP Data, among others.

Mass Processing and Consolidation with Master Data Governance on SAP S/4HANA

Domain Coverage and Choice of Governance

Domains
  • Business Partner, including customer and vendor*

  • Business Partner Relationships*

  • Material Master*

  • Custom Objects**

Choice of Governance Option
  • Can be used with or without central governance

  • Choice: activation with change request

  • Choice: use of master data governance, central governance validations

* For detailed information about the coverage on table-level, see IMG activity "Configure Process Models". Extensibility is supported.

** Based on single database table, master data governance active area (flex) is not supported.

Data Model Extensions

The following tables are now part of the business partner data model:

TableDescription
ADRCTAddress Texts
KNZAPermitted Alternative Payer (Customer)
LFZAPermitted Alternative Payer (Supplier)
KNATTax Categories (Customer)
LFATTax Categories (Supplier)

The preceding figure shows the Data Model extensions on the Edit screen.

The screenshot shows the edit screen with the new extensions chosen as filter.

The following tables are now part of the business partner data model:

TableDescription
/SAPAPO/MATLWHWarehouse
/SAPAPO/MATLWHSTWarehouse Storage Type
/SAPAPO/MATGROUPSCM Product Groups
/SAPAPO/MATLSPPExtended SPP Data (Plan + MRP area)
The screenshots show the edit screen with the new extensions. Three tabs are highlighted in the screenshot: SCM Product Groups, Extended SPP data - MRP area, and Extended SPP data - Plant.

The new UIBBs are part of the main page in each single-object maintenance UI for MDG-BP, MDG-C and MDG-S. The BP web service is enhanced with S/4HANA 2021 release.

Authorization Concept based on Process Step

Authorization Concept based on Process Step

You can control authorizations and activities per process step.

The figure explains that different authorization groups can be assigned to different process steps. In this case, the authorization group A is assigned to the Matching step, and the authorization group B is assigned to the Validation step.

You can manage the following activities:

  • Change data (including remove records, approve/reject match groups)
  • Continue process
  • Rollback process
  • Change step configuration
  • Adjust configuration

Before you can use the authorization groups, you have to define it in the master data governance customizing for consolidation and mass processing. In the second step, assign your authorization group to a process step in a process template. Lastly, you must assign your new authorization object to user authorizations and assign the authorization group and the required activities.

The result is a new authorization object, which controls the step-based authorizations based on the authorization group (MDC_BEGRU).

The figure explains the steps to assign authorization groups to process steps. The steps are: 1. Specify the authorization group. 2. Assign the authorization group to a process step in a process template. 3. Assign new authorization object to user authorizations and assign the authorization group and the required activities.

Strict 4 Eyes Principle

The strict 4 eyes principle is a new action control for process steps.

The process cannot be continued by users who were already involved in the process.

You can track involved users using the audit trail capability of the process.

This strict 4 eyes principle can be combined with the step-based authorization.

The screenshot shows the process steps in the customizing for Business Object Type 147 - Business Partner. In the field labeled Action Control for next step, choose Strict 4 eyes principle.

Apply Data Quality Rules

Consolidation and Mass Processing: Apply Data Quality Rules

As of SAP S/4HANA 1909 FPS2, it is possible to apply data quality rules in the validation and activation step. For this, it is necessary that the data quality rules are defined beforehand. Data quality rules can be used either in Consolidation or in mass processing.

The activation and deactivation of the data quality rule occurs either in the process template or during runtime of a process.

The screenshot shows the possibility to switch on the Data Quality Rules in the Validation step.

Process Step Scheduling

For each of the process steps - Matching, Validation, and Activation - you can specify a threshold as of how many records the system proposes to schedule a start for the next process step. A dialog box offers you the options to either specify the exact starting point or to start the process immediately.

The screenshot shows you can schedule the start for the next process step. There is a Schedule Step popup with a calendar and time selector.

Scheduling the execution of a process step at a predefined date/time allows you to activate change or create master data at a given point of time (for example, 1st of January).

In addition to that, you can prevent the execution of long-running jobs with high system load during business time.

You can define a min and a max number of records for scheduled steps. The Minimum Number of Records field with a field to enter numerical data is highlighted on the screen.

The scheduling dialog will be triggered based on the number of records in a step; threshold can be customized in step configurations.

To use the Step Scheduling, make sure of the following prerequisite settings:

  • In the transaction SWU3Automatic Workflow Customizing under Edit Runtime EnvironmentSchedule Background Jobs SAP Business Workflow, ensure the entry is flagged green.
  • In the transaction SWDDWorkflow Builder, enter workflow WS54500001 and choose Process Process Object. Choose Task description and then choose from the menu Additional dataClassificationDisplay. The General Task indicator has to be selected.

Assignment of Data Controllers

In the consolidation process, you can export the data controller assignments as an Excel/CSV file, and you can import files with data controller assignments. After uploading a file with assignments, you can create business partners with data controller assignments in a mass creation process.

The screenshots show the assigned data controllers during the Best Record Calculation step of the consolidation process.