SAP /SAPAPO/DM_MATID_GET_IO Function Module for Where-Used List for Product









/SAPAPO/DM_MATID_GET_IO is a standard /sapapo/dm matid get io SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Where-Used List for Product 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 matid get io FM, simply by entering the name /SAPAPO/DM_MATID_GET_IO into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SAPAPO/DM_LC_SYNC
Program Name: /SAPAPO/SAPLDM_LC_SYNC
Main Program: /SAPAPO/SAPLDM_LC_SYNC
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /SAPAPO/DM_MATID_GET_IO 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_MATID_GET_IO'"Where-Used List for Product
EXPORTING
* IV_MATID = "interne Nummer (UID) für Produkt
* IV_LOCID = "interne Nummer der Lokation (Kunde, Lieferant oder Werk)
* IT_MATLOC = "Tabelle für MATID und LOCID (Produktlokation)
* IT_MATID = "Tabelle von internen Materialnummern
* IV_IGNORE_INVALID_PEGAREA = GC_TRUE "Dummy Datenlement für Boolean-Felder
* IV_CLASSID = "Einschränkung der Aufträge über CDP-Klassenzuordnung

IMPORTING
ET_IONODES = "
ET_ORD_SHOW = "Ausgabe Aufträge zu Lokationsprodukt
EV_FLAG_IO_EXIST = "Kennzeichen: Es liegen Aufträge vor, die die gegebenen Kriterien erfüllen

EXCEPTIONS
NOT_QUALIFIED = 1
.



IMPORTING Parameters details for /SAPAPO/DM_MATID_GET_IO

IV_MATID - interne Nummer (UID) für Produkt

Data type: /SAPAPO/MATID
Optional: Yes
Call by Reference: Yes

IV_LOCID - interne Nummer der Lokation (Kunde, Lieferant oder Werk)

Data type: /SAPAPO/LOCID
Optional: Yes
Call by Reference: Yes

IT_MATLOC - Tabelle für MATID und LOCID (Produktlokation)

Data type: /SAPAPO/DM_MATLOC_ID_TAB
Optional: Yes
Call by Reference: Yes

IT_MATID - Tabelle von internen Materialnummern

Data type: /SAPAPO/MATID_TAB
Optional: Yes
Call by Reference: Yes

IV_IGNORE_INVALID_PEGAREA - Dummy Datenlement für Boolean-Felder

Data type: /SAPAPO/BOOLEAN
Default: GC_TRUE
Optional: Yes
Call by Reference: Yes

IV_CLASSID - Einschränkung der Aufträge über CDP-Klassenzuordnung

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

EXPORTING Parameters details for /SAPAPO/DM_MATID_GET_IO

ET_IONODES -

Data type: /SAPAPO/OM_IO_PP_TAB
Optional: No
Call by Reference: Yes

ET_ORD_SHOW - Ausgabe Aufträge zu Lokationsprodukt

Data type: /SAPAPO/MATLOC_SHOW_ORDER_TAB
Optional: No
Call by Reference: Yes

EV_FLAG_IO_EXIST - Kennzeichen: Es liegen Aufträge vor, die die gegebenen Kriterien erfüllen

Data type: /SAPAPO/BOOLEAN
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_QUALIFIED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /SAPAPO/DM_MATID_GET_IO 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_iv_matid  TYPE /SAPAPO/MATID, "   
lv_et_ionodes  TYPE /SAPAPO/OM_IO_PP_TAB, "   
lv_not_qualified  TYPE /SAPAPO/OM_IO_PP_TAB, "   
lv_iv_locid  TYPE /SAPAPO/LOCID, "   
lv_et_ord_show  TYPE /SAPAPO/MATLOC_SHOW_ORDER_TAB, "   
lv_it_matloc  TYPE /SAPAPO/DM_MATLOC_ID_TAB, "   
lv_ev_flag_io_exist  TYPE /SAPAPO/BOOLEAN, "   
lv_it_matid  TYPE /SAPAPO/MATID_TAB, "   
lv_iv_ignore_invalid_pegarea  TYPE /SAPAPO/BOOLEAN, "   GC_TRUE
lv_iv_classid  TYPE /SAPAPO/CLASS_ID. "   

  CALL FUNCTION '/SAPAPO/DM_MATID_GET_IO'  "Where-Used List for Product
    EXPORTING
         IV_MATID = lv_iv_matid
         IV_LOCID = lv_iv_locid
         IT_MATLOC = lv_it_matloc
         IT_MATID = lv_it_matid
         IV_IGNORE_INVALID_PEGAREA = lv_iv_ignore_invalid_pegarea
         IV_CLASSID = lv_iv_classid
    IMPORTING
         ET_IONODES = lv_et_ionodes
         ET_ORD_SHOW = lv_et_ord_show
         EV_FLAG_IO_EXIST = lv_ev_flag_io_exist
    EXCEPTIONS
        NOT_QUALIFIED = 1
. " /SAPAPO/DM_MATID_GET_IO




ABAP code using 7.40 inline data declarations to call FM /SAPAPO/DM_MATID_GET_IO

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.

 
 
 
 
 
 
 
 
DATA(ld_iv_ignore_invalid_pegarea) = GC_TRUE.
 
 


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!