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

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 Data Model

Can I have a combined Inventory Management Snapshot and Non Cumulative? By this I mean as follows:
1. Use the Business Content model to load to the Inventory Management (0IC_C03) cube on a daily basis (loading delta from 03_BF and 03_UM)
2. Create a Snap Shot model which is loaded on a monthly basis using 03_BF and 03_UM
Thanks

Hello Niten,
Absolutely. You can use these two scenarios in combination. In fact, it is highly recommended to use snapshot scenario in combination with non-cumulative model and not as a stand alone solution.
But you need to evaluate the business requirement before taking the decesion of going with combined solution. Snapshot scenario is used to improve the query prformance.
Regards,
Praveen

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

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.

Inventory Management - SnapShot Cube

Why am I not able to load the Stock Init extractor 2LIS_03_BX into the SnapShot Cube? Thanks

Hi,
The Diagnosis says:
This InfoSource is specifically set for the initial run of non- cumulatives. Only certain non-cumulative key figures are therefore displayed in the update rules.
If you donot have any Non Cumulative KF in the cube you can not use 2LIS_03_BX.
With rgds,
Anil Kumar sharma .P

Inventory Management: Snapshot ODS 2LIS_03_UM

In the How to guide the Update rule from 2LIS_03_UM for the Key Figure refers to:
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
ELSE.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 4.
ENDIF.
Is there only an error in the comment (duplicated) or is it that we only need one of the statements? Thanks

hi Niten,
returncode = 0 will update, returncode = 4 not update,
seems duplicated, comment will impact nothing to the program/routine.
hope this helps.

Inventory management: non-cumulatives VS. snapshots

In the How to Handle Inventory Management Scenarios in BW, I read that (p. 2):
- Inventory management with non-cumulative key figures is better when "90 percent of all materials were moved 1 time in the month";
- Inventory management with SnapShots is better when "90 percent of all materials were moved 1 time in the month".
I think the second sentence is not correct. But what can be the right number of movements to be considered?
Thanks a lot,
Davide

Hi Ajay,
so my next question is:
Besides the time granularity needed (daily-level vs. monthly-level), is there a threshold for the number of movements, that could be used to choose one of the two models?
I mean, if materials are moved on average e.g. less than 10 times per month, the non-cumulative architecture could be best one. While if there are more than 10 times per month, the snapshot architecture could be more appealing. In this example, 10 movements per month is the threshold.
Cheers, Davide

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

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

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 management with SnapShots

Hi
I've got this document, "How to handle inventory management scenarios in BW".
It's generally very clear, no problem to understand the standard solution (0IC_C03, non-cumulatives).
But I really didn't understand the explanation about Snapshot on the monthly positions.
So I ask someone to explain how does the concept work.
Example:
The document refers to material movements in 01.2004 and 03.2004.
Question 1:
What are the values posted to the DSO and to the InfoCube after initial load (after the first load of datasources BX and BF/UM) ???
Will we have registers to 01.2004, 02.2004, 03.2004 and 12.9999, both in the DSO and in the InfoCube ?
How does month 12.9999 work?
Question 2:
What are the values posted to the DSO and to the InfoCube after the second BF load?
Let's suppose 2 movements in 04.2004 and 2 movements in 05.2004.
Will we add registers to 04.2004 and 05.2004 both in the DSO and in the Cube?
Thanks in advance.
Cesar Menezes

Hi Cesar,
Not sure if this could be helpful.. but still sharing..
http://www.biportal.org/discussion_forum?mode=MessageList&eid=350671
As even I want to understand differences between 2 methods.. Snapshot and 0IC_C03 (non cumulative)
Could you find any leads?
Regards, Vittali

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

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).

Inventory Management SnapShot model

Similar Messages

Maybe you are looking for