Inventory Management Setup Table MC03BF0SETUP

Is there a limit to the number of records this setup table (MC03BF0SETUP) can hold? I am in the process of rebuilding InfoCube 0IC_C03.
Thanks,
Brendan.

Is there a limit to the number of records this setup table (MC03BF0SETUP) can hold? I am in the process of rebuilding InfoCube 0IC_C03.
I got your question . Please follow the steps
First check the data base table how many records its holding .
Delete the contents the of setup table and fill it again and check weather you are getting the same
number of records or not .
If same number of records issue solved .
Assign marks is the best way to appreciate help whoever it is

Similar Messages

Inventory Management: Validity Table

Hi Guys,
For the Stock cube (0IC_C03) in BW, a validity table is generated.How to delete an existing characteristic from the validity table or how to add new characteristics to the validity table.
Thanks.

Hi Govind,
You can use RSDG_CUBE_VALT_MODIFY report for this.
See:
http://help.sap.com/saphelp_bw31/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/content.htm
Best regards,
Eugene

Setup tables Inventory Management

Hi,
I want to fill setup table for BX via tcode MCNB (in R/3).
Can I start with the setup table for BF using tcode OLI1BW parallel or I have to wait till the job RMCBINIT_BW (tcode MCNB)
is finished!
Same question for UM: Can I start the setup table for UM (tcode OLIZBW) parallel with the job RMCBNEUA (tcode OLI1BW)
or I have to wait till the job RMCBNEUA is finished!
Is there any possibilty to enter more company codes for the setup table for UM (tcode OLIZBW) as we have 120 company codes
Or I have to plan the job for each company code separtely.
Moreover I will load data (first opening balance, movement, revalaution) into BW when the setup tables are filled on R/3 side.
Is it ok?
Thanks for the answer.

