PVSHI_SAVE SAP Function module - iPPE: Save Data

PVSHI_SAVE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PVSHI_SAVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PPEHI_ENG
Released Date: 27.10.2003
Processing type: Remote-Enabled

Pattern for FM PVSHI_SAVE - PVSHI SAVE

CALL FUNCTION 'PVSHI_SAVE' "iPPE: Save Data
* EXPORTING
*   flg_commit = 'X'            " ppe_message_option  Message Handling
*   i_mode_all = 'X'            " ppe_mode_all  Ignore Errors
*   i_msg_handling = 'A'        " ppe_message_option  Message Handling
*   i_unlock = '1'              " ppe_unlock_flg  Unlock
*   save_protocol = 'X'         " ppe_save_protocol  Save Application Log File
*   i_no_changedocs = SPACE     " ppe_no_changedocs  Do Not Write Change Documents for iPPE Objects
* TABLES
*   return =                    " bapiret2      Return Parameters
    .  "  PVSHI_SAVE

ABAP code example for Function Module PVSHI_SAVE

The ABAP code below is a full code listing to execute function module PVSHI_SAVE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.


DATA(ld_flg_commit) = 'Check type of data required'.

DATA(ld_i_mode_all) = 'Check type of data required'.

DATA(ld_i_msg_handling) = 'Check type of data required'.

DATA(ld_i_unlock) = 'Check type of data required'.

DATA(ld_save_protocol) = 'Check type of data required'.

DATA(ld_i_no_changedocs) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'PVSHI_SAVE'
* EXPORTING
*   flg_commit =                 ld_flg_commit
*   i_mode_all =                 ld_i_mode_all
*   i_msg_handling =             ld_i_msg_handling
*   i_unlock =                   ld_i_unlock
*   save_protocol =              ld_save_protocol
*   i_no_changedocs =            ld_i_no_changedocs
* TABLES
*   return =                     it_return
    .  "  PVSHI_SAVE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_flg_commit
 
 TYPE PPE_MESSAGE_OPTION ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_i_mode_all
 
 TYPE PPE_MODE_ALL ,
ld_i_msg_handling
 
 TYPE PPE_MESSAGE_OPTION ,
ld_i_unlock
 
 TYPE PPE_UNLOCK_FLG ,
ld_save_protocol
 
 TYPE PPE_SAVE_PROTOCOL ,
ld_i_no_changedocs
 
 TYPE PPE_NO_CHANGEDOCS .


ld_flg_commit = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_i_mode_all = 'Check type of data required'.
ld_i_msg_handling = 'Check type of data required'.
ld_i_unlock = 'Check type of data required'.
ld_save_protocol = 'Check type of data required'.
ld_i_no_changedocs = 'Check type of data required'.

SAP Documentation for FM PVSHI_SAVE