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

Similar Messages

Inventory management snapshot model using Datamart Interface

Hi,
We have implemented Inventory management NON-CUMULATIVE scenario.
Now for reporting needs we are adding snapshot model and trying to use datamart interface to fill up snapshot cube.
But how to get value of KF say "ZTOTALST" becuase NON-*** cube has only changes stored as "0RECTOTSTCK" and "0ISSTOTSTK". If anyone has implemented or has any ideas on using snapshot model with datamart interface , please help .
regards,
Daljit Boparai

Try out with this
http://help.sap.com/bp_biv335/BI_EN/index.htm
Regards
Kumar

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

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.

[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

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 SnapShot Cube and Daily Load Cube

Our requirement from the snapshot cube is to provide queries which show end of month balances similar to as what is shown if I run queries from the Standard daily cube (0IC_C03).
The scenario is as follows:
Query requirements are to show ending balances for the period:
Details are as follows
1) I create a query based on the 0IC_C03 cube, the characteristics are say for example plant and fiscal period and the key figure is Quantity Stock
The results will display the balance at the end of each period so for example
The Key Figure in this cube is non cumulative and is 0TOTALSTCK
Period: 01 Quantity: 0
Period: 02 Quantity: 5
Period: 03 Quantity: 8
Period: 04 Quantity: 2
Period: 05 Quantity: 2
Period: 06 Quantity: 2
Period: 07 Quantity: 2
2) I create the same query off a version of the SnapShot cube as defined in the How to Inventory guide
The results displayed are the movements (changes)
Period 02 Quantity: 5
Period 03 Quantity: 3
Period 04 Quantity: -6
Has anyone got a solution so that I can have the same result set for example 2 than what I get in example 1?
At the moment the approach I plan to take is to datamart 0IC_C03 and work with the cumulative key figures which are used in 0TOTALSTCK. I would like thoughts on this approach and solutions otherwise. Thanks

hi
You have to compare the exception aggregation set for every key figure and the defined time charecterist
Regards
N Ganesh

Inventory SnapShot ODS

The key figures which are defined in the How to Inventory guide for the SnapShot ODS are overwrite or addition? Thanks

As i understand it is addition, load source is 2lis_03* as in the cube, the thing is to have a picture of stock at end of each period

Snapshot Inventory Management with Cummulative key figures

Experts,
We are implementing the snapshot model in parallel with the Daily cube. When trying to create the update rules from 2LIS_03_BX, we get a warning message saying 2lis_03_bx is setup for noncummulatives only followed by an error stating that there are no key figures in the cube.
How do we circumvent this issue?
All thoughts appreciated!

Pls go though below link which will help you to implement snapshot Inventory " How to handle Inventory"
https://websmp108.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002121282004E
Regards
Sangita

Inventory Modelling

I am looking to finalise on an inventory model which will include using the standard inventory 03 extractors. The details are as follows:
1. I will load a version of the 0IC_C03 daily cube as per description in the How to guide
2. The snapshot model does not give me end of balance values which we require
3. I will build an alternate to the snapshot model, which will not include a load from the BX extractor since I have another source which will allow me to provide total stock balances represented as end of period (as per client requirement) and I will load these key figures up until the last period. We will call this key figure total stock and we will assume that the load has been successful and I have been able to load total stock values up until the last period
4. I now plan to datamart the daily load cube and from this load to my alternative to snapshot scenario. I will load the Issuing and Receiving Total Stock into two seperate kf respectively from current period (at the end of the period) onwards
5. My idea from this point is that I will need to either write a formula or routine to populate the Total Stock key figure by adding the sum of Issuing and Total Stock to the value which is in the Total Stock Key figure for the last period. I would need help in establishing this process
General thoughts on this approach and any flaws issues to be aware of. In terms of Data marting from 0IC_C03 as far as I am aware the issue is with Non Cumulative KF which in this case will not be referenced
My thoughts otherwise
1. If this model is suitable should I load to ODS prior to cube and if so why
2. How do I establish 5 above?
3. Is there a better alternative?
Thanks
Message was edited by:
Sorry but any thoughts on this? Thanks
Niten Shah
Message was edited by:
Niten Shah

Hi Roberto,
You are right but the problem that we have is that the Non Cumulative will be calculated at query run time rather than part of the load process, this is what we are having the problem with.
I am aware that I can build a query and run a program or use APD to try and extract the data, I would rather if feasible include it part of the model
Thanks

Loading to Inventory Management Snapshot ODS and Cube

I am trying to develop an Inventory data model and have already created and loaded to the Inventory Management (0IC_C03) cube.
I have now created a Snap Shot ODS and Snap Shot cube, is there a way that I can load to these objects without having to do a re-init? Thanks

Hello Niten,
There is no need to do re-init, you can load the data into non-cumulative and snapshot targets in parallel. Through sam infopackage with which you are loading to 0IC_C03, load to snapshot targets also.
Regards,
Praveen

Inventory Book Monthly snapshot

Hey Team,
I bring in MARD data on 9/30/2008 which gives me an inventory snapshot for the end of month.
how do I get these snapshots everymonth...
meaning...is there a delta method I can use/write an FM on..
or do a full load at the end of each month.
thnx
tb

Hi
You have to implement 2LIS_03_BX and 2LIS_03_BF. There is a detail HowTo document availalble to guide you on using the snapshot vs cumulitive methos. Search SDN for the mentioned datasources to get a link to this doc.
Regards

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

Business Content Inventory Management (0IC_C03) Cube

