Snapshot scenario

Hello,
My inventory cube works quite slowly (1) and work with NCKF is difficult (2) . Thats why I want to create a cube which hold stock for beginning of the month. What do you think about this idea?
For example , i have ods which contains movements. Can I write ABAP cobe that will calculate stock for 1st of each month?

If you haven't already done so then consider compressing the cube.
Also check out the How To Guide for "How to Handle Inventory Management Scenarios in BW"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0ea8a990-0201-0010-2796-fa9ae8691203
This provides a discussion of snapshot vs NCKF.
Cheers Matt
Before compressing the Inventory cube review note
643687 http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000022922003
and
586163 http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000022922003
Message was edited by: Matt Mills

Similar Messages

Inventory Management, New Snapshot Scenario

We are planning to implement the New Snapshot scenario for Inventory Management. This is based on the "How to...." document. As per what is shown in the document, all the 3 extractors feed into the same DSO. However, when I try to create the Update Rules for <b>BX</b>, I get a error that there is no key figure. However, the DSO (Standard) has the Key figures. These are cummulative. Maybe, because of that I get the error when I create update rules for BX. But then, in the document the key figures appear. How is this possible.
Has anyone tried this and has been successful. If so, I'd appreciate if you could send some tips.
Thanks

hello
can you please take a screenshot of your data model and update rules (inside) and send me to (see email in card)
It will really help me!
Alex

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

Inventory Management - Snapshot Scenario

Hi,
We are implementing the Snapshot scenario for inventory management based on the "How to Handle Inventory Management Scenarios in BW" and am facing the problem on the point 51 in the document.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
"51. Create a start routine to multiplicate the old row with minus 1, set the record mode to R Reverse-Image and create a new row with the month 12.9999, if the ...."
the logic seems to be incomplete. Has anyone implemented this scenario. Please let me know what is the missing piece.
Thanks
RK

I am only in design phase. I have post this message because the How to guide is old and I would know if someone have find a new solution ( with less step to reduce development phase).
As not recent solution is provided, I use the how to guide and adapt because I have more indicator to implement in my solution.

Procedures for implementing a snapshot scenario with custom DataSources

Hi Gurus,
I have checked the How To paper ([How to Handle Inventory Management Scenarios in BW (NW2004)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]). However, only SAP standard BW objects are mentioned in the paper e.g. InfoCube (0IC_C03), Material Stock InfoSource (2LIS_03_BX), Material movements IS (2LIS_03_BF) and Revaluations IS (0LIS_03_UM).
On the contrary, I need to handle custom DataSources for the Snapshot scenario. Are there any differences in the implementation methodology? Which additional aspects should I take into consideration? For example, the load sequence, delta type, etc.
Could you please list out the step-by-step procedures for such an implementation?
Thanks in advance!
Regards,
Meng

Hi Meng,
You can approach this in two ways.
1) If the volume of data is not much, you can derive the balance at query level, as follows.
User enters the date, based on this restrict your key figure to display all values less than this date.
2) If the volume of data is high, then you will have issues with performance if you are calculating the balance in the front end. In this case, you can model this with 'Non cumulative' key figure. Again there are 2 ways of approaching this back end solution based on the volume of data. ( Say in one case you have 2 years of history in your DSO and in the second case, you have 5 years of history ).
A) For example, If there are only 2 years of history
Create a non cumulative Key figure 'ZBALANCE' with inflow and outflow, in a cube.
Map this to your credit and debit as + and - respectively and map the calender day to posting date.
Just initialise the dataload with data transfer and start loading the delta as normal.
You will be able to see the balances for each and every calday in your reporting.
This approach is straight forward and simple.
Compress the cube for getting the better performance.
B) If there are 5 years of history and you are not interested in loading all the 5 years data in getting the balance
Here you want to have the initial balance, continue delta and would like to load 2 years of history.
The cube and non cumulative KF are created as mentioned above.
For generating initial balance, you have to create another DSO without calander day and ZBalance mapped to credits and debits in additive mode. Load your DSO data into this new DSO to generate initial balance. This balance will be loaded to your cube as initial balance. ( Like 2LIS_03_BX ).
You have to compress this request with marker update ( Must ).
Load your historical data for 2 years from the original DSO. Compress without marker update ( Must ).
initialise without data transfer from DSO to cube and load deltas normally.
Compress the delta requests normally for performance reasons.
Please read the 'Inventory document' in detail.
Please let me know, if any of the information is still not clear.
Thanks,
Krishnan

