Kontakt

Ansicht
Dokumentation

LCM_LT_WF_AGENTS_DET - Determine Workflow Agents

LCM_LT_WF_AGENTS_DET - Determine Workflow Agents

Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in Enterprise Contract Management (ECM).

You can use this BAdI to implement your own workflow agent determination.

To create a BAdI implementation, you can use the transactions SE18 or SE19, or you can use the Custom Logic app in the front-end system. If you use the Custom Logic app, the following applies:

  • The app provides a special ABAP language version ABAP for Key Users. This makes the implementation of BAdIs for business experts and implementation consultants easier.
  • The app ensures that you can use only released interfaces.

If you use the transactions SE19 or SE18 to create a BAdI implementation, the implementation is not visible in the Custom Logic app.

If several BAdI implementations exist, the system runs through the implementations in the following order:

  1. Implementations created in the transactions SE18 or SE19.
  2. Implementation created in the Custom Logic app.

  • In the standard system, the BAdI is not active.
  • The BAdI is filter-independent.
  • With the app Custom Fields and Logic, you can create exactly one active implementation.

Based on the import data, you can define the list of approvers. The import parameters IT_PreviousApproverList and IS_StepInfoprovides information about where you are in the workflow and helps you to determine the current approval level and the corresponding approvers.

Main method of implementation is GET_APPROVERS.

Import Parameters:

The following import parameters are provided:

  • IV_LEGALTRANSACTIONUUID:,,This parameter provides the Legal transaction Universal Unique identifier.
  • IV_LEGALTRANSACTIONID:,,,,This parameter provides the Legal Transaction ID.
  • IT_PREVIOUSAPPROVERLIST: ,,This parameter provides the approvers of the previous approval steps. This information needed to determine the current position in approval workflow.
  • IS_STEPINFO:,,,,,,,,This parameter provides information about current step, total steps in workflow and details for each step.

Details of IS_STEPINFOparameter:

  • The parameter has a table with the step details. The table contains the field SKIP_STATUS - this status is populated with 3 possible values:
  • 'C' - Skipped by Condition. Whenever a task is skipped from the workflow by not satisfying the condition configured in the step definition.

  • 'O' - Skipped by Is Optional Stepproperty. This status is populated only if the task is skipped if 'Is Optional Step' Property is set as 'Yes' and no agents were determined.

  • ' ' - Task is not skipped and is part of a workflow.

  • SKIP_STATUS fields are populated with status 'C' for the whole workflow at initiation. This means that the table would have the value 'C' even for tasks that are have not started yet. The SKIP_STATUS value 'O' is populated only when a workflow reaches the task at runtime and the task is skipped by the functionality of 'Is Optional Step' property.

Change Parameter:

  • CT_APPROVERLIST This parameter contains the approvers of the current approval level

Note:

The logic for the BAdI implementation is executed by a technical user for the workflow. Make sure that technical user SAP_WFRTwould have authorizations that are required to execute this implementation.






General Data in Customer Master   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4382 Date: 20240606 Time: 215623     sap01-206 ( 63 ms )