Enhancing Inventory Compressed cube - existing cube data handling

[Former Member]

Dear Experts

Existing inventory cube does not have a infoobject.

The extractor was enhanced with new fields and new infoobject added in development system.

As this inventory cube is compressed, deletion of existing cube data would be a problem as far as I understand.

So, I am not sure what is the best practice to handle this sort of situation where existing data need to be populated with new field from the extractor.

I heard there is this technique called reverse posting. Could you kindly provide the documents or cookbook to perform reverse postings?

Is it in effect deleting existing cube data and then reloading from R/3 such that the new field is populated at time of extraction?

Our delta mode is Unserialized V3 update.

Thank you for reading.

Best regards

Pascal

[former_member182343 · Accepted solution]

HI,

Down time is mandatory.

If not enhanced new field will capture data from the data it moves to production. Historical data for that field will not captured.

If you know Material dos you an do reverse posting .

Fill setup table table for those mat dos and run BF and edit stock qty/value at PSA and load to target and compress accordingly.

Vijay

[Former Member · Accepted solution]

Dear Vijay

From the link I read provided by KR, by Reverse Posting, it seems that it goes by cube Request ID.

However, these material reversals (as in goods returns/reversals done in R/3) indicated in R/3 are within the various Request IDs . So, Reverse Posting (not R/3  material Reversals) not so practical in our case where there are numberous requests existing in the cube now and the cube contains data for many companies over many years starting from 2007.

As we are processing now for 1 company first, we can selectively delete only those material document numbers with reversals by looking up R/3. There are about 50K such records that are relevant.

So, it leaves me with only option to do selective deletion and then use reload from Setup table for BF.

Is this method feasible?

1.  Alternatively, can I reload to a copy cube from R/3 when the Setup table with the BX done in 2007 has been deleted before? Can the same extractor do another BX init but meant for the copy cube which will not load from the existing cube but directly from the R/3 via a fresh BX init and BF and UM init ?  I suspect not possible but seeking confirmation.

2. Alternatively,  if I load from existing cube to copy cube using DTP , should I use DTP delta only or DTP full load or DTP Initial with non-cumulative? Is the DTP initial non-cumulative option for the 1st load only?

While loading to the copy cube , can I also change the posting date based on other dates for some material documents and skip loading the reversal material documents? I know that this way, the stock balance will be wrong but for my purpose, its ok as long as the GR and GI stock quantities are correct.

In short, Alternative 2 is to use 2 cubes , one for Stock Balance (MB5B) and one for the GR GI. A program will call one query from each to derive the aging. If possible, how should the 2 copy cube load from existing cube for delta ? Shall I trigger an event after existing cube delta is loaded to trigger a  DTP delta in copy cube?

I sincerely need some advice if these alternatives are feasible or plausible as this Inventory data is kind of complicated than normal cubes for data handling.

Thanks for reading.

Best regards

Pascal

[former_member182343 · Accepted solution]

HI,

Do selective deletion from OIC_C03 Plant wise / Material wise.

Try to get down time from that Plant and reload data.

Delete setup tables.

Clear SMQ1/RSA7.

Fill setup table selectively for that plant.

Load data to target through PSA.

Compress accordingly.

- Vijay

[RamanKorrapati]

Hi pascal,

If you very less records combination of enhanced fields, Mr Vijay solution will be the good one.

Below thread discussed on 0IC_C03..check the last reply, will be helpful to you.

https://scn.sap.com/thread/1757471

Regards

[Former Member]

Hi KR

Thanks for the useful link.

There are about 50K records involved.

Seems like not possible or practical to do selective BF reload by full load from setup table?

Thanks.

Pascal