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

Similar Messages

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

Monthly snapshot for Open / Cleared Cube

Can the standard Delta extractor 0FI_AR_4 be leveraged to get a monthly snapshot of Open and Closed items?
Open - All and Closed only for the past year.
Currently I am thinking of feeding a delta upto a standard DSO at the Account number, line item level.
The next level will be a Monthly DSO at the Business area level, which summarizes the open balance and weighted days to pay for cleared. This feeds to a Monthly snapshot Cube.
Now between the line item DSO and the Monthly DSO, I am thinking of Full loads that bring all the Open and only the past year of Cleared records. The way I build snapshot is, compare posting date of the documents to the current fiscal period. If the posting date is less than the current fiscal period, I duplicate that record and put it in the previous month and this current month. This way, we are building two months history at a time. And at the end of the current month, the previous month snapshot is frozen.
Is there a way with Deltas to accomplish a 12 month snapshot ( and not just two months with Full) ?
All thoughts appreciated

The requirement is to show Outstanding Balance not just as of today but as it was each month.
say item A was open in Jan through today
       item B was open Jan through March
       item C was open Jan and Feb
The report should show, item A in Months JAN, FEB, MARCH, APRIL
                                                B in Months JAN , FEB, MARCH
                                                C in Months JAN and FEB
With conventional reporting, there will be one entry for A in Jan as Open and when that closes in May, it will have a reverse entry for Jan and a After image for May.
What I need is to show A as Open in all Months through April, B Open in all months through March, etc.
Hence the name snapshot.
Edited by: CC on Apr 20, 2010 9:17 PM

Monthly Snapshot

Hi experts,
I'm working in the monthly snapshot scenario, following the instruction given in the related How-To from SAP. But I've one problem:
When I load data from goods receipts or issues, all is ok, but when I load stacok types changes, the 0BASE_UOM and 0LOC_CURRCY gets empty.
For example, I've already loaded one register with the following:
0BASE_UOM.|.0LOC_CURRCY.|.ZTOTALST.|.0STOC_TYPE
.......EA...........|...........MXN........|.......30.......|......A..........
If I load a 2LIS_03_BF delta with one stock change from A to D type, of 666 Units (using transaction code MB1B in R/3, with the movement type 344 from unrestricted to blocked stock), the following registers appear
0BASE_UOM.|.0LOC_CURRCY.|.ZTOTALST.|.0STOC_TYPE
.......................|.........................|......-636.......|......A..........
.......................|.........................|......666........|......D..........
Without base units nor currency.
Does anybody have any idea?
Best regards
Edited by: Angel Moro on Jun 26, 2008 4:35 PM

Hi,
I think 0RECORDMODE is necessary in 2LIS_03_bf infosource, just for other purposes, and I can't leave it unmapped.
My question was if it is used for other things appart from calculating the sign of the key figures.
If it is it's only purpose, then I could delete that flag in order to update the 0BASE_UOM and 0LOC_CURRCY.
Regards
Edited by: Angel Moro on Jun 30, 2008 3:46 PM

WM-Implem -Physical inventory and Month end process- Need configuration

Hi
    Iam doing WM implementation, i need to know what are the configuration required for Physical inventory and
    Month end process .
    kindly suggest me
    With Regards
    dinesh
Edited by: code acess on Dec 7, 2011 7:55 AM
Moderator message:
Locked. Reason: basic question
Please search before posting question.
Edited by: Csaba Szommer on Dec 7, 2011 8:27 AM

Hi
There is no standard settings for your requirement. With a help of abaper you need to define an enhancement.
Regards
Antony

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

Non-cumulative Inventory cube to snapshot Inventory cube scenario

We currently have a non-cumulative Inventory cube in production system and the stock values match to ECC data. Now we want to build a snapshot cube (to improve query performance) and the question is can we use the current cube (non-cumulative) as data source for the new snapshot cube or do we need to load it from ECC? Is there any special handling needed if it is loaded from current cube?
Thanks!

Hi,
You can use the existing cube, but make sure that you have implemented the OSS Note 1426533 before doing this.
Regards,
Raghavendra.

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: Month beginning and ending inventory levels

