SAP MSAM_MO_CORDER_GETDETAIL Function Module for Read Order Processing profile in Customizing









MSAM_MO_CORDER_GETDETAIL is a standard msam mo corder getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Order Processing profile in Customizing 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 msam mo corder getdetail FM, simply by entering the name MSAM_MO_CORDER_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSAM_MO_CUSTOMIZING
Program Name: SAPLMSAM_MO_CUSTOMIZING
Main Program: SAPLMSAM_MO_CUSTOMIZING
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MSAM_MO_CORDER_GETDETAIL 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 'MSAM_MO_CORDER_GETDETAIL'"Read Order Processing profile in Customizing
EXPORTING
PROFILE_ORDER = "Order Profile

IMPORTING
ORDER_PROFILE = "Order Profile

TABLES
* RETURN = "Return parameter

EXCEPTIONS
ENTRY_NOT_FOUND = 1
.



IMPORTING Parameters details for MSAM_MO_CORDER_GETDETAIL

PROFILE_ORDER - Order Profile

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

EXPORTING Parameters details for MSAM_MO_CORDER_GETDETAIL

ORDER_PROFILE - Order Profile

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

TABLES Parameters details for MSAM_MO_CORDER_GETDETAIL

RETURN - Return parameter

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

EXCEPTIONS details

ENTRY_NOT_FOUND -

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

Copy and paste ABAP code example for MSAM_MO_CORDER_GETDETAIL 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_order_profile  TYPE MSAM10_ORDER_PROFILE, "   
lv_profile_order  TYPE MSAM10_ORDER_PROFILE-PROFILE_ORDER, "   
lv_entry_not_found  TYPE MSAM10_ORDER_PROFILE. "   

  CALL FUNCTION 'MSAM_MO_CORDER_GETDETAIL'  "Read Order Processing profile in Customizing
    EXPORTING
         PROFILE_ORDER = lv_profile_order
    IMPORTING
         ORDER_PROFILE = lv_order_profile
    TABLES
         RETURN = lt_return
    EXCEPTIONS
        ENTRY_NOT_FOUND = 1
. " MSAM_MO_CORDER_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM MSAM_MO_CORDER_GETDETAIL

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 PROFILE_ORDER FROM MSAM10_ORDER_PROFILE INTO @DATA(ld_profile_order).
 
 


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!