SAP MEPO_CALL Function Module for Obsolete









MEPO_CALL is a standard mepo call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolete 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 call FM, simply by entering the name MEPO_CALL into the relevant SAP transaction such as SE37 or SE38.

Function Group: MEGUI
Program Name: SAPLMEGUI
Main Program: SAPLMEGUI
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MEPO_CALL 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_CALL'"Obsolete
EXPORTING
IM_EBELN = "
* IM_EBELP = "
IM_TRTYP = "
* IM_DATABLADE = "

EXCEPTIONS
INVALID_TRANSACTION_TYPE = 1 INVALID_CALL = 2 NO_AUTHORITY = 3
.



IMPORTING Parameters details for MEPO_CALL

IM_EBELN -

Data type: EKKO-EBELN
Optional: No
Call by Reference: Yes

IM_EBELP -

Data type: EKPO-EBELP
Optional: Yes
Call by Reference: Yes

IM_TRTYP -

Data type: T160-TRTYP
Optional: No
Call by Reference: Yes

IM_DATABLADE -

Data type: MMPUR_DATABLADE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID_TRANSACTION_TYPE -

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)

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MEPO_CALL 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_invalid_transaction_type  TYPE EKKO, "   
lv_im_ebelp  TYPE EKPO-EBELP, "   
lv_invalid_call  TYPE EKPO, "   
lv_im_trtyp  TYPE T160-TRTYP, "   
lv_no_authority  TYPE T160, "   
lv_im_datablade  TYPE MMPUR_DATABLADE. "   

  CALL FUNCTION 'MEPO_CALL'  "Obsolete
    EXPORTING
         IM_EBELN = lv_im_ebeln
         IM_EBELP = lv_im_ebelp
         IM_TRTYP = lv_im_trtyp
         IM_DATABLADE = lv_im_datablade
    EXCEPTIONS
        INVALID_TRANSACTION_TYPE = 1
        INVALID_CALL = 2
        NO_AUTHORITY = 3
. " MEPO_CALL




ABAP code using 7.40 inline data declarations to call FM MEPO_CALL

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 EBELP FROM EKPO INTO @DATA(ld_im_ebelp).
 
 
"SELECT single TRTYP FROM T160 INTO @DATA(ld_im_trtyp).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!