Inventory Consumption/usage calculation in BI for cube 0IC_C03

What is the standard SAP formula for Inventory usage or consumption in BI? How is in calculated using the key figures provided in the standard business content cube Material Stocks / Movements (0IC_C03)? We were using the old version of an inventory cube Material movements: Plant and periodical plant stocks(0IC_C01) to track usage and turnover but that cube is now obsolete.

Hi,
The problem arises from the fact that there doesn't seem to be any values provided in the data source that address usage the way there were in the old cube, so it seems there is nothing to work with in attempting to build a report to track usage. We used to have Total quantity consumed and Total value consumed. Those or anything like those are missing. The only key figured that addresses consumption is the Vendor consignment stock consumption which represents an extremely small portion of usage for us.

Similar Messages

Help!Create Aggregates For Cube 0C_C03 Ocurs Eror

When I create a aggregate for cube 0ic_c03, and fixed value to characteristic '0PLANT', Error occurs as following: ,how can I do?
'acna': InfoCube '0IC_C03 contains non-cumulatives: Ref. char. 0PLANT not summarized
Message no. RSDD430
Diagnosis
InfoCube 0IC_C03 contains key figures that display non-cumulative values. The non-cumulative values, however, can only be correctly calculated, if the aggregate contains all characteristic values of the reference characteristics (the characteristics for the time slice).
System response
The aggregation level was set to 'not aggregated' for the reference characteristics.

Hi Shangfu,
Info cube 0IC_C03 consists of non-cumulative key figures which means breifly the values are aggregated in run-time based on Time characteristics.
Include time characteristics "0CALDAY" as part of the aggregate in addition to "0PLANT" object to avoid this problem.
There are many OSS Notes explaining the purpose and usage of Non-cumulative key figures.
Cheers
Bala Koppuravuri

Are Cube organized materialized view with Year to Date calculated measure eligible for Query Rewrite

Hi,
Will appreciate if someone can help me with a question regarding Cube organized MV (OLAP).
Does cube organized materialized view with calculated measures based on time series Year to date, inception to date eg.
SUM(FCT_POSITION.BASE_REALIZED_PNL) OVER (HIERARCHY DIM_CALENDAR.CALENDAR BETWEEN UNBOUNDED PRECEDING AND CURRENT MEMBER WITHIN ANCESTOR AT DIMENSION LEVEL DIM_CALENDAR."YEAR")
are eligible for query rewrites or these are considered advanced for query rewrite purposes.
I was hoping to find an example with YTD window function on physical fact dim tables with optimizer rewriting it to Cube Org. MV but not much success.
Thanks in advance

I dont think this is possible.
(My own reasoning)
Part of the reason query rewrite works for base measures only (not calc measures in olap like ytd would be) is due to the fact that the data is staged in olap but its lineage is understandable via the olap cube mappings. That dependency/source identification is lost when we build calculated measures in olap and i think its almost impossible for optimizer to understand the finer points relating to an olap calculation defined via olap calculation (olap dml or olap expression) and also match it with the equivalent calculation using relational sql expression. The difficulty may be because both the olap ytd as well as relational ytd defined via sum() over (partition by ... order by ...) have many non-standard variations of the same calculation/definition. E.g: You can choose to use or choose not to use the option relating to IGNORE NULLs within the sql analytic function. OLAP defn may use NASKIP or NASKIP2.
I tried to search for query rewrite solutions for Inventory stock based calculations (aggregation along time=last value along time) and see if olap cube with cube aggregation option set to "Last non-na hierarchical value" works as an alternative to relational calculation. My experience has been that its not possible. You can do it relationally or you can do it via olap but your application needs to be aware of each and make the appropriate backend sql/call. In such cases, you cannot make olap (aw/cubes/dimensions) appear magically behind the scenes to fulfill the query execution while appearing to work relationally.
HTH
Shankar

T-code for getting consumptions / usage on special stock Q materials?

Hi,
I am facing an issue: special stock Q is not included in all T-codes that I know for getting the consumptions / usage over a period.
--> MC.9, MCBE etc.. are all not showing any results for those kind of materials.
I found the explanation: it's depending on special stock valuation indicator (Blank, A or M), and only A permits to see the consumptions with MCxx T-codes, which is not the one used in the plant I'm currently working in (M)
Since this valuation indicator is a FICO defined parameter, I cannot make it changed to be able to check those materials usage.
Anyone has a tip or know a way to get usage on special stock Q materials?
Thanks for any help!

Hi Sanil Bhandari,
Thanks for trying to help.
Unfortunately MMBE is a snapshot of stock level and reservations by storage location on a single material, and does not display the consumption over a predefined period.
I am still looking for any solution that works with special stock Q materials.

Missing content for inventory management (cube 0IC_C03)

