SAP COMPONENT_DATA_BUFFER_IN Function Module for NOTRANSL: Buffer component data for later processing in MEPO
COMPONENT_DATA_BUFFER_IN is a standard component data buffer in 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: Buffer component data for later processing in MEPO 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 component data buffer in FM, simply by entering the name COMPONENT_DATA_BUFFER_IN into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2012_COMP
Program Name: SAPL2012_COMP
Main Program: SAPL2012_COMP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COMPONENT_DATA_BUFFER_IN 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 'COMPONENT_DATA_BUFFER_IN'"NOTRANSL: Buffer component data for later processing in MEPO.
EXPORTING
* IM_COMP_EXT = "Generic Type
* IM_MODE = 'W' "Generic Type
* IM_EBELP = "Item Number of Purchasing Document
IMPORTING
EX_COMP_EXT = "Predefined Type
IMPORTING Parameters details for COMPONENT_DATA_BUFFER_IN
IM_COMP_EXT - Generic Type
Data type: ANYOptional: Yes
Call by Reference: Yes
IM_MODE - Generic Type
Data type: CDefault: 'W'
Optional: Yes
Call by Reference: Yes
IM_EBELP - Item Number of Purchasing Document
Data type: MEPOITEM-EBELPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for COMPONENT_DATA_BUFFER_IN
EX_COMP_EXT - Predefined Type
Data type: ANY TABLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for COMPONENT_DATA_BUFFER_IN 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_ex_comp_ext | TYPE ANY TABLE, " | |||
| lv_im_comp_ext | TYPE ANY, " | |||
| lv_im_mode | TYPE C, " 'W' | |||
| lv_im_ebelp | TYPE MEPOITEM-EBELP. " |
|   CALL FUNCTION 'COMPONENT_DATA_BUFFER_IN' "NOTRANSL: Buffer component data for later processing in MEPO |
| EXPORTING | ||
| IM_COMP_EXT | = lv_im_comp_ext | |
| IM_MODE | = lv_im_mode | |
| IM_EBELP | = lv_im_ebelp | |
| IMPORTING | ||
| EX_COMP_EXT | = lv_ex_comp_ext | |
| . " COMPONENT_DATA_BUFFER_IN | ||
ABAP code using 7.40 inline data declarations to call FM COMPONENT_DATA_BUFFER_IN
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.| DATA(ld_im_mode) | = 'W'. | |||
| "SELECT single EBELP FROM MEPOITEM INTO @DATA(ld_im_ebelp). | ||||
Search for further information about these or an SAP related objects