Functionality
This method creates a new InfoPackage.
The exporting parameter INFOPACKAGE delivers the technical name of theInfoPackage if it can be created.
The table RETURN contains error messages if there were errors. If thisis the case, the InfoPackage is not created.
The importing parameters
DETAILS
SCHEDULING_PARAMS
DESTINATIONS
and importing parameters
FILE_PARAMS
HIE_PARAMS
and the tables
SELECTIONS
INFOCUBES
THIRD_PARTY_PARAMS
must completely, or at least partly, be filled (depending on type ofInfoPackage).

Description
Technical name for an InfoPackage.

Description
Importing Parameter SCHEDULING_PARAMS: Data Target: Fields andMeaning:

• ONLYENTRANCE:

Only load data in the entry (PSA or IDoc), no
further processing.

• ONLYCUBETAB:

Only load data in the data target concerned without PSA..
Flags have no effect on data transfer using IDoc.

• PARALLEL:

Update data in PSA and the data target in parallel.
Flags have no effect on data transfer using IDoc.

• CUBEAFTERODS:

Update data automatically into the data target, when all data is
availalbe in PSA. In this way, a batch process is started up.
Flags only have an effect when you set the flag ONLYENTRANCE = 'X' andthe flag ONLYCUBETAB is initial.
Flags have no effect on data transfer using IDoc.

Description
Importing Parameter DETAIL: Fields and meaning:


• INFOPACKAGE:

Char 30 Field: Contains the technical name of the InfoPackage(ZPAK_49FEGSER95... or 0PAK_KI988Jj8...). It is empty when you create anew InfoPackage.

• INFOSOURCE:

Char 30 Field: Contains the technical name of the BW InfoSource onwhich the DataSource is mapped.

• INFOSOURCETYPE:

Char 1 Field: Contains the technical type of InfoSource. There are 2technical types: 'I' for InfoSources and 'O' for ObjectSources.
InfoSources are transaction data sources (DataSourcetype 'D') andObjectSources are master data, text or hierarchy sources(DataSourcetype 'M', 'T' or 'H').

• LOGSYS:

Char 10 Field: Contains the technical name of the source system.

• DATASOURCE:

Char 30-Field: Contains the technical name of the DataSource that ismapped on the BW InfoSource.

• DATASOURCETYPE:

Char 1 Field: Contains the technical type of DataSource. There are 4technical types: 'D' fo transaction data, 'M' for master dataattributes, 'T' for texts and 'H' for hierarchies.

• HIERACT:

Numc 1 Field: Activates hierarchies after loading. '0' if the hierarchyis not to be activated after loading and '1' if it is to be activated.

• CHAVL_CHECK:

Char 1 Field: Indicator of whether the data has to be checked forconsistency after loading ('X').

• UPDATEMASTERDATA:

Char 1 Field: Indicator of whether the system only loads data, ifmaster data exists for the data. If UPDATEMASTERDATA is 'initial', notransaction data is updated in InfoCubes, for which all master data isnot yet loaded or, no master data is loaded, if all master data is notyet loaded for all attributes.

• TEXT:

Char 60 Field: Name of InfoPackages in logon language.

• LOAD_STATUS:

Char 1 Field: Shows the sm37-Status of an InfoPackage that has beenscheduled or is already running:
'S' : Load job scheduled.
'R' : Load job already running.
'F' : Load job ended.
'A' : Load job cancelled.
everything else: interim status that only lasts for a short time and ifit appears for a long time, indicates an error in Basis backgroundprocessing.

• UPDMODE_READ:

Char 2 Field: InfoPackage processing mode: The following specificationsexist:
'F' : Full Update.
'D' : Delta Update.
'R' : Repeat Update = repeat request of last delta.
'C' : Initialization of delta procedure.
'I' : Construct intial count.
The field UPDMODE_READ is filled with the method BAPI_IPAK_GETDETAILwhen reading an InfoPackage, but when creating an InfoPackage, however,it is not interpreted with the method BAPI_IPAK_CREATE, or whenchanging it, it is not interpreted with the method BAPI_IPAK_CHANGE.
At the moment, you can only create InfoPackages with the processingmode 'F' and this is programmed permanently in the BAPIs.
You have to create InfoPackages with other processing modes using AWB.

Description
Importing Parameter FILE_PARAMS: File Selections: Fields and meaning:


• LOCATION:

Type of external system:
'0' : External data from application server
'1' : External data from client workstation

• FILENAME:

Char 128 Field: Name of file to be loaded.

• FILETYPE:

Type of external file:
'1' : File is Ascii file with CR as separator.
'2' : File is type Excel CSV

• FILESEP:

Separator for Excel format.
In Europe default = ';', in USA default = ','.

• ESC:

Escape character for Excel file
Default = '"'.

