Functionality
This method provides all the settings of an InfoPackage.
You can transfer these settings (after changes are made), to the methodBAPI_IPAK_CREATE or BAPI_IPAK_CHANGE, to create a new InfoPackage or tochange an existing one.

Description
Import Parameter SCHEDULING_PARAMS: Data Targets: Fields and theirMeaning:

• ONLYENTRANCE:

Load data only at the start (PSA or IDoc). No subsequent processing.

• ONLYCUBETAB:

Load data only in the relevant data target, without PSA.
Indicator has no effect on data transfer using IDocs.

• PARALLEL:

Update data in the PSA and data target in parallel
Indicator has no effect on data transfer using IDocs.

• CUBEAFTERODS:

Update data automatically in the data targets, if all the data is
available in the PSA. A background process is started.
Indicator has an effect, only if the indicator ONLYENTRANCE = 'X' isset, and the indicator ONLYCUBETAB is blank.
Indicator has no effect on data transfer using IDocs.

Description
Import Parameter DETAIL: Fields and their Meanings


• INFOPACKAGE:

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

• INFOSOURCE:

Char 30 field: Contains the technical name of the BW InfoSource, towhich DataSource is mapped.

• INFOSOURCETYPE:

Char 1 field: Contains the technical type of the InfoSource. There are2 technical types: 'I' for InfoSources and 'O' for ObjectSources.
InfoSources are transaction DataSources (DataSource type '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 to the BW InfoSource.

• DATASOURCETYPE:

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

• HIERACT:

Numc 1 field: Activates hierarchies after loading. '0' if you do notwant to load the hierarchy after loading, '1' if you do want toactivate it.

• CHAVL_CHECK:

Char 1 field: Indicator showing whether the data is checked forconsistency after loading ('X').

• UPDATEMASTERDATA:

Char 1 field: Indicator, showing whether the data is loaded only ifmaster data exists for the data. If UPDATEMASTERDATA is blank, notransaction data is updated in the InfoCubes, for which not all themaster data has been loaded yet, or no master data is loaded if not allthe master data has been loaded for all the attributes yet.

• TEXT:

Char 60 field: Name for the InfoPackages in the log on language.

• LOAD_STATUS:

Char 1 field: Shows the sm37 status for an InfoPackage that is eitherscheduled or currently running:
'S' : Load job scheduled.
'R' : Load job currently running.
'F' : Load job complete.
'A' : Load job terminated..
Everything else: Interim status, that appears only briefly. If itappears more frequently, this could mean there is an error in the basisbackground processing.

• UPDMODE_READ:

Char 2 field: Processing mode for InfoPackages: There are the followingvalues:
'F' : Full-Update.
'D' : Delta-Update.
'R' : Repeat-Update = Requests the last data record again.
'C' : Initialization of the delta process.
'I' : Generate start status.
The field UPDMODE_READ is filled during an InfoPackage read, using theBAPI_IPAK_GETDETAIL method. It is not interpreted when you create anInfoPackage using the BAPI_IPAK_CREATE method, or when you change anInfoPackage with the BAPI_IPAK_CHANGE method.
Only InfoPackages with processing mode 'F' can be created at thepresent time. This is programmed in the BAPIs.
InfoPackages with other processing modes, have to be created in theAWB.

Description
Import Parameter FILE_PARAMS: File Selections: Fields and theirMeanings:


• LOCATION:

Type of External System:
'0' : External Data from the application server
'1' : External Data from the client workstation

• FILENAME:

Char 128 field: Name of the file that you want to load.

• FILETYPE:

Type of External File:
'1' : File is an ascii file with CR as a separator.
'2' : File is an Excel-CSV type.

• FILESEP:

Separator for Excel Format.
Default in Europe = ';', default in USA = ','.

• ESC:

Escape symbol for Excel files.
Default = '"'.

• CHAR1000:

Thousands separator.

• DECICHAR:

Symbol for a decimal point.

• CURRCONV:

Switches on currency conversion for external systems.

Description
Import Parameter HIE_PARAMS: File Selections: Fields and theirMeanings:


• HIENM:

Char 30 field: Name of the hierarchy that you want to load.

• HIEVERS:

Char 3 field: Hierarchy version that you want to load.

• HIEDATETO:

Dats field: To-date in the hierarchy that you want to load.

• HIEDATEFROM:

Dats field: From-date in the hierarchy that you want to load.

• HIECLASS:

Char 4 field: Hierarchy class for the hierarchy that you want to load.

• NEW_HIENAME_ON:

Flag: If = 'X', the loaded hierarchy is not stored under a name in theHIENM field in BW. Instead, it is stored under a name in the NEW_HIENMfield.

• NEW_HIENM:

Char 30 field: Name under which you want to store the loaded hierarchyin BW.
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 waituntil the requested data is loaded into BW or not.

Description
Technical name of InfoPackage.

Description
The default setting is that only filled selection fields are returned tothe SELECTIONS table.
If parameter WITH_EMPTY_SELFIELDS is filled with 'X', initial selectionfields that are not filled are also returned to the SELECTIONS table.

Value range
' ' or 'X'
' ' is the default
The parameter is optional.

Default
' ' (empty)

Description
Table INFOCUBES: Fields and their Meanings


• INFOCUBE:

Char 30 field: Name of the InfoCube or ODS object, in which you want to
update data.

• LOADCUBE:

Flag: Only the data targets with this flag are loaded from the tableINFOCUBES.

• DELETEALLBEFORE:

Flag: If this flag is set, the contents of this data target are deleted(completely) before loading.

Description
Error messages
If this table is empty, no errors occurred. Otherwise the call failedand the return was not defined.

Description
Table SELECTIONS: Fields and their Meaning:


• FIELDNAME:

Char 30 field: Field name for which the selection is carried out.

• IOBJNM:

Char 30 field: InfoObject to which the field, for which the selectionis carried out, is mapped in BW.
This entry is optional; you can also select data for fields, which arenot mapped to InfoObjects.

• SIGN:

Char 1 field: Only 'I' is allowed !

• OPT:

Char 2 field: Only 'EQ' is allowed for a single value in LOW, or 'BT'for a range LOW HIGH.

• LOW:

Char 45 field: From_value of the selection.

• HIGH:

Char 45 field: To_value of the 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).