UPC_FIXED_METHODS_GET SAP Function module - Get

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

Associated Function Group: UPC_FIXED_METHODS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM UPC_FIXED_METHODS_GET - UPC FIXED METHODS GET

CALL FUNCTION 'UPC_FIXED_METHODS_GET' "Get
  EXPORTING
    i_area =                    " upc_y_area    Planning Area
    i_plevel =                  " upc_y_plevel  Planning Level
    i_method =                  " upc_y_method  Planning Function
*   i_enqmode =                 " enqmode       Lock Mode
*   i_langu = SY-LANGU          " sy-langu      Language
  IMPORTING
    e_methodt =                 " upc_y_methodtxt  Description planning function
  EXCEPTIONS
    NO_EXISTENCE = 1            "               Method does not exist
    LOCKED = 2                  "               Method is locked
    PLEVEL_ERROR = 3            "               Errors in the planning level
    .  "  UPC_FIXED_METHODS_GET

ABAP code example for Function Module UPC_FIXED_METHODS_GET

The ABAP code below is a full code listing to execute function module UPC_FIXED_METHODS_GET 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_methodt  
 
 TYPE UPC_Y_METHODTXT
.


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

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

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

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

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

CALL FUNCTION 'UPC_FIXED_METHODS_GET'
  EXPORTING
    i_area =                     ld_i_area
    i_plevel =                   ld_i_plevel
    i_method =                   ld_i_method
*   i_enqmode =                  ld_i_enqmode
*   i_langu =                    ld_i_langu
  IMPORTING
    e_methodt =                  ld_e_methodt
  EXCEPTIONS
    NO_EXISTENCE =               1
    LOCKED =                     2
    PLEVEL_ERROR =               3
    .  "  UPC_FIXED_METHODS_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_methodt
 
 TYPE UPC_Y_METHODTXT ,
ld_i_area
 
 TYPE UPC_Y_AREA ,
ld_i_plevel
 
 TYPE UPC_Y_PLEVEL ,
ld_i_method
 
 TYPE UPC_Y_METHOD ,
ld_i_enqmode
 
 TYPE ENQMODE ,
ld_i_langu
 
 TYPE SY-LANGU .


ld_i_area = 'Check type of data required'.
ld_i_plevel = 'Check type of data required'.
ld_i_method = 'Check type of data required'.
ld_i_enqmode = 'Check type of data required'.
ld_i_langu = 'Check type of data required'.