Not sure I understand your problem.
Are you saying in delta load you got 3 records for the same PO? that could be due to 3 images ( after before and reverse)
Or you are getting fewer records in InfoPackage than expected? If you are doing full load check if you have filled up setup table.
It capturs the diffrent update type and delta
Complete delta update with deletion indicator using delta queue (Cube-compatible).
I am run the setup table for this... one Invoice number, but there're 3 records there... not sure why?
The value fo ROCANCEL is blank for all 3 records in RSA3...why there are 3 records? even if this is capture for before and after image, we should only have 2 records...
can you try in your system?
Delete your setup table contents from LBWG
Re-fill setup table and then pull full load via InfoPackage. You would not get 3 records for a combination of Key.
Remember Setup table is a cluster table and not a transparent table. So running setup table filling up job more than once for same selection might give you more than once record in InfoPackage.
I have deleted the setup table and re-fill it again with one Invoice.
Again, in RSA3, I have 3 records... the content of the records are not the same althouhg belongs to same invoice number.
i.e. on the very fisrt record, I have a lot of fields are blank. Second record, I have more value, and same as third record.
Do you have this problem in your system?
I checked in my system , I am getting more than 3 records
Please check RBKP and RSEG table in ECC system to check how many entries are there.
2LIS_06_INV is item level extractor, so for one Invoiced multiple item is possible. Data is also dependent on the Fiscal year selection you give during setup run.
It is according to the standard design that RSA3 shows three lines for
invoice. The first line is the invoice header (similar to table RBKP).
Therefore the invoice item and the purchase order is here not filled.
The second line is for the invoice item (similar to RSEG) and the third
item shows the account assignment data (similar to RBCO).
Not all lines can have the same data filled because the BW system makes
a sum over the lines and then the content (the sum) would be too high
(higher than e.g. the invoice quantity really is).