Problems Implementing SnapShots Scenario for Stock Management

Hello All,
I am trying to configure the Inventory Management with snapshots and I am using the snapshot scenario. According to the document I have created alternative ODS ODSSNAP and infocubes to accumulate 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
My problem is with the key figures ZTOTALST,ZVALSTCKV and ZVALSTCKQ.
I am facing this problem in the ODS when i try to create the update rule for 2LIS_03_BX. I have the two Characteristics Unit and Currency automatically mapped but i don´t see the key figures of the ODS. I supposed that my key figures may appear without assignment but they don´t appear.
I should have my key figures non mapped but instead I cannot see them.I tried with another standard infosource 2LIS_03_BF and I see my key figures.
I have BW 3.5 patch level 20.
Can you please let me know any ideas?
Thanks
TK

OK, non cumulative are not stored in your provider but calculated on the fly:
NonCum = InFlow - OutFlow.
then you have to work with your good receipts and goods issue flow key figures....
For your scenario, as far as I understood you just need to see a "snapshot" (latest know stock values) you just need to update your receipts and issues with summation in your ODS; your stock will then be calculated.
Usually a "snapshot" scenario means that you want to store your stock at the end of each month for example; in this case you need to use cumulatives with exception aggregation "LAST" on your time period so that the stocks aren't summarized over time. This way you update your cumulative Stk KF is updated with goods receipts - good issues. Also remind that in this scenario you'll have to load the previous month stock into the next
Stock July = Stock June + Receipts July - Issues July.
As you realize, it can get quite complex...
Please precise your requirement and we'll help you further since I am doing all kind of scenario re stocks...
hope this helps...
Olivier.

Snapshot scenario of Inventory

Hi Expert,
While I am trying to create update rules for snapshot scenario of Inventory in InfoCube object
u201CICSNAP1u201D. It will not shows the non-cumulative key figure for those we have to write the update
rules. It only shows the inflow and outflow keys.........
Thanks and Regards
Lalit Kumar

Hi Experts,
Thanks for answer but my problem is something diffrent.
for snap shot scenario for inventory management while creating update rules from infosource 2LIS_03_BF to snap shot infocube
i want to write routine for the non-cumulative key figures i m only getting the outflow and and the inflow infoobject for mapping.
though when i was creating update rules for same infosource and snap shot dso i got all the non-cumulative key figure and their outflow and inflow infoobject in the update rules.
please tell me how to get non-cumulative key figures in update rules.
Thanks and Regards
Lalit Kumar

Snapshot scenario in Inventory Mnagement

Hi Experts,
I just came across the Snapshot scenario in Inventory Mnagement which is used to improve query run time.Can anyone explain the Concept of Snapshot and method of using the same.
Thanks,
Meera

Hi Experts,
Thanks for answer but my problem is something diffrent.
for snap shot scenario for inventory management while creating update rules from infosource 2LIS_03_BF to snap shot infocube
i want to write routine for the non-cumulative key figures i m only getting the outflow and and the inflow infoobject for mapping.
though when i was creating update rules for same infosource and snap shot dso i got all the non-cumulative key figure and their outflow and inflow infoobject in the update rules.
please tell me how to get non-cumulative key figures in update rules.
Thanks and Regards
Lalit Kumar

Inventory snapshot scenario - Data load frequency?

