SAP UMC_DIMENSION_VALUES_GET Function Module for

Search SAP Function Modules

UMC_DIMENSION_VALUES_GET is a standard umc dimension values get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for umc dimension values get FM, simply by entering the name UMC_DIMENSION_VALUES_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: UMC_BW_METADATA
Program Name: SAPLUMC_BW_METADATA
Main Program: SAPLUMC_BW_METADATA
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMC_DIMENSION_VALUES_GET pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'UMC_DIMENSION_VALUES_GET'"
  EXPORTING
   I_DESTINATION =  "RFC Destination
   I_INFOCUBE =  "InfoCube (ODBO - identifier)
   I_QUERY =  "BW Report (ODBO Name)
   I_DIMENSION =  "Field Name Dimension (ODBO Identifier)
*  IT_RESTRICTION =  "Restrictions for CHAVAL Selection

 IMPORTING
   ET_DIMVALS =  "Characteristic Values: Identifier, Description

EXCEPTIONS
   ODBO_ERROR = 1    RFC_ERROR = 2    BWSERVER_NOT_EXIST = 3 

.

IMPORTING Parameters details for UMC_DIMENSION_VALUES_GET

I_DESTINATION - RFC Destination

Data type: UMC_Y_RFCDEST
Optional: No
Call by Reference: Yes

I_INFOCUBE - InfoCube (ODBO - identifier)

Data type: UMC_Y_TCUBE
Optional: No
Call by Reference: Yes

I_QUERY - BW Report (ODBO Name)

Data type: UMC_Y_TQUERY
Optional: No
Call by Reference: Yes

I_DIMENSION - Field Name Dimension (ODBO Identifier)

Data type: UMC_Y_TCHANM
Optional: No
Call by Reference: Yes

IT_RESTRICTION - Restrictions for CHAVAL Selection

Data type: UMC_YT_RSDRI_RANGES
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for UMC_DIMENSION_VALUES_GET

ET_DIMVALS - Characteristic Values: Identifier, Description

Data type: UMC_YT_DIMVALS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ODBO_ERROR - Error when calling up the ODBO - interface

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BWSERVER_NOT_EXIST - Target system is not a BW system

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UMC_DIMENSION_VALUES_GET Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM UMC_DIMENSION_VALUES_GET

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects