Ansicht
Dokumentation
MDG_CUST_WF_BRFPLUS - Assign Processor to Change Request Step Number in BRFplus for Customer
Fill RESBD Structure from EBP Component Structure SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
In this Customizing activity, you assign processors to the individual change request step numbers for each type of change request, company code, sales area or central data. This determines which tasks the processors need to perform. To assign a processor to a change request step number, specify the type of change request and the change request step number (Step). Furthermore, you can process a company code, a sales area, or the indicator for central data. Afterward, assign a processor to the change request step number by entering the object type and the processor ID.
The following prerequisites must be met:
- If required, you have modeled an organizational plan of your enterprise in the system.
- You have made the basic Customizing settings for the workflow.
Master Data Governance for Customer uses the agent determination in Business Rule Framework plus (BRFplus).
For more information about BRFplus, see SAP Help Portal under http://help.sap.com -> SAP NetWeaver.
SAP delivers the system application MDG_BS_ECC_CUSTOMER_WORKFLOW with the AGENT_DETERMINATION function with a predefined context, which is accessed in the example implementation.
As the example implementation, SAP delivers the Customizing application MDG_BS_ECC_CUSTOMER_WF_CUSTM with a rule set, a rule, and the decision table GET_AGENT.
To assign a processor to a change request step number, specify the type of change request and the change request step number (Step). And if necessary fill in company code or sales area or set flag for central data.
Afterward, assign a processor to the change request step number by entering the object type and the processor ID.
You make the entries listed below to determine that change request type CUST1P2 (Create Customer (parallel WF)) has the following properties: (a) approval is done by approver of organizational unit central team, for example 50000103; (b) process is done by processor for company code 1000, for example user CUS_CC1000 and processor for sales.org 0001 01 01, for example user CUS_SA0001; (c) approval is done by approver of organizational unit for company code1000 for example 50000103 and approver for sales.org 0001 01 01, for example user CUS_SA0002. In addition you need a processor of the corresponding organizational unit for step 04 (Revision After Rejection) and step 07 (Decision: Activation Despite Discrepancy).
| Type | Step | Company Code | Sales.Org. | Distr.Chn. | Divis. | Flag Central Data Changed | Object Type | ID |
|---|---|---|---|---|---|---|---|---|
| CUST1P2 | 01 (Approval) | O | 50000103 | |||||
| CUST1P2 | 04 (Revision After Rejection) | O | 50000103 | |||||
| CUST1P2 | 05 (Subworkflow: Data Maintenance) | 1000 | US | CUS_CC1000 | ||||
| CUST1P2 | 05 (Subworkflow: Data Maintenance) | 0001 | 01 | 01 | US | CUS_SA0001 | ||
| CUST1P2 | 06 (Subworkflow: Approval) | 1000 | O | 50000103 | ||||
| CUST1P2 | 06 (Subworkflow: Approval) | 0001 | 01 | 01 | US | CUS_SA0002 | ||
| CUST1P2 | 07 (Decision: Activation Despite Discrepancy) | O | 50000103 |
General Material Data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5631 Date: 20240523 Time: 193103 sap01-206 ( 68 ms )
