Kontakt

Ansicht
Dokumentation

DMS_BADI_OWN_WFSLAVE - BAdI: Selection of Customer-Specific Slave Workflow

DMS_BADI_OWN_WFSLAVE - BAdI: Selection of Customer-Specific Slave Workflow

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

You can call this Business Add-In (BAdI) when converting original application files for document info records. This lets you call a customer-specific slave workflow and make customer-specific adjustments after each conversion.

  • You have defined the Customizing settings for Conversion in Customizing for Document Management under Conversion of Original Application Files.
  • You have defined the Customizing settings for Workflow in Customizing for SAP Web Application Server Customizing under Business Management → SAP Business Workflow.
  • The tasks of the three workflows (see SAP Note 687 199) must be classified as general tasks (transaction SWDD).
  • As standard, this Business Add-In is not active.
  • This BAdI can be used multiple times.
  • The BAdI is not filter dependent.
  • No standard implementations are delivered for the BAdI.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

Methods

Interfaces

IF_EX_CONV_OWN_WF_SLAVE

SAP Note

687 199






rdisp/max_wprun_time - Maximum work process run time   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4251 Date: 20240523 Time: 161819     sap01-206 ( 53 ms )