SAP UMC_DIM_VALUE_F4_2 Function Module for

Search SAP Function Modules

UMC_DIM_VALUE_F4_2 is a standard umc dim value f4 2 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 dim value f4 2 FM, simply by entering the name UMC_DIM_VALUE_F4_2 into the relevant SAP transaction such as SE37 or SE38.

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

Function UMC_DIM_VALUE_F4_2 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_DIM_VALUE_F4_2'"
  EXPORTING
   I_DESTINATION =  "RFC Destination
   I_INFOCUBE =  "InfoCube (ODBO - identifier)
   I_QUERY =  "BW Report (ODBO Name)
   I_DIMENSION =  "Field Name Dimension (ODBO Identifier)
*  I_DISPLAY = ' ' "DD: truth value
*  I_BWVAR_SINGLE = ' ' "
*  IT_QUERY =  "BW Query

 IMPORTING
   ES_DIMVALS =  "Characteristic Values: Identifier, Description

CHANGING
   CT_DIMCMP_VALS =  "Compound Dimensions Member Values

EXCEPTIONS
   BW_ERROR = 1 

.

IMPORTING Parameters details for UMC_DIM_VALUE_F4_2

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

I_DISPLAY - DD: truth value

Data type: DDBOOL_D
Default: ' '
Optional: Yes
Call by Reference: Yes

I_BWVAR_SINGLE -

Data type: AS4FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

IT_QUERY - BW Query

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

EXPORTING Parameters details for UMC_DIM_VALUE_F4_2

ES_DIMVALS - Characteristic Values: Identifier, Description

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

CHANGING Parameters details for UMC_DIM_VALUE_F4_2

CT_DIMCMP_VALS - Compound Dimensions Member Values

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

EXCEPTIONS details

BW_ERROR -

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

Copy and paste ABAP code example for UMC_DIM_VALUE_F4_2 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_DIM_VALUE_F4_2

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