Ansicht
Dokumentation
EHSS_HITLIST - BAdI: Enhancement of Hit Lists
rdisp/max_wprun_time - Maximum work process run time Vendor Master (General Section)This documentation is copyright by SAP AG.
This Business Add-In is used in the Product Safety and Stewardship and Recipe Management (PLM-RM) components.
You use this BAdI to enhance the functions of the hit lists. The BAdI is called when the following hit lists are compiled generically:
- Hit list for specifications
- Hit list for phrases
- Hit list for phrase sets
- Hit list for generation variants
- Hit list for report templates
- Hit list for report shipping orders
- Hit list for parameter values in report shipping
- Hit list in the WWI monitor
- Hit list of ALE recipients for distribution of objects (specifications, phrases, and reports) via Application Link Enabling (ALE)
- You access this hit list when you choose -> Data Exchange -> ALE with Recipient Selection in the menu of the hit list for the object.
The BAdI is called in the function group C14T (function module C14T_LISTTOOL_CALL_ALV_GRID). The methods of the BAdI (see below) are triggered by events in the hit list.
The methods are supplied with a default implementation that guarantees the standard functions of the hit lists. You can enhance the default implementations with your own implementations. In this case, transfer the default implementation for the other hit lists.
If the BAdI is used outside the function group C14T, the method INITIALIZATION must be called. It initializes the methods for the events.
Caution:
- You must not change the method INITIALIZATION, otherwise the standard functions cannot be guaranteed.
The Business Add-In is not filter-dependent and not designed for multiple use.
After you have called the IMG activity, proceed as follows:
- 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.
- In the corresponding field, enter a short text for implementation .
- In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
- 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.
- Save your entries and assign a package.
- Position the cursor on a method. Call up the Class Builder by double-clicking it.
- Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
- Save and activate your coding, and navigate back to the screen Change Implementation.
- 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.
- Choose Activate.
- When the application program is executed, the coding you have created will be run.
Methods
BAL_S_LOG - Application Log: Log header data ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 5202 Date: 20240523 Time: 171926 sap01-206 ( 65 ms )
