SAP PVSDBCMP_SAVE Function Module for NOTRANSL: Sichern PVS Tabellen für Anwendungsobjekt CMP
PVSDBCMP_SAVE is a standard pvsdbcmp save 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: Sichern PVS Tabellen für Anwendungsobjekt CMP 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 pvsdbcmp save FM, simply by entering the name PVSDBCMP_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PVSDBCMP
Program Name: SAPLPVSDBCMP
Main Program: SAPLPVSDBCMP
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PVSDBCMP_SAVE 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 'PVSDBCMP_SAVE'"NOTRANSL: Sichern PVS Tabellen für Anwendungsobjekt CMP.
EXPORTING
IM_PPECNTL = "Control Parameters for Update
CHANGING
* T_PNODID = "
* T_POSVID = "
* T_POSVTX = "
* T_PVCMPD = "
* T_PVCMPV = "
* T_PVCMPP = "
* T_PVCMPR = "
* T_PVCMP = "
* T_PVCMPH = "
* T_PNODTX = "
* T_PNCMP = "
* T_PALTID = "
* T_PALTTX = "
* T_PACMP = "
* T_PRELID = "
* T_PRELIDH = "
* T_PRPVR = "
IMPORTING Parameters details for PVSDBCMP_SAVE
IM_PPECNTL - Control Parameters for Update
Data type: PPET_PPECNTLOptional: No
Call by Reference: Yes
CHANGING Parameters details for PVSDBCMP_SAVE
T_PNODID -
Data type: PPET_PNODID_TABOptional: Yes
Call by Reference: Yes
T_POSVID -
Data type: PPET_POSVID_TABOptional: Yes
Call by Reference: Yes
T_POSVTX -
Data type: PPET_POSVTX_TABOptional: Yes
Call by Reference: Yes
T_PVCMPD -
Data type: PPET1_PVCMPD_TABOptional: Yes
Call by Reference: Yes
T_PVCMPV -
Data type: PPET1_PVCMPV_TABOptional: Yes
Call by Reference: Yes
T_PVCMPP -
Data type: PPET1_PVCMPP_TABOptional: Yes
Call by Reference: Yes
T_PVCMPR -
Data type: PPET1_PVCMPR_TABOptional: Yes
Call by Reference: Yes
T_PVCMP -
Data type: PPET1_PVCMP_TABOptional: Yes
Call by Reference: Yes
T_PVCMPH -
Data type: PPET1_PVCMPH_TABOptional: Yes
Call by Reference: Yes
T_PNODTX -
Data type: PPET_PNODTX_TABOptional: Yes
Call by Reference: Yes
T_PNCMP -
Data type: PPET1_PNCMP_TABOptional: Yes
Call by Reference: Yes
T_PALTID -
Data type: PPET_PALTID_TABOptional: Yes
Call by Reference: Yes
T_PALTTX -
Data type: PPET_PALTTX_TABOptional: Yes
Call by Reference: Yes
T_PACMP -
Data type: PPET1_PACMP_TABOptional: Yes
Call by Reference: Yes
T_PRELID -
Data type: PPET_PRELID_TABOptional: Yes
Call by Reference: Yes
T_PRELIDH -
Data type: PPET_PRELIDH_TABOptional: Yes
Call by Reference: Yes
T_PRPVR -
Data type: PPET1_PRPVR_TABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PVSDBCMP_SAVE 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_t_pnodid | TYPE PPET_PNODID_TAB, " | |||
| lv_im_ppecntl | TYPE PPET_PPECNTL, " | |||
| lv_t_posvid | TYPE PPET_POSVID_TAB, " | |||
| lv_t_posvtx | TYPE PPET_POSVTX_TAB, " | |||
| lv_t_pvcmpd | TYPE PPET1_PVCMPD_TAB, " | |||
| lv_t_pvcmpv | TYPE PPET1_PVCMPV_TAB, " | |||
| lv_t_pvcmpp | TYPE PPET1_PVCMPP_TAB, " | |||
| lv_t_pvcmpr | TYPE PPET1_PVCMPR_TAB, " | |||
| lv_t_pvcmp | TYPE PPET1_PVCMP_TAB, " | |||
| lv_t_pvcmph | TYPE PPET1_PVCMPH_TAB, " | |||
| lv_t_pnodtx | TYPE PPET_PNODTX_TAB, " | |||
| lv_t_pncmp | TYPE PPET1_PNCMP_TAB, " | |||
| lv_t_paltid | TYPE PPET_PALTID_TAB, " | |||
| lv_t_palttx | TYPE PPET_PALTTX_TAB, " | |||
| lv_t_pacmp | TYPE PPET1_PACMP_TAB, " | |||
| lv_t_prelid | TYPE PPET_PRELID_TAB, " | |||
| lv_t_prelidh | TYPE PPET_PRELIDH_TAB, " | |||
| lv_t_prpvr | TYPE PPET1_PRPVR_TAB. " |
|   CALL FUNCTION 'PVSDBCMP_SAVE' "NOTRANSL: Sichern PVS Tabellen für Anwendungsobjekt CMP |
| EXPORTING | ||
| IM_PPECNTL | = lv_im_ppecntl | |
| CHANGING | ||
| T_PNODID | = lv_t_pnodid | |
| T_POSVID | = lv_t_posvid | |
| T_POSVTX | = lv_t_posvtx | |
| T_PVCMPD | = lv_t_pvcmpd | |
| T_PVCMPV | = lv_t_pvcmpv | |
| T_PVCMPP | = lv_t_pvcmpp | |
| T_PVCMPR | = lv_t_pvcmpr | |
| T_PVCMP | = lv_t_pvcmp | |
| T_PVCMPH | = lv_t_pvcmph | |
| T_PNODTX | = lv_t_pnodtx | |
| T_PNCMP | = lv_t_pncmp | |
| T_PALTID | = lv_t_paltid | |
| T_PALTTX | = lv_t_palttx | |
| T_PACMP | = lv_t_pacmp | |
| T_PRELID | = lv_t_prelid | |
| T_PRELIDH | = lv_t_prelidh | |
| T_PRPVR | = lv_t_prpvr | |
| . " PVSDBCMP_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM PVSDBCMP_SAVE
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