SAP Netweaver Business Intelligence BI / BW

Symptom

You load a Datastore object (DSO) using either of the following scenario:
You use 3.x mode of loading using Infopackage andTransfer rulesandUpdate ruleswithStart RoutineYou use the 7.x mode of loading using Data Transfer Process (DTP),TransformationusingStart Routine,End RoutineorExpert Routine

You may end up in incorrect results for the characteristics which have not been used as key fields and the technical aggregation type is ‘MOV’ ( description: ‘overwirte / move’) for that characteristics.
Key figures which are updated by aggregation type ‘overwirte / move’ could also have the wrong aggregated values after processing a datapackage.
Other terms

Transfer rules, Update rules, Start routine
Transformation, Start routine, End Routine, Expert Routine
Chronological sequence of records;
Incorrect data; unexpected data
Reason and Prerequisites

REASON: This works as designed for Data aggreated by ‘MOV’ option. Records with the same key are always aggregated by principle ‘the last records wins’.
Solution

By activating data of a Datastore, datapackages are always process in the correct chronological sequence. Therefore it doesn’t matter whether the datapackages are loaded in ’serial’ or ‘parallel’. By using the following kind of routine, which are more easyly named aspackage routines:
Start routine in the Transfer Rules
( record sequence given by column = ‘RECORD’ )Start routine in Update Rules
( record sequence given by column = ‘RECNO’ )Start, Endroutine or Expert Routine in Transformation
( record sequence given by column = ‘RECORD’ )

It mustbe ensuredthat thechronological sequenceof the records inside a single datapackageisn’t changedafter processing a package routine.
The chronological sequence inside a datapackage is determined by the values of column ‘RECORD’ or ‘RECNO’ of the inbound data package.
If you need due to technical reasons inside a package routine adifferent orderyou must bring the outbound data at the end of the processing into thecorrect choronological sequenceagain.
You could da that by a abap statement like “SORT BY ‘RECORD’ or ‘RECNO’ ASCENDING” or you could ensure by your own logic the correct sequence of rows of the outbound datapackage.
Limitation: If you add new records you have to ensure the right sequence by your own logic. For details on adding records in package routines refer to consulting notes:
Transformations: 1258089, 1227667, 1223532Transfer rules: 710673Update rules: The behavior described in note 710673 is also valid.