Now we can load data into the ODS object.
Step 1. Repeat the procedure outlined in Section 3.9 to create an InfoPackage. Select the Only PSA option in the InfoPackage.
As of BW 2 releases, when loading data into ODS objects BW requires us to select the Only PSA option because ODS objects do not support parallel loads.
A load request can be processed in parallel when the data are sent in multiple packets from the source system. Each packet will use one SAP work process. This parallel processing generates an ORA-54 error when multiple processes compete for the same table lock on the ODS tables. This table lock is essential so that the Overwrite option selected in Screen 9.12 will not cause data consistency problems when the data load executes. Loading data from PSA to an ODS object or an InfoCube is handled by a single SAP work process, which prevents the table locking problem.
BW release 3.0A removes this restriction. Data can now be loaded into an ODS object in multiple packets, through parallel processing. The new release achieves this goal via a queuing mechanism. Data requests are identified uniquely by a combination of several key fields.
Step 2. Under the Update parameters tab, we see another difference between ODS objects and InfoCubes: We do not have the delta load option. In Section 9.5, we will see how to perform delta data loading into the ODS object using 0RECORDMODE.
Step 3. After loading the data, go to PSA to check its contents using the procedure outlined in Section 4.3.
Step 4. After checking the data in PSA, load it into the ODS object following the step shown in Screen 4.16.
Next, we need to check and set the data quality status. To do so, right-click the ODS and select Manage.
Step 5. Click in the QM…column.
QM stands for "quality management." Before the loaded data will be available for reporting, the QM status must be set to "OK," as indicated by the green light on the right.
We could have skipped Step 5 if we had selected the option Set quality status to 'OK' automatically in Screen 9.3.
Step 6. Change the status from Status indifferent; not yet f to Status OK, and then click to save the change.
Step 7. Click to pass the message.
The loaded data are available for reporting only after being activated, which takes place in Step 10.
Step 8. Click to pass the message.
Step 9. The icon in the Request for reporting available column indicates that the loaded data are available for reporting, which is not correct. Screen 9.28 indicated that the data were not ready for reporting yet. As mentioned earlier, to make the data ready for reporting, we need to activate it.
Step 10. To make the data ready for reporting, right-click the ODS object, and then select Activate data in ODS….
We could have skipped Step 10 if we had selected the option Activate ODS object data automatically in Screen 9.3.
Step 11. Select the data load request, and then click. A background job is launched, which will move the data from one ODS table into another ODS table, from which we can display data using a BEx query.
You have loaded data into the ODS object and made it ready for reporting. Repeating the Section 5.1 procedure, you can define a query as shown in Screen 9.33. Screen 9.34 shows the result of this query.
Each ODS object has three database tables. In our case, they are /BIC/AODS_DEMO10 for the new data, /BIC/AODS_DEMO00 for the active data, and /BIC/B0000842000 for the change log. You can display each table's contents by clicking the appropriate button under the Contents tab in Screen 9.35.
Before the ODS data were activated in Screen 9.30, only /BIC/AODS_DEMO10 had data. Clicking , we can see its contents (Screen 9.36).
After the ODS data were activated (see Screen 9.30), /BIC/AODS_DEMO10 no longer had data; the data had been moved into /BIC/B0000842000 and /BIC/AODS_DEMO00. Clicking on Screen 9.35, we see the /BIC/B0000842000 contents (Screen 9.37). Clicking, we see the /BIC/AODS_DEMO00 contents (Screen 9.38).
In BW release 3.0A, an ODS object will have an active table and a change log. The data are loaded directly to the change log and arrive in the active table when it becomes activated. This change shortens data loading time and makes data available for reporting more quickly.
Part I. Guided Tours
Business Scenario and SAP BW
Creating an InfoCube
Loading Data into the InfoCube
Checking Data Quality
Creating Queries and Workbooks
Managing User Authorization
Part II. Advanced Topics
Aggregates and Multi-Cubes
Operational Data Store (ODS)
Generic R/3 Data Extraction
Appendix A. BW Implementation Methodology
Appendix B. SAP Basis Overview
Appendix C. Glossary
Appendix D. Bibliography