Initially, all of the Business Content objects are set to the D version, so we must activate them before we can use them. This section provides the procedure for doing so, using 0PLANT as an example.
Business Content objects come in three versions:
The D version consists of the object's meta-data defined in Business Content. An A version object has been physically created. It appears as an M version when the object has been modified and saved, but has not yet been activated.
In BW, activating Business Content object is called Install(ing) the object.
Step 1. In Administrator Workbench, click the Business Content bar in the leftmost panel, and then click to set the default source systems.
Step 2. The default source systems are displayed. Click to accept them and continue.
Step 3. Click , and then select the collect automatically option. The collect automatically option means that BW will collect related objects for us.
A Business Content object cannot be activated if the objects on which it depends do not exist. Therefore, it is recommended that you select this option when installing a Business Content object.
Step 4. Click , and then select the in dataflow before and aftrwds option. With the in dataflow before and aftrwds option, objects that depend on 0PLANT and objects on which 0PLANT depends will be collected and activated together.
Step 5. Next, we will select a Business Content object and activate it. Click Select objects under InfoObject to locate 0PLANT.
Step 6. Select 0PLANT, and then click .
Step 7. Notice that 0PLANT and the associated objects are listed in the rightmost panel.
Next to column Collected objects are two columns, Install and Match (X) or copy. If 0PLANT has not been installed previously, then by default the collected objects will be checked only in Install, not Match (X) or copy. We can use the check boxes to select objects for installation.
If 0PLANT has been installed previously, Screen 10.51 displays, in which the collected objects are checked in Match (X) or copy, not Install. With this setting, the installation will do nothing to the object, keeping its A version untouched.
If an object is checked in both Match (X) or copy and Install, the installation process will open a new screen, asking us whether to merge the A version object with its D version definition.
You can use this feature to update an object with the most recently delivered Business Content, but you should not depend on it. For example, if the A version 0PLANT does not have the option with hierarchies checked (Screen 3.34), the installation will not automatically check the option with hierarchies although the D version of 0PLANT has the option with hierarchies checked. It means that the A version and the D version do not always merge.
If an object is checked in the column Install and unchecked in the column Match (X) or copy, the installation will make the A version object have its D version definition.
Without any warning, this setting can cause the installation to overwrite the A version object. Accordingly, some data in the object will be deleted, too.
Step 8. Click Install, and then select Install to activate 0PLANT and the associated objects.
BW takes care of the sequence of activating objects.
Use the Install in background option when activating a large object.
0PLANT and the associated objects, including transfer rules, are activated.
Next, to load 0PLANT data from the SND_250 source system, we need to create InfoPackages (Screen 10.53).
As mentioned earlier in conjunction with Screen 10.40, Screen 10.53 includes an entry called Plant under the Select data tab. This entry is used as a data selection condition when extracting data from the SND_250 source system.
Following the same procedures in Sections 3.4 and 3.5, we can load and check 0PLANT data.
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