Create an InfoPackage to Load Transaction Data

Now we are ready to create an InfoPackage to load the transaction data. In this InfoPackage, we will specify how and when to load data.

Work Instructions

Step 1. Right-click Source System demo: flat file, and then select Create InfoPackage….

 

 

SCREEN 3.66

Step 2. Select DataSource InfoSource Demo: IC_DEMOBC, enter a description for the InfoPackage, and then click to continue.

 

 

SCREEN 3.67

Step 3. Under the Select data tab, note the fields we selected in Screen 3.56. We can use the selection condition on 0CALDAY to load 1999 data first, 2000 data second, and 2001 data last. If we do not enter anything, all of the data will be loaded together in one data load request. Because we do not have a large volume of data, we load them all together.

 

 

SCREEN 3.68

Note

0CALDAY (Calendar day) is the characteristic in Screen 2.28 that represents the Transaction Date in Table 1.4. We also included it in the InfoSource definition.

Step 4. Under the External data tab, select options as shown in the screen, and enter a file name with a path. The file contains the data from Table 3.3.

 

 

SCREEN 3.69

Step 5. Under the Data targets tab, select the option Select data targets, and then select the first row for our InfoCube IC_DEMOBC.

 

 

SCREEN 3.70

Note

If the InfoSource appears in the update rules for other InfoCubes, all of the InfoCubes will be listed in the table. We can then specify into which InfoCubes we want to load the data.

Step 6.

Under the Schedule tab, select the option Start data load immediately, and then click to load the data.

SCREEN 3.71

Result

A status message Data was requested will appear at the bottom of Screen 3.71.

Note

We can check whether the data were loaded successfully by using BW Monitor as shown in Screen 3.22. Section 4.1, "Checking InfoCube Contents," and Section 12.2.1, "InfoCube Contents," both describe techniques for checking the InfoCube contents to confirm that the data loading process worked correctly.

Table 3.3 shows the sales data for our example. In the table, CS, EA, and DZ are abbreviations for Case, Each, and Dozen, respectively. The IO_REV column will hold the sales revenue data, which will be calculated by the transfer rule.

Table 3.3. SALES DATA

IO_CUST	IO_SREP	IO_MAT	IO_PRC	0UNIT	IO_QUAN	IO_REV	0CALDAY
CUST001	SREP01	MAT001	2	CS	1		19980304
CUST002	SREP02	MAT002	2	CS	2		19990526
CUST002	SREP02	MAT003	5	CS	3		19990730
CUST003	SREP03	MAT003	5	CS	4		20000101
CUST004	SREP04	MAT004	50	EA	5		19991023
CUST004	SREP04	MAT005	100	EA	6		19980904
CUST004	SREP04	MAT005	100	EA	7		19980529
CUST005	SREP05	MAT006	200	EA	8		19991108
CUST006	SREP06	MAT007	20	EA	9		20000408
CUST007	SREP07	MAT008	3	DZ	10		20000901
CUST007	SREP07	MAT008	3	DZ	1		19990424
CUST008	SREP08	MAT008	3	DZ	2		19980328
CUST008	SREP08	MAT009	2	CS	3		19980203
CUST008	SREP08	MAT010	1	LB	4		19991104
CUST009	SREP09	MAT011	1.5	LB	5		20000407
CUST010	SREP10	MAT011	1.5	LB	6		20000701
CUST010	SREP10	MAT011	1.5	LB	7		19990924
CUST010	SREP10	MAT012	2	LB	8		19991224
CUST010	SREP10	MAT013	3	CS	9		20000308
CUST011	SREP10	MAT014	1	LB	10		19980627
CUST012	SREP11	MAT014	2	LB	1		19991209
CUST012	SREP11	MAT015	3	CS	2		19980221
CUST012	SREP11	MAT015	2	CS	3		20000705
CUST012	SREP11	MAT015	3.5	CS	4		20001225