Show TOC

Background documentationConfigure Activation for Material

 

Within the process step activation records are activated and thereby added to the systems active area. You can configure how the system proceeds with different types of active data and you can set up a parallelization for the activation process.

Features

The activation can be adapted for all three possible types of records:

  • New record: Record does neither yet exist in the active area nor does it have any duplicates.

  • Updated record: Record already existed in the active area.

  • Match group: Record does not exist in the active area, but has duplicates in the process data.

Records that did not pass all validity requirements are considered as records with errors. You can specify an individual system reaction for each type of record, depending whether a record contains errors or not. If you use SAP MDG, central governance in parallel with SAP MDG, consolidation and mass processing you can use change requests to have your records approved.

Activities

To configure the activation run the Customizing activity under Start of the navigation path Master Data Governance Next navigation step Consolidation and Mass Processing Next navigation step Configure Activation Next navigation step Configure Activation for Material End of the navigation path.

  1. Select New Entries

  2. Enter a Configuration ID and a Description.

  3. Configure the parallelization for the activation adapter.

    The activation is running without configuring the parallelization for the activation adapter. Nevertheless you can configure the number of parallel processes to improve the performance of the process.

    Note Note

    To use parallelization in SAP MDG, consolidation you have to set up an RFC destination:

    • To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity 02 and type 07 has to be assigned to you.

      1. Run transaction SBGRFCCONF.

      2. On the Define Inbound Dest. tab choose Create.

      3. Enter a name in the Destination field.

      4. Enter MDC_QUEUE_ in the Prefixes field.

        If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding field as described below.

      5. On the Scheduler: Destination tab select the destination by double clicking on it.

        If the destination does not exists, proceed as described:

        1. Choose Create and on the bgRFC Configuration dialog box select Inbound.

        2. Enter the destination name into the Destination field and leave all other values as defaulted.

      6. In the Open Connections field enter the number of allowed parallel processes or queues you wish to be managed by this destination. This number also specifies the maximum of parallel processes to be configured during the step configuration.

    • If you do not create the bgRFC inbound destination manually the very first consolidation process will trigger the automatic creation of the inbound destination under prerequisite that the authorization object S_BGRFC with full authorization is assigned to workflow system user.

    For more information see http://help.sap.com/saphelp_nw70ehp2/helpdata/de/f0/225c3c60065627e10000000a114084/content.htmInformation published on SAP site

    End of the note.
    1. In the field Number of Parallel Processes, enter the number of processes you want to be processed in parallel.

    2. If required enter the Prefix for Queue Name.

      Note Note

      If you use queue prefixes other than MDC_QUEUE_ these have to be entered in the Prefix for Queue Name field.

      End of the note.
  4. Specify the types of activation dependent on different record types and whether these records are considerd as correct or incorrect by the process step validation:

    Note Note

    Records that did not pass all validity requirements are considered as records with errors. You can specify an individual system reaction for each type of record, depending whether a record contains errors or not. If you use SAP MDG, central goverance in parallel with SAP MDG, consolidation and mass processing you can use change requests to have your records approved.

    End of the note.

    Note Note

    If you want to activate using change requests make sure the selected change request type does not run checks that prevent the creation of the record:

    Run the Customizing activity Configure Properties of Change Request Step and for Change Request Step 00 check the setting under Enhancements and Checks per Change Request Step and Entity Types per Change Request Step.

    End of the note.

    Note Note

    For mass processing only the activation of updated records is relevant.

    End of the note.
    1. Configure the system behavior for New Records. In the field Activation Target for New Records, select an entry using the input help and assign a corresponding change request type. In the field Target for New Incorrect Records, select an entry using the input help assign a corresponding change request type.

    2. Configure the system behavior for Updated Records. In the field Activation Target for Updated Records, select an entry using the input help and assign a corresponding change request type. In the field Target for Updated Incorrect Records, select an entry using the input help and assign a corresponding change request type.

    3. Configure the system behavior for Match Groups. In the field Activation Target for Match Groups, select an entry using the input help and assign a corresponding change request type. In the field Activation Target for Mtch Grps (Errors), select an entry using the input help and assign a corresponding change request type.

  5. If you want the records to be replicated to connected systems set the Call DRF after Activation indicator. If you use the activation using change requests, we recommend to set the Call DRF after Activation indicator.

    Note Note

    The Call DRF after Activation indicator is only valid for the process goal Central Maintenance. For the process goal Consolidation no replication is executed.

    End of the note.
    • If you activate all types of records using change requests or cleansing cases flag does not have any impact.

    • If you activate all types of records with the Direct Activation you can choose the setting to meet your requirements.

    • If you activate using change requests and Direct Activation, we recommend to set the flag.

  6. If you want to execute MDG, central goverance validation checks select the Execute Central Governance Checks (Validation Rules (BRF+) & BAdI Validations) indicator.

    Note Note

    The Execute Central Governance Checks (Validation Rules (BRF+) & BAdI Validations) indicator only appears if you run MDG, central governance.

    End of the note.
  7. If you want to execute BRF+ checks, select the Execute BRFplus Checks indicator.

    Note Note

    As a prerequisite run the Customizing activity under Start of the navigation path Master Data Governance Next navigation step Consolidation and Mass Processing Next navigation step Define Rules Using the Business Rule Framework plus End of the navigation path. For more information, see Define Rules Using the Business Rule Framework plus.

    End of the note.
  8. If you want to check the data after the final process step, the activation, specify the retention time in days and the retention time in hours.

    Note Note

    To use the Retention Time make sure of the following settings:

    • In the transaction SWU3 Automatic Workflow Customizing under Edit Runtime Environment the entry Schedule Background Job for Condition Evaluation is flaged green.

    • In the transaction SWDD Workflow Builder enter workflow WS54500001. Press Enter and choose Process Process Object. ChooseTask description and then choose Start of the navigation path Additional Information Next navigation step Classification Next navigation step Display End of the navigation path. The General Task indicator has to be selected.

    End of the note.

Constraints

If you use SAP MDG, consolidation and mass processing without activating SAP MDG, central governance the possibilities for this configuration step are reduced, as less activation targets are offered and no selection fields for Change Request Type are displayed.

Record

With MDG, central governance

Without MDG, central governance

Activation Target for New Records

No Activation

Direct Activation

Activation with Change Request

No Activation

Direct Activation

Target for New Incorrect Records

No Activation

Direct Activation

No Activation

Activation Target for Updated Records

No Activation

Direct Activation of Best Record

Activation of Best Record with Change Request

No Activation

Direct Activation of Best Record

Target for Updated Incorrect Records

No Activation

Activation of Best Record with Change Request

No Activation

Activation Target for Match Groups

No Activation

Direct Activation of Best Record

Activation of Best Record with Change Request

No Activation

Direct Activation of Best Record

Activation Target for Mtch Grps (Errors)

No Activation

Activation of Best Record with Change Request

No Activation