SAP PM_UPDATE_PMPL Function Module for NOTRANSL: PM: Update PMPL Print log record
PM_UPDATE_PMPL is a standard pm update pmpl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: PM: Update PMPL Print log record 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 pm update pmpl FM, simply by entering the name PM_UPDATE_PMPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: IPRT
Program Name: SAPLIPRT
Main Program: SAPLIPRT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function PM_UPDATE_PMPL 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 'PM_UPDATE_PMPL'"NOTRANSL: PM: Update PMPL Print log record.
EXPORTING
INDUPD = "(I)nsert (U)pdate (D)elete
WPMPL = "PMPL Record - * for generic delete ...
EXCEPTIONS
INVALID_GENERIC_ACTION = 1 INVALID_PARAMETER = 2 KEY_NOT_FULLY_SPECIFIED = 3
IMPORTING Parameters details for PM_UPDATE_PMPL
INDUPD - (I)nsert (U)pdate (D)elete
Data type: RIUPD-INDUPDOptional: No
Call by Reference: No ( called with pass by value option)
WPMPL - PMPL Record - * for generic delete ...
Data type: PMPLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_GENERIC_ACTION - Generic WORKPAPER and COPY_NR are
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PARAMETER - Only I U and D are valid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KEY_NOT_FULLY_SPECIFIED - Complete key not entered
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PM_UPDATE_PMPL 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_indupd | TYPE RIUPD-INDUPD, " | |||
| lv_invalid_generic_action | TYPE RIUPD, " | |||
| lv_wpmpl | TYPE PMPL, " | |||
| lv_invalid_parameter | TYPE PMPL, " | |||
| lv_key_not_fully_specified | TYPE PMPL. " |
|   CALL FUNCTION 'PM_UPDATE_PMPL' "NOTRANSL: PM: Update PMPL Print log record |
| EXPORTING | ||
| INDUPD | = lv_indupd | |
| WPMPL | = lv_wpmpl | |
| EXCEPTIONS | ||
| INVALID_GENERIC_ACTION = 1 | ||
| INVALID_PARAMETER = 2 | ||
| KEY_NOT_FULLY_SPECIFIED = 3 | ||
| . " PM_UPDATE_PMPL | ||
ABAP code using 7.40 inline data declarations to call FM PM_UPDATE_PMPL
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.| "SELECT single INDUPD FROM RIUPD INTO @DATA(ld_indupd). | ||||
Search for further information about these or an SAP related objects