• CHAR1000:

Thousandth separator.

• DECICHAR:

Character for the decimal point.

• CURRCONV:

Currency conversion for external system

Description
Importing parameter HIE_PARAMS: File selections: Fields and meanings:


• HIENM:

30-character field: Name of the hierarchy you want to load.

• HIEVERS:

3-character field: Version of the hierarchy you want to load.

• HIEDATETO:

Date field: To_date of the hierarchy you want to load.

• HIEDATEFROM:

Date field: From_date of the hierarchy you want to load.

• HIECLASS:

4-character field: Hierarchy class of the hierarchy you want to load.

• NEW_HIENAME_ON:

Flag: If = 'X', then the loaded hierarchy is not saved under the namein the field HIENM in BW, but under the name in the field NEW_HIENM.

• NEW_HIENM:

30-character field: Name under which you want to save the loadedhierarchy.

Description
Importing parameter SCHEDULING_PARAMS: Scheduling selections: Fieldsand meaning:


• STARTDTTYP:

1-character field: Indicates type of start date:
'I' : Immediate start.
SDLSTRTDT, SDLSTRTTM, EVENTID, EVENTPARM PERIODIC, CANCELPERIOD areempty.
'D' : Start on a particular date/at a particular time.
Field SDLSTRTDT contains the date, and field SDLSTRTTM contains thetime.
EVENTID, EVENTPARM, PERIODIC, CANCELPERIOD are empty.
'E' : Start after sm62 event:
Field EVENTID contains the event, and field EVENTPARM contains theevent parameter.
SDLSTRTDT, SDLSTRTTM are empty.

• SDLSTRTDT:

Dats field: Contains the date on which the job is to start.

• SDLSTRTTM:

Tims field: Contains the time at which the job is to start.

• EVENTID:

32-character field: Contains the event the job waits for afterscheduling. The event starts the job.

• EVENTPARM:

64-character field: Contains the parameter of the event.
If a job had a filled parameter at event scheduling, it only starts ifthe event is also triggered with this parameter.
If a job had an empty parameter at event scheduling, it always starts,regardless of the parameter of the event.

• PERIODIC:

1-character field = 'X'.
It can only be used with event-jobs. Periodic jobs with other startconditions must be created with the AWB.

• CANCELPERIOD:

10-character field:
If the field is empty, the job never terminates with periodicscheduling.
If the field contains a number greater than 0, the period job isterminated when the CANCELPERIOD starts.

• EVENT_ID_OK:

32-character field: Contains the event that the job triggers if it hasbeen successfully completed.

• EVENT_PM_OK:

64-character field: Contains the parameter of the successful event.

• EVENT_ID_ER

32-character field: Contains the event that the job triggers if it hasbeen completed with errors.

• EVENT_PM_ER:

64-character field: Contains the parameter of the event with errors.

• FUNCTION_CALL:

1-character field: Indicates whether the function moduleRSSM_START_SECOND_PROCESS is to be executed at the end of the loadingprocess.

• EXIT_CALL:

1-character field: Indicates that the Business Add-In BW_SCHEDULER isto be executed at the end of the loading process.

• BATCH_WAIT:

1-character field: Indicates whether the requested job is to wait untilthe requested data is loaded into BW or not.

Description
Table INFOCUBES: Fields and meanings:


• INFOCUBE:

30-character field: Name of the InfoCube or ODS object to which thedata is to be posted.

• LOADCUBE:

Flag: Only those data targets that have this flag set are loaded fromthe table INFOCUBES.

• DELETEALLBEFORE:

Flag: If this flag is set, the contents of the data target are deletedbefore it is loaded (completely).

Description
Returning errors
If the parameter is empty, no errors are returned.

Description
Table SELECTIONS: Fields and meanings:


• FIELDNAME:

30-character field: Field name of the field on which selections are tobe made.,,,,

• IOBJNM:

30-character field: InfoObject onto which the field is mapped in BW, onwhich the selection are to be made.
This entry can be missing - data can also be selected for fields thatare not mapped onto InfoObjects.

• SIGN:

1-character field: Only 'I' is allowed!

• OPT:

2-character field: Only 'EQ' is allowed for a single value in LOW, and'BT' for a value in LOW HIGH range.

• LOW:

45-character field: From_value of selection.

• HIGH:

45-character field: To_value of selection.

Description
Table THIRD_PARTY_PARAMS: Fields and meanings:
You only need this table for 3rd party tool source systems.


• RFCFIELDNM:

30-character field: Field name.

• RFCVALUE:

128-character field: Value of the data entry for the RFC of the 3rd
party tool.

• RFCUSER:

32-character field: User name for logging on to the 3rd party tool(optional).

• PASSWORD:

8-character field: password for logging on to the 3rd party tool(optional).