Loading Time-Dependent Hierarchies

Use

The procedure for loading time-dependent hierarchies is described in Loading Hierarchies. Also note the following special features when loading time-dependent hierarchies.

If you load a time-dependent hierarchy into a BW system and a hierarchy with the same technical name exists in this system already, the new hierarchy overrules the old one. If the time interval of the hierarchy that you want to load does not completely match the time interval of the existing hierarchy, the time interval of the existing hierarchy is adjusted accordingly.

Caution

If the time interval of the new hierarchy overlaps the time interval of the existing hierarchy, the time interval of the existing hierarchy is reduced so that the two time intervals run seamlessly into one another.

This does not apply if the time interval of the existing hierarchy contains the time interval of the new hierarchy. That is,if the from-date of the new hierarchy is greater than the from-date of the existing hierarchy and the to-date of the new hierarchy is less than the to-date of the existing hierarchy. In this case, the new hierarchy cannot be loaded. You have to change the time interval for either the new hierarchy or the existing hierarchy, so that the time interval of the new hierarchy is not contained in the time interval of the existing hierarchy.

If there are existing hierarchies with time intervals that are included in the time interval of a new hierarchy, the existing hierarchies are deleted.

Note

If you do not want to specify the validity of a hierarchy in advance, you specify the current date as the from-date and the latest date possible as the to-date, for example, 12.31.9999. You do the same for any other hierarchies that are subsequently loaded. When you load each hierarchy, the system automatically sets the to-date of the last hierarchy that was loaded as the day before the from-date of the new hierarchy. This procedure applies only to hierarchies that support transfer rules, see Special Features when Loading Data using the PSA.

Hierarchy Structure is Time-Dependent

In the scheduler, you select the time intervals that you want to load. For more information, see Tab Page: Update in the Time Selections for Time-Dependent Data section..

Whether the hierarchy is extracted as time-dependent or not depends on the properties the hierarchy has in the SAP source system and in the DataSource.

Example

There are two DataSources for the InfoObject 0CUST_SALES:

· The first DataSource extracts the hierarchy that is valid for the current date. The extracted hierarchy is not time-dependent.

· The second DataSource extracts the complete hierarchy as time-dependent.

You are able to load a time-independent DataSource for an InfoObject, whose hierarchies are set as time-dependent. The date fields are set to the lowest (1.1.1000) and the highest (12.31.9999) dates possible. On the other hand, you are not able to load a time-dependent DataSource for an InfoObject, whose hierarchies are not time-dependent, because the time-dependent hierarchy nodes will be duplicated at various points in the hierarchy.