Handling Inventory managment

Hi Friends,
May be this topic might have delt many times in this forum ,
I am new to handling 0IC_C03 Cube where in i went through the doucument How to handle the inventory managment(snap shot scneriao).
I went through some OSS notes regarding the Marker settings and Compressions.
I have some basic answers and very enthusiastic to know more abt the cube.
I do know we have to set the marker when you load data source 2LIS_03_BX,and do not set the marker when we load/delta load with out marker(no marker).My question is.
1) when opening balance is taken we do set the marker and compress,is that we set marker only first time we we load BX data source.
2) how frequently we should compress the request
3) BX data soure is loaded only for one time.
4)How will be fact table look like when we set marker.
Thanks & Regards
Ram
Edited by: Ram on May 31, 2008 8:30 PM

hi,
1) when opening balance is taken we do set the marker and compress,is that we set marker only first time we we load BX data source.
Ans - yes, this compression will update the reference point (markar) for the non cumaltive key figures used in cube.(BX load is done only once)
2) how frequently we should compress the request
Ans - once the init is compressed, delta loads were not mandatory to compress, but if you do compression then report performance will be good.(non cumulative KFs will get values only at the report run time with the help of markar set for them.
3) BX data soure is loaded only for one time.
Yes
4)How will be fact table look like when we set marker.
Ans- All the data from F table will be moved to E table as in ordinary compression the reference point is get updated.
Ramesh

Similar Messages

Posting block Question in How to handle inventory management scenarios

Hi all - I have a question in document
"How to...Handle Inventory Management Scenarios in BW"
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

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

How to Handle Inventory Management Scenarios in BW (NW2004) BW7

Hello,
does anybody know if there is a more actual version of the document available?
Thx,
Christian

Hi,
Before posting please search on Google.
please find the link.
SAP BW - Inventory data loading step by step(0IC_C03)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906b837a-0d54-2c10-08b8-bde70337547e?overridelayout=t…
Thanks,
Phani.

Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

Hello all.
I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures. I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
Steps I followed:
1. Ran initialization of beginning balance with 2LIS_03_BX
2. Ran the historical job with 2LIS_03_BF
3. Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
4. Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
Now, to this point, everything was fine. Quantities were as expected. Dollar values were as expected. The problem occurs once I load deltas:
5. Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
Query example:
MATERIALA:
Initial Stock Balance = 1000 EA
Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
Now, I have the record in BW showing the stock issue of 150. However, the non-cumulative key figure within the query still shows 1000. And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance. It is like it is not recognizing the updates.
Any help would be appreciated.
Thanks,
Brent

Hi!
Here is what helped in my case, very similar to your:
In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

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: Validy dates in queries???

Hi experts,
We have BW 7.0.
I have loaded data on 04.03.2010 with BF- and UM-datasources and compressed it correctly.
When I now look into the validy table for plant 0001 there is a validy range from 03.07.1997 to 08.02.2010.
But when I start a query for 09.02.2010 system says "no data found".
The document "How To Handle Inventory Management Scenarios in BW" says that I should show the result in parenthesis!
What is up here?
But I don't want to update this validy table!!!
Pls help!
KR,
Raimund
Text in document:
...For example, if data with document data was loaded into the
InfoCube with values from 01.01.2002 to 15.02.2002 (assigned to the respective time
characteristic), the validity interval is also determined by these two date values. You can
extend the intervals by maintaining the table (transaction RSDV). Stock balances are
displayed for requests that relate to this period. If you start a query that requests the
stock balance for 16.02.2002 or later, the result is displayed in parenthesis (a blank
value is displayed in BW 2.0B and 2.1C), since it lies outside the validity area (providing
that the validity table was not manually extended using transaction RSDV)....

Hi,
Hi,
Use 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to 0IC_C03 Cube and design the report.
Use :
0VALSTCKVAL   " for Value
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month
Use the above combinations in New Selections in columns and go it.
For Qty Opening:
New Selection bad drag abd drop following things
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input) and set the offeset
                               value = -1 bcoz if user will give 12.2009 , so it will display 11.2009 closing stock, this is opening for 12.2009.
