Historical Data Capture in Years

Purpose

The system needs the demand history in years to be able to perform phase-out planning and surplus and obsolescence planning . To do this, the system saves the yearly demand history in the InfoCube 9ADEMANN during historical data capture for each combination of the following factors:

Calendar Year
Product
Location

At the end of each year, you can load the demand history of a year from the InfoCube 9ADEMAND into the InfoCube 9ADEMANN. The system does not realign the data of the yearly demand history and you cannot change it manually.

Prerequisites

You have performed historical data capture so that InfoCube 9ADEMAND is filled.
You have transferred and activated InfoCube 9ADEMANN. In doing so you have also activated the update rules for this InfoCube and for the InfoSource 89ADEMAND.
You have created an InfoPackage for InfoSource 89ADEMAND.
- On the Update tab page you have selected the update mode Full Update .
- On the Data Selection you have considered the following when defining the selection criteria:
  - You have specified a time period for the characteristics that contain a periodicity. If you want to create the yearly demand history for the year 2005, you have specified 01.01.2005 in the From Value field and 12.31.2005 in the To Value field for the Calendar Year/Month (0CALMONTH) characteristic.
  - For the characteristic Demand Category (9ADEM_CAT), you have specified the demand categories whose demands should be included in the yearly demand history.
  - For the Indicator: TPOP (9ATPOP) characteristic, you have defined an ABAP routine that only selects data that has an initial TPOP indicator. To do so, proceed as follows:
    
    In the Type (Variable Change to Selection Values with Background Processing) field, choose ABAP Routine from the input help. A dialog window opens. Here you enter a description of the ABAP routine and confirm. A screen is opened on which you can expand the delivered ABAP routine.
    
    We deliver the following code:
    
    data: l_idx like sy-tabix
    
    read table l_t_range with key
    
    fieldname = ‘/BI0/9ATPOP’.
    
    l_idx = sy-tabix.
    
    Leave this code as it is and enter the following as the next row:
    
    l_t_range-low = ‘ ‘.
  - You have specified the customer-facing location for the characteristic Location (Customer-Facing Location) (9AFACING).
Caution
If you wish to specify multiple customer-facing locations and use the value range for this, each location contained in the value range must be a customer-facing location.

End of the caution.

Note
If you do not wish to specify a customer-facing location in the InfoPackage you can enter the following ABAP statement in the start routine of the update rule:

DELETE data_package[] WHERE /BI0/9AFACING = SPACE

For more information about InfoPackages, see SAP Library for SAP NetWeaver under SAP NetWeaver Library SAP NetWeaver by Key Capability Information Integration by Key Capability Business Intelligence Data Warehousing Data Warehouse Management Scheduler Creating InfoPackages .

End of the note.
If you only want to save the aggregated demand in posting periods but not in months, you must implement a specific mapping.

Process

The following figure shows how the system creates the yearly aggregated demand history from the demand history in the InfoCube 9ADEMAND:

This graphic is explained in the accompanying text.

The system extracts the demand history data in InfoCube 9ADEMAND into the InfoSource 89ADEMAND. The extraction occurs depending on your definition of the InfoPackage. The system thus extracts the data that lies within the time period defined by you and the demands of the demand categories that you selected in the InfoPackage, for example.
The system applies update rules to the InfoSource data. In these update rules, the mapping from the periodicity chosen by you, such as month, to the calendar year is defined on the Time Ref. tab page.
The system saves the yearly aggregated demand history in the InfoCube 9ADEMANN.