Hi,
I have gone through "How to" document for inventory snapshot extraction.
Here are few questions for which I could not find answers in the document -
1. Process 1 loads initial stock using BX data source into ODS.
2. Then Process 2 - I assume there are two steps in this -
a) Init using BF/UM Data source - If this is done, historical movements get added to initial stock in this ODS, which yields wrong results. So, is mapping to ODS required while doing init from BF/UM data sources? Init(Process 3) adds stock into snapshot cube for all the months from date of movement to current(system) date.
b) Delta using BF/UM Data source - Adding delta to snapshot ODS makes sense. Is it also required to load this parallelly to snapshot cube(as mentioned in process 3)?
No intention to confuse anybody.. Just wanted to know which of the following data load scenario yields perfectly fine results? The document is not self explainatory on this topic -
I assume that, 0IC_C03 is being updated in parallel.
1. Initial stock load using BX datasource into ODS. Then Initialize BF/UM data source into snapshot cube ONLY(Does this actually store historical snapshot?). Then do delta from BF/UM to ODS ONLY. Then follow rest of the steps.
2. Initial stock load using BX datasource into ODS. Then Initialize BF/UM data source into snapshot cube and ODS. Then do delta from BF/UM to snapshot cube AND ODS. Then follow rest of the steps.
3. Initial stock load using BX datasource into ODS. Initialize BF/UM data source WITHOUT DATA TRANSFER. Then start delta into snapshot cube AND ODS.
Any help on this will be greatly appreciated.
Thanks and Regards,
Anup

Hi,
Ensure that the 3 key figures inlcuded in communication structure (of course it will get inluded as it is standard datasource)and when u create the update rules,this 3 key figures will set to no update and then you have to populate the 3 kf's using a routine.
Hope this helps.
Thanks,Ramoji.

Snapshot scenario or non cumulative key figure in inventory management

Hi
We are currently using Inventory Management with non-cumulative key figures but we get very high performance problems due to so big number of lines in info cube.
We are analyzing the other scenario with snapshot and I am asking if it would be very realistic to use it to satisfy our requirement: to be able to get inventory management at day level for about 2 000 000 combinations article-site and about 100 000 stock movement lines per day (we are retailer!).
Is there somebody to give me advice about it?
Tanks a lot
Anne

Being a non-cumulative KF, total stock is automatically takes care of that.
Try putting all the restrictions which you have included for total receipts and total issues, for eg, restrict Total Stock with the movement types used in Receipts as well as Issues.
Check and revert.
Regards
Gajendra

Inventory - Snapshot Scenario

Hi,
I have the data model inventory with detail of the 0CALMONTH in the cube. I have read from the document SAP the scenario Snapshot and I wondered me:
1) when I extract from 2LIS_03_BF and by 2LIS_03_UM every day (the data in BW are up to the preceding day), I have not given future greater of the date of system, therefore in the ODS Snapshot I will always have in 0calmonth 12.9999 (process 2)
2) in the Process 4 before making the loading are FULL in the cube it needs to cancel the data presents in the cube?
3) in the Process 5 (ODS on himself) which the future are movements if in the ODS I always have 12.9999 loaded through the Process 2? What do I have to select in the Infopackage?
Thanks to all those that you/they know me to give a detailed explanation and some example of content in ODS and cube in 2 different months.

You should have a routine between ODS and the infocube to populate the month.
By doing so, you will have snapshots of every month.

Inventory Management SnapShot model

In the How to guide it discusses on how to create a SNAPSHOT model for monthly loads.
Can I create a SNAPSHOT ODS and eliminate the Cube as part of my Data Flow and if so I believe the only change that I need to make is to check the BEx reporting flag in the ODS. Is this correct and are there any possible limitations with this approach? Thanks

Hi Niten,
I read in the document...
"If the SnapShot Scenario is chosen to reduce the Query-Runtime it should be taken in account that for recovery reason and for the ability to retrace the data it is only advisable to run an InfoCube with non-cumulative keyfigures with all the movements in parallel for a certain timeframe. For the administrator it is much easier to avoid, find and repair inconsistencies in the data. Inconsistencies could happen if data in the PSA is deleted and the update-/ transferrules do not fulfill all the EndUser requirements or the coding is just wrong. A reinitialization of all the past data could be necessary. In the SnapShot Scenario the past data is nowhere stored."
Hope it helps!
Bye,
Roberto

