Delta update (2LIS_11_VAITM) shows added records to DSO, but DSO is empty

[Former Member]

Hi,

I have an issue with SD delta loads. I am loading delta to DSO, with certain restrictions in start rotuine, and DSO is not being filled with any records, although monitor and "manage DSO" shows some added records.

At the side of normal data loads of Sales Orders to DSO, I am trying to collect the deleted Sales Orders and Items to another DSO. I have ABAP code in start routine of the update rules (BW 7.0) to second DSO, where unnecessary lines are deleted using STORNO (reversal indicator).

The whole data load process runs as expected, showing right number of added records based on the STORNO field. Monitor and data package simulation all show that the valid records are passed through. Still, DSO shows no data records after being activated.

Is there something hardcoded for the delta updates that messes up the process?

For our scenario, we don't want to change the current delta logic, as it is needed to remain the same in the normal data loads to original DSO.

[Former Member]

Thanks John for your answer!

We're using transformations and the coding is done correctly in start routines. That is also validated in the simulation from PSA, that the data records go correctly through the routines and to target. Also, transferred records explains the number of loaded records, added records explains how many were added to target after the update rules. The data appears to "disappear" during the DSO activation from new to active table.

I am thinking the delta procedure and manipulation of the delta image would require the use of 0RECORDMODE instead of the 0STORNO. More explained in the SAP note 333492.

Cheers,

Lauri

[john_hawk]

Hi Lauri.

My guess is that your are a victim of improper use of copy and paste.

The Start Routine and End Routined of the Transformation to the deleted items DSO was probably copied from the "normal" DSO , so that both transformations are deleting deleted items.

The "Added Records" indicator may be correct - it is telling you how many deleted records were loaded.

It just not telling you how many deleted items records were subsequently deleted by the improperly copied routine.

Good luck, and let us know your final solution.

John Hawk