Several business requirements and implementation methods for displaying Historical Changes of primary data

A data warehouse is a topic-oriented, integrated, relatively stable data set that reflects historical changes. It is used to support management decisions. Reflecting historical changes and meeting different needs for historical data analysis is a serious issue for data warehouse modeling. SAP
Bi divides data into primary data and transaction data. transaction data reflects the actual situation when a business transaction occurs, with less impact on changes in the enterprise architecture and product category. The impact of changes in Enterprise Architecture, product categories, and other data is usually reflected by changes in primary data.

Due to changes in the organizational structure, the group's management may have different requirements for business data analysis. Different users often have different ideas on how to analyze historical data for different business needs. In this part, we will explore 4
Different business needs. Due to the separation of the master data and the information cube of SAP Bi, these different business needs can be met through the same information cube at the same time. The difference is only the setting method of the master data.

For example, a subsidiary (zsubcomp) in 2008.07 belongs to the parent company (zparcomp) X, and is changed to parent company Y in 2008.08 due to organizational structure changes.

I. Real historical scenarios

Some books also call this requirement "Old Architecture and old data", that is, statistical data based on the data generated at that time.

Implementation Method: zparcomp is the attribute of zsubcomp. In transformation, the zparcomp rule is to read the master data.

 

Ii. Take the current standard as the statistical standard

Implementation Method 1: zparcomp is the navigation attribute of zsubcomp.

Method 2: Use hierarchy not time-dependent.

 

Iii. Time-related scenarios

Implementation Method 1: zparcomp is the time-related navigation attribute of zsubcomp.

Implementation Method 2: Use time-related hierarchies.

 

Iv. Comparable architecture scenarios

That is, only the data that has not changed the master data within a period of time is displayed.

It is a time-related navigation Attribute Table that stores the parent company and two additional attributes "valid from" and "valid to" in the information object "subsidiary" primary data. These fields defined by the system that indicate the start time and end time are not used for the report navigation purpose, nor are they directly displayed in the query designer. The key date fields in the query attribute use the information of these two date fields. These fields that determine the key date and validity period can provide flexible REPORT query options. You can use a key date in a query to access different primary data records with the same feature value. However, you can only specify a key date, but cannot specify a date range for selection. In this way, we cannot use the two fields defined by the system to meet our business scenario 4 requirements.