SAP UJO_CREATE_AXIS_DATA Function Module for BPC10: For asynchronous expanding memberset formula
UJO_CREATE_AXIS_DATA is a standard ujo create axis data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC10: For asynchronous expanding memberset formula 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 ujo create axis data FM, simply by entering the name UJO_CREATE_AXIS_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: UJO0
Program Name: SAPLUJO0
Main Program: SAPLUJO0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UJO_CREATE_AXIS_DATA 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 'UJO_CREATE_AXIS_DATA'"BPC10: For asynchronous expanding memberset formula.
EXPORTING
I_APPSET_ID = "SAP BusinessObjects - AppSet ID
I_APPL_ID = "SAP BusinessObjects - Application ID
I_KEYDATE = "Current Date of Application Server
* I_USER_ID = SY-UNAME "BPC: User ID
IT_DIM_DET = "detailed query axis
* IF_FILL_ACCTYPE = ABAP_FALSE "BPC: Generic indicator
I_ACC_DIM = "BPC: Dimension Name
IT_SLICER = "table of members
IMPORTING
ET_DIM_DET = "detailed query axis
EF_SUCCESS = "BPC: Generic indicator
ET_MESSAGE = "BPC: Messages
EHT_INC_LEQ_MEMBER = "BPC: dimension member hash table
IMPORTING Parameters details for UJO_CREATE_AXIS_DATA
I_APPSET_ID - SAP BusinessObjects - AppSet ID
Data type: UJ_APPSET_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_APPL_ID - SAP BusinessObjects - Application ID
Data type: UJ_APPL_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_KEYDATE - Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_USER_ID - BPC: User ID
Data type: UJ_USER_IDDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_DIM_DET - detailed query axis
Data type: UJO_T_QUERY_DIM_DETOptional: No
Call by Reference: No ( called with pass by value option)
IF_FILL_ACCTYPE - BPC: Generic indicator
Data type: UJ_FLGDefault: ABAP_FALSE
Optional: No
Call by Reference: No ( called with pass by value option)
I_ACC_DIM - BPC: Dimension Name
Data type: UJ_DIM_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
IT_SLICER - table of members
Data type: UJO_T_MEMBERSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UJO_CREATE_AXIS_DATA
ET_DIM_DET - detailed query axis
Data type: UJO_T_QUERY_DIM_DETOptional: No
Call by Reference: No ( called with pass by value option)
EF_SUCCESS - BPC: Generic indicator
Data type: UJ_FLGOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGE - BPC: Messages
Data type: UJ0_T_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
EHT_INC_LEQ_MEMBER - BPC: dimension member hash table
Data type: UJO_T_KV_ACC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UJO_CREATE_AXIS_DATA 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_et_dim_det | TYPE UJO_T_QUERY_DIM_DET, " | |||
| lv_i_appset_id | TYPE UJ_APPSET_ID, " | |||
| lv_i_appl_id | TYPE UJ_APPL_ID, " | |||
| lv_ef_success | TYPE UJ_FLG, " | |||
| lv_i_keydate | TYPE SY-DATUM, " | |||
| lv_et_message | TYPE UJ0_T_MESSAGE, " | |||
| lv_i_user_id | TYPE UJ_USER_ID, " SY-UNAME | |||
| lv_eht_inc_leq_member | TYPE UJO_T_KV_ACC_TYPE, " | |||
| lv_it_dim_det | TYPE UJO_T_QUERY_DIM_DET, " | |||
| lv_if_fill_acctype | TYPE UJ_FLG, " ABAP_FALSE | |||
| lv_i_acc_dim | TYPE UJ_DIM_NAME, " | |||
| lv_it_slicer | TYPE UJO_T_MEMBERS. " |
|   CALL FUNCTION 'UJO_CREATE_AXIS_DATA' "BPC10: For asynchronous expanding memberset formula |
| EXPORTING | ||
| I_APPSET_ID | = lv_i_appset_id | |
| I_APPL_ID | = lv_i_appl_id | |
| I_KEYDATE | = lv_i_keydate | |
| I_USER_ID | = lv_i_user_id | |
| IT_DIM_DET | = lv_it_dim_det | |
| IF_FILL_ACCTYPE | = lv_if_fill_acctype | |
| I_ACC_DIM | = lv_i_acc_dim | |
| IT_SLICER | = lv_it_slicer | |
| IMPORTING | ||
| ET_DIM_DET | = lv_et_dim_det | |
| EF_SUCCESS | = lv_ef_success | |
| ET_MESSAGE | = lv_et_message | |
| EHT_INC_LEQ_MEMBER | = lv_eht_inc_leq_member | |
| . " UJO_CREATE_AXIS_DATA | ||
ABAP code using 7.40 inline data declarations to call FM UJO_CREATE_AXIS_DATA
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 DATUM FROM SY INTO @DATA(ld_i_keydate). | ||||
| DATA(ld_i_user_id) | = SY-UNAME. | |||
| DATA(ld_if_fill_acctype) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects