SAP UJN_API_IPAK_CREATE Function Module for BPC: Create InfoPackage
UJN_API_IPAK_CREATE is a standard ujn api ipak create 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 InfoPackage 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 ipak create FM, simply by entering the name UJN_API_IPAK_CREATE 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_IPAK_CREATE 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_IPAK_CREATE'"BPC: Create InfoPackage.
EXPORTING
I_DETAILS = "Scheduler: General Data
I_SCHEDULING_PARAMS = "Scheduler: Scheduling Selections
I_DESTINATIONS = "Scheduler: Data Target
* I_FILE_PARAMS = "Scheduler: File Selections
* I_HIE_PARAMS = "Scheduler: Hierarchy Transfer Structure
* I_USE_SERVICE_USER = ABAP_TRUE "BPC: Generic indicator
IMPORTING
E_INFOPACKAGE = "Logical InfoPackage variant (ID)
TABLES
* SELECTIONS = "Scheduler: Selection Structure
* INFOCUBES = "Scheduler: InfoCube Table
* THIRD_PARTY_PARAMS = "Scheduler: TCPIP External Data Selections
* RETURN = "Return Parameter
IMPORTING Parameters details for UJN_API_IPAK_CREATE
I_DETAILS - Scheduler: General Data
Data type: BAPI6109Optional: No
Call by Reference: No ( called with pass by value option)
I_SCHEDULING_PARAMS - Scheduler: Scheduling Selections
Data type: BAPI6109BTCHOptional: No
Call by Reference: No ( called with pass by value option)
I_DESTINATIONS - Scheduler: Data Target
Data type: BAPI6109DESTOptional: No
Call by Reference: No ( called with pass by value option)
I_FILE_PARAMS - Scheduler: File Selections
Data type: BAPI6109FILEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_HIE_PARAMS - Scheduler: Hierarchy Transfer Structure
Data type: BAPI6109HIEOptional: Yes
Call by Reference: No ( called with pass by value option)
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)
EXPORTING Parameters details for UJN_API_IPAK_CREATE
E_INFOPACKAGE - Logical InfoPackage variant (ID)
Data type: BAPI6109-INFOPACKAGEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for UJN_API_IPAK_CREATE
SELECTIONS - Scheduler: Selection Structure
Data type: BAPI6109SELOptional: Yes
Call by Reference: Yes
INFOCUBES - Scheduler: InfoCube Table
Data type: BAPI6109ICOptional: Yes
Call by Reference: Yes
THIRD_PARTY_PARAMS - Scheduler: TCPIP External Data Selections
Data type: BAPI6109TCPOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for UJN_API_IPAK_CREATE 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_details | TYPE BAPI6109, " | |||
| lt_selections | TYPE STANDARD TABLE OF BAPI6109SEL, " | |||
| lv_e_infopackage | TYPE BAPI6109-INFOPACKAGE, " | |||
| lt_infocubes | TYPE STANDARD TABLE OF BAPI6109IC, " | |||
| lv_i_scheduling_params | TYPE BAPI6109BTCH, " | |||
| lv_i_destinations | TYPE BAPI6109DEST, " | |||
| lt_third_party_params | TYPE STANDARD TABLE OF BAPI6109TCP, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_i_file_params | TYPE BAPI6109FILE, " | |||
| lv_i_hie_params | TYPE BAPI6109HIE, " | |||
| lv_i_use_service_user | TYPE UJ_FLG. " ABAP_TRUE |
|   CALL FUNCTION 'UJN_API_IPAK_CREATE' "BPC: Create InfoPackage |
| EXPORTING | ||
| I_DETAILS | = lv_i_details | |
| I_SCHEDULING_PARAMS | = lv_i_scheduling_params | |
| I_DESTINATIONS | = lv_i_destinations | |
| I_FILE_PARAMS | = lv_i_file_params | |
| I_HIE_PARAMS | = lv_i_hie_params | |
| I_USE_SERVICE_USER | = lv_i_use_service_user | |
| IMPORTING | ||
| E_INFOPACKAGE | = lv_e_infopackage | |
| TABLES | ||
| SELECTIONS | = lt_selections | |
| INFOCUBES | = lt_infocubes | |
| THIRD_PARTY_PARAMS | = lt_third_party_params | |
| RETURN | = lt_return | |
| . " UJN_API_IPAK_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM UJN_API_IPAK_CREATE
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 INFOPACKAGE FROM BAPI6109 INTO @DATA(ld_e_infopackage). | ||||
| DATA(ld_i_use_service_user) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects