Loading of Inventory Management

I am trying to load data in parallel into the Non Cumulative Inventory (0IC_C03) cube and the SnapShot (ODSSNAP) ODS. The steps that I have followed is as follows:
1) Load into PSA
2) Subsequently load into Data Targets
This failed so I deleted the load from the targets and reloaded from PSA. I am currently monitoring the loads and it seems that I am likely to have a fail since the monitor has been on Data Package 129 for a long period.
Is there anything that I can do to the extraction is the BF init and last week I did manage to load to 0IC_C03 when I had not built the snapshot in the model.
The size of the packages are approximately 65,000 records and there are 139 packages
Thanks

Hi Niten,
if the upload has stopped without any particular error message in monitor maybe is a tablespace problem, temp or roll.
Take a look in DB02 - SM21 - ST22.
If it is a problem of roll, make separate upload.
In any case ask DB administrator to enlarge tablespace.
Ciao.
Riccardo.

Similar Messages

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

Consignment Stock for Inventory Management

Posting as a new thread...
I have installed and loaded the Inventory Management Cube 0IC_03 in our development and quality systems. During testing we have found just one problem with Consignment Stock. The Stock Initialization (2LIS_03_BX) does not bring in an initial quantity (BWMNG) for any material flagged as a Consignment Stock (Stock Category = K, field BSTTYP).
My question - is there a good reason for this or is this a problem? It causes a problem with reporting, because balances are now off. Do I need to change how reporting is done for Consignment?
It seems to me that the BX extractor should be picking up the initial balance. I am trying to debug the code, but am getting a headache!
Any help would be appreciated!
Yes, I have reviewed the "How To..." documentation, but don't see anything regarding consignment stock.
We are at BW 3.0b Support Pack 25.
Lisa.

Thanks, Ken. I don't know that this note actually helped me, but I did another review of OSS notes. We have applied 3 of them (726485, 756151, 762219) and our consignment issue has been resolved.
Thanks for pointing me back in the right direction!
Lisa.

Inventory Management Loads

Hi
I have a requirement in Inventory Management where the client wants to empty the complete Infocube(0IC_C03).
Now he is just interested in loading previous 3 months data as historic data.
Now my problem is how do i go about it once i have cleared the Infocube.
all standard datasources are in use.
2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
Summary
Restart Reporting with previous 3 months data available in BIW and delta loads every day later on.
Also guide me over the downtime required.
Akshay Chonkar

Hi All
I wish to Clear the Infocube completely so as to start afresh.
Please correct me if i am wrong
Fill Setup table for 2LIS_03_BX
I will run the Opening Stock Infopackage for 2LIS_03_BX
Compression without marker update
I will be filling setup tables of 2LIS_03_BF and 2LIS_03_UM giving posting date range of previous 3 months and will run Init with data transfer infopackage of the two data sources.
Followed by Compression with marker update for the two requests
Regards
Akshay Chonkar

Inventory Management Loading clarification - loading BX , BF and UM

Hi,
I want to load inventory management from scratch.
I have ready lots of documents from this site related to this but still unsure.
In SAP document, It says that BX should be compressed with NO MARKER UPDATE and while BF and UM should be compressed with NO MARKER Update box checked.
I also read some where that
BX and UM should be compressed with No marker update not selected while only BF should be compressed with marker update box checked.
which is the correct version or whats the difference between these two.
thanks

Hi Vaidya,
Inventory calculate all non cumulative values based on a reference +/- delta principle.
The reference is called the marker.
Answer to the question when should I do a marker update?
Initially, for first load to BW, if R/3 system has gone live earlier, each material would have some stock value in the plant. But if BW has to load only deltas , then it should have this initial stock figures.
So we do a statsitcal run for BX. This statistical run.. consider intial stock of R/3 when it went live + incoming material movement documents - outgoiong material movements and loads BX.
So after this load in BW, we compress the request in BW to create our marker to say 100PCS for material A in plant A as on 31.03.2009.
Now if you are interested in seeing on what were material movements(incoming/outgoing) for 01.02.2009 in BW, you would have to load BF to BW.
So you rean intialization for BF and loaded BF in BW.
But this movement of material A on 01.02.2009 was considered in getting our marker value when we did BX load. This is because in our statistical run for BX we had calculated = R/3 initail stock + incoming movements - outgoing movements until 31.03.2009. So if we consider this historical movement for marker uppdae again our marker would become incorrect.
So when we load BF until 31.03.2009(initialization run) we do not update the marker. So we compress the marker without update.
From 31.03.2009 onward when you load detlas to BW for BF and UM every day, you would like to update the marker to keep it current as of date.
ie say material A moved out on 01.04.2009 - 20 pcs.
say material A moved in on 03.04.2009 - 40 pcs.
So on 4th when you load delta and update the marker , the marker value would be - 100 - 20 + 40 =120.
You update the marker because business is most often interested to see stock of previous or two to three days before. If the marker is updated then it has to check fewer records to get the delta to goe the the stock figure then.
Thus, for all future delta loads you would compress with marker update.
Hope this helps,
Best regards,
Sunmit.

Inventory Management loading

hi xperts,
I am loading infocube,0IC_C032 from the infosource LIS_03_BX,with business content updaterules.
But no data is coming into the cube,I set the option as GENERATE INTIAL STATUS,I checked RSA3 in source system data is there.
please somebody help with this inventory management.

Hi,
you have to run MCNB in R/3 to perform the stock initialization.
You do this vis SBIW - Setings for App Spec DS - Logistics - Settings Inventory Controlling - Stock initialization.
Kind regards
/martin

Stock Valuation - Inventory Management Cube

Dear Sap Gurus,
We have implemented the Inventory Management Cube in BW.
Quantities are correct, but we have difference on the stock valuation.
For some material stock value are correct, for some other they are not correct.
A saw a lot of OSS notes and how to on this subject, I am trying to solve this issue using these documents, but based on your experience could you explain me how you solved this issue ????
Thanks,

Hi
Did you follow the correct steps?
Initialisation of BX data in the first step.(Loading of Opening Stock)
Then The request in which the opening stock was loaded must always be
compressed with a marker update
Init load of BF And UM in the second step
The request in which the historical material documents were contained
must always be compressed without a marker update and
Successive delta uploads must always be compressed with marker
updates
Check this whether you have done this or not.
Because of missing the steps here also would give you wrong values,
Regards
Ram

Initial load of inventory level from csv - double datarows in query

Hello everybody,
a query result shown in a web browser seems strange to me and I would be very glad, if anyone can give me some advice how to solve the problem. As I do not think that it is related to the query, I posted it into this forum.
The query refers to an InfoCube for inventory management with a single non-cumulative key figure and two other cumulative key figures for increase and decrease of inventory. The time reference characteristic is 0CALDAY. The initial load has been processed reading from a flat file (CSV), the structure looks like this:
Product group     XXX
Day               20040101
Quantity          1000
Increase          0
Decrease          0
Unit               ST
The initial load runs fine, the system fills all the record sets into the InfoCube. Unfortunately I do not know how to look at the records written into the cube, because only the cumulative key figures are shown in InfoCube-> Manage-> Contents.
Well, when executing the query, a really simple one, the result is just strange, because somehow there are now two rows for each product group with different dates, one with the 1st of January, 2004 and the other for the 31st of December, 2003 containing both 1000 units. The sum is 2000.
It became more confusing, when I loaded the data for increase and decrease: now the quantities and sums      are correct, but the date of the initial load is a few days later than before, the data table in the query does not contain the 1st of January.
Does anybody know, what I did wrong or where there is information about how to perform an initial load of inventory from csv in a better way?
Kind regards
Peter

Peter,
Inventory is not that straight forward to evaluate as it is non-cumulative. Basically it means that one KF is derived from one/two other KFs. You cannot see non-cumulative KFs in manage infocube.
Have you uploaded opening balances separately? If so, your data for 31st of december is explained.
In non-cumulative cubes, there need not be a posting for a particular day for a record to exist. For e.g. if you have stock as 10 units on 1st and then no posting for 2nd and 3rd and then increase 10 units on 4th, even for 2nd and 3rd, the non-cumulative KF will report as 10 units (stock on 1st rolled forward).
There is a how to...inventory management document on service market place that explains this quite nicely.
Cheers
Aneesh

Inventory Management: Valuated Stock Value

Hello Experts -
We're using inventory management. We're just bringing in 2lis_03_bf which is the material movements and the standard price datasource.
The plant valuated stock quantity and the valuated stock value are fine. The SLOC valuated stock quantity is fine. We're using the non-cumulative key figures for the valuated stock quantity and the valuated stock value. The SLOC valuated stock value isn't correct. So I just created a calculated key figure where I'm multiplying the quantity with the standard price.
This works fine but when I look at the plant level and use this CKF, the aggregation threw me off. So I changed the aggregation on CKF at the Bex level.
This works fine in dev and qa where I don't have too much of data. But as soon as I'm in in production, the query times out and gives me an error saying I reached the buffer limit.
I was thinking of calculating the valuated stock value at the ETL layer but now I'm thinking that if I do that and the price of a material changes, I'll again have the same problem. I can't re-load every time a material price changes.
Can someone please help me with this scenario?
Thanks!
Edited by: Siegfried Szameitat on Oct 29, 2008 9:30 AM
do not offer points, it is against the rules

Hi Syed,
Deriving values by multipling with price also not correct. results will not match with R/3.
Value Calculation
In principle, values are updated with Plant, Material, and Stock Category only. Quantities are updated with these characteristics, as well as with Storage Location, Batch Number, and Stock Characteristic
Check SAP Note 589024: Evaluations in BW with the Characteristics Storage Location and Stck Char.).
Hope it Helps
Srini
Edited by: Siegfried Szameitat on Oct 28, 2008 4:17 PM

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

Gurus,
My inventory scenario is one where I am starting the BW system up at the same time as my go-live. I am proficient in the inventory management scenarios, however, I am finally at a client who is starting their BW implementation up at the same time as their R/3 system goes live.
I do not need to initialize my stock (2LIS_03_BX). However in my testing environment the have already done goods receipts into inventory. When I try to bring my Inventory into BW and compress the request with "No stock marker" update checked for my INIT on BF I get 0 quantities and values.
When I try the opposite (and manage no stock marker update) as if it were a delta, I balance to R/3 invetory just fine. This tells me that I should not check the "No stock marker" update. IS THIS OK? In other words, when I go into our Production environment, and for some reason, I need to reinitialize 2LIS_03_BF, can I do it without activating 2LIS_03_BX?
Kind Regards,
Alex

Hi,
If you are using BFwith out Bx,then you do not need to check the "No stock marker" update for DELTA INIT and Delta Loads of BF. That means you are updating stock in BIW with Bf only.
With rgds,
Anil Kumar Sharma .P

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

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 of Inventory Management

Similar Messages

Maybe you are looking for