Kontakt

Ansicht
Dokumentation

MDG_BADI_DYN_AGT_SEL - BAdI: Dynamic Selection of Agent in Rule-Based Workflow

MDG_BADI_DYN_AGT_SEL - BAdI: Dynamic Selection of Agent in Rule-Based Workflow

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

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

You can use this BAdI to implement dynamic agent selection in the rule-based workflow. Therefore, in addition to rules that have been predefined, with this BAdI, you can change agent values in the workflow by creating your own programs. This is also true for other values in the workflow, such as the following:

  • Workflow Generic-Context Table
  • Next Change Request Step
  • Next Change Request Status
  • Number of Hours to Expected Completion of the Next User Dialog Task
  • Parallel-Merge Type
  • Parallel-Merge Service Name
  • User Agent(s) and the Non-User Agent(s) of the Next Step

This BAdI uses the method GET_DYNAMIC_AGENTS.

The input for this BAdI is the change request number and the service name. By using the change request number, it is possible to access all data within this change request.

The input parameter Service Name enables you to use the same BAdI implementation for multiple service names. For example, when two service names are used in the configuration of the same change request workflow, and the user wants to create only one BAdI implementation, having the service name as the input parameter enables you to separate the processing logic based on the service name input.

You have defined the filter value Service Name in the view V_USMD201C_SSW.

You need to create a separate implementation for your specific dynamic agent selection step.

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).

No default BAdI implementation is preactivated in the standard system.

The BAdI is filter-dependent.

The BAdI is not designed for multiple use.

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.






Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3065 Date: 20240523 Time: 185717     sap01-206 ( 111 ms )