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

Similar Messages

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

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.

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

How to impliment inventory Management in BI using BX/BF/UM

Experts !
i have to impliment Inventory management Data flow. i was reading SAP documentation on it, but i fount it bit confusing.
Could you please help me out to undertstand how does these 3 DS works ? and why do we need 3 diff. DS ?
I know , i am asking a big question, and it would be bit tough to explain. but any kind of documentation will help.
i did research , but couldnt find the right way of doing it.
Please give me some thoughts !
Appreciate it.

Hi,
There are 3 DS for IM :-
2LIS_03_BX: extracts stock data from MM Inventory Management for initialization to a BW system.
2LIS_03_BF: extracts material movement data from MM Inventory Management (MM-IM) consistently to a BW system.
2LIS_03_UM: extracts revaluation data from MM Inventory Management (MM-IM) consistently to a BW system.
Maintain the following entries intables of the ECC System:
Table TBE11:
Maintain entry 'NDI' (text: New dimension integration) and u2018BWu2019 and the flag Active.
Also refer : OSS note 315880 & 571669.
Step 1:
Go to transaction RSA5 and activate the 3 DS.
Step 2: Delete Historical Data.
Step 3: Delete Data from setup Tables.
Step 4: Take reqd ECC downtime
Step 5: Stock Initialization : use transaction MCNB for 2LIS_03_BX data source.
Step 6: Fill Setup Tables for 2LIS_03_BF. (U can acces this from SBIW)
Step 7: Fill Setup Table for 2LIS_03_UM
Step 8: Pull Data for 2LIS_03_BX (the "NO marker update" shouldnt be ticked)
Step 9: Pull Data for 2LIS_03_BF.(the "NO marker update" should be ticked)
Successive delta loads should be with marker Updates (No Tick).
Step 10:Pull Data for 2LIS_03_UM.
Hope this helps.
Regards,
Rahul

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

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 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 (Advanced - Marker update)

I have been following your discussion regarding Inventory Management and the use of 2LIS_03_BX and 2LIS_03_BF extractors, and I have also been studying the How to guide on Inventory Management.
I am currently only using 2LIS_03_BF with no data restriction in the setup-run or in the initialization. The stock balance is correctly even though I am not using 2LIS_03_BX (because the sum of all historical movements equals the current balance).
But I am facing performance problems because I am not using compression. I am considering 2 solutions:
Solution A (the easy)
1. Compression on all request (with marker update)
Solution B (as suggested in the How-to-guide)
1. Delete InfoCube data
2. Generate new balance with 2LIS_03_BX
3. Compression of 2LIS_03_BX (with marker update)
4. Reconstruct old 2LIS_03_BF requests from PSA
5. Compression of old 2LIS_03_BF requests (No maker update - because all these will new be considered historical in relation with the newly generated stock balance).
6. Future deltaloads from 2LIS_03_BF and compression (with marker update).
As I see both solutions will solve the problem but A is by far the easiest. I would like your opinion!
When you do the marker update during compression does it matter wether you do it as described in the how-to-guide I can you do it as follows instead:
1. Compression of Historical Movements (2LIS_03_BF) (with marker update)
2. Compression of Stock balance (2LIS_03_BX) (No marker update)
3. Compression of Future Movements (2LIS_03_BF) (with marker update)
As I see the only important thing is that you do the marker update with eitherHistorical Movements (2LIS_03_BF) or Stock balance (2LIS_03_BX), but not both of them or none of them. I am not 100% sure but please give me your opinion.

Hello Thomas,
I have never tried doing the marker update other way around (through BF instead of BX), but I don't see any reason why it will not work. You are right that marker update should be done either with snapshot or material movement as both datasources bring same data at different granularity level. Solution A seems to be simpler and straightforward, but I am not sure if there will be any impact on performance if we update the marker intially with lot of requests from BF instead of a single BX request.
Regards,
Praveen

Database design (ERD )for Inventory Management System

Dear All,
I am going to develop a simple Inventory Management System software using C# .NET for my learning. After searching different forums, many people have suggested to first create a database design for the software. I want a database design, in short, an ERD
diagram for simple Inventory Management System which shows proper entities(tables), attributes and relationship between entities.
It would be highly helpful for me as I am newbie to C# and databases.
Thanks,
momersaleem

Dear Rebecca,
Thanks for you suggestions.
As I am going to develop IMS for learning purposes so I think I wouldn't need to go in detail regarding Customer name and addresses. However, I am still thinking of adding country attribute in customers' table which I think will be helpful to sort out customers.
What's the difference between a purchase and an order? They're usually the same thing, which doesn't mean you're
wrong, but what are you picturing here? Purchase entity will be used to keep record of purchases you made and an order entity will be used to keep record of orders that cutomers placed.
Pricing:
Any order system needs to manage two very distinct bits of data that are easy to confuse. The price in the Product entity is the current
price. The price in the Order entity is the selling
price. Not at all the same thing--current price is almost certainly going to change over time. Selling price won't.
Does it mean that I'll change the price attribute for product to current_price and add selling_price to order table which will help to keep record of price at the time of order?
Why did you include a quantity field in the Products table? Is it meant to represent stock on hand?
Yes you are right. It represents stock in hand.
Could you please recheck the entities relationships as I am not confirmed whether these are correct or not?
Thanks,
momersaleem

Recreating inventory manager

Hi
I am having problem with inventory manager and it is getting down frequently and there is no prblm with other managers.How can i recreate it i want to recreate the INVLIBR
rgds
rajesh

What is the error you are getting? Recreating the inventory manager may not be the solution.
Try to relink Inventory Manager (INVLIBR) manually using the following command:
- Login as applmgr user
- Run the following:
$ AD_TOP/bin/adrelink.sh force=y ranlib=y "inv INVLIBR"
$ AD_TOP/bin/adrelink.sh force=y ranlib=y "inv INCTM"
- Bounce the Concurrent Manager

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

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

Inventory management snapshot model using Datamart Interface

Similar Messages

Maybe you are looking for