Ansicht
Dokumentation

FMDM_USMD_WF_AGENT - BAdI: Assign Processor to Change Request Step

TXBHW - Original Tax Base Amount in Local Currency Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Master Data Governance (CA-MDG)component.

You can use this BAdI to define rules according to which a processor is allocated to the individual change request step processing of a change request.

The BAdI contains the following, interdependent methods:

GET_BRANCHES

This method is called during the workflow task 75707944 (Get Number of Parallel Steps) and is used to determine the number of parallel workflow branches for the change request step that follows. For technical reasons, this must be an upstream step.

GET_AGENTS

This method is called by rule 75700139 during the role determination and is used to determine the processors for each branch.

Standard implementations exist for both methods for the workflow templates delivered by SAP.

To be able to use this BAdI, you need to have defined the required change request step numbers. SAP delivers all change request steps you need for the workflow templates delivered by SAP. When you copy and extend the templates, you also need to create the new steps in Customizing to be able to use role determination of Master Data Governance.

The BAdI implementations listed below are activated in the standard system. The default code is executed automatically.

The BAdI is filter-dependent. The filter is a freely defined text that is passed to the role determination in the workflow definition and can control the type of role determination.

The BAdI is not designed for multiple use.

USMD_WF_AGENT_STANDARD with filter AGENT_FILTER = STANDARD

Reads the settings you made under Master Data Governance -> General Settings -> Process Modeling -> Workflow -> Other MDG Workflows -> Assign Processor to Workflow Step Number (Simple Workflow). This implementation is used in the workflow templates WS75700027 and WS75700040.

USMD_WF_AGENT_BY_USER with filter AGENT_FILTER = ALL_USERS_NO_DUPLICATED

Reads the settings you made under Master Data Governance -> General Settings -> Process Modeling -> Workflow -> Other MDG Workflows -> Workflow Step Number (Simple Workflow). Each entry is resolved to the extent that the return table only contains users and no organizational units. For this reason, the work item must be approved by each individual user.

USMDA4_WF_AGENT_STANDARD with filter AGENT_FILTER = ZVSTANDARD

Reads the settings you made under Master Data Governance for Financials -> Workflow -> Assign Processor to Workflow Step Number (Extended Workflow). This implementation is used in workflow template WS75700043.

USMDA4_WF_AGENT_SINGLE_PROC with filter AGENT_FILTER = ZVSINGLEPROC

MDG_BS_SUPPL_WF_AGENT_ERP with Filter AGENT_FILTER = MDGS_ERP

This implementation determines processors and is used in the following workflow templates:

WS60800041 Create Supplier (subworkflow WS60800042)

WS60800048 Change Supplier

WS60800059 Block/Unblock Supplier

WS60800068 Mark Supplier for Deletion

WS60800095 Processing of Multiple Suppliers

The implementation reads the settings you have made in an application of Business Rule Framework plus (BRFplus). For more information about BRFplus, see SAP Help Portal at http://help.sap.com-> SAP NetWeaver.

SAP delivers the system application MDG_BS_ECC_SUPPLIER_WORKFLOW with the AGENT_DETERMINATION function with a predefined context, which is accessed in the example implementation.

As example implementation, SAP delivers the Customizing application MDG_BS_ECC_SUPPLIER_WF_CUSTM with the AGENT_DETERMINATION function with a predefined context. This function evaluates the decision table GET_AGENT to determine the workflow processors.

To assign a processor to a workflow step number, specify the type of change request and the change request step number (step). Furthermore, you can process a company code, a purchasing organization, 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.

For more information, see Assign Processor to Change Request Step Number in BRFplus for Supplier.

You make the entries listed below to determine that change requests of the type SUPPL02 are simultaneously approved by organizational units 55555 and 77777, and that organizational unit 88888 decides about processing the contact person:

CREQUEST_TYPE	WORKFLOW-STEP_NUMBER	CoCode	Flag CentrlData Chgd	Obj.Type
SUPPL02	01	0001	O	55555
SUPPL02	02	0002	O	77777
SUPPL02	03	0003	O	88888

MDG_BS_CUST_WF_AGENT_ERP with Filter AGENT_FILTER = MDGC_ERP

As example implementation, SAP delivers the Customizing application MDG_BS_ECC_CUSTOMER_WF_CUSTM with the AGENT_DETERMINATION function with a predefined context. This function evaluates the decision table GET_AGENT to determine the workflow processors.

To assign a processor to a workflow step number, specify the type of change request and the change request step number (step). Furthermore, you can use company code, sales organization, distribution channel, division, and the indicator for central data for more specific assignments. Afterwards, assign a processor to the change request step number by entering the object type and the processor ID.

For more information, see Assign Processor to Change Request Step Number in BRFplus for Customer.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

O O

This BAdI uses the interface IF_USMD_WF_AGENT. For more information, display the interface in the Class Builder.

RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.

Length: 9508 Date: 20240523 Time: 202324 sap01-206 ( 199 ms )

Ansicht Dokumentation

FMDM_USMD_WF_AGENT - BAdI: Assign Processor to Change Request Step

Ansicht
Dokumentation