Non-cumulative Inflow and Outflow explanation

Hello Everyone,
We are just implementing Inventory reporting in BW and cannot understand query results. We have searched the forums and documenation, but cannot find an answer.
We have a Non-*** Key Figure that we have defined an Inflow and Outflow for (in the aggregation tab). Can someone please explain in detail how this Non-*** will be calculated with Inflow and Outflow.
The Non-*** has Aggregation of SUM and exception of LAST
Here are our results (and the Inflow and Outflow KF's are ***)
We have a test query showing the KF for Inflow, KF for Outflow and KF for the Non-*** value.
The Inflow KF shows 26320
The Outflow KF shows 12428
The Non-*** KF (with the 2 above Inflow/Outflow) shows 66002
We thought this Non-*** would be calculated as Inflow (minus) Outflow. So the total of the Non-*** we were expecting 13892.
How does this Non-*** work with Inflow/Outflow? We can't find anything on this.
Thanks so much,
CM

Hi CM,
this has been discussed so many number of times in SDN.. and please search the forum on the same..
Also for ur ref:
non-cumulative key figures
Inventory management: non-cumulatives VS. snapshots
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
http://help.sap.com/saphelp_nw70/helpdata/EN/7e/96cc373de44040e10000009b38f8cf/frameset.htm
How to implent inventory cube 0IC_C03 with Transformation & DTPs
Thanks
Assign points if this helps

Similar Messages

Non cumulative key figure is not getting filled based on inflow and outflow

hi,
i have a non cumulative key figure which is having inflow and outflow.
i have these three info objects in dso.
as i know non *** key figure is calculated based on inflow and outflow.
i am getting values for inflow and outflow so non *** should be calculated based on this values.
<b>but the collumn is blank in the dso</b>
in that non *** keyfigure i have added two info objects in inflow and outflow.
is there any other setting i nedd to do?
please sugest me.
its urgent

Hi Venkat,
Have you followed the process right. First Filling the Initial Stocks and then Inflow and Out Flow and then Delta. If you follow the process correctly then you can able to view the Data in the Reporting Level.
For Initial Stocks the Marker Should be set. For Inflow and Outflow the Marker should not be set.
Hope This Helps,
Regards,
rik

What is inflow and outflow?

What is inflow and outflow?

hi,
for example u take stocks in the godown
what r material coming in to the godown is infow
what r the material going out is outflow
so total stock of the material can br found out based on inflow and outflow
this behavior is mainly seen in inventory management
There are two ways of implementing Non cumulative Key figure...inflow outflow is one way of doing that...mainly used in inventory scenario...take an example...you have issued stock and received stock data coming from R/3...in report you need current stock based on key date ( That may be current date ) so u cant directly subtract the two values and cumulate them because its Non cumulative KF and aggregated in different way.....
To implement this we create infoObject for current stock and check the third option in infoObject " Inflow Outflow" and there u will specify Inflow = received qty and Outflow = Issued qty so this infoObject will always contain difference of these two
current stock = received - issued
Also you initialize the current stock with some value initially

Any SAP report to capture Foreign currency Inflow and outflow

Hi Guru
Any report available which can provide Inflow and Outflow amount in a Company code in Foreign currency.
Account recievable report+ Account Payable report
I was thinking of using BSIK/BSAK and BSAD/BSID tables for this.
Report shud have these columns
For Each Vendor and Customer >>>>>>
Opening Balance This month Debit This month credit
it is to get closing balance..
please advise.........if no standard report than any logic will also be welcomed.
Edited by:
Edited by: AJeet N on Sep 14, 2010 1:27 PM

You can also try out the report HINUACRP.
Regards,
Santosh.

Cash Inflows and Outflows- company code wise, project wise etc.

Hi Gurus,
Client's requirement says they need cash inflows and cash outflows related to a company code, project wise etc. for a specified period.
What needs to be done for this requirement? Do we have to implement Cash Management and liquidity forecasting module to fulfill this requirement???
Please revert asap.
Thank You

Hi
You need to setup the cash journal configuration where cash inflows and outflows will be recorded.
The path is as follows:
SPRO>Financial Accounting>Bank Accounting>Business Transactions>Cash Journal
Hope it will solve your problem.
Regards
Tapan

Can anyone explain me abt Cash inflow and outflow

Hi all,
Can anyone explain me the cummulative cash inflow and out flow available while creating an info object. with an example in realtime scenario.
thanxs in advance
hari

Hi,
Mainly inflow and outflow is using in inventory only. So take the inventory live scenario and understand the logic. Pay some passion to read the below doc. Coz it will explain the complete design of the inventory.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Regards,
Vivek V

Key figure non-cumulative/ Inflow / Outflow

On the tab page Aggregation of a Key-figure, you are able to choose non-Cumulative values with in- and out-flow. What is the exact function of the in- and out-flow fields?

Hello,
please have a look into the documentation:
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
The inflow / outflow keyfigures is the delta of your non cumulative key figure.
kind reg.
michael

Multiprovider containing non-cumulative KF and cumulative KF

I have two infocubes that I have placed in a multiprovidor. Infocube #1 contains one non-cumulative key figure and some cumulative key figures. Infocube #2 contains all cumulative key figures. When running a query against the multiprovider, all key figures (from both infocubes) are displayed except for the non-cumulative key from Infocube #1, in which case the value is blanks. Is there something I am missing?

Yes SAP has defined some Restriction for Creation of MultiProvider for Non Cummulatived Key Figures.
"<b>MultiProviders
When the reporting scenario is to be extended, use a MultiProvider as central interface between
query definition and basic InfoProviders. When another InfoProvider is added to the MultiProvider
definition, the technical name of a query based on the MultiProvider remains unchanged.
Use a MultiProvider to reduce the size of the basic InfoProviders. Advantages: parallel access to
underlying basic InfoProviders, load balancing, resource utilization, query pruning.
Make sure that your MultiProvider only retrieves data from relevant basic InfoProviders at query
runtime by
o Using constants in the design of the basic InfoProviders
o Using different key figures in the design of the basic InfoProviders
o Using characteristic 0INFOPROV when designing a query on the MultiProvider
Are you planning to use a MultiProvider? If so, you have to ensure that the characteristics you want
to report exist in all basic InfoProviders.
Do not use more than one non-cumulative InfoCube (InfoCube with at least one non-cumulative key
figure) because this could lead to incorrect query results.
Do not use calculations before aggregation on MultiProvider because this may lead to wrong query
results.
Do not combine basic InfoProviders having inhomogeneous data models in a MultiProvider. Use the
report-report interface between queries defined on the basic InfoProvider instead.
Avoid using only parts of compound characteristics in the constituent basic InfoProvider of a
MultiProvider. For more information, see SAP note 702542."</b>
RefS: How to Do Docs

Inventory Inflow and outflow calculation

Hi ,
I am working with inventory cube my value for the Current stock ie.valuated stock is not getting tally with R/3 hence i would like to calculated that in the Query level and check..when i wrote formulae like this
Current stock = value stock recieved - value stock issued
but when we click on ok button we get the enhance button but in BI 7.0 we had some else setting becasue i am not getting this option to set the aggregation and exception aggregation please kindly can anyone will help..
thanks

Done

Non cumulative with inflow and out flow vales cant be seen in report

Hello
I have 0VALSTCKVAL Value of Valuated stock with inflow 0RECVS_VAL and Outflow 0ISSVS_VAL.
The Data is loaded into 0IC_C03 cube From BX Extractor and when I create the BEx Report it shows me the value only for the 0VALSTCKVAL.
I cannot see the value for inflow 0RECVS_VAL and Outflow 0ISSVS_VAL. What is the logic used behind this!
How can we know the reference value?
Informations please!
Points will be assigned!!
Thanks
Ram

Hello
0ISSVS_VAL : *12.236,39 *
0RECVS_VAL : *23.155,20 *
0VALSTCKVAL: 39.897,96 EUR
I have the issued stock ,received stock and the valuated stock! The issued stock and the received stock is used as an inflow and outflow for valuated stock.
Now how the values is calculated ?
Thanks
Ram!
Points will be assigned!

Transformation between DS and DSO missing Non-cumulative KYF

Hi SDN,
I installed the business content for CML, and am working with 0CML_DELTA_CAP datasource. I would like to create a transformation between this datasource and DSO 0CML_O03.
By default, when you install the CML business content, the datasources use the 3.x dataflow concept (transfer rules, infosources, and update rules).
I would like to use the 7.x dataflow concept and created a transformation between the 0CML_DELTA_CAP datasource and the 0CML_O03 DSO. In the transformation, it is missing the fields 0CML_B330, 0CML_B340, 0CML_B360, 0CML_B380 in the datatarget. These key figures are non-cumulative with NCum Value change (0CML_B330 uses 0CML_B331 as value change). The value change key figures show up in the transformation, but the non-culmulative key figures do not.
Does anyone have any ideas why the non-cuml. kyf are not showing up in the transformation?
Thanks,

Hi Brendon,
The non- cumulative key figures are not mapped in the transformation. Only the 'Inflow' and 'Outflow' key figures for the non- cumulative key figure are mapped.
You can check the property for the non- *** KF in RSD1, where you would find the corresponding inflow and outflow kf. If both of these are mapped in the transformation, the non- *** kf would calculate the value in the report in which it is included as:
Non-*** KF value = Inflow value - Outflow value.
Hope this helps.
Regards,
Abhishek.

Cumulative key figure and non cumulative key figure

Hi BW Expertz
Could any one give me the clarification about cumulative and non cumulative key figures .Why we go for cumulative key figure and non cumulative key figure.If any docs could u just mail to the following [email protected]
Thanx In advance
Best regards
sankar prasad

Cumulative values are those key figures (KF) that are cumulated using all characteristics, thus also using time.
Ex: Sales revenue, Quantity....
Non-cumulative values are those key figures that are measured in relation to a period in time; they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so called exception aggregation.
Ex: Number of employees, Inventory, Stock prices, Account balance,.....
AGGREGATION TAB
Non cumulatives are evaluated by non-cummulative values. Non-cummulative values are special key figures that are different from other key figures (cummulative values) in data transfers and saving as well as in aggregational behaviour. These are measured in relation to a period in time; that is to say, they cannot be meaningfully cumulated over time. Non-cumulative value are summaraized over-time using exception aggregation.
Non-cumulative values such as 'number of employess' are cumulated using characteristics such as 'cost center'. It does not make any sense, however, to cumulate the number of employees using different periods. The result at the end of any particular period would be the sum total of number of employees for each posting during the period. This would of course be wrong.
Instead, the aggregation of the KF can be defined as exception aggregation wherein an additional references characteristics is utilized to tell BW which value to use during the period, in this case, 0CALMONTH is used, in the above example, to indicate that only the last value of 0HEADCOUNT, updated by costcenter, is to be taken for any calender year and month.
Cummulative vs Non-Cumulatives
The purpose of non-cumulatives is to optimize the data transfer in BW, the data retention and the database access. The data transfer from OLTP to BW is minimized and only the meaningful data is saved and processed.
It is recommended that you use non-cumulative values for areas that dont change frequently such as warehouse stock or number of employees.
Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it for storing the non-cumulative or for inflows or outflows.
Non-cumulative values are stored with special KF that differ in terms of data transfers and aggregational behaviour.
Features of NON-Cumulative Values Transfering and Saving Data:
- NC values are mapped uisng one KF for NC changes or two KF for inflows and outflows.
-NC are transferred in an initialization run and the change runs that follow (initialization can also be omitted here)
- A non-cumulative value always has a time-related exception aggegation.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm
with Example
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
****Assign Points If Useful*********

Integrated Planning and Non-cumulative key figure

Hi
I´m creating an Integrated Planning application and a problem has occurred. The users want to plan on inflow and outflow and at the same time have a row with the total sum in the same layout (they are planning on 0CALMONTH and 0ORGUNIT) This can e.g. be solved through use Web Application Designer with one planning query and one traditional query.
Any way. I have created a non-cumulative key figure with an inflow- and an outflow key figure. The problem is that the non-cumulative key figure starts working first when I change the planning mode from plan status to load status. I could use function modules, to change the status, behind the save button but there are several users who are planning at the same cube at the same time and I don´t want to lock the others from planning.
How to solve this?
- Is it possible to restrict the switching, from plan to load, by setting some kind of filter at the users org.unit? (0ORGUNIT is an authorization object)
- Is it possible to create a process chain and then load the data to another cube for reporting at just this key figure? And also here have a filter at the org.unit
I will gladly get all kind of idea and input to solve this problem. Maybe there is some other way to go than using non-cumulative key figureu2026

Thanks for your answers
I have tried different scenarios and I will use a u201Dsave-buttonu201D. In the save-button I use the commands SAVE_DATA and EXECUTE_PROCESS_CHAIN. The command u201CEXECUTE_PROCESS_CHAIN starts a process chain that switches from plan mode to load mode and then back to plan mode again.
One new problem has arisen. The non-cumulative key figure is updating if an existing value (inflow- or outflow) is changed. But if an input is made to an empty cell, without value, nothing happen when I press on the start-button. BUT if I refresh the browser the non-cumulative value is updated!!!
Is there any command in WAD that refresh the whole page? If so I can include it in my start-button.
If not, any sugestion on how to solve the problem?
Best regards
Mikael

Difference between Snapshot scenario and non cumulative scenario

Hi,
Can any one please tell me the difference between snapshot scenario and non cumulative scenario in
inventory management.
Also please give example. I read the pdf " how to handle inventroy management scenarios", but can any one please give some easy to understand examples.
full points guaranteed-

hi,
In Non-cummulative method your stock movements are stored in the cube (inflow and outflow of NC KF) and the Total stock is calculated during query execution. Hence if there are lot of movements in the stock for the period you want to report on, query will take long time to execute.
In case of Snap shot scenario Stock movements are not loaded to cube. you use ODS to load the status of the stock and then from ODS you can load to Cube once in a month. So only summarized data will be availabe in Cube. Reporting will be fast.
Check the below threads
Inventory Management - SnapShot model
snapshot scenario?
SNAP SHOT Scenario in IM

Cumulative and Non-cumulative KFs

Guys,
so I am confused about cumulative/Non-cumulative keyfigures. I read what it says about them on help.sap.com
Flow/non-cumulative value
You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
Non-cumulative with non-cumulative change
The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
Non-Cumulative with inflow and outflow
The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, and quantity) as the non-cumulative value."
and also checked a few threads on sdn but still a little confused about their purpose.
Can someone tell me when do we use which one?
Thanks,
RG.

Hi Ram,
Cummulative & Non Cummulative Key Figures :
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
u2022 Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
u2022 Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope it helps you.
Thanks & Regards,
SD

Non-cumulative Inflow and Outflow explanation

Similar Messages

Maybe you are looking for