Regarding Non cumulative options

Hi Friends,
we have two options in aggregate tab while creating key figures.
In that we have two options
1) ncum value with ncum value chage.
2) ncum value with in-and-out-flow.
Please can any one explain above two options clearly.
Thanks in advance,
ramnaresh.

Hi Ram,
A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
A non-cumulative key figure is modeled in BI using the corresponding field for the non-cumulative value change or the corresponding fields for inflows or outflows. You can determine the current non-cumulative or the non-cumulative at a particular point in time. You can do this from the current, end non-cumulative and the non-cumulative changes and/or the inflows and outflows.
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 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.
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, quantity) as the non-cumulative value.
For Additional Information about non cummilative keyfigures plese go through these links:
Non-Cumulatives: [http://help.sap.com/saphelp_nw70/helpdata/EN/8f/da1640dc88e769e10000000a155106/content.htm]
Non-Cumulative Key Figures:[http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a62ebe07211d2acb80000e829fbfe/content.htm]
Modeling Non-Cumulatives with Non-Cumulative Key Figures:[http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a62dee07211d2acb80000e829fbfe/content.htm]
Regards,
Rajkandula

Similar Messages

Regarding Non-Cumulated Key figures

Dear All,
I wanted to create Multiprovider which includes infocube having Non-cumulative key figures .When I am including that Non-cumulative key figure in the Multiprovider , I am getting an error "Inconsistencies were found when checking MultiProvider ZMULTIPTP"
detail fo this error is
Define the characteristics of the validity table for non-cumulatives
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.

Hello,
See this Validity table for non-cumulatives in a self defined cube
Thanks
Chandran

HT2534 Regards none payment option

Respected Sir,
none payment option is not showing in my account.Please need your support to donwload free apllication,my user id xxxxxx.I'm waiting for you kind response in my favour.thanking you
<Edited By Host>

Welcome to the Apple Community.
I have asked for your email address to be edited out. Post your address in an open thread is a sure way to be bombarded by unwanted email, remember it will be here long after you have resolved your problem, for automated detection software to find.
If you want people to contact you, enable others to see your email address in your profile.
Open iTunes and navigate to the app store. Select a free app to download. A simple way to do this is to scroll down to the top free apps box on the right hand side, hover your mouse over the first item and click on the free button that appears when you hover over it.
A pop up will open asking you to sign in with your Apple ID click "create new account", click continue to create your account. Check the box to accept the store terms and conditions and click continue.
Enter your email address, password, security question, and date of birth, click continue. Now, you will be asked to provide a payment method. Note now that the last option says "none".

Regarding Non cumulative key figure

Hi Friends,
While we are doing Inventory mgmt we use three data sources.
1) 2LIS_02_BX - why it is used?
( As far my knowledge is concerned This is Used to extract an opening stock balancce means when ever we are implementing the inventory for client then we need to load the historical data )
2)2lis_02_BF - why is it used?
(It is used for material movements How it can be used.I studied some where this is also used for material movement how is this discriminate from above data source)
3)2LIS_02_UM - Why is it used?
Are we using really?
Please explain me?
Thanks & Regards,
Ramnaresh.P.

From help.sap.com
2LIS_03_BX3 Material stock
2LIS_03_BF Material movements
2LIS_03_UM Revaluations
The first DataSource (2LIS_03_BX) is used to extract an opening stock balance on a
detailed level (material, plant, storage location and so on). At this moment, the opening
stock is the operative stock in the source system. "At this moment" is the point in time at
which the statistical setup ran for DataSource 2LIS_03_BX. (This is because no
documents are to be posted during this run and so the stock does not change during this
run, as we will see below). It is not possible to choose a key date freely.
The second DataSource (2LIS_03_BF) is used to extract the material movements into
the BW system. This DataSource provides the data as material documents (MCMSEG
structure).
The third of the above DataSources (2LIS_03_UM) contains data from valuated
revaluations in Financial Accounting (document BSEG). This data is required to update
valuated stock changes for the calculated stock balance in the BW. This information is
not required in many situations as it is often only the quantities that are of importance.
This DataSource only describes financial accounting processes, not logistical ones. In
other words, only the stock value is changed here, no changes are made to the
quantities. Everything that is subsequently mentioned here about the upload sequence
and compression regarding DataSource 2LIS_03_BF also applies to this DataSource.
This means a detailed description is not required for the revaluation DataSource.

Archive Stock Cube with non-cumulative nature

Hi All,
I have been trying to archive the Inventory (Stock) Infocube as we have more than couple of hundread million records in the cube and it is taking long time to execute query.
I know how to acrive the regular cubes and DSOs, but I couldn't find any helpful documentation where I can know how to archive the Infocube with non-cumulative nature or containing Marker update.
Can anyone pleaes post the link of document?
BTW, we are using BI7.0 SP15
Thanks,
Dhaval

Hi,
There are two ways of archiving data from a non-cumulative InfoCube - time slot archiving and archiving with selection characteristics.
Time slot archiving (recommended)
As an archiving method, you must choose for a non-cumulative InfoCube, time slot archiving for the time reference characteristic. When you recreate an archiving object for a non-cumulative InfoCube, this characteristic is also suggested by the system.
Only archive non-cumulative changes up to a specific point in the past. This reduces the volume of data in the InfoCube. The marker (= end non-cumulative) remains unchanged.
In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements Only option.
You are only able to archive the marker if you also archive all of the non-cumulative changes. Subsequently, the contents of the non-cumulative InfoCube are archived completely. In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements and End Non-cumulative option.
You must archive the non-cumulative changes (for all times) first, and then archive the marker in a separate archiving run, so that the non-cumulative changes and the marker are stored separately in the archive.
The advantage of time slot archiving is that archiving runs can be carried out periodically using a single variant with a relative time restriction. The alternative archiving method described below does not have this advantage.
Archiving with selection characteristics
In some cases, archiving based only on time slots does not have the required effect of reducing the volume of data in the InfoCube. This is the case, for example, if the non-cumulative bearing objects are subject to high fluctuations, meaning that data is constantly being loaded for new objects and old objects are made obsolete. With time slot archiving, the end non-cumulative remains for all objects until all of the data in the InfoCube is finally archived, even if all the non-cumulative changes for an object have been archived already.
In this case, you want to archive and delete completely any objects that are no longer active in the InfoCube. This means archiving the marker as well. For other objects that are still active, you only need to archive the non-cumulative changes from the past, which means the marker is retained.
When you define the archiving properties for a non-cumulative InfoCube, do not therefore choose the time slot archiving method. Instead, select individually the characteristics that are relevant to restricting archiving runs. The time reference characteristic should also be included in this selection whenever possible.
Using this archiving method, for each archiving run, you need to create selection conditions in a variant. In the variant for the archiving run, in addition to the selection conditions, you can also specify for the selected characteristics whether or not non-cumulative changes and marker data is archived. If you choose to archive marker data, be aware that the time selection contains the maximum value for time.
Please refer to the below link to archive the data for Stock Cube:
http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/c219fe9a46194aa66d55254fdab182/frameset.htm
Hope this helps.
Regards
Tanuj

KF creation - Non-cumulative value with NCUM value change - option

What is the use above option in the KF creation?
Thanks

Hi,
A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory.
If you use non-cumulative key figures, an absolute non-cumulative value (the marker) and all non-cumulative value changes are saved in the fact table of the InfoCube. In this way, the retention and volume of data in the data loading process is optimized. A data record is then only loaded to the InfoCube if a non-cumulative changes because of a transaction. Non-cumulatives can then be evaluated at any time in queries, using non-cumulative key figures.
Pls chk this links;
http://sap.seo-gym.com/inventory.pdf
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Reagrds
CSM Reddy

Aggregates on Non-cumulative InfoCubes, stock key figures, stock, stocks,

Hi..Guru's
Please let me know if anybody has created aggregates on Non-Cumulative Cubes or key figure (i.e. 0IC_C03 Inventory Management.)
I am facing the problem of performance related at the time of execution of query in 0IC_C03.( runtime dump )
I have tried lot on to create aggregate by using proposal from query and other options. But its not working or using that aggr by query.
Can somebody tell me about any sample aggr. which they are using on 0ic_c03.
Or any tool to get better performance to execute query of the said cube.
One more clarification req that what is Move the Marker pointer for stock calculation. I have compressed only two inital data loading req. should I compress the all req in cube (Regularly)
If so there would be any option to get req compress automatically after successfully load in data target.
We are using all three data sources 2lis_03_bx,bf & um for the same.
Regards,
Navin

Hi,
Definately the compression has lot of effect on the quey execution time for Inventory cubes <b>than</b> other cumulated cubes.
So Do compression reqularly, once you feel that the deletion of request is not needed any more.
And ,If the query do not has calday characterstic and need only month characterstic ,use Snap shot Info cube(which is mentioned and procedure is given in How to paper) and divert the month wise(and higher granularity on time characterstic ,like quarter & year) queries to this cube.
And, the percentage of improvement in qury execution time in case of aggregates is less for non cumulated cubes when compared to other normal(cumulated) cubes. But still there is improvement in using aggregates.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Non-Cumulative KF data loading

Hi,
I have to copy the data from a non-cumulative cube to it's copy cube(Created using the copy cube option). I have created the DTP and directly loaded the data to copy cube.
When i compare the data between these two cubes, it is not same for the non cumulative key figures.
How can i load the data to overcome the data mismatch. Any special care to be taken to load the non-keyfigure values. (i can see one extra option in DTP i.e 'Initial Non cumulative for Non Cumulative values', i tried this, but it is loading only non cumulative values, other keyfigure data is not loading).
Regards,
Vishnu

