SAP Function Modules

comments icon Comments

UPF_PARAM_SAVE SAP Function module - Save planning functions on DB







UPF_PARAM_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 UPF_PARAM_SAVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UPFE
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM UPF_PARAM_SAVE - UPF PARAM SAVE 





CALL FUNCTION 'UPF_PARAM_SAVE' "Save planning functions on DB
* EXPORTING
*   i_no_transaction_data =     " char1         Single-Character Flag
  IMPORTING
    et_mesg =                   " upc_yt_mesg
    .  "  UPF_PARAM_SAVE

ABAP code example for Function Module UPF_PARAM_SAVE





The ABAP code below is a full code listing to execute function module UPF_PARAM_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:
ld_et_mesg    TYPE UPC_YT_MESG
.




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

CALL FUNCTION 'UPF_PARAM_SAVE'
* EXPORTING
*   i_no_transaction_data =      ld_i_no_transaction_data
  IMPORTING
    et_mesg =                    ld_et_mesg
    .  "  UPF_PARAM_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_et_mesg  TYPE UPC_YT_MESG ,
ld_i_no_transaction_data  TYPE CHAR1 .




ld_i_no_transaction_data = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name UPF_PARAM_SAVE or its description.


   
 

UPF_PARAM_SAVE - Save planning functions on DB
UPF_PARAM_READ - Planning functions: Read parameters
UPF_PARAM_OK_CODE - Parameter group OK-codes
UPF_PARAM_INIT - Start Edit Parametergroup
UPF_PARAM_INFO_SET - read buffered information about the planning functions
UPF_PARAM_INFO_GET - read buffered information about the planning functions