Delta - Purchasing , Inventory Cubes

I want to set up the delta mechanism for 0PUR_C01 , OPUR_O01 , 0PUR_C08 , 0IC_C03 and 0COPC_C04 business content cubes.
In RSA7 , for the relevant datasources , I see 0 records. Can some one tell me , how to enable the delta for these datasources:
2LIS_02_ITM
2LIS_02_SGR
2LIS_02_SCN
2LIS_02_CGR
2LIS_03_BF
2LIS_03_UM
0CO_PC_ACT_02
0CO_PC_ACT_05
Thanks

Hello Jimmy,
Assuming that you have installed these from the business content and the respective datasources on r/3 side are also active(i.e u can see all of these in rsa6),
you need to run the setup on r/3 side in the logistic cockpit section for the respective application component.
The set up tables when filled, can be pulled(the data) in bw with initialisation option.
Once the init requests in these cubes are loaded, you need to set up delta jobs on the r/3 side. please refer to the types in the earlier answers/posts like direct delta etc.
once the delta jobs are scheduled on r/3 side, you can view them in rsa7. the delta queues are populated after the delta runs on r/3 side and seen in rsa7.
these then can be pulled in bw by schduling bw jobs with delta options.
the selections used in inits can be automatically picked up in these delta jobs(on bw side).
hope it helps..
thanks,

Similar Messages

Records is not coming in Delta for Inventory Cubes.

Hi..All
We are working on BW3.5 SP11 since 01.07.2005.
We are facing a very serious problem in Inventory management data extraction from R/3 since 24.08.2005.
Our active data sources of Inventory Mangement are as follow.
     2LIS_03_BF
     2LIS_03_BX
     2LIS_03_UM
We were regularly getting records through delta as per given schedule after intialisation on 01.07.2005 to till 23.08.2005.
On 24.08.2005 -- Delta schedule we had find out there are some records that were created in R/3 did not come in BW.
On 24.08.2005 -- records loaded in PSA was 20550. The same is appering in RSA3(EXTRACTORS) also.
The Last material document loaded was 4900154552 date 23.08.2005 time 16:56:05 of R/3, but there are many other material documents that were created on the same day but are missing in the extraction.
On 25.08.2005 delta schedule records are getting 0 (Zero). Not a single record is getting in RSA3 (Extractor).
on 26.08.2005 situation is still as it is. No record is coming.
Where as our average records per day is approx. 20000 nos.
The update mode for inventory is Unserialised V3 update, and the update program in R/3 is running perfectly fine as per schdule with no errors.
We could not understand why suddenly stop the extraction of records FOR INVENTORY MANAGEMENT. Because rest all
data sources like Purchasing,Sales and Distribution,Quality Mangement, and PP is working fine on same date.
We checked the data in extractor checker with giving UPDATE MODE "F"-Transfer all requested data.
Still it is showing 0 (Zero Records) for data sources 2LIS_03_BF,2LIS_03_UM.
The situation is still as it is as of now.
This is very crutial for our business. All inventory reports are showing data which is 3 days old.
Please give your advice on this issue. And how to get the records in PSA from R/3.
Regards,
Navin

Hi Ravindra,
Thanks for giving input. The problem got solved.
There was a problem with QRFC Table. Tcode LBWQ
Status was wait.
Thanks for giving feedback.
Regards,
Navin

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

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 load: can I use full load?

hi,
I have an inventory cube with non-cumolative chars. Can I use full load option or I thave to load with delta for non-cumulative KFs?
Regards,
Andrzej

Hi Aksik,
The load will not matter in the Addregation option.You can load by full or delta.
Now the reports creation has to be done with this in mind that the figures has to come correctly.Specify the aggregation required in the properties of the keyfigure in the query.If required use a ODS in the data flow.
regards
Happy Tony

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 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 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 0CP_IC_C1 enhancement

Hi,
I want to enhance the Inventory cube 0CP_IC_C1 inorder to get the Purchasing details in to the inventory cube. Because i need the PO details pertaining to the particular Good Receipt values.
Is there any way to get the PO details based on the GR values or can i go ahead and enhance the Inventory cube to get the PO Details.
Please advise.
Thanks,
Sheshu

Remember thst if yo want the MM Stock related for materials for each 0PLANT you must use the infocube 0IC_C03 not the 0CP_IC_C1.
Check this document in order to see if the 0IC_C03 infocube is useful for you...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Regards

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

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.

Display seles unit convert of material at inventory cube

Hello all,
At Report on the Inventory Cube ( 0MM_C02) i need to display the sales unit of material.
at material master in ecc the data exist at tran mm03 --- > additional data -----> unit of messure - all the convertion unit of measure.
exp:
base unit: 10 pc
sales unit : 1 KAR.
also i need to display this sales unit at purchasing and sales cubes.
how can i do this ?
Regards,
yuval

Hi Yuval,
This is related to Material Master -0MATERIAL.
Not surebut I think the UoM are getting captured in material master...check it out...else they may be there in either MARA,MARC,MARD or any of the material related tables..check with Functional Consultant.
Enhance the material master with the these UoM and then stamp them in the Cube while loading.
Or
Create a seperate master for this.
For calculations ..you can also make Char as Key Figure and use them calclualtons.....Google how to do it.
Let us know if you require any further info.
rgds
SVU

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.

Delta - Purchasing , Inventory Cubes

Similar Messages

Maybe you are looking for