Hello Moha,
Yes, Venkat, is right.
This is the order
2LIS_03_BX3 Material stock (Parallel)
2LIS_03_BF Material movements (Parallel or with UM)
2LIS_03_UM Revaluations
Please see this Inventory Document
[How to Handle Inventory Management Scenarios in BW (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
[Non-Cumulative Values / Stock Handling|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31]
Thanks
Chandran

What are tables in Inventory Management in SAP-MM

Hi all,
i would like to know the nemes of tables in SAP-MM Inventory Management. Plz provide me ur help.
Thanks....
Bandhan

Hi Bandhan,
Below are the some tables used for IM.
MSEG -Material document / transaction details
MKPF - Material document header information
MARD - Material stock
MBEW -Material stock with valuation
MSKA -Stock balance with associated sales
EKUB -Index for Stock Transport Orders for
MDUB -Material Reading View of Stock Transport Ord. for|
MKOL-Special stocks- Consignment, material provided to

Re : Condition table missing: Access Y003 10 (Output Inventory Management)

Hi
While doing migo using movement type 501 the following error is coming.
"Condition table missing: Access Y003 10 (Output Inventory Management)"
How to solve this.
Thanks
Anto

Hi
After creation of PO, any body chaged the access sequence?
Check this out in SPRO- SAP IMG- Material Management- Purchasing- Conditions- Define Price determination process - Define access sequence.
Regards,
Raman

Inventory Load - Running Init of Setup tables

I'm planning the initial load of Inventory data and want to make sure that I understand what needs to be done.
Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel. Or do I have to wait for one to finish before I submit the next?
Thanks,
Chris

Chris,
Question 2 - To save time can I run the initialization of the setup tables for 2LIS_03_BX,BF,UM in parallel. Or do I have to wait for one to finish before I submit the next?
--> You can run parallel, you can also run parallel for each datasouce(eg: BF) by providing proper selection(like, Plant, date..ect)
Hope it Helps
Srini

Issue while filling Inventory setup tables.

Hi,
Here we are facing a critical issue, while filling Inventory setup tables, we have done BX setup successfully. Not able complete BF and UM because of performance issues.
We filled 40% of BF and UM, since we dont have system downtime and stoped the setup at that movement. Shall we do BF & UM setup without R/3 system downtime. Is there any other way we can fill the BF, UM setup tables.
Your help is really appreaciated.
Thanks
BK

Hi BK,
Ideally you need the downtime when doing the setup for current and previous period as these are the only open ones where you can expect changes to happen due to user postings. What selection did you give when doing the set up? One idea is to break up the set up job so that each job loads for a week and then run the jobs in parallel. This would work for BF and then for UM of course you need to run it per company code. Are you using on ODS in your data model?

Setup table for Inventory

Hi Friends !
Was reading the inventory docs for the setup table. How to perform step 2?
2. Setup of statistical data for material documents in the R/3 source system. Here, all
historical material movements are to be set up that has lead to the opening stock in
step 1 (this makes it later possible in BW to calculate historical stock values). Ideally
you still keep the posting block during this run. If this is not possible you have to
make sure that by restrictions for posting date or the material document number you
only select those material documents that have created the opening stock (step 1).
Please consider that material movements that have been posted into the future for a
date (field BUDAT) after the initial stock date are not getting selected if the upper
restriction bound is exactly this date. In this case you have to choose an appropriate
upper bound like 31st December 2099 and to keep the posting block. Also if you
post new documents to a date (field BUD AT) earlier than the initial stock date you
have to keep the posting block as time restrictions wonu2019t help to determine the right
documents (maybe restrictions by document number help).
With Regards
Rekha

Hi Rekha,
Posting block is nothing but downtime. While filling the setup tables you should ensure that no postings happen in the system. To summarize step 2 -
You should run the BX load and the Init BF load for the same selections. If there is any difference, it would lead to wrong stock values in BW. BX is used to setup the opening balance. BF init should be run with same selections so that it brings all movements which resulted in a stock setup by BX. We compress BF init load without marker (NO MARKER ticked) so that the stock doesn't get doubled because the result of the movements setup by BF is already extracted by BX.

Need to convince manager on posting downtime during build of setup tables

Can any one suggest some pointers in writing a business case for downtime during build up of setup tables
this is for Sales Application component.

Delta loads especially for LO extraction is governed by the V3 jobs scheduled in the source system.
These V3 jobs will post into the delta queue even if there is some activity in the R/3 system.
To ensure that no transactions get missed - a downtime is taken in the source system so that no documents are changed.
If you want to avoid downtime :
1. You should know which documents changed during the period the extractors were refreshed. this is in order to fo a full repair request.
Typical procedure involves :
1. Take downtime.
2. Clear delta queues into SAP BI
3. Deschedule V3 jobs
4. Move enhancements into the production R/3 system.
5. Do an init without data transfer into SAP BI to create the delta queues
6. Schedule the V3 collection jobs
7. open the system for users to post / change documents etc
8. Continue deltas into SAP BI
If you want to avoid downtime then
1. Clear delta queues into SAP BI
2. Deschedule V3 jobs
3. Move enhancements into R/3 production
4. Init without data transfer
5. Schedule V3 jobs
6. Continue deltas
7. Perform full repair request for documents that have changed between steps 1 and 5 into SAP BI.
I have gioven the steps for an enhancement - but then any activity involving changes to V3 extractions or Upgrade activity in SAP BI would fall into the same category.

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

Starting Inventory Management in BW

Hi experts,
I am starting Inventory Management in BW and using the How to Guide.
I understand how important the Stock init is and the need to block postings or to init during a period when no sotck movements occur.
This is especially important for us as we have stocks in Europe and Stock in the US.
Though I am still a little confused of during which steps of the Init the stock movements have to be blocked.
Here is how I processed in Dev system:
1- Activated necessary BI content in BW and 2LIS_03_ datasources in R/3 (transaction LBWE)
2- Intilialized the current stock in R/3 (transaction MCNB)
3- Executed INIT Infopackage to load current stock PSA table and then DTP (Extraction mode set to Initial Non-Cumulative for Non-Cumulative Values) to load the 0IC_C03 Cube
4- Deleted 03 Setup Tables in R/3 (transaction SBIW)
5- Initialized 03 Setup Tables (transaction SBIW)
6- Executed INIT Infopackage to load Good Movements PSa and then DTP to 0IC_C03 Cube (delta extraction)
7- Handle Delta movements in Process chain
Here are the questions I have:
- Am I missing any steps (except stock valuation part)?
- Do Stock posting have to be blocked during all these phases ? Or can they be queued in delta queue before doing the INIT of Infopackage (Step 6)?
- There doesn't seem to go through step 5 restricting on plant/stock. So I need to init for all plants (seems to be only possible to restrict on posting date or document) and make sure all postings are blocked right?
Thanks a lot for your answeres.
Olivier

See if this helps:
http://help.sap.com/saphelp_nw04/helpdata/en/99/27443cbe062e59e10000000a114084/frameset.htm

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

Posting block Question in How to handle inventory management scenarios

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

Prod issue with Inventory management in BW ..please help

hi Folks
i am new into inventory management extraction into BW. i have read all the document regarding the extraction. My question is
1. what all the comon produciton issues you wil come across when you do the inventory management
2. what is the dificlut challenge you face during extraction and validation
3. what all things you need to consider or keep in mind while doing this process
4. what is pros and cons of this process ..any bettar way to improve this process?
please shoot me your thougths ..which will helpfull for my new task..

My Dear Friend...
Typical Steps for refreshing your understanding :
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 initialization.
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.
ALWAYS LOAD in order as BX datasource first then BF datasource and then UM datasource in cube
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.
And about Reconcilitation of data ...Count the number of records in R/3 in particular table and check with BW is its matching...When you request in Detail Tab you can find the number of records...
Then check if the balances are matching in R/3 and BW...saying for ex: Check opening Stock for today in both the systems...
If you follow the process properly I dont think you will face any issues...I havent ever seen any complication in Inventory loading...Dont worry...Just follow the typical LO Extraction steps...All Good
Regards...
Sandhya

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

Inventory Management Setup Table MC03BF0SETUP

Similar Messages

Maybe you are looking for