SAP UMC_BW_HINODE_F4 Function Module for

Search SAP Function Modules

UMC_BW_HINODE_F4 is a standard umc bw hinode f4 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 bw hinode f4 FM, simply by entering the name UMC_BW_HINODE_F4 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:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMC_BW_HINODE_F4 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_BW_HINODE_F4'"
  EXPORTING
   I_RFCDEST =  "Logical Destination (Specified when Calling Function)
   I_INFOCUBE =  "InfoCube (BW)
   I_QUERY =  "BW Report (ODBO Name)
   I_DIMENSION =  "Technical Name of Characteristic (BW)
*  I_HINAME =  "Hierarchy Name (BW)
*  I_CUBE_DEPENDENT = ' ' "Flag (X or Blank)

 IMPORTING
   ES_HINODE =  "Hierarchy Nodes: Identifier, Description

TABLES
   CT_DEP =  "Values of Compound Characteristics

EXCEPTIONS
   CONVERSION_ERROR = 1 

.

IMPORTING Parameters details for UMC_BW_HINODE_F4

I_RFCDEST - Logical Destination (Specified when Calling Function)

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

I_INFOCUBE - InfoCube (BW)

Data type: UMC_Y_ICUBE
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 - Technical Name of Characteristic (BW)

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

I_HINAME - Hierarchy Name (BW)

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

I_CUBE_DEPENDENT - Flag (X or Blank)

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

EXPORTING Parameters details for UMC_BW_HINODE_F4

ES_HINODE - Hierarchy Nodes: Identifier, Description

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

TABLES Parameters details for UMC_BW_HINODE_F4

CT_DEP - Values of Compound Characteristics

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

EXCEPTIONS details

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UMC_BW_HINODE_F4 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_BW_HINODE_F4

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