SAP ISHMED_ME_ORDER_END Function Module for









ISHMED_ME_ORDER_END is a standard ishmed me order end SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ishmed me order end FM, simply by entering the name ISHMED_ME_ORDER_END into the relevant SAP transaction such as SE37 or SE38.

Function Group: N1ME_WS
Program Name: SAPLN1ME_WS
Main Program: SAPLN1ME_WS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ISHMED_ME_ORDER_END 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 'ISHMED_ME_ORDER_END'"
EXPORTING
I_MEORDID = "
* I_DATE = "
* I_TIME = "
* I_GPART = "
* I_RCODEID = "

IMPORTING
ET_ERROR_MESSAGES = "
ET_MESSAGES = "
E_MAXTY = "
E_RC = "
.



IMPORTING Parameters details for ISHMED_ME_ORDER_END

I_MEORDID -

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

I_DATE -

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

I_TIME -

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

I_GPART -

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

I_RCODEID -

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

EXPORTING Parameters details for ISHMED_ME_ORDER_END

ET_ERROR_MESSAGES -

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

ET_MESSAGES -

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

E_MAXTY -

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

E_RC -

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

Copy and paste ABAP code example for ISHMED_ME_ORDER_END 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_i_meordid  TYPE N1ME_MEORDID, "   
lv_et_error_messages  TYPE ISH_T_WS_MSG, "   
lv_i_date  TYPE N1ME_PBDAD, "   
lv_et_messages  TYPE ISHMED_T_BAPIRET2, "   
lv_i_time  TYPE N1ME_PBTAD, "   
lv_e_maxty  TYPE ISH_BAPIRETMAXTY, "   
lv_e_rc  TYPE ISH_METHOD_RC, "   
lv_i_gpart  TYPE N1MITARB, "   
lv_i_rcodeid  TYPE N1ME_RCODEID. "   

  CALL FUNCTION 'ISHMED_ME_ORDER_END'  "
    EXPORTING
         I_MEORDID = lv_i_meordid
         I_DATE = lv_i_date
         I_TIME = lv_i_time
         I_GPART = lv_i_gpart
         I_RCODEID = lv_i_rcodeid
    IMPORTING
         ET_ERROR_MESSAGES = lv_et_error_messages
         ET_MESSAGES = lv_et_messages
         E_MAXTY = lv_e_maxty
         E_RC = lv_e_rc
. " ISHMED_ME_ORDER_END




ABAP code using 7.40 inline data declarations to call FM ISHMED_ME_ORDER_END

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



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!