SAP /SAPAPO/DM_CUST_ORDER_GET Function Module for Read Sales Orders from Database
/SAPAPO/DM_CUST_ORDER_GET is a standard /sapapo/dm cust order get 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 Sales Orders from Database 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 /sapapo/dm cust order get FM, simply by entering the name /SAPAPO/DM_CUST_ORDER_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SAPAPO/DM_CUST_ORDER
Program Name: /SAPAPO/SAPLDM_CUST_ORDER
Main Program: /SAPAPO/SAPLDM_CUST_ORDER
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /SAPAPO/DM_CUST_ORDER_GET 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 '/SAPAPO/DM_CUST_ORDER_GET'"Read Sales Orders from Database.
EXPORTING
IS_GEN_PARAMS = "
IT_ORDER = "
IV_OM_ORDER_TYPE = "
IV_SIMSESSION = "
IMPORTING
ET_SCHEDULE = "
ET_CHARACT_REQ_INPNODE = "
ET_POSITIONS = "Auftragspositionstabelle
ET_RC = "
EXCEPTIONS
LC_CONNECT_FAILED = 1 LC_COM_ERROR = 2 LC_APPL_ERROR = 3
IMPORTING Parameters details for /SAPAPO/DM_CUST_ORDER_GET
IS_GEN_PARAMS -
Data type: /SAPAPO/OM_GEN_PARAMSOptional: No
Call by Reference: No ( called with pass by value option)
IT_ORDER -
Data type: /SAPAPO/OM_ORDERID_TABOptional: No
Call by Reference: Yes
IV_OM_ORDER_TYPE -
Data type: /SAPAPO/OM_ORDER_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_SIMSESSION -
Data type: /SAPAPO/OM_SIMSESSIONOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /SAPAPO/DM_CUST_ORDER_GET
ET_SCHEDULE -
Data type: /SAPAPO/OM_SCHEDULE_LINE_TABOptional: No
Call by Reference: Yes
ET_CHARACT_REQ_INPNODE -
Data type: /SAPAPO/OM_CHARACT_REQ_TABOptional: No
Call by Reference: Yes
ET_POSITIONS - Auftragspositionstabelle
Data type: /SAPAPO/OM_ORDER_POSITION_TABOptional: No
Call by Reference: Yes
ET_RC -
Data type: /SAPAPO/OM_LC_RC_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
LC_CONNECT_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LC_COM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LC_APPL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /SAPAPO/DM_CUST_ORDER_GET 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_et_schedule | TYPE /SAPAPO/OM_SCHEDULE_LINE_TAB, " | |||
| lv_is_gen_params | TYPE /SAPAPO/OM_GEN_PARAMS, " | |||
| lv_lc_connect_failed | TYPE /SAPAPO/OM_GEN_PARAMS, " | |||
| lv_it_order | TYPE /SAPAPO/OM_ORDERID_TAB, " | |||
| lv_lc_com_error | TYPE /SAPAPO/OM_ORDERID_TAB, " | |||
| lv_et_charact_req_inpnode | TYPE /SAPAPO/OM_CHARACT_REQ_TAB, " | |||
| lv_et_positions | TYPE /SAPAPO/OM_ORDER_POSITION_TAB, " | |||
| lv_lc_appl_error | TYPE /SAPAPO/OM_ORDER_POSITION_TAB, " | |||
| lv_iv_om_order_type | TYPE /SAPAPO/OM_ORDER_TYPE, " | |||
| lv_et_rc | TYPE /SAPAPO/OM_LC_RC_TAB, " | |||
| lv_iv_simsession | TYPE /SAPAPO/OM_SIMSESSION. " |
|   CALL FUNCTION '/SAPAPO/DM_CUST_ORDER_GET' "Read Sales Orders from Database |
| EXPORTING | ||
| IS_GEN_PARAMS | = lv_is_gen_params | |
| IT_ORDER | = lv_it_order | |
| IV_OM_ORDER_TYPE | = lv_iv_om_order_type | |
| IV_SIMSESSION | = lv_iv_simsession | |
| IMPORTING | ||
| ET_SCHEDULE | = lv_et_schedule | |
| ET_CHARACT_REQ_INPNODE | = lv_et_charact_req_inpnode | |
| ET_POSITIONS | = lv_et_positions | |
| ET_RC | = lv_et_rc | |
| EXCEPTIONS | ||
| LC_CONNECT_FAILED = 1 | ||
| LC_COM_ERROR = 2 | ||
| LC_APPL_ERROR = 3 | ||
| . " /SAPAPO/DM_CUST_ORDER_GET | ||
ABAP code using 7.40 inline data declarations to call FM /SAPAPO/DM_CUST_ORDER_GET
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