cancel
Showing results for 
Search instead for 
Did you mean: 

Truncate table DFKKOPBW

Former Member
0 Kudos

Hello SAP Guru's,

I have an issue in my ECC system. My DFKKOPBW table huge and I have added couple of columns in this table for BW.

The import is taking forever and finally failed. I have no way to proceed without deleting entries from this table.

Is there any implication if I ask my database team to "truncate table DFKKOPBW"? I donot need any past data from this table.We are using Oracle database.

Please Help!

Thanks

Romy

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member93896
Active Contributor
0 Kudos

Hello Romy,

don't truncate the table. The proper way is to use to mark the extracts for deletion in transaction FPBWS and schedule the report RFKKOPBW_DELETE.

Performance issues can occurs during marking and deletion of extracts. Please check if SAP Note 1427449 still needs to be applied.


Regards,
Marc

SAP Customer Solution Adoption (CSA)

Former Member
0 Kudos

Hello Marc,

Is there any way to automatically delete extracts? Or is it mandatory to manually mark the extracts in FPBWS?

We face following issue:

We would like to prepare and extract Open Items through RFKK_MA_SCHEDULER (mass activity OPBW). We use the process chain - run ABAP program with variant. The first run prepares data, but any following run on next day or week doesn't fetch any data (0 rows created). The only option is to delete the first extract and then we get the full Open Item extract.

EDIT: by searching around SCN, I found solution in http://scn.sap.com/thread/203737 - program RFKKOPBWS_DELETE_MARK in Note 1112938.

Thank you for any hint,

Marek

RamanKorrapati
Active Contributor
0 Kudos

Hi Romy,

When you won't need past data in future, then you can for deletion. before that cross check iwth users and once confirmed go for deletion.

If any extrcators pulling data from this table to bw side or any ECC reports are used data from this table, those will impact.

Thanks

Former Member
0 Kudos

Thanks for the reply. We alaredy pulled this data into BW and available for reporting. So no need to keep this data into the temperary table DFKKOPBW and planning to truncate.

RamanKorrapati
Active Contributor
0 Kudos

Hi,

Thats nice, Even check at ECC side, if any reprots are build on this table, it will impact.

if no reprots developed on this table at ecc side, then go for deletion with help of DB Team.

Once you pulled data into bw side. Unschedule the loads which pulled data from this table.

Thanks