Inventory cube compression

Hi
We are live with Inventory cube filling and delta of material movements, for past 1 year, However we had not automated compression of cube with marker update, What are the steps to automate rollup & compression of inventory cube, is this recommended as a standard practice?.

Dear Anil
I have followed the same procedure
i.e.
BX-init: Compression with marker update
BF-init: Compression without marker update
UM-init: Compression without marker update
BF-delta loads: Compression with marker update
UM-delta loads: Compression with marker update
But surprisingly the values are not reflecting correctly
Thanks & Regards
Daniel

Similar Messages

Inventory Cube Compression - Non-Cumulative

Dear All
I have loaded setup tables in R/3
BX as on date TAC MCNB1
BF i.e. Historical TAC OLI1BW
UM TAC OLIZBW
I have loaded the Inventory Cube form all the three Data Sources
2LIS_03_BX : Initial Status
2LIS_03_BF : Initialization
2LIS_03_UM : Initialization
The queries are fine without compression
I have compressed the cube
2LIS_03_BX : with marker update
2LIS_03_BF : without marker update
2LIS_03_UM : without marker update
After compression the data for Stock issues in 24,36,48,60 months is giving vague values i.e.. IT IS ADDING UP ALL THE PREVIOUS VALUES TO SHOW FINAL VALUE
WHAT ARE THE SETTINGS TO BE MADE FOR COMPRESSION OF NON-CUMULATIVE CUBES ?
AM I MISSING ANYTHING (STEPS) ?
Thanks & Regards
Daniel

Dear Anil
I have followed the same procedure
i.e.
BX-init: Compression with marker update
BF-init: Compression without marker update
UM-init: Compression without marker update
BF-delta loads: Compression with marker update
UM-delta loads: Compression with marker update
But surprisingly the values are not reflecting correctly
Thanks & Regards
Daniel

Compression to inventory cube

Hi
I am initializing data to Inventory cube (with cumulative key figures) from
data sources 2lis_03_bx, 2lis_03_bf, 2lis_03_UM.
Could any body explain how to compress cube once data is loaded. I mean like non- cumulative cube do i need to use marker update and not marker update?
if yes whice data sources i need to use marker update.
Regards.
Sarath

Load opening Balance with 2LIS_03_BX. Compress with marker update(mandatory).
But your BI still does not know how this stock was arrived at, it needs the historical movements, should you need to know some stock value prior to initialization.
So you do a statistical setup for 2LIS_03_BF and bring this data to BW by an INIT. Now these movements are already accounted for, they reflect the current stock(marker) - means MARKER UPDATE is NOT required. Hence, when compressing historical data with 2LIS_03_BF, you check the "NO MARKER UPDATE" box. Because, if you update marker, it will ruin you current stock figure.
After this you open you OLTP system to users, they post new movements. You now load these to BI using BF datasource as delta. When compressing these, marker should be updated to reflect the new movements. Hence, you uncheck the flag "NO MARKER UPDATE". For subsequent loads too, this checkbox remains unchecked.
2LIS_03_UM does not deal with quantities, only valuations, compress it in the same way as you do for 2LIS_03_BF.
I hope this answers your question.
Edited by: SDX BI on Oct 10, 2008 3:49 PM

Compressing Inventory Cube

Hi all,
Is there a way to see whether compression of the Inventory Cube was done with the "No Marker Update" flag checked or unchecked? Is there some sort of tracking method. System is BW3.5
Regards,
Meurant Naude

Hi ya,
For Movements cube, firstly we load initial stock(BX) by using Compression check box in cube setting. then onwords we will load BF & UMs normally. Please note that we load BX, we load only once in a time.
This option you can check in:
cube>manage>in request tab it will get checked under Compression box.
i guess, by this way you can find whether cube has been compressed or not.
//Khan.

Effect of Cube Compression on BIA index's

What effect does cube compression have on a BIA index?
Also does SAP recommend rebuilding indexes on some periodic basis and also can we automate index deletes and rebuild processes for a specific cube using the standard process chain variants or programs?
Thank you

Compression: DB statistics and DB indexes for the InfoCubes are less relevant once you use the BI Accelerator.
In the standard case, you could even completely forgo these processes. But please note the following aspects:
Compression is still necessary for inventory InfoCubes, for InfoCubes with a significant number of cancellation requests (i.e. high compression rate), and for InfoCubes with a high number of partitions in the F-table. Note that compression requires DB statistics and DB indexes (P-index).
DB statistics and DB indexes are not used for reporting on BIA-enabled InfoCubes. However for roll-up and change run, we recommend the P-index (package) on the F-fact table.
Furthermore: up-to-date DB statistics and (some) DB indexes are necessary in the following cases:
a)data mart (for mass data extraction, BIA is not used)
b)real-time InfoProvider (with most-recent queries)
Note also that you need compressed and indexed InfoCubes with up-to-date statistics whenever you switch off the BI accelerator index.
Hope it Helps
Chetan
@CP..

Inventory Cube Stock Quantity/Value Issue

Hi Experts,
I have an issue regarding inventory cube about the stock value and quantity.
The Issue is:
1. I Loaded the 2LIS_03_BX first to initialise the materials opening balance, after compressed ther request with the Marker (checked) .
2. I loaded the 2LIS_03_BF with Initialize without data transfer infopackage and compressed in the cube
3. And I did full load 2LIS_03_BF and compressed with check box selected for marker update.
The issue I have is, when the stock quantity/value of a material ( BX , for example is taken on Dec.2011) is calculated(non cumulative key figure ex.0VALSTCKVAL/0VALSTCKQTY in the inventory cube) backwards based on Issues and received stock/value of material , I am not getting the value/stock equal to the value when the business started ( i.e for example Dec.2009, time at which the material opening stock is counted and entered in the system).
example: When I loaded BX ( intialize opening stock), let us suppose for Material A , have 1000kg in Dec 2011. When the non cumulative key figure (0VALSTCKQTY/0VALSTCKVAL) is calicualted for each month or day , at the end of the period for example Dec.2009 the stock should be 100, but I am getting more than 100 like 150 for example, even though all the issued,received and 0valstckval/0valstckqty are correct upto Dec.2009.
am i missing any steps or please let me your thoughts on this one.
Regards
Vamsi

Hi,
Please follow the steps mentioned in this link.I think 2LIS_03_BX full load should not be compressed with marker update only deltas to be updated in marker table of BF and UM.
http://wiki.sdn.sap.com/wiki/display/BI/StepbyStepLoadingDatatoInventory+Cube
Hope it helps.
Regards,
AL

Inventory Cube Issue

Hi Experts,
We have created a copy of 0IC_C03 with more no of fields added to the copy cube CIC_C03. We had lot of data mismatch in the earlier stage & now after a long time this copy cube is working fine in production. We have not yet compressed the deltas in the cube.
Now, later there was a field to be added in the inventory cube which takes data from an ODS. For this we created one more copy cube as we didnot want to disturb the inventory cube in production, hence we created one Zcube which is the copy of CIC_C03 with an added field. In the update rules we have a routine which fills with data from the ODS. The CIC_C03 acts as datasource for this Zcube.
My question is:
1) I dont feel that after a month or so, we require the data in CIC_c03 as the same data comes in ZCube. So will deletion of data from CIC_C03 affect my data?
2) The intial data in CIC_C03 are compressed whereas the deltas are not yet compressed. Should the full upload to Zcube take after compression only?
3) Suppose we delete the data from CIC_C03 after 2 months after a full upload is taken till that point. After deletion, the deltas will be coming in CIC_C03, canl these everyday delta be transfeered to Zcube?
Waiting for reply.
Regards,
Vaishnavi.

Hi,
The note(637927) is saying that the KFs which represents the values of Stock-in-transit (issue, receipt, current) are deleted in the cube . But still the cube is containint the KF which represents the quntity of Stock-in-transit (issue, receipt, current) .
So the deleted KF are :
0VALTRANSST - Stock-in-transit value
0RECCCNSVAL - Stock-in-transit issue value
0RECTRFSTVA - Stock-in-transit receipt value
Available KF are:
0TRANSSTOCK - Stock in transit Qty
0RECTRANSST - Receipt quantity: stock in transit
0ISSTRANSST - Issue quantity: stock in transit
So to find out the value of Stock-in-transit , you will use the Stock in transit. The scenario has to be used in this calculation is same as explained in note:589024.
With rgds,
Anil Kumar Sharma .P

Inventory Cube Loading - Questions....

This is the process I intend to follow to load InfoCube 0IC_C03 and the questions therein. I have the "how to handle inventory scenarios" document, so please don't suggest I read that.
1A) Delete Set-up tables for application 03
1B) Lock Users
1C) Flush LBWQ and delete entries in RSA7 related to application 03 (optional - only if needed)
2A) Fill set up tables for 2LIS_03_BX. Do Full load into BW Inventory Cube with "generate initial status" in InfoPackage.
2B) Compress request with a marker update
3A) Fill set up table for 2LIS_03_BF with posting date 01/01/2006 to 12/31/2007 (Historical) and load to Inventory Cube with a full update
      QUESTION1: Does this need a marker update?
      QUESTION2: Is this a good strategy - do movement documents that old get updated once posted?
      QUESTION3: Does the posting dates restriction depend on on how far back in history we want to go and look at stock values?
3B) Fill set up table for 2LIS_03_BF with posting date 01/01/2008 to 9/9/999 (Current) and load to Inventory Cube with a delta init with data transfer.
3C) Compress load in 3B without a marker update
4A) Fill set up table for 2LIS_03_UM and load to Inventory Cube with a delta init
4B) Compress load in 4A without a marker update
      QUESTION4: How should we select the posting date criteria? Do I need to load from 01/01/2006 to 9/9/9999 since that's the range used for BF?
5) Start V3 update jobs via Job Control
6) Intiate subsequent delta loads from BF and UM and compress with marker update
QUESTION 5: Is the sequence of loading BX first, then BF and UM fixed? or can I do BF and then BX, UM
QUESTION 6: Any tips on minimizing downtime in this particular scenario? Please don't suggest generic steps. If you can suggest something specific to this situation, that'd be great.
I hope you can help with the 6 questions I asked above.
Regards,
Anita S.

Hi Anita,
Please find my answers below. I have worked enough with this scenario and hence feel that these would be worth considering for your scenario.
3A) Fill set up table for 2LIS_03_BF with posting date 01/01/2006 to 12/31/2007 (Historical) and load to Inventory Cube with a full update
QUESTION1: Does this need a marker update?
In this step we dont need marker update while compressing.
QUESTION2: Is this a good strategy - do movement documents that old get updated once posted?
I am able to get the question quite clearly.
QUESTION3: Does the posting dates restriction depend on on how far back in history we want to go and look at stock values?
Yes. We need to start from latest and then go back as backwards as we want to see the stock values. This holds true when we are using non cumulative key figures
4B) Compress load in 4A without a marker update
QUESTION4: How should we select the posting date criteria? Do I need to load from 01/01/2006 to 9/9/9999 since that's the range used for BF?
No need to provide any selection criteria for UM while loading to BW, as this would fetch the same data filled in setup of revaluations.Unless you are looking for only some history other wise you can fill that for company code list and bring the whole data to BW by a single full load, as the data wont be that huge as compared to BF
6) Intiate subsequent delta loads from BF and UM and compress with marker update
QUESTION 5: Is the sequence of loading BX first, then BF and UM fixed? or can I do BF and then BX, UM
This is fixed in terms of compression with marker updates.
QUESTION 6: Any tips on minimizing downtime in this particular scenario? Please don't suggest generic steps. If you can suggest something specific to this situation, that'd be great.
*Yes. Most of time consuming activity is for filling BF history. Negligable for BX and UM comparitively.
Either try having multiple BF selective setup filling based on posting date based on available background processes or filli open months setup during downtime and rest history once you unlock the system for postings. The reason for this being we dont expect any posting for history*
Feel free to ask any further questions about this.
Naveen.A