Hi everybody,
I installed the following BI content for inventory management: Cube 0IC_C03, InfoSource 2LIS_03_BX and transfer rules from data source 2LIS_03_BX to info source 2LIS_03_BX. However, I'm not able to the update rule from info source 2LIS_03_BX to info cube 0IC_C03. I can only find the old update rule 0IC_C032LIS_40_S278 -> 0IC_C03.
I also couldn't find the update rule for material movements from 2LIS_03_BF to infocube 0IC_C03.
How can I find this missing content. We are using BI Content Release 704 Level 1.
Thanks for your help!
Thomas

Hi Oscar,
unfortunately, I was not able to find a transformation for the datasource migrated to 7.0.
Btw, how do I determine to which version data sources are replicated. I have an underlying ECC6.0 system. When I replicate all data sources for that source system, datasources automatically show up as 7.0. I'm missing the pop-up question whether or not I want to replicate as 3.5 or 7.0.
Thanks in advance!
Thomas

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

SSAS Multidimensional Time Intelligence YTD calculation showing BLANK for Date level

Hi there,
I am working with SSAS Multidimensional Cube, basically I have defined a Time Intelligence calculations for just YTD in the Cube, the calculation was created in the Calculations tab of the cube as follows:
/*Year to Date*/
[Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Year to Date],
[Dimension Dim Time].[Year].Members,
[Dimension Dim Time].[Date].Members
=
Aggregate(
{ [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Current Dimension Dim Time] }
PeriodsToDate(
[Dimension Dim Time].[Calendar].[Year],
[Dimension Dim Time].[Calendar].CurrentMember
My Calendar hierarchy is as follows:
Year -> Quarter -> Month -> Week -> Date
The problem I have is that when I am at Date level I am not getting the cumulative YTD value, instead I am just getting blank cells:
Could anyone help me defining a Time Intelligence YTD calculation that works for all levels including the Date (highlighted in yellow above)?
Thanks and best regards,
Joss

The only strange thing is the MDX script, I would have used this one instead (sse below) - but if this is not the issue, I would suggest you to isolate the issue in a simpler MDX script removing any other calculation.
Also take a look at the DateTool solution for these calculations - I really don't like the wizard provided by the development environment, it has other issues but not something that should affect your calculation:
http://www.sqlbi.com/articles/datetool-dimension-an-alternative-time-intelligence-implementation
/*Year to Date*/
[Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Year to Date],
    [Dimension Dim Time].[Calendar].Members,
[Dimension Dim Time].[Date].Members
=
Aggregate(
{ [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Current Dimension Dim Time] }
PeriodsToDate(
[Dimension Dim Time].[Calendar].[Year],
[Dimension Dim Time].[Calendar].CurrentMember
Marco Russo http://ssasworkshop.com http://www.sqlbi.com http://sqlblog.com/blogs/marco_russo

Inventory Management Cube 0ic_c03, 0StockType

In the Inventory Management Cube 0ic_c03 queries,I've found that 0StockType has descriptions that are misleading because of the way they are written in domain bstaus (R3 side), especially when seeing the key and SHORT description (truncated beyond meaning).
OK I can correct these by changing BStaus 's texts.
The main changes I'd do are for the Customer Consigment, Customer Return Packaging and Material Provided to Vendor descriptions.
But what does 0StockType 'blank' (or #) mean ?
(It seems to mean something like Valuated Stock Valuation and 'Not Defined' is not very good in a Query result)

Well, no one replied, but I got feedback from OSS. So just in case anyone is interested.....
I had to use r3 > se11 to change the domain descriptions myself.
Bstaus 'blank' I put as 'Valuation'
I also improved some of the Bsttyp descriptions whilst there

Inventory loads to cube 0IC_C03

Hi Guys ,
I am loading data to Inventory Cube 0IC_C03 .I have done all the steps .I have 1 question ie ..intilally i loaded data to cube from 2LIS_03_BF data source .I did the following steps :
u2022 Init Delta (2LIS_03_BF) with data transfer.
u2022 Release Request with No Marker Update (Tick).
Now from tomorro we will get delta loads .My question is do we need to compress delta request with NO MARKET UPDATE (TICK) ?
Or
Do i need to unTick The option NO MARKER UPDATE .
The data is very critical here .Please let me know if you have the right answer .
Regards
Santosh

Hi,
Pl look at below
Marker Update is used to reduce the time of fetching the non-cumulative key figures while reporting. It helps to easily get the values of previous stock quantities while reporting. The marker is a point in time which marks an opening stock balance. Data up to the marker is compressed.
The No Marker Update concept arises if the target InfoCube contains a non-cumulative key figure. For example, take the Material Movements InfoCube 0IC_C03 where stock quantity is a non-cumulative key figure. The process of loading the data into the cube involves in two steps:
1) In the first step, one should load the records pertaining to the opening stock balance/or the stock present at the time of implementation. At this time we will set marker to update (uncheck 'no marker update') so that the value of current stock quantity is stored in the marker. After that, when loading the historical movements (stock movements made previous to the time of implementing the cube) we must check marker update so that the marker should not be updated (because of these historical movements, only the stock balance / opening stock quantity has been updated; i.e. we have already loaded the present stock and the aggreagation of previous/historical data accumulates to the present data).
2) After every successful delta load, we should not check marker update (we should allow to update marker) so that the changes in the stock quantity should be updated in the marker value. The marker will be updated to those records which are compressed. The marker will not be updated to those uncompressed requests. Hence for every delta load request, the request should be compressed.
Check or uncheck the Marker Option:
Compress the request with stock marker => uncheck the marker update option.
Compress the loads without the stock maker => check the marker update option.
Relevant FAQs:
1) The marker isn't relevant when no data is transferred (e.g. during an delta init without data transfer).
2) The marker update is just like a check point (it will give the snapshot of the stock on a particular date when it is updated).
Reference information:
Note 643687 Compressing non-cumulative InfoCubes (BW-BCT-MM-BW)
Note 834829 Compression of BW InfoCubes without update of markers (BW-BEX-OT-DBIF-CON)
Note 745788 Non-cumulative mgmnt in BW: Verifying and correcting data (BW-BCT-MM-BW)
Note 586163 Composite Note on SAP R/3 Inventory Management in SAP BW (BW-BCT-MM-IM)
Thanks and regards

Customization of Inventory Cube - 0IC_C03

Hi gurus,
I need to implement the Inventory for my client using the Std cube 0IC_C03.
Here the client wants me to take the Total stock as the sum of the following stocks in MARD Table
LABST - Unrestricted
UMLME - Stock in Transfer
EINME - Restricted Use
SPEME - Blocked
RETME - Return
In the Standard Content we are considering only Stock in transfer & Blocked stock.
Please help me in suggesting what are the changes needed in Transformations for both 2LIS_03_BX and 2LIS_03_BF.
Thanks in Advance
Seshu

Hi ,
The fields LABST - Unrestricted
UMLME - Stock in Transfer
EINME - Restricted Use
SPEME - Blocked
RETME - Return
The fields other than blocked and Stock in transfer are not present in the datasources 2LIS_03_BX and 2LIS_03_BF .
If you need these fileds , you can go ahead with a function module datasource based on MARD , MSEG tables from where you can take these fields directly .
You can also refer to the links below for other options
Datasource for MARD table
Re: MARD Table - Not giving Stock in Transit Value
If in case the relevant fields are not seen in the datasource , you can go to transaction LBWE, CLICK ON 03 :Inventory Controlling(your case), click on maintainence tab and just drag the required fields to the left .
Also you need to delete and fill the setup tables after this step.

Inventory Management Extractors via DSO to Cube 0IC_C03

Dear experts,
to fulfill the requirements of DataWarehouse spirit using Entry-, Harmonization- and Reporting-Layer I want to use for Inventory Management a Data Flow from extractors 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM via DSO/DSOs and later on to Cube 0IC_C03.
In this forum there are some opened threads about this issue, but none has been resolved! Many hints are about the "How to Inventory Management..." - some other say: "You can use DSO's!" - others say: "Don't use DSOs!". So: Where is the truth? Is there anybody who can provide a really praticable way to implement the above mentioned data flow?
I'm so excited about your suggestions and answers.
Thanks in advance and regards
Patrick
--> Data Flow has to be in BW 7.0

Hi Patrick,
Yes indeed there is.
Using DSOs in inventory flow is absolutely possible. Here's what you need to know and do:
1 - Firstly don't be apprehensive about it. Knowledge is power! We know that inventory uses ABR delta update methodology and that is supported by DSOs so no doubt abt it.
2 - Secondly Inventory is special because of non-cumulative and several rule group at cube level for BX and BF.
3 - Now as you want to use a DSO and I am presuming that this will be used for staging purpose, use a write optimized DSO as the first layer. While mapping from DS to this DSO, keep one to one mapping from field to Info-objects.
4- Keep in mind that from Infosource to 0IC_C03 there would be multiple rule groups present in transformations.
These rule groups will have different KPIs mapped with routines. The purpose is that from ECC only 1 field for quantity (BWMNG) and one field for value (BWGEO) is coming but from Infosource to 0IC_C03 the same fields in different rule groups are mapped to different KPIs (Stock in transit, vendor consignment, valuated stock etc) based on stock category, stock type and BW transaction keys.
5- So create a write optimized DSO. map it one to one from datasource fields. create/copy transformations from this DSO to cube maintaining the same rule groups and same logic.
6- you can also use standard DSO and create rule groups and logic at DSO level and then do one to one from DSO to Cube.
Keep in mind that these rule groups and logic in them should be precisely the same as in standard flow.
This should work.
Debanshu

What is the field " Consumption based calculations " in EC 3.0

Hi,
In the consumptions tab page of a facility, what is the importance of the field " Consumption based calculations ". Please explain step by step procedure to make use of it instead of providing links
Thanks in advance
Srinivas

Hello Srinivasa,
Consumptions are time dependent consumption information for a facility object like coal consumption.
Consumption based calculation is used to calculate Emissions quantities based on amount of materials consumed.
Consumption based calculations are defined in calculation manater and are assigned in tab Consumption material.
For simple example without any major parameters emissions if you want to calculate sulfur dioxide emissions =
Sulfur dioxide) in defined unit = Consumptions * EF
If you want to enter detailed equations taking into consideration facility parameters like temperature, control efficiency then you consumption based quations includes all such parameters
The field you are referrring here - "consumption based calculation" - is automatically populated, based on material - consumption based equation assignment in tab Consumption materials.
Thanks
Jayakumar

