SAP MEPOBADI_OPEN Function Module for Open a Purchase Order
MEPOBADI_OPEN is a standard mepobadi open SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Open a Purchase Order 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 mepobadi open FM, simply by entering the name MEPOBADI_OPEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEPOBADI
Program Name: SAPLMEPOBADI
Main Program: SAPLMEPOBADI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MEPOBADI_OPEN 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 'MEPOBADI_OPEN'"Open a Purchase Order.
EXPORTING
IM_TRTYP = "Transaction Type
IM_HEADER = "PO Header External View
CHANGING
CH_VALID = "Successful
CH_DISPLAY_ONLY = "Process in Display Mode Only
IMPORTING Parameters details for MEPOBADI_OPEN
IM_TRTYP - Transaction Type
Data type: TRTYPOptional: No
Call by Reference: Yes
IM_HEADER - PO Header External View
Data type: IF_PURCHASE_ORDER_MMOptional: No
Call by Reference: Yes
CHANGING Parameters details for MEPOBADI_OPEN
CH_VALID - Successful
Data type: MMPUR_BOOLOptional: No
Call by Reference: Yes
CH_DISPLAY_ONLY - Process in Display Mode Only
Data type: MMPUR_BOOLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MEPOBADI_OPEN 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_valid | TYPE MMPUR_BOOL, " | |||
| lv_im_trtyp | TYPE TRTYP, " | |||
| lv_im_header | TYPE IF_PURCHASE_ORDER_MM, " | |||
| lv_ch_display_only | TYPE MMPUR_BOOL. " |
|   CALL FUNCTION 'MEPOBADI_OPEN' "Open a Purchase Order |
| EXPORTING | ||
| IM_TRTYP | = lv_im_trtyp | |
| IM_HEADER | = lv_im_header | |
| CHANGING | ||
| CH_VALID | = lv_ch_valid | |
| CH_DISPLAY_ONLY | = lv_ch_display_only | |
| . " MEPOBADI_OPEN | ||
ABAP code using 7.40 inline data declarations to call FM MEPOBADI_OPEN
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