Hi Ravi,
As you said, we have two records at DSO1 level, because as it is write optimized dso. 2 records only will be there even if it is Standard DSO ( it depends on primary key).
| 100 | MP04 | 1800 | 10.01.2014 | 0 | 10 | 3 |
| 100 | MP05 | 1800 | 10.01.2014 | 8 | 0 | 22 |
When we we load data to integration layer (DSO2), it will pick data with combination of order only from DSO1 (W.r DSO active table) , because as it is primary key in DSO2. It means, the data will be like below only.
| 100 | 3600 | 10.01.2014 | 8 | 10 | 25 |
We can do one thing.
Better add Resource filed in DSO2 or else use standard DSO at Acquisition layer ( Later we will get performance issue if we use standard DSO at Acquisition layer)
As per my understanding, we should use filed "Resource" in both DSO's.We shouldn't club both Resource Quantities into single Order ( its depends on Business).Because, Quantity hasreleasedwith combination of "Order and Resource" in R/3.
If really want see Quantity only at Orders wise, then we can restrict at Query level also.
Is this problem in production system.if yes, then better to add " Resource" filed in DSO2.
Please do the below test for better understanding:
Load first record and then second record. Finally check output.
Regards,
Mahesh