I am thinking of adding a data staging ODS to our Inventory Management model. However, I wanted to check whether the delivered cube 0IC_C03 is aggregated or whether it is a representation of the R3 extraction. If the latter is the case I do not see the purpose of an additional ODS layer. Could anyone pass their thoughts? Thanks

hi Niten,
check oss note 581778-ODS capability of extractors from Inventory Management
Symptom
Data is not updated into the ODS when you load certain data records of the 2LIS_03_BF extractor.
Other terms
ODS, 2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 0STORNO, ROCANCEL, RODMUPDMOD, 0RECORDMODE, Inventory Management, 0IC_C03,
Application 03, Logistics Extraction Cockpit, LBIW
Reason and Prerequisites
The 2LIS_03_BF extractor does not return any "connected" after and before images, as in the SD extraction, for example.
Originally, the extractor was only designed for updating into an InfoCube. The extraction method was converted from the "D" delta process to "ABR1" with PI 2000.1 patch 4, or PI-A 2000.1 patch 4 so that it could be updated into an ODS object (see notes 322303, 385703 and 323811).
If documents are canceled in Inventory Management, a new document is generated (new document and item number).
This type of operation is transferred into BW with the "ROCANCEL" field set to 'X'. This results in the necessary inversion of quantities or value key figures. A new record is generated for this in the ODS (the "preceding document" has another key).
Example:
ODS key: Doc.
Movement data:
Document   Item    Document year   Movement type     Qty     ROCANCEL
4711       1       2002             101              +100
4712       1       2002              102              -100     X
ODS contents:
Document   Item.   Document year   Movement type    Quantity
4711       1       2002             101                 +100
4712       1       2002                                   -100
The "Movement type" field was set to "initial" in the data record for document "4712" by the processing during the ODS update.
Document 4712 is a before image (0RECORDMODE = 'X') for the ODS. Therefore, this data does not arrive in the ODS. Nevertheless, the before image (document 4712) does not have any context with the after image (document 4711) because there are different keys (document/item/document year). The SAP R/3 inventory management controls these activities with new material documents and (reversal) movement types.
BW technology note no. 747037 provides more information.
Solution
You have two options to evaluate cancellations or operations which contain reversal movement types and ROCANCEL = "X" in the ODS:
1. Implement a start routine
Insert the following code into the start routine of your update:
ODS key: Material doc.|Item number|Calendar year
BEGIN******************************
LOOP AT DATA_PACKAGE.
if DATA_PACKAGE-recordmode eq 'X'.
    DATA_PACKAGE-recordmode = ''.
    modify DATA_PACKAGE.
endif.
endloop.
END********************************
2. Change the transfer rules
With the transfer rules, do not assign the "ROCANCEL" DataSource field to the "0RECORDMODE" InfoObject in the InfoSource. As a result, only records with "0RECORDMODE" = ' ' are transferred to the ODS. For the ODS, the after images whose characteristics or key figures that are set to overwrite, are not deleted.
Other special features when updating the extractors of the inventory management into ODS objects:
1. 2LIS_03_BF and 2LIS_03_UM
a) ODS capability
For more information, see notes 322303, 323811 and 385703.
b) Key creation
For 2LIS_03_BF, see note 417703.
The following keys are available for 2LIS_03_UM:
1. MCMSEG-BUKRS
2. MCMSEG-BELNR
3. MCMSEG-GJAHR
4. MCMSEG-BUZEI
Field no. 4 is not delivered as standard in the extract structure, but it can be added using the Logistics extract structures Customizing Cockpit.
Field no. 1 may not be included in the relevant organizational structure.
2. 2LIS_03_BX (up to and including 3.0B 2LIS_40_S278)
The dynamic stock calculation from stocks (2LIS_03_BX) and movements (2LIS_03_BF) is only possible with (non-cumulative) InfoCubes.
Using ODS technology is only useful in this context for:
- an Enterprise DataWarehouse layer
- the realization of a snapshot scenario:
See the How to paper for this topic at:
-> http://service.sap.com/bw
-> left navigation area: SAP BW InfoIndex
-> info index: N ("Non-cumulatives") ->
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Use note 773823 to update the 2LIS_03_BX InfoSource into an ODS.
Note also that you cannot update any key figures into an ODS object (see notes 752492 and 782314).

Modelling Issue

Hi,
We have account receivables datamodel, wherein the histroy cube is updated weekly in Finance application.
As we are updating this every Sunday, it may or may not fall on the end of the month/ end of period.
Example:
suppose if the weekly load happens to be on 28 th of the month, then the next load will be on 4th of the next month. And in this process the posting period has been ended on the end of the month.
As the weekly snapshots were gathered correctly but when it comes to the end of the month this cube is not upto date.
what can be done inorder to get the snapshot of end of period/end of month in a weekly snapshot model..
we are against creating one more cube for the monthly snapshots..

Hi Veerendra,
Inlcuding a monthly dataload request in a weekly snapshot report hinders the very purpose of weekly snapshot cube as it has chronological data weekly and at the end of month you have monthly dataload request.
This is tircky situation for us. As we have developed whole model considering weekly snapshot scenario ( We wanted to compare the progress/status of Accounst receivables and this comparing is no longer possible if you include the monthly dataload to the same cube)
We want to retain the weekly snapshot datamodel and somehow want to include the monthly data update which seems like impossible with out a new monthly cube.
if there are any tricky way then pls let me know..

Inventory SnapShot Model

Similar Messages

Maybe you are looking for