Bi 7.0 for cube and master data steps

hi friends,
can u give me step by step comparision between bi 7.0 and bi 3.0 for cube ods and master data, ple explaing me what are the steps difference for those in bi 7.0 .
and reporting is same or any difference in bi 7.0 .
other than sap.help.com material, if u have any other or any screen shots. ple send me.
Thanking u
suneel.

what abt master data, in master data we are using only transfer rules, here also we are using transformation and dtp again.
Yes we would be using transformations and DTP's on the masterdata too. but the system would prompt to make IO a infoprovider in order to use the new functionality. There is another work around for it, but we can discuss it later, orelse search the forum for that option, i have replied to couple of questions regarding that.
what abt reporting any things other than calculated kf restricted kf, filters rows columns, free chaststics, variables, any chnages in screen.
The basic functionality of all the above mentioned objects havent changes, and the query designer itself, there are hell a lot of changes in the appearance and it will take a while to get used to it and find your way with all the functionalities.
i have doubt bps menas businees planning simulation what is this, bec i have idea we can use transactional cube and transactional ods for write accress for planninmg also
BPS is something I have no clue abt... (you dont see me answering in Business planning forum)

ENT-06954: Error while Displaying BIBean for Cube/Dimension Dataviewer.

Hi all,
I have defined a cube with three dimensions. All elements are deployed and the mappings is executed successfully. If I try to open the dataviewer either for the cube or for the dimensions I receive the following errors:
ENT-06954: Error while Displaying BIBean for Cube Dataviewer.
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerMain.getDataviewObject(CubeDataViewerMain.java:391)
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerEditor._init(CubeDataViewerEditor.java:66)
     at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
     at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
     at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
