Editions in SAP MDG
- By Harshavardhan Karidi
Brief about Editions in SAP MDG:
An edition enables time-dependent maintenance of master data. Financial master data objects such as cost centers and profit centers require time-dependent master data, so editions are used. Such time-dependent master data objects automatically inherit the valid-from date from the editions valid-from date.
Editions are used to schedule changes to master data and in SAP MDG. Editions allow combining either the changes that are logically related or that need to be valid from the same date. It’s possible to use editions for custom objects modeled in SAP MDG if the objects are modeled as flex objects.
The typical edition-based process follows these steps:
- Create the edition and provide validity dates.
- Initiate the change request process for all changes that are related to each other or that become active from the validity date of the edition.
- The edition can be released after all change requests are approved, rejected, or withdrawn.
- Change requests can be replicated to target systems after approval, via a manual replication, or after the release of the edition.
SAP delivers an edition type 0G_ALL, which is defined with all entity types and can be used in the finance (0G) data model.
An edition type is defined with the following:
- Name of the edition type and description
- The data model to which the edition type is linked
- Whether the edition has period-specific or date-specific validity
- Fiscal year variant
- An indicator to identify if the edition type is retired
Note An edition type can be retired only if there are no open editions. After an edition type is retired, change requests can’t be created referencing that edition type. A retired edition type can’t be activated or used in consistency checks.
The SAP MDG framework provides the change request UIBB (CRUIBB) and the validity UIBB. CRUIBBs provide the change request header information such as description, priority, created date, created by, and so on. Validity UIBBs display the time validity details of the edition-based entities. These UIBBS are integrated with the object-specific Web Dynpro applications using the SAP MDG communicator settings at runtime.
My change request: Provides the list of change requests associated with the user. You can filter this view based on the date and also by created requests, processed requests, and to-be-processed requests. The Web Dynpro application related to this functionality is USMD_EDITION_CREQUEST with component configuration USMD_EDITION_CREQUEST_OIF.
Edition comparison: Compares editions to identify objects and changes associated with each edition. The Web Dynpro application related to this is USMD_EDITION_COMPARE. Editions are mainly used for finance data objects as well as custom objects if needed. Edition history can be viewed using the Web Dynpro application USMD_EDITION_HISTORY2.
Distribution monitor: Monitors the replication of data records based on editions in both a hierarchy view and a standard view. The application lists the edition with the respective replication model and provides the status.
Direct or Automatic Replication: Direct or automatic replication takes place after a change request is activated. If a change request isn’t edition dependent, replication is triggered after activation by default. For change requests that are edition dependent, automatic replication will depend on the settings of the corresponding edition type.