SAP PVSDBFRM_SAVE Function Module for RMS-FRM: Save PVS Tables for Application Object FRM









PVSDBFRM_SAVE is a standard pvsdbfrm 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 RMS-FRM: Save PVS Tables for Application Object FRM 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 pvsdbfrm save FM, simply by entering the name PVSDBFRM_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PVSDBFRM
Program Name: SAPLPVSDBFRM
Main Program: SAPLPVSDBFRM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PVSDBFRM_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 'PVSDBFRM_SAVE'"RMS-FRM: Save PVS Tables for Application Object FRM
  EXPORTING
   IM_PPECNTL =  "

CHANGING
*  T_PNODID =  "
*  T_PVFRMD =  "
*  T_PVFRMS =  "
*  T_PVFRMM =  "
*  T_PVFRMI =  "
*  T_PVFRMH =  "
*  T_PNODTX =  "
*  T_PNFRM =  "
*  T_PALTID =  "
*  T_PALTTX =  "
*  T_PAFRM =  "
*  T_PRELID =  "
*  T_POSVID =  "
*  T_POSVTX =  "RMS-ATL: Table Type for Variant Texts for DB Layer
.



IMPORTING Parameters details for PVSDBFRM_SAVE

IM_PPECNTL -

Data type: PPET_PPECNTL
Optional: No
Call by Reference: Yes

CHANGING Parameters details for PVSDBFRM_SAVE

T_PNODID -

Data type: PPET_PNODID_TAB
Optional: Yes
Call by Reference: Yes

T_PVFRMD -

Data type: FRMPV_PVFRMD_TAB
Optional: Yes
Call by Reference: Yes

T_PVFRMS -

Data type: FRMPV_PVFRMS_TAB
Optional: Yes
Call by Reference: Yes

T_PVFRMM -

Data type: FRMPV_PVFRMM_TAB
Optional: Yes
Call by Reference: Yes

T_PVFRMI -

Data type: FRMPV_PVFRMI_TAB
Optional: Yes
Call by Reference: Yes

T_PVFRMH -

Data type: FRMPV_PVFRMH_TAB
Optional: Yes
Call by Reference: Yes

T_PNODTX -

Data type: PPET_PNODTX_TAB
Optional: Yes
Call by Reference: Yes

T_PNFRM -

Data type: FRMPV_PNFRM_TAB
Optional: Yes
Call by Reference: Yes

T_PALTID -

Data type: PPET_PALTID_TAB
Optional: Yes
Call by Reference: Yes

T_PALTTX -

Data type: PPET_PALTTX_TAB
Optional: Yes
Call by Reference: Yes

T_PAFRM -

Data type: FRMPV_PAFRM_TAB
Optional: Yes
Call by Reference: Yes

T_PRELID -

Data type: PPET_PRELID_TAB
Optional: Yes
Call by Reference: Yes

T_POSVID -

Data type: PPET_POSVID_TAB
Optional: Yes
Call by Reference: Yes

T_POSVTX - RMS-ATL: Table Type for Variant Texts for DB Layer

Data type: RMSATY_POSVTX_DB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for PVSDBFRM_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_pvfrmd  TYPE FRMPV_PVFRMD_TAB, "   
lv_t_pvfrms  TYPE FRMPV_PVFRMS_TAB, "   
lv_t_pvfrmm  TYPE FRMPV_PVFRMM_TAB, "   
lv_t_pvfrmi  TYPE FRMPV_PVFRMI_TAB, "   
lv_t_pvfrmh  TYPE FRMPV_PVFRMH_TAB, "   
lv_t_pnodtx  TYPE PPET_PNODTX_TAB, "   
lv_t_pnfrm  TYPE FRMPV_PNFRM_TAB, "   
lv_t_paltid  TYPE PPET_PALTID_TAB, "   
lv_t_palttx  TYPE PPET_PALTTX_TAB, "   
lv_t_pafrm  TYPE FRMPV_PAFRM_TAB, "   
lv_t_prelid  TYPE PPET_PRELID_TAB, "   
lv_t_posvid  TYPE PPET_POSVID_TAB, "   
lv_t_posvtx  TYPE RMSATY_POSVTX_DB. "   

  CALL FUNCTION 'PVSDBFRM_SAVE'  "RMS-FRM: Save PVS Tables for Application Object FRM
    EXPORTING
         IM_PPECNTL = lv_im_ppecntl
    CHANGING
         T_PNODID = lv_t_pnodid
         T_PVFRMD = lv_t_pvfrmd
         T_PVFRMS = lv_t_pvfrms
         T_PVFRMM = lv_t_pvfrmm
         T_PVFRMI = lv_t_pvfrmi
         T_PVFRMH = lv_t_pvfrmh
         T_PNODTX = lv_t_pnodtx
         T_PNFRM = lv_t_pnfrm
         T_PALTID = lv_t_paltid
         T_PALTTX = lv_t_palttx
         T_PAFRM = lv_t_pafrm
         T_PRELID = lv_t_prelid
         T_POSVID = lv_t_posvid
         T_POSVTX = lv_t_posvtx
. " PVSDBFRM_SAVE




ABAP code using 7.40 inline data declarations to call FM PVSDBFRM_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



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!