Show TOC

Background documentationConfigure Change Request Settings

 

Depending on your company’s requirements, you might want to adjust and enhance the change request default values.

The following information describes exemplary settings required for a standard governance process. For more information about each Customizing activity, see the relevant documentation for that Customizing activity.

  1. Review and/or define which statuses the change requests can have, and which processing options are enabled for those statuses. Optionally, you can add new statuses to be used in the change request types defined in the next step.

    For more information, see Customizing for Master Data Governance, Central Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Edit Statuses of Change Requests End of the navigation path.

    The following statuses are required for the SAP standard process:

    Status Value

    Description

    Permitted Processing

    00

    To Be Evaluated

    Change of Object List

    01

    To Be Considered and Approved

    Change of Object List

    02

    Changes to Be Executed

    Execution of Changes

    03

    To Be Revised

    Change of Object List

    04

    Final Check to Be Performed

    No Processing

    05

    Final Check Approved

    No Processing

    06

    Final Check Rejected

    No Processing

    07

    Activation Failed

    No Processing

    08

    Approved, to be Replicated

    No Processing

    09

    Dependent Data to Be Processed/Approved

    Execution of Changes

    10

    To Revise: Perform Changes

    Execution of Changes

    11

    Process Errors After Activation

    Execution of Changes

    12

    Approved, Contact Person to be Processed

    No Processing

    99

    No Status Set

    No Processing

  2. Check in the Customizing that the following business activities are in your system under Start of the navigation path Master Data Governance, Central Governance Next navigation step General Settings Next navigation step Process Modeling Next navigation step Business Activities Next navigation step Create Business Activity End of the navigation path and make sure that they are assigned to the default data model BP.

    • CUP1 (Create Customer)

    • CUP2 (Process Customer)

    • CUP3 (Display Customer)

    • CUP5 (Block/Unblock Customer)

    • CUP6 (Mark Customer for Deletion)

    • BPPI (MDG Hub Inbound: Create Customer)

    • BPPC (Business Partner Data Cleansing)

    • BPPU (MDG Hub Inbound: Process Customer)

    • BPPH (Process Business Partner Hierarchies)

    • BPPL (Business Partner Initial Load)

    • BPPM (Business Partner Mass Maintenance)

  3. Create new change request types for data model BP, or validate after import using business configuration set (BC Set).

    For more information, see Customizing for Master Data Governance, Central Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Create Change Request Type End of the navigation path.

    1. The following table shows the change request types for data model BP of the customer UI. Only the relevant columns are included.

      Change Request Type

      Data Model

      Description

      Single Object

      Main Entity Type

      Workflow

      CUST1P2

      BP

      Create Customer (parallel WF)

      Yes

      BP_HEADER

      WS54400001

      CUST2P1

      BP

      Process Customer

      Yes

      BP_HEADER

      WS54300003

      CUST5P1

      BP

      Block/Unblock Customer

      Yes

      BP_HEADER

      WS54300003

      CUST6P1

      BP

      Mark Customer for Deletion

      Yes

      BP_HEADER

      WS54300003

      CUSTHI01

      BP

      Local Maintenance: Create Customer

      Yes

      BP_HEADER

      WS46000023

      CUSTHI02

      BP

      Local Maintenance: Process Customer

      Yes

      BP_HEADER

      WS46000027

      BPHP1

      BP

      Process Business Partner Hierarchies

      No

      BP_HEADER

      WS60800095

      BPLP1

      BP

      Business Partner Initial Load

      No

      BP_HEADER

      WS72100006

      BPMP1

      BP

      Business Partner Mass Maintenance

      No

      BP_HEADER

      WS60800095

      BPCC2

      BP

      Process Business Partner Cleansing Case

      Yes

      BP_HEADER

      WS60800086

      The following settings should exist in the substructures of the change request types:

      Substructure of Change Request Types:

      CUST1P2:

      Note Note

      The change request type CUST1P2 supports distributed workflow for customers. It is delivered with the business function Master Data Governance for Customer 7.0 Feature Pack.

      End of the note.

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_REL: Msg.Output = Standard

      • Business Activity: CUP1

      CUST2P1:

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_REL: Msg.Output = Standard

      • Business Activity: CUP2

      CUST5P1:

      • Entity type: BP_HEADER: Msg. Output = Standard

      • Business Activity: CUP5

      CUST6P1:

      • Entity type: BP_HEADER: Msg. Output = Standard

      • Business Activity: CUP6

      CUSTHI01

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_REL: Msg.Output = Standard

      • Business Activity: BPPI

      CUSTHI02

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_REL: Msg.Output = Standard

      • Business Activity: BPPU

      BPHP1:

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_HRCHY: Msg. Output = Standard

        • BP_REL: Msg. Output = Standard

        • BP_SUBHRY: Msg. Output = Standard

      • Business Activity: BPPH

      BPLP1

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_HRCHY: Msg. Output = Standard

        • BP_REL: Msg. Output = Standard

        • BP_SUBHRY: Msg. Output = Standard

      • Business Activity: BPPL

      BPMP1

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_HRCHY: Msg. Output = Standard

        • BP_REL: Msg. Output = Standard

        • BP_SUBHRY: Msg. Output = Standard

      • Business Activity: BPPM

      BPCC2

      • Entity types:

        • ADDRNO: Msg. Output = Standard

        • BP_HEADER: Msg. Output = Standard

        • BP_REL: Msg. Output = Standard

      • Business Activity: BPPC

      Note Note

      In an optional step you can specify Service Level Agreement for all the mentioned change request types.

      End of the note.

      Note Note

      ERP Customer UI Specific Settings

      • If you use the ERP Customer UI, check that the following business activities are in your system:

        • CLP1 (Create Customer)

        • CLP2 (Process Customer)

        • CLP3 (Display Customer)

        • CLP5 (Block/Unblock Customer)

        • CLP6 (Mark Customer for Deletion)

        • BPPH (Process Business Partner Hierarchies)

        • BPPL (Business Partner Initial Load)

        • BPPM (Business Partner Mass Maintenance)

      • The following table shows the change request types for data model BP of the ERP Customer UI. Only the relevant columns are included.

        Change Request Type

        Data Model

        Description

        Single Object

        Main Entity Type

        Workflow

        CUSTL1

        BP

        Create ERP Customer (Lean Request)

        Yes

        BP_HEADER

        WS54300004

        CUSTL1P2

        BP

        Create ERP Customer (parallel WF)

        Yes

        BP_HEADER

        WS54400001

        CUSTL2P1

        BP

        Process ERP Customer

        Yes

        BP_HEADER

        WS54300003

        CUSTL5P1

        BP

        Block/Unblock ERP Customer

        Yes

        BP_HEADER

        WS54300003

        CUSTL6P1

        BP

        Mark ERP Customer for Deletion

        Yes

        BP_HEADER

        WS54300003

        BPHP1

        BP

        Process Business Partner Hierarchies

        No

        BP_HEADER

        WS60800095

        BPLP1

        BP

        Business Partner Initial Load

        No

        BP_HEADER

        WS72100006

        BPMP1

        BP

        Business Partner Mass Maintenance

        No

        BP_HEADER

        WS60800095

        The following settings should exist in the substructures of the change request types: Substructure of Change Request Types:

        CUSTL1

        Note Note

        The change request type CUSTL1 supports a lean request UI for ERP customers. It is delivered with the business function Master Data Governance for Customer 7.0 Feature Pack.

        End of the note.

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

          • BP_REL: Msg. Output = Standard

        • Business Activity: CLP1

        CUSTL1P2

        Note Note

        The change request type CUSTL1P2 supports distributed workflow for ERP customers. It is delivered with the business function Master Data Governance for Customer 7.0 Feature Pack.

        End of the note.

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

          • BP_REL: Msg. Output = Standard

        • Business Activity: CLP1

        CUSTL2P1

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

        • Business Activity: CLP2

        CUSTL5P1

        • Entity type: BP_HEADER: Msg. Output = Standard

        • Business Activity: CLP5

        CUSTL6P1

        • Entity type: BP_HEADER: Msg. Output = Standard

        • Business Activity: CLP6

        BPHP1:

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

          • BP_HRCHY: Msg. Output = Standard

          • BP_REL: Msg. Output = Standard

          • BP_SUBHRY: Msg. Output = Standard

        • Business Activity: BPPH

        BPLP1

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

          • BP_HRCHY: Msg. Output = Standard

          • BP_REL: Msg. Output = Standard

          • BP_SUBHRY: Msg. Output = Standard

        • Business Activity: BPPL

        BPMP1

        • Entity types:

          • ADDRNO: Msg. Output = Standard

          • BP_HEADER: Msg. Output = Standard

          • BP_HRCHY: Msg. Output = Standard

          • BP_REL: Msg. Output = Standard

          • BP_SUBHRY: Msg. Output = Standard

        • Business Activity: BPPM

        For more information about the ERP customer UI, see Customizing for Master Data Governance, Central Governance under Start of the navigation path Master Data Governance for Customer Next navigation step ERP-Customer UI (Alternative to the Customer UI) End of the navigation path.

      End of the note.

  4. Import Predefined Field Modification Criteria for Transaction BP Using MDGC

    Run this activity in Customizing for Master Data Governance, Central Governance under Start of the navigation path Master Data Governance for Business Partner Next navigation step Import Predef. Fld Modif. Criteria for Trans. BP Using MDG-C End of the navigation path.

  5. Optionally, you can define priorities, reasons, or rejection reasons for change requests. You can enter codes and a short description to tag or classify your change requests. These codes can be used later for change request analytics (process quality analysis). They also can be used to influence the workflow-driven processes. For example, depending on the priority of a change request, you can mark it for special processing.

    For more information, see Customizing for Master Data Governance, Central Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Define Priorities for Change Requests / Define Reasons for Change Requests / Define Rejection Reasons for Change Requests End of the navigation path.

Note Note

You can apply system settings that allow you to monitor in detail how effectively your organization processes change requests. For details, see Enabling Detailed Analysis of Change Requests.

End of the note.