SAP MEPO_DOC_ITEM_PROCESS Function Module for NOTRANSL: Verarbeiten einer Einkaufsbelegposition im SAPMM06E
MEPO_DOC_ITEM_PROCESS is a standard mepo doc item process 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: Verarbeiten einer Einkaufsbelegposition im SAPMM06E 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 mepo doc item process FM, simply by entering the name MEPO_DOC_ITEM_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: MECOM1
Program Name: SAPLMECOM1
Main Program: SAPLMECOM1
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MEPO_DOC_ITEM_PROCESS 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 'MEPO_DOC_ITEM_PROCESS'"NOTRANSL: Verarbeiten einer Einkaufsbelegposition im SAPMM06E.
EXPORTING
* IM_ITEMX = "Change Parameter: Purchase Order Item
* IM_EKPVX = "Change Parameter: Shipping Data EKPV
IMPORTING
EX_EBELP = "Item Number of Purchasing Document
CHANGING
CH_ITEM = "Purchase Order Item
* CH_ITEM_SERVICE_DATA = "Service Data for Purchase Order Item
* CH_EKPV = "Shipping Data For Stock Transfer of Purchasing Document Item
* CH_EIPO = "Foreign Trade: Export/Import: Item Data
TABLES
* CHT_SCHEDULES = "Fields for Purchase Order Delivery Schedule Lines
* CHT_ACCOUNTINGS = "Purchasing Document Number
* CHT_CONDITIONS = "Pricing Communications-Condition Record
* CHT_SERVICE_ACCOUNTINGS = "Structure for Change Document: Generated by RSSCD000
* IMT_BAPI_EKET = "Fields for Purchase Order Delivery Schedule Lines
* IMT_BAPI_EKETX = "Fields for Purchase Order Delivery Schedule Lines
* IMT_BAPI_EKKN = "Account Assignment Fields for Purchase Order
* IMT_BAPI_EKKNX = "Account Assignment Fields for Purchase Order
EXCEPTIONS
INVALID_CALL = 1
IMPORTING Parameters details for MEPO_DOC_ITEM_PROCESS
IM_ITEMX - Change Parameter: Purchase Order Item
Data type: MEPOITEMXOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_EKPVX - Change Parameter: Shipping Data EKPV
Data type: MEPO_EKPVXOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for MEPO_DOC_ITEM_PROCESS
EX_EBELP - Item Number of Purchasing Document
Data type: EKPO-EBELPOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for MEPO_DOC_ITEM_PROCESS
CH_ITEM - Purchase Order Item
Data type: MEPOITEMOptional: No
Call by Reference: No ( called with pass by value option)
CH_ITEM_SERVICE_DATA - Service Data for Purchase Order Item
Data type: MEPOCOMSRVOptional: Yes
Call by Reference: Yes
CH_EKPV - Shipping Data For Stock Transfer of Purchasing Document Item
Data type: EKPVOptional: Yes
Call by Reference: Yes
CH_EIPO - Foreign Trade: Export/Import: Item Data
Data type: MEPO_EIPOOptional: Yes
Call by Reference: Yes
TABLES Parameters details for MEPO_DOC_ITEM_PROCESS
CHT_SCHEDULES - Fields for Purchase Order Delivery Schedule Lines
Data type: MEPOSCHEDULEOptional: Yes
Call by Reference: No ( called with pass by value option)
CHT_ACCOUNTINGS - Purchasing Document Number
Data type: MEPOACCOUNTINGOptional: Yes
Call by Reference: No ( called with pass by value option)
CHT_CONDITIONS - Pricing Communications-Condition Record
Data type: KOMVOptional: Yes
Call by Reference: No ( called with pass by value option)
CHT_SERVICE_ACCOUNTINGS - Structure for Change Document: Generated by RSSCD000
Data type: UESKNOptional: Yes
Call by Reference: No ( called with pass by value option)
IMT_BAPI_EKET - Fields for Purchase Order Delivery Schedule Lines
Data type: MEPOSCHEDULEOptional: Yes
Call by Reference: Yes
IMT_BAPI_EKETX - Fields for Purchase Order Delivery Schedule Lines
Data type: MEPOSCHEDULEXOptional: Yes
Call by Reference: Yes
IMT_BAPI_EKKN - Account Assignment Fields for Purchase Order
Data type: MEPOACCOUNTINGOptional: Yes
Call by Reference: Yes
IMT_BAPI_EKKNX - Account Assignment Fields for Purchase Order
Data type: MEPOACCOUNTINGXOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MEPO_DOC_ITEM_PROCESS 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_ch_item | TYPE MEPOITEM, " | |||
| lv_ex_ebelp | TYPE EKPO-EBELP, " | |||
| lv_im_itemx | TYPE MEPOITEMX, " | |||
| lv_invalid_call | TYPE MEPOITEMX, " | |||
| lt_cht_schedules | TYPE STANDARD TABLE OF MEPOSCHEDULE, " | |||
| lv_im_ekpvx | TYPE MEPO_EKPVX, " | |||
| lt_cht_accountings | TYPE STANDARD TABLE OF MEPOACCOUNTING, " | |||
| lv_ch_item_service_data | TYPE MEPOCOMSRV, " | |||
| lv_ch_ekpv | TYPE EKPV, " | |||
| lt_cht_conditions | TYPE STANDARD TABLE OF KOMV, " | |||
| lv_ch_eipo | TYPE MEPO_EIPO, " | |||
| lt_cht_service_accountings | TYPE STANDARD TABLE OF UESKN, " | |||
| lt_imt_bapi_eket | TYPE STANDARD TABLE OF MEPOSCHEDULE, " | |||
| lt_imt_bapi_eketx | TYPE STANDARD TABLE OF MEPOSCHEDULEX, " | |||
| lt_imt_bapi_ekkn | TYPE STANDARD TABLE OF MEPOACCOUNTING, " | |||
| lt_imt_bapi_ekknx | TYPE STANDARD TABLE OF MEPOACCOUNTINGX. " |
|   CALL FUNCTION 'MEPO_DOC_ITEM_PROCESS' "NOTRANSL: Verarbeiten einer Einkaufsbelegposition im SAPMM06E |
| EXPORTING | ||
| IM_ITEMX | = lv_im_itemx | |
| IM_EKPVX | = lv_im_ekpvx | |
| IMPORTING | ||
| EX_EBELP | = lv_ex_ebelp | |
| CHANGING | ||
| CH_ITEM | = lv_ch_item | |
| CH_ITEM_SERVICE_DATA | = lv_ch_item_service_data | |
| CH_EKPV | = lv_ch_ekpv | |
| CH_EIPO | = lv_ch_eipo | |
| TABLES | ||
| CHT_SCHEDULES | = lt_cht_schedules | |
| CHT_ACCOUNTINGS | = lt_cht_accountings | |
| CHT_CONDITIONS | = lt_cht_conditions | |
| CHT_SERVICE_ACCOUNTINGS | = lt_cht_service_accountings | |
| IMT_BAPI_EKET | = lt_imt_bapi_eket | |
| IMT_BAPI_EKETX | = lt_imt_bapi_eketx | |
| IMT_BAPI_EKKN | = lt_imt_bapi_ekkn | |
| IMT_BAPI_EKKNX | = lt_imt_bapi_ekknx | |
| EXCEPTIONS | ||
| INVALID_CALL = 1 | ||
| . " MEPO_DOC_ITEM_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM MEPO_DOC_ITEM_PROCESS
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 EBELP FROM EKPO INTO @DATA(ld_ex_ebelp). | ||||
Search for further information about these or an SAP related objects