Infopackages

These are used to fetch data from ECC to BW. There are different update modes which can be used when fetching data from the source system.

Above is the picture of the various tabs of an infopackage.

• The data selection tab is the place where we can add filters when extracting data from the source. The filters needed to be maintained in the source system to be seen here.
• The extraction tab gives the details of type of the datasource (*needs more appropriate explanation)
• Processing tab gives you the detail till what level the data will be processed, like till psa, data targets only.
• Data Targets gives the detail of all the objects for which data needs to be loaded.
• Update tab is the most important tab as it has details on how the datasource should work. More details are given below.
• Schedule is for triggering the data extraction

Update Tab
This is the important tab in the infopackage. here, we mention the type of update.

Full Update

When you run the using Full Upload, what ever data is there in source everything will be pulled to BW. If you use this, you can't run the Delta as there is no pointer set to find delta records. Only after initializing the datasource, delta records can be fetched.

A full update requests all data that corresponds to the selection criteria you determined in the scheduler. In a certain period of time specified in the scheduler, 100,000 data records are accumulated. With a full update, all 100 000 data records are requested.

When running the full loads, if we have more down time, we can fill setup tables and do a ful l load, else, we can do an Intialization without data transfer which doesn’t fetch any data but it places a pointer for delta and the next time the data is extracted, it fetches the full load records and delta records.

Initialize Delta Process

Only after doing the initialization with any of the below options, the datasource is made delta capable and can be seen in RSA7. The option of Delta is Infopackage is also available only after this process.

• Initialization with Data Transfer
• When executed, this will create an entry in the RSA7, which means the pointer is set for delta records. It also fetches all records from ECC and after its completed , it places the pointer. It is Full Load + Initialization.
• Initialization without Data Transfer
• When executed, this will create an entry in the RSA7, which means the pointer is set for delta records. It fetches a single record to BW which is a header record.
• Early Delta Initialization
• With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system.
• You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this.

Delta

A delta update only requests data which has appeared since the last delta. Before you can request a delta update, you must first initialize the delta process.  A delta update is only possible for loading from SAP source systems.  If a delta fails (status ’red’ in the monitor) or the overall    status of the delta request has been set to red manually, the next data request will be performed in repeat mode.

• F : Flat file provides the delta
• E : Extractor determines the delta, Ex: LIS, COPA
• D: Application determines the delta, Ex: LO, FI-AR/AP
• A: Use ALE change log delta

Full Repair  Request

This is present in the ‘Scheduler’ menu -> Repair Full Request, on the top when you open the infopackage.  These are used to fill in the gaps where delta extractions did not extract all delta records , when delta extraction process failed and cannot be extracted/restarted.

The request gets data from setup tables without delta being disturbed, wherein the setup tables are filled only according to the criteria.

These are also useful when you are initially extracting large volumes of data, whereby you execute an Init w/o data transfer and execute multiple Infopackage (Only Full Update) that are full repair request with specific selection criteria.

Finding the Infopackage Job

Once the infopackage is triggered for running, if you want to see the job details,

Environment -> Process Overview -> In the Source System

Else,

Copy the request number , go to the source system SM37 Add 'BI<request number>' and user as '*'

Data transfer using Infopackages

Data transfer using infopackes is done using IDocs and TRfc. Check LINK for more info
Infopackages can fail due to a number of reason.
Some of the common issues can be found : LINK