Need Help in Inventory Exercise -

[#1]

Dear All,

I need your help to resolve the issue in Inventory Cube Exercise. I have searched the entire blog for similar problem but i didn't get any solution.

Here is the Problem.

Due to the marker problem the entire data in cube was corrupted, We have removed entire data in Cube. And we have taken the downtime and performed all necessary steps in R/3. The same was loaded to BW.

2lis_03_BX --> Loaded to BW (Initialization Stock, and one time job), But the request was Not Compressed.

2lis_03_BF--> initialize the delta without data transfer - Here i have only 1 record (initialized record) -- Request not compressed

2lis_03_UM--> Initialize the delta without data transfer - Here i have only 1 record (initialized record) -- Request not compressed

After Initialization, daily delta loads are running and those are fine. i am able to see the data in cube.

=>> After this i have loaded historical data from 2007 to 2010. (UM & BF) (each year One Request- Total 8 request for both).

NOW

1. i have Initialize Stock request in infocube for 2lis_03_BX

2. i have Initialization request, delta requests and historical data requests in infocube for 2lis_03_BF

3. i have Initialization request, delta requests and historical data requests in infocube for 2lis_03_UM

Here is the Big task for Me. Since Two months the delta loads are running. Now i need to do compression on this cube.

Please do remember, till now there is no compression (not even initial requests or no single requests) happened in this cube. Now i have to perform this task immedly.

• No requests are compression in the ZINV_C03_C (inventory cube) till now. ****

I need to perform immdly, because i have downtime fror three days from 28 dec to 30th Dec due to plant closing.

Please guide me to do this exercise.

Thanks in Advance

Venkat.

[Former Member]

Hi Maximiliano

I got an idea on compression scenarios, but my question is if i do compression on selective requests (one By one) is there any problem to be face? and how to done. Please suggest me if you have any suggestions.

And i have repairfull requests for Historical Data (2lis_02_bf, 2lis_02_um) 2007 to 2010. so how to do compression on these requests. Please give me your valuable suggestion .

For your idea i am giving my action plan on this cube:

-

---

Request ID Data Source Data Update Action on Compression

-

---

820452 2LIS_02_BX Initialization Compression with Marker (u2018No Ticku2019 Selection) - One time only

-

---

820453 2LIS_02_BF Initialization Compression without Marker (u2018with Ticku2019 Selection)One time only

820454 2LIS_02_BF Delta Compression with Marker (u2018No Ticku2019 Selection) - All following Delta requests for BF

821951 2LIS_02_BF Repairful (2009) What to do ????????????

825106 2LIS_02_BF Repairful (2008) What to do ????????????

etc..

-

---

820455 2LIS_02_UM Initialization Compression without Marker (u2018with Ticku2019 Selection) - One time only

820456 2LIS_02_UM Delta Compression with Marker (u2018No Tick Selection) -All Following Delta requests for UM

821900 2LIS_02_UM Repairful (2009) What to do ????????????

825107 2LIS_02_UM Repairful (2008) What to do ????????????

etc..

-

---

Till this point i dont have any issues, but and how to handle compression for historical data (repairfull requests). "This is only biggest question in my mind".

Please suggest me on this scenario.

Thanks in Advance

Venkat

[SreekanthSurampally]

Hi,

Your repair full request should be with "No marker update". that means you have to check the option "No marker update". for all repair full loads.

Regards

Sreekanth

[Former Member]

Thanks for your prompt reply.

have u seen my last post details. here i have given the requests numbers also. Is there any order to be maintained for compression.

Please suggest me if u have any documents priticular to this scenario.

Thanks in Advance.

Venkat

[maxilopez]

Hi,

Requests should be compressed by ascending order since the selection screen only allows you to set "Up to" a certain request number (upper limit).

The full repair requests add some difficulty to the scenario because of the additive nature of InfoCubes. Before loading a full repair request into the InfoCube (by running the corresponding DTP), you should perform a selective deletion process, so as not to duplicate records in the InfoCube.

I hope this helps you.

Regards,

-

Maximiliano

[Former Member]

Thanks for your Help.

The Problem was resolved for Inventory.

I have started compression request by request. I have started fom old request to New request (Bottom to Top).

For BX, I have done With Marker. i left init request for both UM and BF).

Historical data request are compressed with tick(no marker Update).

Delta request (For UM and BF) are compressed without Tick (with marker).

Executed report, and working great.

I got appreciations from Top Level Management. because they are struggling last 6 months without inventory reports.

Here all people are deserved those appreciations especially Maximiliano.

Thanks for your effort and spent your valuable time to resolve the issue. Thanks alot.. Keep rocking

Thanks & Regards

Venkat.

[maxilopez]

Hi Venkat,

Broadly speaking, the steps to initialize stocks InfoCube include:

1) Loading data from 2LIS_03_BX into the InfoCube.

2) Compressing the request with marker update (The checkbox "No marker update" should not be set).

3) Loading data historic data from 2LIS_03_BF and 2LIS_03_UM.

4) Compressing the request without marker update (The checkbox "No marker update" should be set).

5) From then on, deltas from 2LIS_03_BF and 2LIS_03_UM can be loaded. If you want to compress them, you should not set the aforementioned checkbox.

You can find the detailed procedure at:

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e...

Take into account that if the InfoCube is already loaded and only compression is missing, you do not have to reload it. You can compress in different steps by selecting the corresponding requests ids and setting the checkbox "No marker update" as needed.

I hope this helps you.

Regards,

-

Maximiliano

Edited by: Maximiliano Ariel López on Dec 18, 2010 2:51 PM