SAP G_REPORT_GET_DIMENSION_VALUE Function Module for Determine individual value for a dimension

Search SAP Function Modules

G_REPORT_GET_DIMENSION_VALUE is a standard g report get dimension value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine individual value for a dimension processing and below is the pattern details for this FM, 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 g report get dimension value FM, simply by entering the name G_REPORT_GET_DIMENSION_VALUE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRWC
Program Name: SAPLGRWC
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_REPORT_GET_DIMENSION_VALUE 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 'G_REPORT_GET_DIMENSION_VALUE'"Determine individual value for a dimension
  EXPORTING
   DIM_FIELD =  "Field name of the desired dimensio
   VAL_NUMBER =  "Consecutive number of the transfer

 IMPORTING
   VAL_COUNT =  "Number of individual values for th
   VAL_FROM =  "Individual value (From-value).
   VAL_TO =  "Individual value (To-value).

EXCEPTIONS
   RC_INTERFACE_NOT_INITIALIZED = 1    RC_INVALID_DIM_FIELD = 2    RC_INVALID_VAL_NUMBER = 3 

.

IMPORTING Parameters details for G_REPORT_GET_DIMENSION_VALUE

DIM_FIELD - Field name of the desired dimensio

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

VAL_NUMBER - Consecutive number of the transfer

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

EXPORTING Parameters details for G_REPORT_GET_DIMENSION_VALUE

VAL_COUNT - Number of individual values for th

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

VAL_FROM - Individual value (From-value).

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

VAL_TO - Individual value (To-value).

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

EXCEPTIONS details

RC_INTERFACE_NOT_INITIALIZED - Interface not initialized.

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

RC_INVALID_DIM_FIELD - Dimension name invalid.

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

RC_INVALID_VAL_NUMBER - Number of individual value invalid

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

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

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