Building ODS in SAP BW 2.0B

Team-Fly

In the previous section, you learned how to define ODS objects in SAP BW 2.0A. The ODS development and management options in SAP BW 2.0A were not fully integrated in the Administrator Workbench. In SAP BW 2.0A, you manually invoke an ODS transaction to launch ODS object design facility. Moreover, in SAP BW 2.0A, the ODS objects were displayed under the InfoCube tree, which was confusing if you were dealing with ODS, PSA, or InfoCube when loading data in ODS objects. It was expected because then, in SAP BW 2.0A, ODS was introduced to get feedback from SAP customers on how the ODS environment should be integrated in SAP BW and the Administrator Workbench. I had several discussions with the ASUG ODS requirement and SAP BW ODS development manager, Rainer Hoeltke, and his team on naming schemes, integration, and its extended capabilities. The ODS development team was very quick to take feedback to integrate ODS functionality in the SAP BW 2.0B Administrator Workbench. Thus far, they have done a great job. Note that there have been changes in the SAP BW Administrator Workbench, as shown in Figure 17-6. Now you have the option to create InfoCubes and ODS objects from within the Administrator Workbench.

click to expand
Figure 17-6: The Administrator Workbench in SAP BW 2.0A and SAP BW 2.0B. The InfoCube Tree Hierarchy No Longer Exists in SAP BW 2.0B. Instead, Both InfoCubes and ODS Objects are Listed Under the Data Targets Tree.

Creating ODS Objects in SAP BW 2.0B

Creating objects in SAP BW 2.0B is similar to what was described previously. Now instead of executing the ODS transaction, as shown in Figure 17-2, you go to the Data targets tree, right-click an InfoArea, and select Create ODS object, as shown in Figure 17-6. You are then prompted for the ODS object name and taken to the ODS design window, as shown in Figure 17-7.

click to expand
Figure 17-7: Defining New DDS Objects in SAP BW 2.0B. Note that the ODS Design Layout is Very Different From in SAP BW 2.0A, as Shown in Figure 17-2.

Figure 17-7 shows the definition of an ODS object to capture schedule line item level detailed order information. Note that each subsection in the right pane is like a tabstrip in Figure 17-2. For example, Key section in Figure 17-7 is the same as the Compounding tabstrip in Figure 17-2.

The term key figures has nothing to do with the Key section when defining the ODS object. In the ODS object definition, as stated earlier, the Key section is to select a unique set of data elements to make the ODS record unique. In other words, it is the "grain" of the ODS object. In Figure 17-7, the ODS record is uniquely identified by a combination of division, document, order item line number, and schedule line number. Defining ODS object attributes is a very simple process. Select the appropriate InfoObject catalog in the left pane and expand it. Then simply drag and drop the selected InfoObjects from the left pane in the appropriate ODS object attribute sections shown in the right pane (see Figure 17-7). Click the Check icon icon. If no error is reported, click the Activate icon to save the ODS object definition and create database tables in the SAP BW database.

Note 

If the ODS object will be directly accessed by end users, make sure to check the BEX Reporting option, as shown in Figure 17-7. This will build SID tables and indexes to speed data access. You may not want to always check this, such as when you are building database tables to stage data.

Two types of database tables are created for each ODS object-one for active usage and the other as a backup or for working copy to prepare new data. For more information on how ODS objects are defined in the database, click the menu option Extras and select Information (Logs/Status), as shown in Figure 17-8.

click to expand
Figure 17-8: Getting Detailed Information on ODS Objects in SAP BW 2.0B.

After activating the ODS objects, define the update rules and load data. The update rules definition and the data loading process has not changed. It is the same as if you are working with an InfoCube or ODS object defined in SAP BW 2.0A. When you load data in the ODS object, new data will be kept in the New Data table instead of the Active ODS database table. To view new data or active data, select an ODS object, right-click, and select Manage, as shown in Figure 17-9. Click New Data to verify the data that has been loaded in the ODS object but users do not have access to. To make this data available for analysis, you must activate new data. To roll over new data in the active ODS object, select the ODS object, right-click, and select Activate data in ODS, as shown in Figure 17-9. From here, the activated ODS object is ready for end users. They can access it via InfoSet Query, BEX Analyzer, or third-party data-access tools via ODBO.

click to expand
Figure 17-9: Managing Data in ODS Objects.


Team-Fly


Business Information Warehouse for SAP
Business Information Warehouse for SAP (Prima Techs SAP Book Series)
ISBN: 0761523359
EAN: 2147483647
Year: 1999
Pages: 174
Authors: Naeem Hashmi

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net