Hello,
I need to have beginning and end of month inventory levels. I havent been given any functional specs . The only favor I would like from you is to know what standard chars and key figs you are using in your rows and column. And how are you using the objects in the forumla Naveen A suggested in the thread [SAP Business Explorer (SAP BEx);.
Specially where he mentions formula, I would like to know what key figures does it consist of and are they restricted to the current or prior month.
Let the end inventory be the same way and the begin inventory be as end inventory - ( total receipts current month - total issues current month).
Thanks

Anyone...Naveen A ....Arun????
This is a simple one...
Thanks
Edited by: Navi Singh on May 1, 2009 9:51 PM

Calculate Inventory Value - Month end

Hi guys,
How do I calculate Inventory value end of every month from 0IC_C03 ?
What variable can I use to restrict my 0CALDAY ? OR any other ways to achieve this ?

Please check this http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328&overridelayout=true
This link helped me a lot. Check out the section for snap shot scenario and follow the steps given.
They have provided screen shots for assistance
hope it helps

Inventory Mangement with SnapShots

Hi experts,
I've been trying to implement the SnapShot scenario following the How To paper and I'm not able to create the update rules from 2LIS_03_BX to ODS ODSSNAP and the Cube ICSNAP1. I can not see the key figures to implement rhe uodate routines as it's said on the guide. With the cube I'm having the error No key figures exists for the Infocube.
Has been someone in the same situation?? Any ideas of what I'm doing wrong??
Thanks in advance...
regards,
Carlos

The problem is solved!!!
You can not load the opening stocks to the snapshot ODS untill you create a manual entry in RSADMIN table for the ODS as it's said on the prerequisite note 773823.
I was a missunderstood because the note talks about a support package that we allready had implemented....but it seems you have to create the manual entry for the ODS in the table anyway.
Regards,
Carlos.

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

Freeze book inventory

Hi All,
During the cycle count, physical inventory document is generated with indicator Freeze book inventory balance is set.
That means the inventory will be freeze in the background. That has no impact to production or some other departments. They could work normally during the inventory freeze. Please confirm.
When will be the system freeze inventory? is it after generating the document?
Is it applied to every cycle count?
Thanks

When will be the system freeze inventory
- If you check freeze inventory in MICN, system freezes the book inventory for the physical inventory process. i.e system considers the book stock before the creation of physical inventory document. for ex. you are creating the physical inventory doc. for a material and the stock at that time is 100 EA. Now system freezed the book for physical inventory process. you can still receive the stock but it will not be considered as part of the physical inventory process. issue comes here.. you freeze the book and recevieved another 50 qty before counting. As per physical inventory, book quantity is 100 and when person counts real book quantity is 150 EA.. so will you post this 50 as difference? so its not advisable to freeze if your physical inventory process takes long time. But if you block indicatory you can do transaction with that material..
is it after generating the document?
- Freeze starts from the moment physical inventory document created and it's unfreezed after the posting.
Is it applied to every cycle count?
- it depends how you check freeze icon in MICN.. you can uncheck it if you dont want but understand the implications.

Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?

A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
(1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
(2) The query runtime can be affected by the calculation of the non-cumulative.
(3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
(4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) , Issue Stock Quantity(0ISSTOTSTCK)
, Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03 business content cube. Your honest suggestions and comment are greatly appreciated!

Hello Marc,
Thanks for the reply.
I work for Dongxin, and would like to add couple of points to the original question...
Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
We would like to confirm if there would be any long term issues doing so.
To optimize the performance we are planning to create aggregates at plant level.
Couple of other points we took into consideration for using cumulative keyfigures are:
1. Parallel processes possible if non-cumulative keyfigures are not used.
2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
Once again, thanks for your input on this issue.
Thanks
Dharma.

Tnventory Management Weekly snapshot 0IC_C03

Hi,
We are trying to instal the stocks Flow, with the 0IC_C03 cube. Our Business Content (Release 703 Level 8) has the new Infosources (2LIS_03_BF_TR, 2LIS_03_BX_TR and 2LIS_03_UM_TR) and the related transformations from the Infosources to the cube. But We've realized taht there is not one of the Transformations from 2LIS_03_BF datasource to 2LIS_03_BF_TR infosource. (The othrer 2 transformations appear in our Business Content)
We are thinking to do the following: mantain the transformations for the 2LIS_03_BX and 2LIS_03_UM side, and copy from another business Content (manually, of course) the 2LIS_03_BF side. Has anybody know if it is OK?
On the other hand, we need to create a Weekly snapshot, and reviewing the document "How to... handle Inventory Management Scenarios in BW", there is described the process to make a monthly snapshot if the old flow of the 3 datasources (2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM) is built (the flow with the Transfer and Update Rules)
So, is it recomended to implement the old flow for the 3 datasources (the one with Transfer and Update Rules)? And does anybody knows how can we modify the routines in order to make it weekly, not monthly?
Thanks in advance for your help.
Best regards

Hello Angel Moro,
Were you able to implement weekly snapshot cube? If yes, Can you please email me step by step how you did it at [email protected]

Inventory Book Monthly snapshot

Similar Messages

Maybe you are looking for