SAP RSAPO_MEMBERS_CUBE_GET Function Module for F4 for InfoObject restricted on InfoCube









RSAPO_MEMBERS_CUBE_GET is a standard rsapo members cube get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for F4 for InfoObject restricted on InfoCube 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 rsapo members cube get FM, simply by entering the name RSAPO_MEMBERS_CUBE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSAPO
Program Name: SAPLRSAPO
Main Program: SAPLRSAPO
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RSAPO_MEMBERS_CUBE_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 'RSAPO_MEMBERS_CUBE_GET'"F4 for InfoObject restricted on InfoCube
EXPORTING
I_IOBJNM = "Name of Characteristic
I_INFOCUBE = "Name of the InfoCube
* I_WITH_AUTH = RS_C_TRUE "With Authorization Check

TABLES
E_T_MEMBER_LIST = "List of Characteristic Values

EXCEPTIONS
INFOCUBE_NOT_FOUND = 1 ILLEGAL_INPUT = 2 INFOOBJECT_NOT_FOUND = 3 SYNTAX_ERROR_IN_GENERATION = 4 DIMENSION_NAME_ERROR = 5 IOBJ_NAME_ERROR = 6 PREFIX_INVALID = 7 INHERITED_ERROR = 8
.



IMPORTING Parameters details for RSAPO_MEMBERS_CUBE_GET

I_IOBJNM - Name of Characteristic

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

I_INFOCUBE - Name of the InfoCube

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

I_WITH_AUTH - With Authorization Check

Data type: RS_BOOL
Default: RS_C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RSAPO_MEMBERS_CUBE_GET

E_T_MEMBER_LIST - List of Characteristic Values

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

EXCEPTIONS details

INFOCUBE_NOT_FOUND - InfoCube not found

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

ILLEGAL_INPUT - Invalid Entry

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

INFOOBJECT_NOT_FOUND -

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

SYNTAX_ERROR_IN_GENERATION -

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

DIMENSION_NAME_ERROR -

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

IOBJ_NAME_ERROR -

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

PREFIX_INVALID -

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

INHERITED_ERROR -

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

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

DATA:
lv_i_iobjnm  TYPE RSAPO_INT_CHARS-IOBJNM, "   
lt_e_t_member_list  TYPE STANDARD TABLE OF RSAPO_INT_MEMBERS, "   
lv_infocube_not_found  TYPE RSAPO_INT_MEMBERS, "   
lv_i_infocube  TYPE RSAPO_INT_CUBES-INFOCUBE, "   
lv_illegal_input  TYPE RSAPO_INT_CUBES, "   
lv_i_with_auth  TYPE RS_BOOL, "   RS_C_TRUE
lv_infoobject_not_found  TYPE RS_BOOL, "   
lv_syntax_error_in_generation  TYPE RS_BOOL, "   
lv_dimension_name_error  TYPE RS_BOOL, "   
lv_iobj_name_error  TYPE RS_BOOL, "   
lv_prefix_invalid  TYPE RS_BOOL, "   
lv_inherited_error  TYPE RS_BOOL. "   

  CALL FUNCTION 'RSAPO_MEMBERS_CUBE_GET'  "F4 for InfoObject restricted on InfoCube
    EXPORTING
         I_IOBJNM = lv_i_iobjnm
         I_INFOCUBE = lv_i_infocube
         I_WITH_AUTH = lv_i_with_auth
    TABLES
         E_T_MEMBER_LIST = lt_e_t_member_list
    EXCEPTIONS
        INFOCUBE_NOT_FOUND = 1
        ILLEGAL_INPUT = 2
        INFOOBJECT_NOT_FOUND = 3
        SYNTAX_ERROR_IN_GENERATION = 4
        DIMENSION_NAME_ERROR = 5
        IOBJ_NAME_ERROR = 6
        PREFIX_INVALID = 7
        INHERITED_ERROR = 8
. " RSAPO_MEMBERS_CUBE_GET




ABAP code using 7.40 inline data declarations to call FM RSAPO_MEMBERS_CUBE_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.

"SELECT single IOBJNM FROM RSAPO_INT_CHARS INTO @DATA(ld_i_iobjnm).
 
 
 
"SELECT single INFOCUBE FROM RSAPO_INT_CUBES INTO @DATA(ld_i_infocube).
 
 
DATA(ld_i_with_auth) = RS_C_TRUE.
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!