Compression failed - Inventory Cube - 2LIS_03_BX

HI Experts,
the compression of the initial request from datasource 2LIS_03_BX failed. The compression will be done with "no marker update".
On the development system it works fine, but on the test system the compression failed. The time dimension is with 0FISCPER and 0FISCYEAR.
All checks with RSDV are successfull.
Please find below the Job Log. Have anyone an idea ?
Thanks
Constantin
Message text
Message class
Message no.
Message type
Job started
0
516
S
Step 001 started (program RSCOMP1,
variant &0000000002226, user ID xxx)
0
550
S
Performing check and potential update for
status control table
   RSM1
490
S
FB RSM1_CHECK_DM_GOT_REQUEST called from
PRG RSSM_PROCESS_COMPRESS; row 000200
    RSM
53
S
Request '3.439.472'; DTA 'TKGSPLB16';
action 'C'; with dialog 'X'
    RSM
54
S
Leave RSM1_CHECK_DM_GOT_REQUEST in row
70; Req_State ''
    RSM
55
S
RSS2_DTP_RNR_SUBSEQ_PROC_SET
GET_INSTANCE_FOR_RNR   3439472 LINE 43
   RSAR
51
S
RSS2_DTP_RNR_SUBSEQ_PROC_SET
GET_TSTATE_FOR_RNR 2 LINE 243
   RSAR
51
S
Status transition 2 / 2 to 7 / 7
completed successfully
   RSBK
222
S
RSS2_DTP_RNR_SUBSEQ_PROC_SET
SET_TSTATE_FURTHER_START_OK LINE 261
   RSAR
51
S
Aggregation of InfoCube TKGSPLB16 to
request 3439472
   DBMAN
396
S
statistic data written
   DBMAN
102
S
Requirements check compelted: ok
   DBMAN
102
S
enqueue set: TKGSPLB16
   DBMAN
102
S
compond index checked on table:
/BIC/ETKGSPLB16
   DBMAN
102
S
ref. points have const. pdim: 0
   DBMAN
102
S
enqueue released: TKGSPLB16
   DBMAN
102
S
Prerequisite for successful compression
not fulfilled
   DBMAN
378
S
Collapse terminated: Data target
TKGSPLB16, from to 3.439.472
    RSM
747
S
Aggregation of InfoCube TKGSPLB16 to
request 3439472
   DBMAN
396
S
statistic data written
   DBMAN
102
S
Requirements check compelted: ok
   DBMAN
102
S
enqueue set: TKGSPLB16
   DBMAN
102
S
compond index checked on table:
/BIC/ETKGSPLB16
   DBMAN
102
S
ref. points have const. pdim: 0
   DBMAN
102
S
enqueue released: TKGSPLB16
   DBMAN
102
S
Prerequisite for successful compression
not fulfilled
   DBMAN
378
S
Collapse terminated: Data target
TKGSPLB16, from to 3439472
    RSM
747
S
Report RSCOMP1 ended with errors
   RSM1
798
E
Job cancelled after system exception
ERROR_MESSAGE
0
564
A

---> Compressing the request containing the opening stock that was just uploaded. Make
sure the "No marker update" indicator is not set.
The Problem is the time period 0FISCPER....
When I substitue it with 0CALMONTH and so on it works!

Similar Messages

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

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

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

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.

Cube compression failing

When compressing the Inventory Movements infocube, we are getting an ORA-01422, does anybody know what could cause this error?
Help will be highly appreciated

A more specific question:
When trying to find the cause of this issue, it turns out that the DSI_IMTKST contains several DIm Id's with the value 31.12.9999 for the Calendar Date(which seems to be the marker).
The error is being returned cause it is fetching more than one Dimension ID that contains the value 31.12.9999 for the Calendar Date
Any ideas why is this happening (having more than one Dimension ID with this calendar date value)?
Any help will be highly appreciated as this is not letting us compress the cube.
Thanks,
Arturo

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 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

Handling inventory cubes

Hi All,
I 'm working on inventory cube 0IC_c03( Material Movements).
I loaded the opening balance from 2lis_03_bx and compressd the request with no marker update.I got more added records than transfered records. later i loaded movements 2lis_03_bf (initilize delta process).0 records r updated and same as 2lis_03_um. Is that necessary to compress with marker update?.
If we get more added records how do we compare the date with source?
Its very urgent.

1)Activate the DSes-BX,BF,UM in RSA5
2)Activate the ES for BF,UM
3)Lock all other R/3 users
4) delete the set up table LBWQ for apllication 03
5) Delete the entries in LBWQ/SM13 for your application(03) by sheduling collective run(LBWE)
6) Fill the setup table for BX by running MCNB
Fill the setup tables for BF,UM from SBIW tcode.
7) Release R/3 users
8) Complete the Initialization of stock by using BX datasource in BIW
9)Complete the Delta init for BF,UM
10) Schedule Collective run
11) Create and Schedule periodic Delta loads
12) ) In case of Delta initialization request 0f 2LIS_03_BX, we must do compression with 'Marker update'.(any way then onwards there will be no delta loadings from this DS)
13) In case of Delta initialization request 0f 2LIS_03_BF, we must do compression with 'No Marker update'.
14) In case of Delta Loads 0f 2LIS_03_BF, we must do compression with 'Marker update'.
Here I assumed that you already activated the required Cubes/ODS,Update rulesa and transfer rules ,before 6th step menioned above.

