SAP /SAPAPO/DM_PEGAREA_UPDATE Function Module for Update Pegging Area After Product Changes

Search SAP Function Modules

/SAPAPO/DM_PEGAREA_UPDATE is a standard /sapapo/dm pegarea update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Pegging Area After Product Changes 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 pegarea update FM, simply by entering the name /SAPAPO/DM_PEGAREA_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SAPAPO/DM_PEGAREA
Program Name: /SAPAPO/SAPLDM_PEGAREA
Main Program: /SAPAPO/SAPLDM_PEGAREA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SAPAPO/DM_PEGAREA_UPDATE 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_PEGAREA_UPDATE'"Update Pegging Area After Product Changes
  EXPORTING
*  IV_MATID =  "
*  IT_MATLOCSIM =  "
*  IV_RQMID =  "
*  IV_ASYNC =  "Dummy Datenlement für Boolean-Felder
*  IV_COMMIT = GC_TRUE "Dummy Datenlement für Boolean-Felder

 IMPORTING
   ET_RC =  "

EXCEPTIONS
   NOT_QUALIFIED = 1    LC_CONNECT_FAILED = 2    LC_COM_ERROR = 3    LC_APPL_ERROR = 4 

.

IMPORTING Parameters details for /SAPAPO/DM_PEGAREA_UPDATE

IV_MATID -

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

IT_MATLOCSIM -

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

IV_RQMID -

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

IV_ASYNC - Dummy Datenlement für Boolean-Felder

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

IV_COMMIT - Dummy Datenlement für Boolean-Felder

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

EXPORTING Parameters details for /SAPAPO/DM_PEGAREA_UPDATE

ET_RC -

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

EXCEPTIONS details

NOT_QUALIFIED -

Data type:
Optional: No
Call by Reference: Yes

LC_CONNECT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

LC_COM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LC_APPL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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