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.

Similar Messages

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.

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

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.

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 Management Scenario

Hi BW Experts,
I was working on the Inventory Management screnario as in How to Handle Inventory Management Scenarios in BW with cumulative KFs. I read many of the forum postings but I am still little bit confused about the sequence of the loading. As per my understanding, BX goes to 0IC_C03 bus. content cube and snapshot ODS. BX load in 0IC_C03 is compressed. Then BF and UM goes to snapshot ODS, snapshot infocube and 0IC_C03 (initilized for Delta). Then the generic extractor from snapshot ODS goes to snapshot infocube as monthly load and also to ODS itself. Now the questions are:
1-) Is the sequence above correct? If not could you pls. explain? What are reasons behind of this?
2-) What are the functions of these objects exactly, in detailed? How do you validate data (by comparing 0IC_C03 and snapshot cube)?
3-) Why the generic extractor goes to infocube and ODS together, what is the reason?
4-) Is snapshot infocube loaded with BF and UM as delta daily? After initialization am I going to load the snapshot infocube every night or just the 0IC_C03?
5-) Do I have to put 0CALDAY into Agg. Ref. char. in the maintenance screen of the defined custom KFs (Z* keyfigurs for this scenario) or just in the report enough?
6-) Are the routines working correctly except for
diff_month(2) type i-> "i" is going to be changed into "n"
After I loaded in the above sequence when the bx is loaded into 0IC_C03 cube transferred data records are less than added. What is the reason?
Contributions are highly appreciated. Thanks.
Best Regards,
Message was edited by: John Seker
Message was edited by: John Seker

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

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

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.

How to handle inventory management scenario

Hi All,
In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
Thanks
PB

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

Inventory SnapShot Model

I have built an Inventory SnapShot model as per the How to guide with a few amendments by adding additional characteristics and key figures.
I now need to include the SnapShot cube in a MultiCube with Sales. The problem is that by doing this I will have inconsistencys with the time dimensions since I need to be able to work with Fiscal Periods so as to avoid inconsistencies on the query.
Is there a formula or method which will for example allow me to take Posting Date and convert to a fiscal date? Thanks

Thanks Dinesh,
Currently in the SnapShot cube model we have the following scenario:
1) In the SnapShot model the time characteristics are 0CALMONTH and 0CALYEAR
2) The cube is updated from the SnapShot ODS, the BF and UM InfoSources
3) The SnapShot ODS is loaded from the BX, BF and UM InfoSources
4) The SnapShot ODS only contains 0CALMONTH as the time characteristics which in its Update Rules is mapped either to a date in the future or to Posting Date. Can I therefore add 0FISCPER rather than 0CALMONTH to the ODS and populate with the same routines or in effect does it not matter whether I replace 0CALMONTH since it is in effect populated by posting date
5) Would you suggest that I change my model of the SnapShot cube to include the time characteristics 0CALMONTH, 0CALYEAR, 0FISCPER, 0FISCVARNT or just replace 0CALMONTH, 0CALYEAR with 0FISCPER, 0FISCVARNT and if the first option what should I do with mapping 0CALMONTH, 0CALYEAR the other date field is 0DOC_DATE should I map here
Hope this is clear

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

Posting block Question in How to handle inventory management scenarios

Hi all - I have a question in document
<b>"How to...Handle Inventory Management Scenarios in BW"</b>
can anyone please tell me what a posting block is in this document...
also I did not understood what a Validity table is?
thanks,
Sabrina.

Hi Sabrina!
A 'posting block' period is something that now you are facing in inventory management, but you have to consider it in ALL logistic cockpit flows (what you can see in LBWE).
This requirement can be easily explained in this way: as you know, to fill a setup table you have to activate the extract structure of the datasource for which you want to run the setup job (otherwise the system says that no active extract structure exists, do you remember ?); but, by doing so with the posting operations open (in other words, users can create new document or change the existing ones), you run the risk that these records are automatically included in the extraction queue (or in SM13 if you are using unserialized method) AND also collected in setup table ! And you will have the same records with the initial load (from setup table) and then the same from delta load (from the queue): a nice data duplication.
To avoid this situation, a "posting block" (or a "free-posting period" or a "downtime") is requested. No one can post new document during your setup job...
Hope now is clearer...
Bye,
Roberto

[Schema Design]: How to reduce inventory snapshot table size

We are planning to store inventory level's periodic snapshot at the end of each day. We have close to 50k different products.
But on a given day only 5-6k products inventory changes.
As I understand if I start inserting just the products which have changed inventory, analysis around semi-additive dimension (Quantity) doesn't work properly.
For better understanding, lets take say the fact table looks like:
product_id time_id quantity
1 1 100
2 1 130
3 1 100
1 30 200
So basically, it says product 1,2,3 from time_id 1 to time_id 29 doesn't have any update in quantity. But product_id 1's inventory changes to 200 on time_id 30.
This approach reduces fact table size by approx 90 rows.
My question is, is it a good idea? Would this semi-additive dimension still give the same result (I doubt though)?
If not, then what other approaches I can take?
Thanks in advance.

Another option is to capture just the net changes (sometimes referred to as a journalized fact table). Then you can create a calculated measure that sums all the changes from the beginning of time up to the current time-slice.
This may seem like an inefficient solution, but there are ways to reduce the problem by limiting the history for which inventory snapshots are available. For example, if the business only needs snapshots for the past 90 days, then you can grab a snapshot
of inventory for all products on day 0, and then capture the net changes for each product for days 1-90. Then you can calculate the snapshot in time by adding the baseline snapshot to the sum of all net changes.
BI Developer and lover of data (Blog |
Twitter)

Inventory - Snapshot Scenario

Similar Messages

Maybe you are looking for