Inventory Cube -

Hi All,
I have a need for a customized inventory cube, and am planning to use BX, BF and UM extractors into the same cube. I will enhance all the 3 extractors where they have all the characteristics needed for my cube and queries to match my requirements.
I have the following questions.
1. Some of my reports will require to report weekly and some monthly and some adhoc or when ever they want to see (like daily). So we will be updating the cube every night. Since it gets loaded every night if I left 'No marker Update' unchecked, but COMPRESS the cube after daily load how the data will be kept in the cube? and the impact on the queries.
2. How to decide which key figure should be non-cumulative. I have beginning balance, receipts, issues adjustments and turn rate for each week. But I believe except beg balance rest of the key figures can be cumulative.
If you have done inventory please advice.
Thanks,
Alex.

Alex,
If I define the amount as non-cumulative (what ever the KYF) and gets calculated during the query run time and based on the time requested in the query (cal week, calmonth etc) the value will be internally calculated and displayed in the query. is this a valid stament?
--> Yes. That is the advantage of Non-Cumulative keyfigures.
--> Inventory CUBE: 0IC_C03 contains calday, week, month. Based on user selection it displays balances for day level or week level or monthe level. No need to do any speicific calculation at updaterules or transformation level.
--> Just do delta's daily and compress with marker update(means no check box).
Check: [Inventory management: Usage of 2LIS_03_BX datasource |http://sapbwneelam.blogspot.com/2009/03/inventory-management-usage-of-2lis03bx.html]
[How to Handle Inventory Management Scenarios in BW (NW2004) |http://sapbwneelam.blogspot.com/2008/11/how-to-handle-inventory-management.html]
Srini

Inventory Cube BW on HANA

Hi All,
Could you please do let me know, why is it not required to perform compression of a non-cumulative infocube which is built on BW powered By HANA.
Regards,
Jo

Hi Dinesh & Others,
Thank you for your kind co-operation and information provided.
I have got fair idea now . I have gone through the below document. Please go through for all kind of queries regarding Inventory Cubes in BW on HANA.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50df1d69-4d86-2f10-a2ac-8b95b98dbe85?QuickLink=index&overridelayout=true&58965606021293
Thank you once again.
Regards,
Jo

Selective Deletion on Inventory Cube 0IC_C03 via Calendar Day

Hello Group
I am trying to do a selective delete to our inventory cube 0IC_C03 and found there is not an option to select day.
Does anyone have any thoughts on how do delete using day? Please note that my cube has been compressed and I do not have a request in the cube.
Thanks
Frank

Hi Frank,
REPORT ZRSDRD_SEL_DELETION                     .
DATA:
    l_thx_sel   TYPE rsdrd_thx_sel,
    l_sx_sel    TYPE LINE OF rsdrd_thx_sel,
    l_s_range   LIKE rsdrd_s_range,
    l_t_range   TYPE rsdrd_t_range,
    l_t_msg     TYPE rs_t_msg.
******************* 0CALDAY *****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = '20030308'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0CALDAY'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0PLANT **********************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'PLNT'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0PLANT'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0MATERIAL ****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'MATERIAL'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0MATERIAL'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
CALL FUNCTION 'RSDRD_SEL_DELETION'
     EXPORTING
          I_DATATARGET      = 'ZICRT_C37'
          I_THX_SEL         = L_THX_SEL
          I_AUTHORITY_CHECK = 'X'
          I_THRESHOLD       = '1.0000E-01'
          I_MODE            = 'C'
          I_NO_LOGGING      = ''
          I_PARALLEL_DEGREE = 1
          I_NO_COMMIT       = ''
     CHANGING
          C_T_MSG             = L_T_MSG.

Damaged inventory cube 0IC_C03

Hi all,
          My inventory cube is damanged because some data is not loaded via delta.
what i done is i stopped the back ground job which is running for compression of the request.i done Init with full repair request loaded missing data.(_03_BF). full load.
         now my question is setting up marker for BF . my opening stock is around 2006. I loaded from 02.2007 to till the date. It is not a historical data(Because it after 2006). current data.
can i do compression with marker or without marker.
pls help me this is very important for me.
thanks .

Hi
About the Marker - understood........I did....without checking it.   that is not the issue. Please see below the detail of the error log. Listcube does not show any entries. the range of posting dates i loaded was 1/1/2000 to 1/10/2010....valuated stock only..........
this is the error message..........
Multiple entries found with NCUMTIM 'unlimited'; compression not possible
Message no. DBMAN380
Diagnosis
The time dimension contains multiple entries for which the time
reference characteristic (NCUMTIM) is set to 'unlimited'.
The value 'unlimited' is the maximum possible value for the time
reference characteristic. This value is reserved for markers in
non-cumulative InfoCubes and cannot be used for standard transaction
records.
System Response : Compression is terminated.
Procedure : Contact your system administrator.
Procedure for System Administration
To allow compression to be carried out, the entries must first be
removed from the InfoCube.
To do this, you can proceed as follows:
1. Delete all packages that contain records in which the time reference
characteristic has the value 'unlimited'. You can identify these
packages by using transaction LISTCUBE.
2. Reload these packages and create a rule in the transformation that
maps the value 'unlimited' to a year before 9000.
3. Using transaction RSRV, then delete all entries that are no longer
used from the time dimension.
The InfoCube can be compressed again.

Performance query on 0IC_C03 inventory cube

Hello,
I am currently facing performance problems on this cube. The query is on material groups so the number of row returned are not to high.
The cube is compressed. Could aggregates be a solution, or does this not work well on this cube because on the non-cumulative key figure?
Does anyone have any hints on speeding this cube up? (the only tip I see in the collective note is to always compress)
Best regards
Jørgen

Hi Ruud,
Once compression with Marker update, latest balances will be created automatically for inventory cube: 0IC_C03.
Historic moments only required to show stock status for any historic date(eg: 02-01-2008).
If user not interested to check 3 years old status of stock, old data can be deleted selectively from cube using selective deletion.
Go through doc: [How Tou2026 Handle Inventory Management Scenarios in BW|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328?overridelayout=true]
Srini

0ic_c03 cube compression

Hello gurus,
I want to compress the stock cube (0IC_C03) for the performance issues.
Can you please confirm the process? I'm not sure about steps 3 and 4.
1- Delete the data in the cube
2- Start Delta Dtp from Ods to Cube
3- After the Dtp execution completes, compress the cube by setting "No marker Update" checked
4- After the compression completes, set "No marker Update" NOT checked
5- Start Delta Dtp
Here is the model we have for stock cube:
There is many documents about the issue. For example, I read Oss note 1548125 -Interesting facts about Inventory Cubes.
It is very usefull, but stock issue is a little complicated.Thats why I wanted to create this discussion.
I use aggreagation for my cube. Is it a problem to compress the cube?

Thanks for your messages.
The data in the cube is ensured, we have the historical movements.
I have the ODS with material movements (I have related key fields).
So the steps 3 and 4 are confirmed?
3- After the Dtp execution completes, compress the cube by setting "No marker Update" checked
4- After the compression completes, set "No marker Update" NOT checked
Suhas Karnik, guess you tell the inverse way:
"If you have ensured the above, perform setup, do a full load of all the material movements and compress with marker update (i.e. checkbox unticked). If you are splitting the data loads, ensure that you load the movements chronologically (i.e. load the oldest movements first)."

Logical split of inventory cube

Hi
I am using the inventory cube 0IC_C03 with non cumulative key figures.
this cube has grown to over 100 million records after compression.
I am planning to do a logical split of the cube by time(calendar/month)
ie 3 cubes - one with last 2 years data, the next for 2-5 years and data and the third rest
I am currently using a MP on top of 0IC_C03.
I am not sure how the non cumulative KF will work for inventory balances across 2 or 3 cubes
Any one done this
Lawrence

Hi Lawrence,
it's long ago, but did you solve your problem. We plan to set up inventory reporting and would like to do a logical split by time as well
Regards
Henning

Inventory cube compression

Similar Messages

Maybe you are looking for