SAP UJN_API_CREATE_ADSO Function Module for BPC: Create ADSO
UJN_API_CREATE_ADSO is a standard ujn api create adso SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC: Create ADSO 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 ujn api create adso FM, simply by entering the name UJN_API_CREATE_ADSO into the relevant SAP transaction such as SE37 or SE38.
Function Group: UJN_API_BI_IOBJ
Program Name: SAPLUJN_API_BI_IOBJ
Main Program: SAPLUJN_API_BI_IOBJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UJN_API_CREATE_ADSO 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 'UJN_API_CREATE_ADSO'"BPC: Create ADSO.
EXPORTING
* I_USE_SERVICE_USER = ABAP_TRUE "BPC: Generic indicator
I_ADSONM = "Datastore Object: Name
* I_TEXT = "Datastore Objects: Description
* I_INFOAREA = "InfoArea
I_S_ADSOFLAGS = "Datastore Object Flags
I_T_OBJECT = "ADSO Object Table
I_T_DIMENSION = "ADSO Dimension Table
* I_T_KEY = "ADSO Key Table
* I_WITH_CTO = ABAP_FALSE "
IMPORTING
E_T_MSG = "BW: Table with Messages (Application Log)
IMPORTING Parameters details for UJN_API_CREATE_ADSO
I_USE_SERVICE_USER - BPC: Generic indicator
Data type: UJ_FLGDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ADSONM - Datastore Object: Name
Data type: RSOADSONMOptional: No
Call by Reference: No ( called with pass by value option)
I_TEXT - Datastore Objects: Description
Data type: RSOADSODESCROptional: Yes
Call by Reference: No ( called with pass by value option)
I_INFOAREA - InfoArea
Data type: RSINFOAREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_ADSOFLAGS - Datastore Object Flags
Data type: UJN_TN_S_ADSOFLAGSOptional: No
Call by Reference: No ( called with pass by value option)
I_T_OBJECT - ADSO Object Table
Data type: UJN_TN_T_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
I_T_DIMENSION - ADSO Dimension Table
Data type: UJN_TN_T_DIMENSIONOptional: No
Call by Reference: No ( called with pass by value option)
I_T_KEY - ADSO Key Table
Data type: UJN_TN_T_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WITH_CTO -
Data type: UJ_FLGDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UJN_API_CREATE_ADSO
E_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UJN_API_CREATE_ADSO 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_e_t_msg | TYPE RS_T_MSG, " | |||
| lv_i_use_service_user | TYPE UJ_FLG, " ABAP_TRUE | |||
| lv_i_adsonm | TYPE RSOADSONM, " | |||
| lv_i_text | TYPE RSOADSODESCR, " | |||
| lv_i_infoarea | TYPE RSINFOAREA, " | |||
| lv_i_s_adsoflags | TYPE UJN_TN_S_ADSOFLAGS, " | |||
| lv_i_t_object | TYPE UJN_TN_T_OBJECT, " | |||
| lv_i_t_dimension | TYPE UJN_TN_T_DIMENSION, " | |||
| lv_i_t_key | TYPE UJN_TN_T_KEY, " | |||
| lv_i_with_cto | TYPE UJ_FLG. " ABAP_FALSE |
|   CALL FUNCTION 'UJN_API_CREATE_ADSO' "BPC: Create ADSO |
| EXPORTING | ||
| I_USE_SERVICE_USER | = lv_i_use_service_user | |
| I_ADSONM | = lv_i_adsonm | |
| I_TEXT | = lv_i_text | |
| I_INFOAREA | = lv_i_infoarea | |
| I_S_ADSOFLAGS | = lv_i_s_adsoflags | |
| I_T_OBJECT | = lv_i_t_object | |
| I_T_DIMENSION | = lv_i_t_dimension | |
| I_T_KEY | = lv_i_t_key | |
| I_WITH_CTO | = lv_i_with_cto | |
| IMPORTING | ||
| E_T_MSG | = lv_e_t_msg | |
| . " UJN_API_CREATE_ADSO | ||
ABAP code using 7.40 inline data declarations to call FM UJN_API_CREATE_ADSO
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.| DATA(ld_i_use_service_user) | = ABAP_TRUE. | |||
| DATA(ld_i_with_cto) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects