SAP ABAP IMG Activity BADI_EHS_GLM_014 (BAdI: Print Request via Label Check)

Hierarchy

☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBGLMP_TRIGGER (Package) EHS: Interface for Other Components

IMG Activity

ID	BADI_EHS_GLM_014	BAdI: Print Request via Label Check
Transaction Code	S_EEI_69000003	(empty)
Created on	20120330
Customizing Attributes	BADI_EHS_GLM_014	BAdI: Print Request via Label Check
Customizing Activity	BADI_EHS_GLM_014	BAdI: Print Request via Label Check

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	BADI_EHS_GLM_014

Use

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.

Requirements

You have completed the Customizing activity Configure Label Check.

Standard settings

• 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 (EHS: 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.

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:

• Read Print Request Body
• Record Print Request Body Data
• Create Print Request
• Log Label Check

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_014	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	607