UPC_PACKAGE_GET_2 SAP Function module - read Planning package

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

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

Pattern for FM UPC_PACKAGE_GET_2 - UPC PACKAGE GET 2

CALL FUNCTION 'UPC_PACKAGE_GET_2' "read Planning package
  EXPORTING
    i_area =                    " upc_y_area    Planning Area
    i_plevel =                  " upc_y_plevel  Planning Level
    i_package =                 " upc_y_package  Planning Package
*   i_enqmode = ' '             " enqmode       Lock Mode
  IMPORTING
    eto_cha =                   " upc_yto_cha   Characteristics
    eto_kyf =                   " upc_yto_kyf   Key Figures
    eto_chasel =                " upc_yto_chasel
  EXCEPTIONS
    NO_EXISTENCE = 1            "               Does Not Exist
    LOCKED = 2                  "               Locked
    NO_CONSISTENCE = 3          "               Inconsistent
    PLEVEL_ERROR = 4            "               Errors in the planning level
    .  "  UPC_PACKAGE_GET_2

ABAP code example for Function Module UPC_PACKAGE_GET_2

The ABAP code below is a full code listing to execute function module UPC_PACKAGE_GET_2 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_eto_cha  
 
 TYPE UPC_YTO_CHA
,
ld_eto_kyf  
 
 TYPE UPC_YTO_KYF
,
ld_eto_chasel  
 
 TYPE UPC_YTO_CHASEL
.


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

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

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

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

CALL FUNCTION 'UPC_PACKAGE_GET_2'
  EXPORTING
    i_area =                     ld_i_area
    i_plevel =                   ld_i_plevel
    i_package =                  ld_i_package
*   i_enqmode =                  ld_i_enqmode
  IMPORTING
    eto_cha =                    ld_eto_cha
    eto_kyf =                    ld_eto_kyf
    eto_chasel =                 ld_eto_chasel
  EXCEPTIONS
    NO_EXISTENCE =               1
    LOCKED =                     2
    NO_CONSISTENCE =             3
    PLEVEL_ERROR =               4
    .  "  UPC_PACKAGE_GET_2

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
ELSEIF SY-SUBRC EQ 4. "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_eto_cha
 
 TYPE UPC_YTO_CHA ,
ld_i_area
 
 TYPE UPC_Y_AREA ,
ld_eto_kyf
 
 TYPE UPC_YTO_KYF ,
ld_i_plevel
 
 TYPE UPC_Y_PLEVEL ,
ld_eto_chasel
 
 TYPE UPC_YTO_CHASEL ,
ld_i_package
 
 TYPE UPC_Y_PACKAGE ,
ld_i_enqmode
 
 TYPE ENQMODE .


ld_i_area = 'Check type of data required'.
ld_i_plevel = 'Check type of data required'.
ld_i_package = 'Check type of data required'.
ld_i_enqmode = 'Check type of data required'.