SAP ABAP IMG Activity BADI_EHS_GLM_011_BA (BAdI: Scenario-Dependent Print Request Generation)
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_011_BA BAdI: Scenario-Dependent Print Request Generation  
Transaction Code S_EEI_69000123   (empty) 
Created on 20121009    
Customizing Attributes BADI_EHS_GLM_011_BA   BAdI: Scenario-Dependent Print Request Generation 
Customizing Activity BADI_EHS_GLM_011_BA   BAdI: Scenario-Dependent Print Request Generation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_EHS_GLM_011_BA    

Use

This Business Add-In (BAdI) is used in the Global Label Management component. You can use this BAdI to implement a labeling-scenario-dependent business logic in the interface Create Print Request (PRINTREQUEST_CREATE) for the print request API.

You can implement all other interfaces for the print request API independently of the labeling scenarios. That is, you can change the business logic of these interfaces in the BAdI Business Logic of Print Request API.

The supporting function of the interface Create Print Request is implemented in the BAdI: Business Logic of Print Request API. The calls of the BAdI methods named below are integrated into this BAdI.

The interface Create Print Request can have different functions in print request generation depending on the labeling scenario defined: label determination is implemented differently for the Handling Unit labeling scenario and the Label Check labeling scenario. To make it easy to implement these differences in interface function, you can define a separate filter-dependent BAdI implementation in this BAdI for each labeling scenario or labeling scenario group that you have defined in Customizing for Global Label Management.

This BAdI is called in class CL_EHSGBC_API_FRAMEWORK in method PRINTREQUESTBODY_DET. The BAdI methods are called one after another in the following sequence:

  1. CHECK_INTERFACE_PARAMETER (verification of interface parameter values)
  2. Start of the loop through all entries in the table that contains the header data of the print request
    • DO_INITIALIZE (initialization of start values)
    • DO_LABEL_DETERMINATION (label determination)
    • DO_FILTER_VARIANTS (filter report generation variants)
    • DO_DESTINATION_DETERMINATION (determination of print destination)
    • DO_NO_OF_LABELS_DETERMINATION (determination of number of labels to be printed)
    • DO_SEQUENCE_DATA_DETERMINATION (determination of sequence numbers)
    • DO_SEQUENCE_LIST_DETERMINATION (determination of sequential data)
    • DO_PRTREQ_DESCRIPTION (add description for print request)
  3. End of the loop
  4. DO_DESTINATION_SPLIT (print request is distributed to multiple print destinations)

Requirements

You have completed the Customizing activity Configuration of Global Label Management.

You use the BAdI implementation EHS_LABELING_010 (EHS: API Framework Standard Implementation) or your own implementation in which the interface Create Print Request is implemented in the same way as in the standard implementation of EHS_LABELING_010.

Standard settings

  • The BAdI cannot be used a number of times.
  • The BAdI is filter-dependent. It uses the filter FILT_SCENARIO_ID (key of the labeling scenario).
  • The methods of the labeling-scenario-dependent default implementations 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

The following BAdI implementations use the interface IF_EX_CBGL_BADI_EHS_GLM_011.

  • EHS_LABELING_011_DELIVERY (EHS: Delivery Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_DELIVERY.
    • The filter DELIVERY is used.
  • EHS_LABELING_011_GENERIC    EHS (EHS: Generic Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_GENERIC.
    • The filter GENERIC is used.
  • EHS_LABELING_011_GOODS_RECEIPT (EHS: Goods Receipt Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_GOODS_REC.
    • The filter GOODS_RECEIPT is used.
  • EHS_LABELING_011_HANDLING_UNIT (EHS: Handling Unit Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_HANDL_UNIT.
    • The filter HANDLINGUNIT is used.
  • EHS_LABELING_011_MAKE_TO_ORDER (EHS: Make-to-Order Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_MAKE_TO_ORD.
    • The filter MAKE_TO_ORDER is used.
  • EHS_LABELING_011_MAKE_TO_STOCK (EHS: Make-to-Stock Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_MAKE_TO_STK.
    • The filter MAKE_TO_STOCK is used.
  • EHS_LABELING_011_SAMPLE (EHS: Sample Labeling Scenario)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_SAMPLE.
    • The filter SAMPLE is used.
  • EHS_LABELING_011_VERIFICATION (EHS: Labeling Scenario for Check Process)
    • The default implementation is implemented using class CL_EHSGBC_SCENARIO_VER_PROC.
    • The filter VERIFICATION_PROCESS is used.

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. In 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_011_BA 0 EE50000013 Global Label Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20121206 
SAP Release Created in 617