SAP Function Modules

UPE_DOC_RESERVE SAP Function module - Planning framework SD-INIT







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

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


Pattern for FM UPE_DOC_RESERVE - UPE DOC RESERVE





CALL FUNCTION 'UPE_DOC_RESERVE' "Planning framework SD-INIT
  EXPORTING
    i_fcode =                   " sy-ucomm
    i_area =                    " upc_y_area
    i_plevel =                  " upc_y_plevel
    i_method =                  " upc_y_method
    i_param =                   " upc_y_param
    i_package =                 " upc_y_package
  IMPORTING
    e_repid =                   " sy-repid
    e_dynnr =                   " sy-dynnr
    et_mesg =                   " upc_yt_mesg
  EXCEPTIONS
    ERROR_INIT = 1              "
    .  "  UPE_DOC_RESERVE

ABAP code example for Function Module UPE_DOC_RESERVE





The ABAP code below is a full code listing to execute function module UPE_DOC_RESERVE 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_e_repid  TYPE SY-REPID ,
ld_e_dynnr  TYPE SY-DYNNR ,
ld_et_mesg  TYPE UPC_YT_MESG .

DATA(ld_i_fcode) = 'some text here'.
DATA(ld_i_area) = 'some text here'.
DATA(ld_i_plevel) = 'some text here'.
DATA(ld_i_method) = 'some text here'.
DATA(ld_i_param) = 'some text here'.
DATA(ld_i_package) = 'some text here'. . CALL FUNCTION 'UPE_DOC_RESERVE' EXPORTING i_fcode = ld_i_fcode i_area = ld_i_area i_plevel = ld_i_plevel i_method = ld_i_method i_param = ld_i_param i_package = ld_i_package IMPORTING e_repid = ld_e_repid e_dynnr = ld_e_dynnr et_mesg = ld_et_mesg EXCEPTIONS ERROR_INIT = 1 . " UPE_DOC_RESERVE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_e_repid  TYPE SY-REPID ,
ld_i_fcode  TYPE SY-UCOMM ,
ld_e_dynnr  TYPE SY-DYNNR ,
ld_i_area  TYPE UPC_Y_AREA ,
ld_et_mesg  TYPE UPC_YT_MESG ,
ld_i_plevel  TYPE UPC_Y_PLEVEL ,
ld_i_method  TYPE UPC_Y_METHOD ,
ld_i_param  TYPE UPC_Y_PARAM ,
ld_i_package  TYPE UPC_Y_PACKAGE .

ld_i_fcode = 'some text here'.
ld_i_area = 'some text here'.
ld_i_plevel = 'some text here'.
ld_i_method = 'some text here'.
ld_i_param = 'some text here'.
ld_i_package = 'some text here'.

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 UPE_DOC_RESERVE or its description.