Weekly/Monthly Snapshot Report

Hi,
I have now three cubes Daily,Weekly and Monthly cubes...
I had made copy of the daily cubes as weekly and monthly.. There is no difference as such structure wise...
But what extra i need to do to make these weekly snapshot report and monthly snapshot report..
Now all three cubes are added in multiprovider and multiprovider was used in the definition of the query..
For daily cube report though, i had simply restricted infoprovider as daily cube and designed the query..
But what about weekly and monthly snapshot reports?
as snapshot reports are basically meant for comparing time periods how i could achive the same in reporting?
What i am contemplating as follows:
1) Since these are comparing different times ( for weekly snapshot, you must have at least two different weeks of data to compare ) i guess we need to include a time chararistic 0CALWEEK for Weekly snapshot, 0CALMONTH for Monthly snapshot..
But even after including this time charactristic, how i would be comparing?
i am not clear on how to creata a snapshot report
What one has to do in the weekly and monthly cube to be able to compare the data on weekly/monthly basis?

Simran,
Weekly Snapshot means entire data has to restated against each week.
For example to check open orders status week wise, entire open orders(till end of current week) has to restate against current week. at end of the week, need to pass remaining open orders as next weeks snap shot.
In this way we will get snapshoting of open orders week wise. We can use these weeks to compare.
For weekly snapshot add week to cube, and at end of each week pass current week closing balances as next week opening balances + transactions in that Week gives snap shot of that week.
For example Check: [HOW TO HANDLE INVENTORY MANAGEMENT SCENARIOS IN BW (NW2004)|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
Snapshot scenario.
Hope it Helps
Srini

Inventory Management SnapShot ODS

What is the purpose of the SnapShot ODS, in the sense that why can I not just load directly to the SnapShot cube, my understanding is that if I look at the logic for say the total quantity and value key figures in the update rules to the cube this should be able to give me an upto date scenario or am I mistaken? Thanks

Hi Niten,
I am not sure if you are referring to any standard content ODS. But, generally speaking about snapshot scenarios, the advantages of introducing an ODS layer are:
- Overwrite feature
- you can keep data at a very granular level in ODS and create different cubes for different reporting scenarios or aggregation levels.
- additional flexibilty in loading data to cubes due to the introduction ODS.
Hope this helps. If you are looking at any specific case, do write back with details.

Question on "How to Handle Inv management Scenarios in BW" docuemnt.

Hi all,
I read the document "How to Handle inventory management scenarios in BW" and I did not understood what a snapshot scenario is? Can anyone tell me what is the difference between snapshop and non-cumulative scenario's.
thanks,
Sabrina.

In a non-cumulative scenario the current stock of any day (or month) is not stored physically in the cube. Instead the stock values over time is calculated dynamically at query runtime by the BW OLAP engine, which basically derives the stock by summing up the periodic value changes (cumulative inflow and outflow of the non-cumulative key figure), which are stored in the cube (together with a so called stock marker used as the basis of the calclation).
In the snapshot scenario the current stock of any month is calculated in a snapshot ODS and then loaded to a cube. This means that the the stock value is physically stored in the cube in an ordinary cumulative key figure.
Since a non-cumulative cube store value changes and not the actual stock this means that performance might be bad if there are many value changes for each characteristic combination in a month (since the stock is calculated at runtime and many records must be processed to derive the stock). So in this case the snapshot scenario is better since no runtime calculations of the stock need to occur and since only one record, containing the actual stock value will be stored in each month for each characteristic combination having a stock value.
I think you would be better of with an example, but with this explanation in mind looking at the scenarios in the How to again might clarify things...
Regards,
Christian
/ Christian
Message was edited by: Christian

Snapshot scenario

Similar Messages

Maybe you are looking for