How to display Historical Changes of primary data (3)

Business scenario 3: Optional architecture and flexible data aggregation.

You want to specify a key date. The report uses the key date to calculate the business income of the parent company. That is, if you specify July 1 as the key date, the report willOld Organizational StructureFor statistical standards, the income of subsidiaries AAA and BBB is recorded in the account of Parent Company X, and the income of CCC is recorded in the account of parent company Y. The data of the DDD subsidiary does not belong to the parent company.

If you specify August 1 as the key date, the report willWith a new organizational structureIs the statistical standard. The income of the AAA subsidiary is recorded in the account of the parent company X, and the income of the BBB, CCC, and DDD subsidiaries is recorded in the account of the parent company Y.

The data in this requirement can beSummary by the organizational structure at any time pointThe summarized data reflects the total revenue changes of the parent company of the group's organizational structure at various historical times.

Then, this article can be compatible with the business scenario of my article (for example, how to show the historical changes of the main data ().doc. But with the first article (such as how to display the historical changes of the main data (yiyun.doc) is two completely different scenarios. When is the organizational structure used for statistics, ratherOrganizational structure when business occurs.

Modeling Method: Maintain the parent company as a time-dependent navigation attribute of its subsidiary.

1. Create the subcompany information object sub_comp3. The parent company par_comp3 serves as its time-dependent navigation attribute.

2. After activation, open the sub_comp3 structure and look at its special features. It has two fields: valid to and valid from. The default value is from "01.01.1000" to "31.12.9999 ". When loading the primary data of a subsidiary, it is necessary to define its effective date. The organizational structures of different time periods are stored in different records. Sometimes it does not conform to the habit of reading data. We put "to" in front and "from" in the back.

3. Manually maintain its primary data as follows:

4. Create an infocube: ic_reno14 and click the sub_comp31_par_comp3 switch of navigation attributes.

5. Create ds, transformation, DTP, and infopackage for infocubu: ic_reno14.

6. Import the following transaction data.

7. Create a query and specify the key date: 2008.7.xx. Run the query in rsrt.

8. The query result is: No. Before 2008.7.31, BBB was owned by the parent company X.

9. Change the key date to 2008.8.2.

Simply put, because BBB only changes its organizational structure, the two results only change the parent company of BBB. The above is the parent company of X, and the following is the parent company of Y.

Note: here, the key date should be made into an input variable, which is more suitable for users to enter the corresponding key date as needed. However, in order to display the results, I wrote it to the query attribute. You can do better.

Ic_reno14 is aggregated and par_comp3 of this navigation attribute is used for aggregation.

 

After activation, check the aggregated data: