Transferring Non-Cumulative Data into the BW System
Non-cumulatives can first be included through initialization or by loading a non-cumulative change. With initialization you are only able to post one initial non-cumulative for each combination of characteristics in the InfoCube. This causes non-cumulative changes. There is one InfoSource for the initial non-cumulative and one for non-cumulative changes.
See also, Business Content objects under inventory management (
SAP Library 
SAP NetWeaver Components Information Integration Business Intelligence BI Content Supply Chain Management Supply Chain Performance Management Inventory Management 
).
Data Flow with InfoSource 3.x:
InfoSource for initial non-cumulative: Transfers the current non-cumulatives once from the source system to SAP BW. This is necessary, for example, if you want to connect a system to a BW system later. By doing this you can ensure that the non-cumulative situation in the BW system is the same as the situation in the source system.
InfoSource for non-cumulative changes: Transfers current transactions, goods receipts, goods issues, and so on).
If an initial non-cumulative is to be loaded for a characteristic value combination, then this occurs in the first load procedure with the InfoSource for the initial non-cumulative. If a non-cumulative change is posted first, then no further initial non-cumulative can be posted for this characteristic value combination. The initial non-cumulative is then equal to zero. In the query, the first delta, which actually contains the initial value, appears to be especially high.
For other combinations of characteristics, initialization is permitted. If you load an initialization in an InfoCube that already has data, a warning appears. However, you can continue with the initialization. Both initializations are added to the query. However, you can no longer compress the request. Before compression, you have to delete the request with the second initialization from the InfoCube.
When loading the data, the validity period is determined and updated correspondingly, for every combination of validity-defining characteristic and per request.
An initial non-cumulative is firstly loaded for plant A. Non-cumulative changes are then posted for this plant. Subsequently, a non-cumulative change is posted in the InfoCube for plant B. Data for plant C is then posted in the InfoCube with an initial non-cumulative at first and then with non-cumulative changes.
Only non-cumulative changes, not initial non-cumulatives, can now be posted for all three plants.