Inventory cube 0IC_C03 ,Stock on particular date

Hi All,
 We are trying to get the stock on a particular date using cube 0IC_C03 ,but we are unable to get the total stock on a given date.
1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting null values.
I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
Thanks&regards,
Sunitha

Hi,
Check
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting null values.
 I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
For 2LIS_03_BX it will give the extracted date only
2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
try with below options.
Use :
0VALSTCKVAL " for Value
0VALSTCKQTY " for Qty
0CALMONTH " for Month
Use the above combinations in New Selections in columns and go it.
For Qty Opening:
New Selection bad drag abd drop following things
0VALSTCKQTY " for Qty
0CALMONTH " for Month and restrict with less then or equalto option variable (single value, user input) and set the offeset
 value = -1 bcoz if user will give 12.2009 , so it will display 11.2009 closing stock, this is opening for 12.2009.
For Qty Closing:
New Selection bad drag abd drop following things
0VALSTCKQTY " for Qty
0CALMONTH " for Month and restrict with less then or equalto option variable (single value, user input) .
In the same way build for Value and other Keyfigures on 0IC_C03.
And
Drag & drop
0MATERAIL
0PLANT " Give some Input Variable.
See the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
If it is BI 7 then for BX in in DTP in Extraction Tab you need to select Extacrion mode = NON-Cumulative option.
Thanks
Reddy

Loading to inventory cube - LBWQ ( entry MCEX03 missing )

Dear Guru's,
My main idea is to store only last 1 years of data in inventory cube .
I do not want to load the movements & revaluation data from ECC but reconstruct.
I have successfully initialized only 2LIS_03_BX and filled the set up table and further loaded in to BW.
For movements data i wanted to recontruct , so i reconstructed .
BW --> opening stock is correct.when compared with MB5B
Movements ( some data missing ) -- If i check for the historical stock , results does not tally.
I further checked and found some transactions missing in the cube ( when compared to MB51 movements list )
I tried to bring in these into BW using full load of 2LIS_03_BF.
it fetched 0 records.
I deleted the initialization request from info package in BW for 2lis_03_bf earlier
RSA3 --> also 0 records.
LBWE --> Job control scheduled to run every 1 hour.
RSA7 --> found job scheduled.
LBWQ --> no entry for MCEX03
I have run init with out data transfer and then tried to load full . still 0 records .
Also at rsa3 0 records.
Please help to advise how i can fetch these missing movements / records in to BW
Thanks & regards,
Sudhir.

Hello Janardhan,
When ever a full update is complete, the next records i.e. delta records moves into the Extractor Queue (LBWQ ) and after this moves through Scheduled process in delta Queue ( RSA7) .
The role of Setup tables is limited when you need the full extraction from the Application tables . Setup tables are restructuring tables .. basically are pooled tables which are introduced in the LO Extraction to ease up the extraction . Here System doesn't need to look for the Application table for data , this saves down time and consistency of records.
From Reconstruction it is relevant in 3x. Could you please elaborate what you tried to do..!
You can refer to the below links
Setup tables
LO Cockpit data extraction
Hope this helps...!
Regards
YN

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 datamart from one BW system to other BW system

Hi experts,
I have a requirement wherin I have to load the data from Inventory Cube 0IC_C03 from my old BW system to new BW system along with the markers & historical data.
So I have generated the Export datasource of 0IC_C03 and mapped with transformations to my new cube.
As per the 'Note 375098 - Data mart extraction from non-cumulative InfoCubes' , I have extracted using infopackage from the source infocube using the 0RECORDTP = 1 but I am not getting the option in DTP as 'Initial Non-Cumulative for Non-Cumulative values'.Since my datasource is not having the check box 'Opening balance'.
If I try running it as normal update then the DTP load is failing with the error as unlimited time characteristic as the 0calday is having the date 31.12.9999 for all marker records.
After the Full load (0RCEORDTP=1) to PSA,I also tried making the datasource to have 'Opening balance' marked using the ROOSOURCE table STCKUPD field and then tried using the option 'Initial Non-Cumulative for Non-Cumulative values' but still it's extracting zero records to Target cube from PSA.
Please guide me how to proceed with this without extracting the BX initialisation from R/3 system.
Thanks & Regards,
Ugendhar

Hi Ugendhar,
did you manage to solve your issue? I'm getting the exact same problem....
Thanks,
Enric

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

Compression failed - Inventory Cube - 2LIS_03_BX

Similar Messages

Maybe you are looking for