Skip to Content
0

Pricing Conditions DSO based on std extractor 2lis 13 vdkon has become too big

May 02, 2017 at 09:19 PM

118

avatar image
Former Member

I have just inherited this BW application that has a very large Pricing Conditions DSO that is based on the standard extractor 2lis 13 vdkon (600+ GB).

Underlying DB is MS SQL. Basis tried to compress it at DB Level but its failing.

I am not familiar with this extractor as well as pricing condition tables.

1. Does this table has to be so big and why?

2. How to control its growth and sixe.

3. We have 4 years worth requests in the DSO, do we need all of them?

Is there a recommended regular maintenance for this table.

Any help would be highly apprecuable.

Thanks

RS

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

John Hawk May 05, 2017 at 09:41 PM
0

HI RS

1. Does this table has to be so big and why?

This is based on Billing Document Item Conditions. If you have an average of four Condition (ex Base price, Group discount, Customer discount, Seasonal discount) then the table will be 4 time larger than than the Billing Document Items DSO.

2. How to control its growth and sixe.

Consider selective deletion by time, periodically. If you don't need all the conditions for reporting, consider adding a filter to the extracting InfoPackage,

3. We have 4 years worth requests in the DSO, do we need all of them?

Only your business users can determine. If the DSO feeds an InfoCube which summarizes the data, they may agree to selective deletion of the DSO.

Is there a recommended regular maintenance for this table.

If you have several tables with this problem, explore archiving options with your Basis team.

Let me know if this helps.

John Hawk

Share
10 |10000 characters needed characters left characters exceeded