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

Similar Messages

To load non cumulative cube initialize opening balance in R/3. explain?

To load non-cumulative cube i have to initialize opening balance in R/3(S278). please elaborate and what is S278 means is it LIS datasource please explain?
Thank you,
York

Dear all,
The data source 0EC_PCA_1 doesn't consider the opening balances i believe, can any experts help me solve this problem.
Regards,
M.M
Edited by: Magesh Magesh on Jun 26, 2009 2:55 PM

How to set Non Cumulative Init flag for Generic datasource

Hi all,
I need to create a generic datasource which can be used to initialize the Non Cumulative Cube. Eg. setting the opening balance.
The STOCKUPD field in the ROOSOURCE should be set to X so that the infopackage will have the "Generate Initial Status" option. But there is no interface available in R/3 pluggin to do this.
How can this be done? Or is it not allowed for generic datasources as it is only valid of 2LIS_03_BX datasource
for stock updation.
Will there be other issues if I change the table entry for STOCKUPD in roosource table for my datasource?
regs
Anoop

Hello,
any idea on this?
regs
Anoop

Non-cumulative initialization is not possible with historical data

Hi all,
While loading inventory cube.. 0IC_C03 .. after loading 2LIS_03_BX request get sucessful. while compress that request No Marker update. i getting following error msg.
Non-cumulative initialization is not possible with historical data
Regards
siva.

You sure you didn't use BF instead of BX? This messge indicates that you have historical data in your cube whereas BX only loads a fixed state at a specific point in time... Or maybe, did you initialize BX twice in R/3 without deleting the previous init, I don't know if that could cause that error but it's another possibility.

Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

Hello all.
I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures. I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
Steps I followed:
1. Ran initialization of beginning balance with 2LIS_03_BX
2. Ran the historical job with 2LIS_03_BF
3. Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
4. Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
Now, to this point, everything was fine. Quantities were as expected. Dollar values were as expected. The problem occurs once I load deltas:
5. Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
Query example:
MATERIALA:
Initial Stock Balance = 1000 EA
Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
Now, I have the record in BW showing the stock issue of 150. However, the non-cumulative key figure within the query still shows 1000. And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance. It is like it is not recognizing the updates.
Any help would be appreciated.
Thanks,
Brent

Hi!
Here is what helped in my case, very similar to your:
In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

Unable to compress non-cumulative infocube with 0DOC_NUM

Hi Gurus!
I'm working on a retail project. I've created an infocube based on 0RT_C01 to keep the stock movements. It is a non-cumulative cube.
After the load of the initialization data (2lis_03_bx) ,historical movements, the initialization of 2lis_03_bf, the daily delta loads take about 10-11 hours to complete.This is because the cube has not been compressed due to the existence of infoobject 0DOC_NUM. 0DOC_NUM is of the lowest granularity and so compressing on 0DOC_NUM will not yield any performance benefits. But this has impacted the performance of daily delta loads. Also,the report that uses this cube take about 3-4 hours to open initially.Sometimes a timeout occurs.I've checked in ST22, ST21 and no errors or dumps appear.
Is there anything I can check to speed up the process?
Thanks!
Lucia

Hi,
Compressing the request containing the opening stock that was uploaded. Make sure the "No marker update" indicator is not set. Please consider note 643687 ,before you carry out the compression of requests in stock Info Cubes!
After successfully uploading the historical material movements, the associated request has to be compressed. You must make sure the "No marker update" indicator is set. This is necessary because the historical material movements are
already contained in the opening stock.
Regards,
Suman

Why we need to unload non-cumulative

Dear all,
why we need to unload non-cumulative cube. what are the step needed?
Thanks
V.G.VG

Hi,
Non-cumulative key figures are not summarized: examples are head count, inventory amount;
These are always in relation to a point in time; for example we will ask how many employees we had as of last quarter. We don't add up the head count.
Steps to load non-cumulative cube:
1. Initialize opening balance in R/3 (S278).
2. Activate extract structure MC03BF0 for datasource 2LIS_03_BF.
3. Setup historical material document in R/3.
4. Load opening balance using data source 2LIS_40_S278.
5. Load historical movements and compress without market update.
6. Setup V3 update.
7. Load delta using 2LIS_03_BF.

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.

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

Non-cumulative infocube in Infoset: Inventory

Hi Experts,
I have a requirement to combine a infocube and DSO under Infoset. But the Infocube is non cumulative and is not allowing to add in infoset.
Any solutions for this?
My Infocube is customised and have 3 datasources: 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM
And my DSO contains the alternate UOM with a single datasource: 0MAT_UNIT_ATTR
My Ultimate aim is to bring the alternate UOM.
Please post your suggestions.
Thanks,
Guru

Hi Nirajan,
First of all as I undestood 2LIS_03_BX is the initial upload of stocks, so there is no need of delta load for this datasource, it collects data from MARC, and MARD tables when running the stock setup in R3 and you ahve to load it just one time.
If between delta loads of 2LIS_03_BF you're loading full updates you are dupplicating material movements data, the idea of compression with marker update is that this movements affects to the stock value in the query, it's because of that when you load the delta init you do it without marker update because these movements are contained in the opening stock loaded with 2LIS_03_BX so you dont want to affect the stock calculation.
You can refer to the How to handle Inventory management scenarios in BW for more detail on the topic.
I hope this helps,
Regards,
Carlos.

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

Non-cumulative values

HI All,
when I run a query of a non-cumulative infocube,there's always a "initial record" which actually doesn't exist in the fact table. Documents say "This entry does not remain physically in the table, but it is available for rebuilding the non-cumulative values". So where exactly is the initial value stored ?
Thanks
han.

Hi,
What is teh DataSource and InfoCube?
If you are talking about 0IC_C03, please see the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
See about Non-Cumulatives
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
Thanks
Reddy

Inventory Management (Non-cumulative values)

Dear experts,
I want to extract inventory data from 2LIS_03_BF.
How do I have to configure the Key figures; for example: 0VALSTCKQTY. Is there a need to use Non-cumulative value with in- and outflow as in Content.
Which other possibilities exist?
After InfoObject config. - what are the exact next steps?
Do I load data from the 3 DataSources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM into one DSO first and then into one cube or do I have to split?
I dont want to use the BC data flow.
Thanks for your advice.
Patrick

hi,
Please search the Forum for this, this has been discussed many times.
regards,
Arvind.

Define the Characteristics of the validity table for non-cumulatives

Hi Friends,
Here I am designing MultiProvider ( ZCA_M01), based on the Two Business content info cubes (0IC_C03 & 0SD_C03 ) & one customized info cube (ZPUR_C01).
I done Identification for char & keyfigures also.
When i trying to activating the Multiprovider, here i am getting the error , error message is : Define the Characteristics of the validity table for non-cumulatives.
Even here I am attaching the error message help also.
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.
Please take as a high priority.
Thanks & Regards,
Vanarasi Venkat.

Hi Venkat,
If you want to include 0IC_C03 cube in your multi provider the you must make sure that the time characterestics ( 0CALDAY, 0CALMONTH ....) are present in all of the other info providers which you are including in the MP. The Time char to choose depends upon the Inventory cube in which you have mentioned during the definition. As you are using the standard cube 0IC_C03 it has the time char as 0CALDAY. Try to include this in all the other info providers and dont include more tha one Non-cumulative in the MP.
Try this and see if it helps....

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

Non Cumulative Datasource - Initialization Indicator/flag

Similar Messages

Maybe you are looking for