Hi,
1) Determine in which way you wish to evaluate the non-cumulative value. If you only wish to evaluate the non-cumulative, or the non-cumulative changes as well as the non-cumulative using a particular time period, choose modeling as a non-cumulative value with non-cumulative changes. If you also want to evaluate the inflows and outflows separately, then choose modeling as a non-cumulative key figure with inflows and outflows.
2) The non-cumulative change, or inflows and outflows, which you require for the definition of the non-cumulative value, must already be created as InfoObjects if the non-cumulative value is created. Therefore, firstly define either the non-cumulative change, or the in- and outflows as normal cumulative values where necessary. These key figures must correspond to the non-cumulative values, which still have to be defined, in the type definition. The non-cumulative changes, or inflows and outflows, must have u2018summationu2019 as aggregation and as exception aggregation.
3) Define the non-cumulative value by assigning to it the previously defined non-cumulative change, or in and outflows.
For more info on Non-Cumulative KF go through the below link
http://help.sap.com/saphelp_bw30b/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/content.htm
Regards,
Marasa.

Maintaining non-cumulative values in Mlti provider

Can we maintain non ucmulative values inteh multi ptovider Extras - > Maintain non cumulative values section.
I created few new cubes which has non cumulative keyfigures . In the cube I made 0CAL DAY as reference characteristic and selected Company code (0COMP_CODE) and Posting date in the document (0PSTNG_DATE) as characteristics of validity table for non-cumulatives.
Now I inlcude the new cubes and identified the non cumulative key figures in the multi provider.
Now here also do I need to make 0CAL DAY as reference characteristic and selected Company code (0COMP_CODE) and Posting date in the document (0PSTNG_DATE) as characteristics of validity table for non-cumulatives.I did not find an option in Extras - > Maintain non cumulative values in multi provider. CAn we maintain non cumulatives in MP ?

Hello,
You dont need to maintain it at the MP level also.
Non-cumulative parameters are manitained only at the cube level.This was the case in 3.x so it should be the same in 7.0 also.
Regards
Ajeet

"initial non-cumulative for non-cumulative values" is not available in DTP (0AFMM_C02)

Hi Experts,
We are working for BI implementation for AFS Industry,
when we are working on AFS specific inventory cube 0AFMM_C02 , we are facing stock mismatch problem
for AFS Stock initialization we are using the data source 2LIS_AF_STOCK_INITALIZATION instead of 2LIS_03_BX, this data source is specificly designed for AFS
when we are extracting the data using 2LIS_AF_STOCK_INITALIZATION for stock initialization and
2LIS_03_BF data source to load the Moments.
we compressed cube with Marker update for 2LIS_AF_STOCK_INITALIZATION data load(by deselecting the No marker update check box)
we compressed cube with No Marker update for 2LIS_03_BF historical data load(by selecting the No marker update check box)
we compressed cube with Marker update for 2LIS_03_BF Delta data load(by deselecting the No marker update check box)
Now we are facing stock mistach problem, we found reason for this
"initial non-cumulative for non-cumulative values" option is not available in DTP only Delta & Full options are available
and infopackage of 2LIS_AF_STOCK_INITALIZATION data source also has "Full update" instead of "Generate Intial Status"
Please let us know how can we get the "initial non-cumulative for non-cumulative values" option in the DTP level.
Regards,
Chandra

Hi Chandrakumar,
We are facing the same problem, how do you solve it?
Regards,

Exception aggregation on Non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Maybe a solution with virtual key figures is an option?
Please help me out!
Best regards, Hans de Klein

Reference point in Non Cumulative

Hello ,
What is reference point which is used inventory?
If i compress with Marker update option enabled and
if want to see the values for the previous month after compression will it give the previous month value or how it will be?
Thanks in advance!
Points will be assigned!
Regards
Ram

Hi,
The noncum would not contain any data, but instead would track additions to inventory (inflow) and consumption from inventory (outflow). We use the same concept on AR for debits and credits to have a balance at a specific date.
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
Have a look at the help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Go through these.
Re: Types of non-cumulative keyfigures
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
non-cumulatives KF in reporting
Re: use of non cumulative keyfigure
Re: When do we use Non-Cumulative values?
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Check this very useful docu.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
Reg
Pra

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 Datasource - Initialization Indicator/flag

Hi all,
I've read in one of the documentation for Non cumulative keyigures (eg, stock handling) that the flag which indicates the datasource as Initialization datasource comes from OLTP.
Which is that field?
In a flat file datasource, this option is available but
how to do the same with OLTP datasource.
I want to create a generic datasource for the purpose.
How will I indicate that this datasource is to be used for initialization so that the infopackage will have
"Create Opening Balance" option.
regards
Anoop

Hi Klaus,
Thanks for the reply. Infact, I've found out this myself after some research and I saw your reply when I was posting this question.
Will there be any other settings required other than this field. What are the consequences of changing this value in the table directly?
regs
Anoop

Cumulative and Non Cumulative Keyfigures

Hi,
What are Cumulative and Non Cumulative Keyfigures..? and
what is the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
Can you please tell eloborately?
Regards
Naresh.

Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,

Regarding Non cumulative options

Similar Messages

Maybe you are looking for