Ansicht
Dokumentation
BADI_EHS_GLM_014 - BAdI: Print Request via Label Check
PERFORM Short Reference CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
This Business Add-In (BAdI) is used in the Global Label Management component. You can use this BAdI to enhance print request generation for the label check.
Print request generation is triggered in the default implementation of the BAdI. The print request API is called for this purpose, which means the data is formatted in the BAdI methods in a way that allows the print request API to be called.
The BAdI is called in function group CBGL_TG0 in function module CBGL_TG01_TRIGGER_VERPROC.
You have completed the Customizing activity Configure Label Check.
- The BAdI cannot be used a number of times.
- The BAdI is not filter-dependent.
- The methods of the default implementation EHS_LABELING_014_VERIFICATION are executed.
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder.
BAdI Implementation
- EHS_LABELING_014_VERIFICATION (Label Check)
- This BAdI implementation uses interface IF_EX_CBGL_BADI_EHS_GLM_014.
- The default implementation for the VERIFICATION_PROCESS print scenario is implemented using class CL_EHSGTRIGGER_VERPROC. You can check the objects in the Class Builder.
Own Implementation
If you activate your own implementation, the default implementation is deactivated.
To ensure print request generation is still triggered, you need to implement the print request API using function module CBGL_PRAPI_PRTREQ_CREATE in method DO_RUN. To delete the print requests, use function module CBGL_PRAPI_PRTREQ_DELETE.
Use the default implementation as a copy template.
BAdI method documentation:
ABAP Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 2946 Date: 20240524 Time: 004748 sap01-206 ( 34 ms )
