Configure 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 the minimal settings required for a standard governance process. For more information about each Customizing activity, see the relevant documentation for that Customizing activity.
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 .
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 |
Check in the Customizing that the following business activities are in your system under and make sure that they are assigned to the default data model BP
.
SUP1 (Create Supplier)
SUP2 (Process Supplier)
SUP3 (Display Supplier)
SUP5 (Block/Unblock Supplier)
SUP6 (Mark Supplier for Deletion)
BPPC (Business Partner Data Cleansing)
BPPH (Process Business Partner Hierarchies)
BPPL (Business Partner Initial Load)
BPPM (Business Partner Mass Maintenance)
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 .
The following table shows the change request types for data model BP
of the supplier UI. Only the relevant columns are included.
Change Request Type | Data Model | Description | Single Object | Main Entity Type | Workflow |
|---|---|---|---|---|---|
SUPPL1P1 | BP | Create Supplier | Yes | BP_HEADER | WS54300005 |
SUPPL2P1 | BP | Process Supplier | Yes | BP_HEADER | WS54300007 |
SUPPL5P1 | BP | Block/Unblock Supplier | Yes | BP_HEADER | WS60800059 |
SUPPL6P1 | BP | Mark Supplier for Deletion | Yes | BP_HEADER | WS60800068 |
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:
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
BP_REL: Msg. Output = Standard
Business Activity: SUP1
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
BP_REL: Msg. Output = Standard
Business Activity: SUP2
Entity type: BP_HEADER: Msg. Output = Standard
Business Activity: SUP5
Entity type: BP_HEADER: Msg. Output = Standard
Business Activity: SUP6
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
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
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
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
BP_REL: Msg. Output = Standard
Business Activity: BPPC
Note
In an optional step you can specify Service Level Agreement
for all the mentioned change request types.
Note
ERP Vendor UI Specific Settings
If you use the ERP vendor UI, check that the following business activities are in your system:
VLP1 (Create Supplier)
VLP2 (Process Supplier)
VLP3 (Display Supplier)
VLP5 (Block/Unblock Supplier)
VLP6 (Mark Supplier 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 vendor UI. Only the relevant columns are included.
Change Request Type | Data Model | Description | Single Object | Main Entity Type | Workflow |
|---|---|---|---|---|---|
VENDR01 | BP | Create Supplier | Yes | BP_HEADER | WS54300005 |
VENDR02 | BP | Process Supplier | Yes | BP_HEADER | WS54300007 |
VENDR05 | BP | Block/Unblock Supplier | Yes | BP_HEADER | WS60800059 |
VENDR06 | BP | Mark Supplier for Deletion | Yes | BP_HEADER | WS60800068 |
VENDL1 | BP | Lean Vendor Creation | Yes | BP_HEADER | WS54300013 |
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:
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
Business Activity: VLP1
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
Business Activity: VLP2
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
Business Activity: VLP5
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
Business Activity: VLP6
Entity types:
ADDRNO: Msg. Output = Standard
BP_HEADER: Msg. Output = Standard
Business Activity: VLP1
Note
Quite often many users are supposed to request the creation of new supplier master data. As these users might not be familiar with MDG, they need a UI that is easy to use, even without training. To fulfill this requirement MDG-S provides the lean request UI
as a model.
The lean request UI
is based on the change request type VENDL1. It provides a basic subset of input fields and therefore offers a simplified way to create supplier master data. In a subsequent step, another user can change the data, can enter further data using the complete set of input fields and finally can approve the change request.
To use the lean request UI
the menu role SAP_MDGS_LVC_MENU_03, Master Data Governance for Supplier: Lean Requester Menu is required.
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
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
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 Vendor UI, see Customizing for Master Data Governance, Central Governance
under .
Import Predefined Field Modification Criteria for Transaction BP Using MDG-S
To Run this activity in Customizing for Master Data Governance, Central Governance
under .
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 .
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.