Missing Purchasing docs between EKPO and PSA

[Former Member]

Hi everyone,

We are implementing the purchasing solution for the first time at the client. When testing the data, we noticed that certain PO's that are in the tables EKPO are not showing up in the 2lis_02_ITM PSA. I think even RSA3 doesn't show those records. Can someone please help me understand why that would happen? We have no special logic and these are standard extractors.

There are many PO ranges that seem to have missing PO's, such as 4500 series, 6000, 7000 and 8000 series.

Appreciate all your help and points will be awarded.

[MGrob]

Hi

Not all PO documents will be necessarily caught in 2lis_02_itm. Compare the outcome of DataSource 2LIS_02_ITM to tx ME80FN in ECC. Choose the Header/Item Data view in ME80FN then compare the data in the DataSource fields with the original document data in the ERP system.

hope it helps

Martin

[Former Member]

Hello Martin,

I thought that all PO items in EKPO will be extracted by 2LIS_02_ITM. If there is something missing in 2LIS_02_SCL from EKPO then I can understand that they could be contracts/OA. (Contracts donot have schedule line data). But is there also a criteria by which certain POs in EKPO are restricted from extraction by 2LIS_02_ITM? Can you please tell us if there are such criterias?

Thanks,

Arunan C

[former_member202718]

Hi Arun,

What we did was that we took a dump of EKKO table and we did the set up table fill using this dump and we compared the Cube output with the Dump,none of the data got missed out.

We also compared the data based on the PO Doc type and it was matching.

rgds

SVU123

[MGrob]

Hi

Have a look at note 578471  - Deleted positions in BW and statistics

Certain pos will not be transferred.

hope that clarifies

Martin

[Former Member]

Hello Martin,

Thank you for that.

But in both cases I think that the extractor will still have records for that positions in the extractor. (ROCANCEL - 'R') (even in a full load). Is my understanding wrong?

[arivazhagan_sivasamy]

Hi,

Have you loaded set up table.

Then only you can able to see all the records.

Arivazhagan S

[Former Member]

Hi Arivazhagan,

Thanks for your reply. Yes, I loaded the setup tables . The issue is not how to load data; it's the missing PO's once the tables have been filled and extracted into BW. Some of the PO's can be seen in EKPO but not in BW. Any idea?

[arivazhagan_sivasamy]

Hi,

You may be restricted by any field value or used CMOD or Routines.

Are you talking about Delta load or Full load?

Please check the missing PO's, whether those have any common relations.

Regards,

Arivazhagan S

[Former Member]

We are not restricting on anything and nor do we have any routines. Full load.

[arivazhagan_sivasamy]

Delete setup table content and once again load using OLI3BW.

Because when you using full load, system will take the value from setup table.

Regards,

Arivazhagan.

[Former Member]

May be I am not making myself clear. We are filling the setup tables correctly.The issue is that "some" PO's do not come even in RSA3. They are in EKPO but do not show up in RSA3. We are using standard extractors and there is no customization.

[RamanKorrapati]

Hi,

Assuming as your at dev system, so please take abap expert and debug your extractor at RSA3(ECC). We will get clue why its skipping some series of PO's or how the extractor working.

Thanks

[Former Member]

We are seeing this in QA. I'll see if I can get an ABAP expert to test this. Any other advice in this matter is welcome and appreciated.

[RamanKorrapati]

Mean while please delete and fill setup tables at Dev  ecc system and check it out. whether its pulls above series PO's or not. if it won't pulls then debugging is the option.

if it pulls at dev then there is some thing missing at quality ecc system.

[Former Member]

Data source 2LIS_02_ITM build based on many tables (EKPO + etc) and you are correct it should show all the PO's. It will display based on the code relavance you can observe by give input 2LIS_02_ITM in RSA2 as well.

Table-wise field help shown in this link http://help.sap.com/saphelp_sm32/helontent.htm

Better to confirm all PO related queries by checking data at RSA3 itself; It will save BI replication and loading times.