ENT-06972: Error while Displaying BIBean for Dimension Dataviewer.
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerMain.getDimensionListObject(DimDataViewerMain.java:479)
     at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerEditor._init(DimDataViewerEditor.java:89)
     at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
     at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
     at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
     at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
     at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
In another warehouse this function works properly. I am using OWB 10gR2 (10.2.0.1.31).
Any hints to fix this issue would be appreciated.
Thanks in Advance, C.

If you run OWB using the supplied shell script or batch file are there other errors on the console before the exception. OWB uses a component (OLAPI does some validation over and above any other) which dumps the errors on the the standard output which often illustrates some invalid metadata in the OLAP catalog.

Issue in Calculation schema determination for Scheduling Agreements

Dear All,
I am facing an issue in Calculation schema determination for Scheduling Agreements. The issue is -
"Appropriate calculation schema is not being determined when a scheduling agreement is being created"
The required settings which have been maintained are - The Calculation Schema (ZEIC31) has been created, Vendor Schema group has been created, Purchasing Organisation Schema group has been created, They both have been assigned to the Calculation schema in Schema determination, The Vendor Schema group has been assigned to the Vendor Master Record in master data creation.
When I am creating the scheduling agreement, the system is by default choosing the calculation schema - RM0002. Thus I am not able to put the manual condition types which have been assigned in the calculation schema - ZEIC31.
1> On what logic is the system picking that calculation schema?
2> What settings can I do to make it pick that calculation schema only which has been assigned with POrg Sch Gp and Ve Sch Gp?
Regards,
Sudhanshu

1> On what logic is the system picking that calculation schema?
As per "Define Schema Determination" in spro Purchasing document should pick the Pricing Procedure .
After creation of scheduling agreement have chacked your values in Scheduling agreement (Purchase ORG ,Schema grp in Vendor)
2> What settings can I do to make it pick that calculation schema only which has been assigned with POrg Sch Gp and Ve Sch Gp?
Check in Vendor mater is there any Plant specific Purcahsing data maintained.If it is plant specific Check purchasing data for that Plant.

Inventory Consumption/usage calculation in BI for cube 0IC_C03

Similar Messages

Maybe you are looking for