SAP ABAP IMG Activity BADI_EHS_GLM_012_BA (BAdI: Print Request via Messages)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBGLMP_API (Package) EHS: API Implementations
IMG Activity
ID BADI_EHS_GLM_012_BA BAdI: Print Request via Messages  
Transaction Code S_EEI_69000122   (empty) 
Created on 20121009    
Customizing Attributes BADI_EHS_GLM_012_BA   BAdI: Print Request via Messages 
Customizing Activity BADI_EHS_GLM_012_BA   BAdI: Print Request via Messages 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_EHS_GLM_012_BA    

Use

This Business Add-In (BAdI) is used in the Global Label Management component. You can use this BAdI to enhance automatic print request generation via messages.

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_TG01 in function module CBGL_TG01_TRIGGER_NAST.

Requirements

You have completed the Customizing activity Set Up Automatic Print Request Generation for messages.

Standard settings

  • The BAdI cannot be used a number of times.
  • The BAdI is filter-dependent. The BAdI filter name is KAPPL and specifies the key of an application that is conditioned or triggers messages. The permitted filter values are checked using data element KAPPL.
  • The methods of the default implementations EHS_LABELING_012_DN and EHS_LABELING_012_HU 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 Implementations

  • EHS_LABELING_012_DN (EHS: Print Label from Delivery Using Message Control)
    • This BAdI implementation uses interface IF_EX_CBGL_BADI_EHS_GLM_012.
    • The default implementation for the DELIVERY labeling scenario is implemented using class CL_EHSGTRIGGER_DN.
  • EHS_LABELING_012_HU (EHS: Print Label from Handling Unit Using Message Control)
    • This BAdI implementation uses interface IF_EX_CBGL_BADI_EHS_GLM_012.
    • The default implementation for the HANDLINGUNIT labeling scenario is implemented using class CL_EHSGTRIGGER_HU.

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 EHS_LABELING_013_PP as a copy template. The default implementations for messages only contain an example of how to generate print requests.

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.

Example

See also

BAdI method documentation:

For information about how to implement BAdIs in the Enhancement Framework, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. Under SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> 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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BADI_EHS_GLM_012_BA 0 EE50000013 Global Label Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20130103 
SAP Release Created in 617