Entering the Master Data, Text, and Hierarchy Manually

Using the procedure given in Section 3.5, we can not only display characteristic data, but also enter new data and change existing data. In this section, we use a different technique. First, we show how to enter master data and texts for characteristic IO_SREG. Then, we describe how to create a hierarchy for IO_SREP.

3.6.1 Master Data and Text

Work Instructions

Step 1. Select InfoObjects under Modelling in the left panel, right-click Sales region, and then select Maintain master data in the right panel.

 

 

SCREEN 3.28

graphics/03fig28.gif

Step 2. Click graphics/clock.gif to display master data.

 

 

SCREEN 3.29

graphics/03fig29.gif

Step 3. Click graphics/attribute.gif to create a record.

 

 

SCREEN 3.30

graphics/03fig30.gif

Step 4. Enter data in the fields and click graphics/continue.gif to continue.

 

 

SCREEN 3.31

graphics/03fig31.gif

Step 5. Repeat Steps 3 and 4 to enter two more records, and then click graphics/save.gif to save the data into the database.

 

 

SCREEN 3.32

graphics/03fig32.gif

Result

You have entered data into IO_SREG. A status message Data has been saved will appear at the bottom of Screen 3.32.

Repeat the same procedure to enter data into IO_SOFF.

3.6.2 Hierarchy

Table 1.3 is actually a hierarchy. It should look like the hierarchy depicted in Figure 3.1 when we visualize the table data.

Figure 3.1. TIME-DEPENDENT HIERARCHY STRUCTURES

graphics/03fig01a.gif

This hierarchy indicates the Denver office was in the Midwest region before January 1, 2000. On and after January 1, 2000, the Denver office was part of the West region. In BW, a hierarchy such as the one in Figure 3.1 is called a time-dependent hierarchy structure. Section 7.4, "InfoCube Design Alternative III – Time-Dependent Entire Hierarchies," will discuss another type of hierarchy called a time-dependent entire hierarchy.

The following procedure describes how to create a time-dependent hierarchy structure for IO_SREP.

Work Instructions

Step 1. To create a hierarchy for IO_SREP, we must specify hierarchy properties in the IO_SREP definition. To modify the IO_SREP definition, double-click InfoObject Sales representative ID.

 

 

SCREEN 3.33

graphics/03fig33.gif

Step 2. Under the Hierarchy tab, select the option with hierarchies, and then select the option Hierarchy structure time-dependent.

Next, click graphics/check.gif to check it. If it is valid, click graphics/activate.gif to activate the modification.

 

 

Note

The activation will create three database tables for this hierarchy: /BIC/HIO_SREP (hierarchy table), /BIC/KIO_SREP (hierarchy SID table), and /BIC/IIO_SREP (SID hierarchy structure).

Besides DataSources for master data (IO_SREP_ATTR) and texts (IO_SREP_TEXT), IO_SREP will work with a third DataSource, IO_SREP_HIER. With IO_SREP_HIER, we can use an InfoPackage to load hierarchy data as well.

Section 7.4, "InfoCube Design Alternative III – Time-Dependent Entire Hierarchies," gives an example of Entire hierarchy is time-dependent.

SCREEN 3.34

graphics/03fig34.gif

Step 3. In the Administrator Workbench: Modelling window, right-click the characteristic InfoObject Sales representative ID, and then select Create hierarchy….

 

 

SCREEN 3.35

graphics/03fig35.gif

Step 4. Enter a name and a description, and then click graphics/continue.gif to continue.

 

 

SCREEN 3.36

graphics/03fig36.gif

Step 5. Right-click IO_SREP hierarchy, and then select Insert characteristic node….

 

 

SCREEN 3.37

graphics/03fig37.gif

Step 6. Enter IO_SREG, and then click graphics/continue.gif to continue. Here we use IO_SREG data to create the hierarchy nodes.

 

 

SCREEN 3.38

graphics/03fig38.gif

Step 7. Select all three regions, and then click graphics/continue.gif to continue.

 

 

SCREEN 3.39

graphics/03fig39.gif

Step 8. Three regions are displayed under IO_SREP hierarchy.

To assign offices to each region, right-click one of the regions and repeat Steps 5, 6 (enter IO_SOFF instead of IO_SREG), and 7. This screen shows that Denver, Los Angeles, and Seattle will be assigned to the West region.

 

 

SCREEN 3.40

graphics/03fig40.gif

Step 9. Because the Denver office is already assigned to the Midwest region, we see this message. As noted in Chapter 1, the Denver office was part of the Midwest region before January 1, 2000. For this reason, we need to put the Denver office in two places.

Select the option Copy duplicated node, and then click graphics/continue.gif to continue.

 

 

SCREEN 3.41

graphics/03fig41.gif

Step 10. Now we need to specify the valid date periods for the Denver office. Right-click the first Denver in the Midwest region, and then select Change node(s)….

 

 

SCREEN 3.42

graphics/03fig42.gif

Step 11. Enter dates in Valid from and To, and then click graphics/continue.gif to continue.

 

 

SCREEN 3.43

graphics/03fig43.gif

Step 12. Repeat Steps 10 and 11 to specify valid dates for the Denver office in the West region.

 

 

SCREEN 3.44

graphics/03fig44.gif

Step 13. Next, we assign sales representatives to each sales office.

At the hierarchy leaf level, we can either insert IO_SREP values following the previous steps or right-click an IO_SOFF value, such as Atlanta in the East region, and then select Sales rep. ID insert…. We take the second approach.

 

 

SCREEN 3.45

graphics/03fig45.gif

Step 14. After assigning sales representatives to each sales office, click graphics/save.gif to save the hierarchy. Now we need to activate the hierarchy before we can use it.

 

 

SCREEN 3.46

graphics/03fig46.gif

Step 15. In the Administrator Workbench: Modelling window, right-click the newly created hierarchy IO_SREP hierarchy, and then select Activate.

 

 

SCREEN 3.47

graphics/03fig47.gif

Result

You have created the hierarchy. Its color will change from gray to green.

Now that we have loaded and entered all characteristic data, it is time to load the transaction 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

InfoCube Design

Aggregates and Multi-Cubes

Operational Data Store (ODS)

Business Content

Generic R/3 Data Extraction

Data Maintenance

Performance Tuning

Object Transport

Appendix A. BW Implementation Methodology

Object Transport

Appendix B. SAP Basis Overview

Object Transport

Appendix C. Glossary

Appendix D. Bibliography



SAP Bw. A Step-By-Step Guide
Sap Bw: a Step By Step Guide for Bw 2.0
ISBN: B000LZM8CM
EAN: N/A
Year: 2002
Pages: 106

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