SAP /SAPAPO/DM_PEGID_HAS_CHANGED_V Function Module for Create Planning File Entry in Update Task

Search SAP Function Modules

/SAPAPO/DM_PEGID_HAS_CHANGED_V is a standard /sapapo/dm pegid has changed v SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Planning File Entry in Update Task 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 pegid has changed v FM, simply by entering the name /SAPAPO/DM_PEGID_HAS_CHANGED_V into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SAPAPO/DM_CHANGES_COLLECT
Program Name: /SAPAPO/SAPLDM_CHANGES_COLLECT
Main Program: /SAPAPO/SAPLDM_CHANGES_COLLECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 2

Function /SAPAPO/DM_PEGID_HAS_CHANGED_V 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_PEGID_HAS_CHANGED_V'"Create Planning File Entry in Update Task
  EXPORTING
   IV_EVENT =  "Planungsrelevantes Ereignis
*  IT_MATLOCSIM =  "Tabelle von Produkt-Lokation.Versions Kombinationen
*  IT_TRPROD =  "Bezugsquellen
*  IV_MATID =  "interne Nummer (UID) für Produkt
*  IV_LOCID =  "interne Nummer der Lokation (Kunde, Lieferant oder Werk)

.

IMPORTING Parameters details for /SAPAPO/DM_PEGID_HAS_CHANGED_V

IV_EVENT - Planungsrelevantes Ereignis

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

IT_MATLOCSIM - Tabelle von Produkt-Lokation.Versions Kombinationen

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

IT_TRPROD - Bezugsquellen

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

IV_MATID - interne Nummer (UID) für Produkt

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

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

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

Copy and paste ABAP code example for /SAPAPO/DM_PEGID_HAS_CHANGED_V 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.

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

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