Records deleted in SAP ECC but still showing in SAP BW for master data object.

[abhimanyu_sharma]

Hello Experts ,

Issue : We have master data info Object - Customer Partner Fucntion ( from KNVP Table). It is loading from KNVP table in BW.

           Currently, There are some records which are deleted from Source System but still present in BW as it is already loaded in BW. For this reason,              the report is showing discrepancy.

.

           As this is Master data object, we cannot delete the records since, it might be used in other cubes. Our reports is on the Customer Partner                     function Info Object.  

           When we are running the report, there are 2 partners function records are coming in the reports for the same customer. But in ECC, the previous              record is already deleted.

           Is there any way, by which i can handle this situation. We dont have any deletion Flag in ECC for the table.

Please suggest and share your ideas,

Best Regards,

Abhimanyu Sharma.

[jsmawai]

Hello Abhimanyu,

Are you able to find a solution to fix your issue?

Can you share your approach if you have fixed this!!!

This could be also a reason due to the patch update and version.

We too encountered the same scenario where the deletion of records in ECC table is not being updated to BW master data info object.

Regards

Siddhu

[jsmawai]

Adding to my previous response...

In my case, the table in ECC is a custom table and a custom extractor on it and we have a daily full load cycle to this flow.

Regards

Siddhu

[Former Member]

Hi,

if I get you right, you want to remove data from BW side that is already deleted in ECC side? If so, if u load to a characteristic as info provider, just right click and maintain it and delete the rows u don't need. If you loaded in a DSO, you can try selective deletion. That will surely fix your problem.

Hope this helps.

Thanks,

Regys

[Former Member]

Colleagues,

One question in addition...

Question: We can overwrite master data with FULL load to refresh with each but what about transaction records sitting in cube OR DSO for same customer which have been deleted OR an indicator has been set in ECC ?

Even if customer is deleted and doesn't exist in cube OR DSO, but on other hand query will still show that record as it is still present in cube OR DSO, even though entry has been deleted from master.

What We have in place is that we are bringing delete indicator from KNA1 in our custom data source which is built on KNVP (As standard data source is not available for customer partner function).

Every, weekend when there is less lload on the system, we do a FULL load to refresh customer master in BW, load for KNVP is also refreshed on weekend.

On query level, you can filter out those records which have 'X' present for nav. attribute (LOEVM, deletion indicator) of master object for KNVP (like ZCUS_KNVP__LOEVM = 'X'), Yes but you need to make LOEVM as nav. attribute so that it can be used in query. LOEVM is taken from KNA1 in data source which is built on data for KNVP in ECC.

Thanks & Regards,

M

[Former Member]

Typical problem with extracting KNVP to BW...

Like you said, the entries can probably not be deleted from the Master Data table, so what are you actually looking for as a solution? Do you maybe want to clear all the attribute values of the records that are deleted?

The only real way to get this 'delete' info in BW is either a daily ull load to a DSO so you can compare the snapshots of 2 days to identify the deletes OR via a custom extractor on the change log tables CDHDR/CDPOS

[abhimanyu_sharma]

Hi,

Thanks for the reply.

I dont want to touch CDHDR and CDPOS tables as it ll rasie the performance issues.

Is there any other way by which i can add some indicator in BW for deleted Records ?

[Former Member]

Hi,

Just want to throw some idea for you.

You will need some kind of log as you can't extract anything from nothing.

If you don't want to touch CDHDR/CDPOS, you can create one yourself.

Fill it up with custom code or database trigger, and build a extractor on it.

Regards

Bill