SAP /SAPAPO/DM_NODE_GET_DATA Function Module for Provides Data for Material Receipt/Issue
/SAPAPO/DM_NODE_GET_DATA is a standard /sapapo/dm node get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Provides Data for Material Receipt/Issue 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 node get data FM, simply by entering the name /SAPAPO/DM_NODE_GET_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SAPAPO/DM_NODE
Program Name: /SAPAPO/SAPLDM_NODE
Main Program: /SAPAPO/SAPLDM_NODE
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /SAPAPO/DM_NODE_GET_DATA 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_NODE_GET_DATA'"Provides Data for Material Receipt/Issue.
EXPORTING
IS_NODE = "
* IV_STATUS = "Status eines Auftrags
IMPORTING
EV_MATID = "
EV_R3OBJ = "Typ des OLTP-Objektes
ES_ORDER = "
ES_ACCOUNT = "
ES_CATTEXT = "
EV_EXTRACT = "
EV_TEXT40 = "
EV_ORDER_TYPE_INT = "
EV_LOCID = "
EV_MATNR = "
EV_MAKTX = "
EV_MEINS = "
EV_MANOT = "
EV_LOCNO = "
EV_LOCNO_OTHER = "
EV_LOCID_OTHER = "
IMPORTING Parameters details for /SAPAPO/DM_NODE_GET_DATA
IS_NODE -
Data type: /SAPAPO/OM_IO_PPOptional: No
Call by Reference: Yes
IV_STATUS - Status eines Auftrags
Data type: /SAPAPO/ORDER_STATUSOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for /SAPAPO/DM_NODE_GET_DATA
EV_MATID -
Data type: /SAPAPO/MATIDOptional: No
Call by Reference: Yes
EV_R3OBJ - Typ des OLTP-Objektes
Data type: /SAPAPO/R3OBJOptional: No
Call by Reference: Yes
ES_ORDER -
Data type: /SAPAPO/OM_ORDER_EXT_STROptional: No
Call by Reference: Yes
ES_ACCOUNT -
Data type: /SAPAPO/ACCNTOptional: No
Call by Reference: Yes
ES_CATTEXT -
Data type: /SAPAPO/ATP03TOptional: No
Call by Reference: Yes
EV_EXTRACT -
Data type: /SAPAPO/EXTRAOptional: No
Call by Reference: Yes
EV_TEXT40 -
Data type: TEXT40Optional: No
Call by Reference: Yes
EV_ORDER_TYPE_INT -
Data type: /SAPAPO/OM_ORDER_TYPEOptional: No
Call by Reference: Yes
EV_LOCID -
Data type: /SAPAPO/LOCIDOptional: No
Call by Reference: Yes
EV_MATNR -
Data type: /SAPAPO/MATNROptional: No
Call by Reference: Yes
EV_MAKTX -
Data type: /SAPAPO/MAKTXOptional: No
Call by Reference: Yes
EV_MEINS -
Data type: /SAPAPO/MEINSOptional: No
Call by Reference: Yes
EV_MANOT -
Data type: /SAPAPO/MANOTOptional: No
Call by Reference: Yes
EV_LOCNO -
Data type: /SAPAPO/LOCNOOptional: No
Call by Reference: Yes
EV_LOCNO_OTHER -
Data type: /SAPAPO/LOCNOOptional: No
Call by Reference: Yes
EV_LOCID_OTHER -
Data type: /SAPAPO/LOCIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /SAPAPO/DM_NODE_GET_DATA 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_is_node | TYPE /SAPAPO/OM_IO_PP, " | |||
| lv_ev_matid | TYPE /SAPAPO/MATID, " | |||
| lv_ev_r3obj | TYPE /SAPAPO/R3OBJ, " | |||
| lv_es_order | TYPE /SAPAPO/OM_ORDER_EXT_STR, " | |||
| lv_es_account | TYPE /SAPAPO/ACCNT, " | |||
| lv_es_cattext | TYPE /SAPAPO/ATP03T, " | |||
| lv_ev_extract | TYPE /SAPAPO/EXTRA, " | |||
| lv_ev_text40 | TYPE TEXT40, " | |||
| lv_ev_order_type_int | TYPE /SAPAPO/OM_ORDER_TYPE, " | |||
| lv_ev_locid | TYPE /SAPAPO/LOCID, " | |||
| lv_iv_status | TYPE /SAPAPO/ORDER_STATUS, " | |||
| lv_ev_matnr | TYPE /SAPAPO/MATNR, " | |||
| lv_ev_maktx | TYPE /SAPAPO/MAKTX, " | |||
| lv_ev_meins | TYPE /SAPAPO/MEINS, " | |||
| lv_ev_manot | TYPE /SAPAPO/MANOT, " | |||
| lv_ev_locno | TYPE /SAPAPO/LOCNO, " | |||
| lv_ev_locno_other | TYPE /SAPAPO/LOCNO, " | |||
| lv_ev_locid_other | TYPE /SAPAPO/LOCID. " |
|   CALL FUNCTION '/SAPAPO/DM_NODE_GET_DATA' "Provides Data for Material Receipt/Issue |
| EXPORTING | ||
| IS_NODE | = lv_is_node | |
| IV_STATUS | = lv_iv_status | |
| IMPORTING | ||
| EV_MATID | = lv_ev_matid | |
| EV_R3OBJ | = lv_ev_r3obj | |
| ES_ORDER | = lv_es_order | |
| ES_ACCOUNT | = lv_es_account | |
| ES_CATTEXT | = lv_es_cattext | |
| EV_EXTRACT | = lv_ev_extract | |
| EV_TEXT40 | = lv_ev_text40 | |
| EV_ORDER_TYPE_INT | = lv_ev_order_type_int | |
| EV_LOCID | = lv_ev_locid | |
| EV_MATNR | = lv_ev_matnr | |
| EV_MAKTX | = lv_ev_maktx | |
| EV_MEINS | = lv_ev_meins | |
| EV_MANOT | = lv_ev_manot | |
| EV_LOCNO | = lv_ev_locno | |
| EV_LOCNO_OTHER | = lv_ev_locno_other | |
| EV_LOCID_OTHER | = lv_ev_locid_other | |
| . " /SAPAPO/DM_NODE_GET_DATA | ||
ABAP code using 7.40 inline data declarations to call FM /SAPAPO/DM_NODE_GET_DATA
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