For Qty Closing:
New Selection bad drag abd drop following things
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input) .
In the same way build for Value and other Keyfigures on 0IC_C03.
And
Drag & drop
0MATERAIL
0PLANT " Give some Input Variable.
See the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
If it is BI 7 then for BX in in DTP in Extraction Tab you need to select Extacrion mode = NON-Cumulative option.
See this thread related to Inventory.
Re: Inventory Mangement steps - questions
Thanks
Reddy
Thanks
Reddy

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

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

Using Inventory Management in BI

We are trying to make use of inventory data in BI. Weu2019ve installed business content for the cube 0IC_C03 and followed the steps in u2018How tou2026 Handle Inventory Management Scenarios in BWu2019 to get the data to the cube. The best I can understand I've loaded and compressed in the right order.
When we run a report it only seems to be reporting on the opening balance as defined in the 2LIS_03_BX load. It does not appear to be looking at the material movements as loaded in 2LIS_03_BF to calculate balances in the past. We installed from business content the Stock Overview report. Here is a sample of what Iu2019m seeing when drilled into a specific material that I know had inventory movements in 07 & 08 of 2008:
06/2008 1,002 EA
07/2008 1,002 EA
08/2008 1,002 EA
09/2008 1,002 EA
10/2008 1,002 EA
Anybody have any suggestions on what I need to look at? My understanding was that the query would used the material movements to calculate the balances for those months.
Thanks,
Chris

Hi,
If you followed the steps correctly you must get the correct values in BW report and it will match with MB5B in ECC.
Do like this...
If you have any opening stock problem, please run the report
SAP_REFPOINT_COMPLETE and select Insert of Missing Records
and then check the data in the cube.
While checking data in MB5B, you need to give proper selections i.e. date and check valuated stock radio button.
Note: check what are date ranges that are you are giving in BW report and in ECC
Thanks
Reddy

Problems reloading Inventory Management

We have been struggling to reload our Material Movements cube (0IC_C03). We have been following the SAP documentation titled 'How to handle inventory management scenarios in BW'.
Our initial loads (Stock Opening Balance, Movements Init, Revaluations Init) have all been successful and validation looks good. The problem is that when the first delta UPDATE runs we end up having many negative inventory quantities appearing. We are not sure what we could be doing wrong.
Compression settings are as follows
1) Run stock opening balance (2LIS_03_BX)
2) Run statistical setup for 4/3 only for Revaluations and Movements (2LIS_03_BF, 2LIS_03_UM)
(Compress with Marker option NOT CHECKED)
3) Load Stock infoPackage 2LIS_03_BX with 'Opening stock balance checked ' (ie: not full update)
(Compress with marker option NOT CHECKED)
4) Run delta init for Movements
(Compress delta init with marker option CHECKED)
5) Run delta init for Revaluations
(Compress delta init with marker option CHECKED)
6) Setup job control in logistics cockpit
7) Run delta update for Movements
Compress delta with marker option NOT CHECKED
8) Run delta update for Revaluations
Compress delta with marker option NOT CHECKED
The issue seems to occur with steps 7 and 8. The initial time we do these steps we get zero records and everything looks good. Then the next day the same steps occur in our nightly process chain and then the data is bad with negative values.
Any ideas what we could be doing wrong?
Thanks!

Hello Patrick,
Whic values you are getting as negative, the non-cumulative key figures or the inflow and outflow key figures? If the inflow and outflow KFs are coming correctly, then problem is in BW side e.g. compression sequence. But in case inflow and outflow KFs itself are coming worngly with negative sign from R/3, then problem lies in R/3 side. In that case you can check the corrsponding data in tables MSEG and BSEG. Let me know in which part the problem lies and from there we can take it forward.
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.

Question on "How to Handle Inv management Scenarios in BW" docuemnt.

Hi all,
I read the document "How to Handle inventory management scenarios in BW" and I did not understood what a snapshot scenario is? Can anyone tell me what is the difference between snapshop and non-cumulative scenario's.
thanks,
Sabrina.

