SAP EASYDMS_BOMHEADER Function Module for Conversion exit for BOM Header
EASYDMS_BOMHEADER is a standard easydms bomheader SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion exit for BOM Header 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 easydms bomheader FM, simply by entering the name EASYDMS_BOMHEADER into the relevant SAP transaction such as SE37 or SE38.
Function Group: EASYDMS
Program Name: SAPLEASYDMS
Main Program: SAPLEASYDMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EASYDMS_BOMHEADER 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 'EASYDMS_BOMHEADER'"Conversion exit for BOM Header.
EXPORTING
* IV_OBJECTKEY = "Document description
IMPORTING
EV_BOM = "EATAB BOM Headers
IMPORTING Parameters details for EASYDMS_BOMHEADER
IV_OBJECTKEY - Document description
Data type: BAPI_DOC_DRAW2-DESCRIPTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EASYDMS_BOMHEADER
EV_BOM - EATAB BOM Headers
Data type: RC29KOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EASYDMS_BOMHEADER 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_ev_bom | TYPE RC29K, " | |||
| lv_iv_objectkey | TYPE BAPI_DOC_DRAW2-DESCRIPTION. " |
|   CALL FUNCTION 'EASYDMS_BOMHEADER' "Conversion exit for BOM Header |
| EXPORTING | ||
| IV_OBJECTKEY | = lv_iv_objectkey | |
| IMPORTING | ||
| EV_BOM | = lv_ev_bom | |
| . " EASYDMS_BOMHEADER | ||
ABAP code using 7.40 inline data declarations to call FM EASYDMS_BOMHEADER
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.| "SELECT single DESCRIPTION FROM BAPI_DOC_DRAW2 INTO @DATA(ld_iv_objectkey). | ||||
Search for further information about these or an SAP related objects