Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD5_SSW (Package) Rule based workflow
IMG Activity
| ID | MDG_BADI_PAR_RES_HDL | BAdI: Handling of Parallel Results in Rule-Based Workflow |
| Transaction Code | S_BTD_53000195 | (empty) |
| Created on | 20100118 | |
| Customizing Attributes | MDG_BADI_PAR_RES_HDL | BAdI: Handle Parallel Results in Rule-Based Workflow |
| Customizing Activity | MDG_BADI_PAR_RES_HDL | BAdI: Handle Parallel Results in Rule-Based Workflow |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | USMD_SSW_PARA_RESULT_HANDLER |
Use
This Business Add-In (BAdI) is used in the Master Data Governance (CA-MDG) component.
You can use this BAdI to implement the result of a parallel workflow merge in the rule-based workflow. The BAdI uses the method HANDLE_PARALLEL_RESULT to handle and merge the results of the parallel workflows into one result.
The input for this BAdI is the change request number, current step number, parallel step action table, 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.
With this BAdI, you can change the workflow generic-context table in the workflow. This BAdI also returns the next step, the action taking place in the workflow step, and the message table.
Requirements
You have defined the filter value Service Name in view V_USMD201C_SSW.
You need to create a separate implementation for the handling of a specific parallel result.
Standard settings
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.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20100121 |
| SAP Release Created in | 702 |
