SAP MEPO_DOC_READ Function Module for NOTRANSL: Lesen eines Einkaufsbelegs im SAPMM06E
MEPO_DOC_READ is a standard mepo doc read 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: Lesen eines Einkaufsbelegs 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 read FM, simply by entering the name MEPO_DOC_READ 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_READ 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_READ'"NOTRANSL: Lesen eines Einkaufsbelegs im SAPMM06E.
EXPORTING
IM_EBELN = "Purchasing Document Number
IM_TCODE = "ABAP System Field: Current Transaction Code
IM_TRTYP = "Transaction type
* IM_ID = "Predefined Type
* IM_DOCUMENT = "Purchasing Document
* IM_NO_MESSAGING = "Checkbox
* IM_NO_MESSAGE_REQ = "Checkbox
* IM_NO_AUTHORITY = "No Authorization Check
EXCEPTIONS
DOC_NUMBER_MISSING = 1 TRANSACTION_CODE_MISSING = 2 TRANSACTION_TYPE_MISSING = 3 INVALID_CALL = 4
IMPORTING Parameters details for MEPO_DOC_READ
IM_EBELN - Purchasing Document Number
Data type: EKKO-EBELNOptional: No
Call by Reference: No ( called with pass by value option)
IM_TCODE - ABAP System Field: Current Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IM_TRTYP - Transaction type
Data type: T160-TRTYPOptional: No
Call by Reference: No ( called with pass by value option)
IM_ID - Predefined Type
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_DOCUMENT - Purchasing Document
Data type: MEPO_DOCUMENTOptional: Yes
Call by Reference: Yes
IM_NO_MESSAGING - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
IM_NO_MESSAGE_REQ - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
IM_NO_AUTHORITY - No Authorization Check
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DOC_NUMBER_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TRANSACTION_CODE_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TRANSACTION_TYPE_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
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_READ 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_im_ebeln | TYPE EKKO-EBELN, " | |||
| lv_doc_number_missing | TYPE EKKO, " | |||
| lv_im_tcode | TYPE SY-TCODE, " | |||
| lv_transaction_code_missing | TYPE SY, " | |||
| lv_im_trtyp | TYPE T160-TRTYP, " | |||
| lv_transaction_type_missing | TYPE T160, " | |||
| lv_im_id | TYPE I, " | |||
| lv_invalid_call | TYPE I, " | |||
| lv_im_document | TYPE MEPO_DOCUMENT, " | |||
| lv_im_no_messaging | TYPE XFELD, " | |||
| lv_im_no_message_req | TYPE XFELD, " | |||
| lv_im_no_authority | TYPE XFELD. " |
|   CALL FUNCTION 'MEPO_DOC_READ' "NOTRANSL: Lesen eines Einkaufsbelegs im SAPMM06E |
| EXPORTING | ||
| IM_EBELN | = lv_im_ebeln | |
| IM_TCODE | = lv_im_tcode | |
| IM_TRTYP | = lv_im_trtyp | |
| IM_ID | = lv_im_id | |
| IM_DOCUMENT | = lv_im_document | |
| IM_NO_MESSAGING | = lv_im_no_messaging | |
| IM_NO_MESSAGE_REQ | = lv_im_no_message_req | |
| IM_NO_AUTHORITY | = lv_im_no_authority | |
| EXCEPTIONS | ||
| DOC_NUMBER_MISSING = 1 | ||
| TRANSACTION_CODE_MISSING = 2 | ||
| TRANSACTION_TYPE_MISSING = 3 | ||
| INVALID_CALL = 4 | ||
| . " MEPO_DOC_READ | ||
ABAP code using 7.40 inline data declarations to call FM MEPO_DOC_READ
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 EBELN FROM EKKO INTO @DATA(ld_im_ebeln). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_im_tcode). | ||||
| "SELECT single TRTYP FROM T160 INTO @DATA(ld_im_trtyp). | ||||
Search for further information about these or an SAP related objects