SAP EHS003_BADI_EHS_DG_002_GET_OBJ Function Module for NOTRANSL: EHS: Eine Instanz zum BAdI EHS_DG_002 gepuffert erzeugen
EHS003_BADI_EHS_DG_002_GET_OBJ is a standard ehs003 badi ehs dg 002 get obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EHS: Eine Instanz zum BAdI EHS_DG_002 gepuffert erzeugen processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ehs003 badi ehs dg 002 get obj FM, simply by entering the name EHS003_BADI_EHS_DG_002_GET_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHS003
Program Name: SAPLEHS003
Main Program: SAPLEHS003
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHS003_BADI_EHS_DG_002_GET_OBJ pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'EHS003_BADI_EHS_DG_002_GET_OBJ'"NOTRANSL: EHS: Eine Instanz zum BAdI EHS_DG_002 gepuffert erzeugen.
IMPORTING
E_BADI_OBJECT = "BADI Interface IF_EX_EHS_DG_002
E_IMPL_EXISTS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXPORTING Parameters details for EHS003_BADI_EHS_DG_002_GET_OBJ
E_BADI_OBJECT - BADI Interface IF_EX_EHS_DG_002
Data type: IF_EX_EHS_DG_002Optional: No
Call by Reference: Yes
E_IMPL_EXISTS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: BOOLEANOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EHS003_BADI_EHS_DG_002_GET_OBJ Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_e_badi_object | TYPE IF_EX_EHS_DG_002, " | |||
| lv_e_impl_exists | TYPE BOOLEAN. " |
|   CALL FUNCTION 'EHS003_BADI_EHS_DG_002_GET_OBJ' "NOTRANSL: EHS: Eine Instanz zum BAdI EHS_DG_002 gepuffert erzeugen |
| IMPORTING | ||
| E_BADI_OBJECT | = lv_e_badi_object | |
| E_IMPL_EXISTS | = lv_e_impl_exists | |
| . " EHS003_BADI_EHS_DG_002_GET_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM EHS003_BADI_EHS_DG_002_GET_OBJ
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects