UMC_DIMENSION_HY_GET SAP Function module

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

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

Pattern for FM UMC_DIMENSION_HY_GET - UMC DIMENSION HY GET

CALL FUNCTION 'UMC_DIMENSION_HY_GET' "
  EXPORTING
    i_destination =             " umc_y_rfcdest  RFC Destination
    i_infocube =                " umc_y_tcube   InfoCube (ODBO - identifier)
*   i_query =                   " umc_y_tquery  BW Report (ODBO Name)
    i_dimension =               " umc_y_tchanm  Field Name Dimension (ODBO Identifier)
  IMPORTING
    et_hys =                    " umc_yt_hys    Hierarchies: Identifier, Description
  EXCEPTIONS
    ODBO_ERROR = 1              "               Error when calling up the ODBO - interface
    RFC_ERROR = 2               "
    BWSERVER_NOT_EXIST = 3      "               Target system is not a BW system
    .  "  UMC_DIMENSION_HY_GET

ABAP code example for Function Module UMC_DIMENSION_HY_GET

The ABAP code below is a full code listing to execute function module UMC_DIMENSION_HY_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_et_hys  
 
 TYPE UMC_YT_HYS
.


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

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

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

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

CALL FUNCTION 'UMC_DIMENSION_HY_GET'
  EXPORTING
    i_destination =              ld_i_destination
    i_infocube =                 ld_i_infocube
*   i_query =                    ld_i_query
    i_dimension =                ld_i_dimension
  IMPORTING
    et_hys =                     ld_et_hys
  EXCEPTIONS
    ODBO_ERROR =                 1
    RFC_ERROR =                  2
    BWSERVER_NOT_EXIST =         3
    .  "  UMC_DIMENSION_HY_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_et_hys
 
 TYPE UMC_YT_HYS ,
ld_i_destination
 
 TYPE UMC_Y_RFCDEST ,
ld_i_infocube
 
 TYPE UMC_Y_TCUBE ,
ld_i_query
 
 TYPE UMC_Y_TQUERY ,
ld_i_dimension
 
 TYPE UMC_Y_TCHANM .


ld_i_destination = 'Check type of data required'.
ld_i_infocube = 'Check type of data required'.
ld_i_query = 'Check type of data required'.
ld_i_dimension = 'Check type of data required'.