Show TOC

Background documentationParallel Change Requests

 

  • Creating More Than One Change Request in Parallel for One Business Object

    Since change requests are disjoint you can process change requests separately. You can activate or reject one change request independently from process results of other change requests for the same business object. Therefore you need to process entity data that belongs together in one change request. Changes of a business object in one change request are not visible in another change request for the same business object.

  • Scope on Entity Type Level

    You can edit business data of one business object in several parallel change requests with a special change request type. You can configure these change request types in the Customizing activity Create Change Request Type under Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Process Modeling Next navigation step Change Requests End of the navigation path.

    For each parallel change request you need to configure the scope on entity type level to define which parts of a business object can be edited with a certain change request type. For this change request type scope definition there is a BAdI (CHECK_CREQUEST_TYPE_SCOPE) for the MDG applications to inform you which entities need to be potentially in scope in addition to the already selected entity types.

    Note Note

    Derivations

    A change in one entity may result in a cross derivation of another entity of a different entity type. Both entity types need to be part of the entity type scope.

    End of the note.

    The setting of the indicator for parallel change requests and the setting of the entity type scope are irreversible, once there is an existing change request in your productive system. This implies also that the consistency of the business object of each change request has to be guaranteed. The checks consider only the active and inactive data that belong to the change request.

  • Interlocking

    As in non parallel change requests the whole business object is interlocked by a change request using the object list, in parallel change requests the object list only registers the business object but does not interlock it. Interlocking is done on entity level by creating, changing or deleting the entity of a business object. For this purpose the change list has been introduced for interlocking entities of business objects. The change list contains the entities that are changed with a change request.

  • Checks

    The system checks entity data according to the configuration in the Customizing activity Configure Properties of Change Request Step under Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Process Modeling Next navigation step Change Requests End of the navigation path.

    The system checks on object level on the basis of the entity data assigned to the change request. Using non parallel change requests you can check the whole object including all its changed entities. Using parallel change requests you can check the whole object on the basis of only those changed entities of the assigned change request.

  • Deletion of Entities in Parallel Change Requests

    Dependent entities of a deleted entity are deleted and interlocked.

    Example Example

    • Example 1: If you want to delete an entity in one parallel change request, you cannot create a dependent entity for that deleted entity in another parallel change request.

    • Example 2: If you have created a dependent entity to a parent entity, you cannot delete the parent entity in another parallel change request.

    End of the example.

  • Activating and Rejecting Parallel Change Requests

    There may be inactive data that belongs to several change requests. When you activate one change request then the system only activates inactive data of a business object that belongs to that change request. The same applies for inactive data of a business object in a rejected change request.

Parallel change requests can be used for the following MDG applications:

  • Master Data Governance for Custom Objects

  • Master Data Governance for Material

  • Master Data Governance for Business Partner

  • Master Data Governance for Supplier

  • Master Data Governance for Customer