In a non-cumulative scenario the current stock of any day (or month) is not stored physically in the cube. Instead the stock values over time is calculated dynamically at query runtime by the BW OLAP engine, which basically derives the stock by summing up the periodic value changes (cumulative inflow and outflow of the non-cumulative key figure), which are stored in the cube (together with a so called stock marker used as the basis of the calclation).
In the snapshot scenario the current stock of any month is calculated in a snapshot ODS and then loaded to a cube. This means that the the stock value is physically stored in the cube in an ordinary cumulative key figure.
Since a non-cumulative cube store value changes and not the actual stock this means that performance might be bad if there are many value changes for each characteristic combination in a month (since the stock is calculated at runtime and many records must be processed to derive the stock). So in this case the snapshot scenario is better since no runtime calculations of the stock need to occur and since only one record, containing the actual stock value will be stored in each month for each characteristic combination having a stock value.
I think you would be better of with an example, but with this explanation in mind looking at the scenarios in the How to again might clarify things...
Regards,
Christian
/ Christian
Message was edited by: Christian

Regarding inventory management

Hi,
I have documnet How To Handle Inventory Management Scenarios in BW
Version 1.3 January 2005.
But it gives the details about 3.5 version. If i want to implemnet in 7.0 what all i need?
also i w2as trying to find the 'No marker update' option and all in 7.0 but coudnt find the same. Is thr so much difference in implementing INVENTORY in 7.0
*Please help.

Hi Jino,
Briefly,
a) Single Step transfer: -
this comes in STO, while transfer material between plants.
if you tick the indicator as one step in config,
Generally, when you do the PGI for material from supply plant to receiving plant, goods issue document will generate in Issuing plant.
Similarly goods receipt (GR)document generate in receiving plant.
in One step procedure, GR will create automatically in background after you do PGI.
where as in Two Step Plant Transfer. AFter PGI, you have to create GR-MIGO also.
Hope it clears. Try and let me know

Indication of documents about Inventory management in BW

H
I've got this excellent document "How to handle inventory management scenarios in BW". Very clear, easy to understand.
I'd like to go into more details about 2LIS_03_BX (initialization of the current stock), compression of requests and marker update.
Does anyone have indication of other documents that deal with these subjects?
Thanks in advance
César Menezes

Hi Cesar:
Please refer to the documentation below:
"10 important points to consider while working with inventory management", blog by Ranjit Rout.
/people/ranjit.rout/blog/2009/06/14/10-important-points-to-consider-while-working-with-inventory-management
"Non-cumulatives / Stock Handling"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31?quicklink=index&overridelayout=true
"BI Inventory Management- Data Loading", paper by Gaurav Kanungo.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906b837a-0d54-2c10-08b8-bde70337547e?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 1", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60101663-3cb7-2c10-3687-8d1e0ef51b0d?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 2", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0783925-f4be-2c10-9c89-ffa108f72547?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 3", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e00860a4-350f-2d10-29a0-fc09681a8bae?quicklink=index&overridelayout=true
"Inventory Management in SAP BW", article by Harishraju Govindaraju.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9054ac59-aac4-2d10-3d9b-df98c52b4f31?quicklink=index&overridelayout=true
"Loading to the Inventory Cube 0IC_C03", blog by Akshay Chonkar.
/people/akshay.chonkar2/blog/2010/05/19/loading-to-the-inventory-cube-0icc03
"Insights into Cube compression", blog by Arun Varadarajan.
/people/arun.varadarajan/blog/2008/08/19/insights-into-cube-compression
SAP Note 643687 - "Compressing non-cumulative InfoCubes"
SAP Note 745788 - "Non-cumulative mgmnt in BW: Verifying and correcting data"
SAP Note 1548125 - "Interesting facts about Inventory Cubes"
Regards,
Francisco Milán.
Edited by: Francisco Milan on May 7, 2011 12:08 PM

Handling Inventory managment

Similar Messages

Maybe you are looking for