Inventory Management Collection run

We would like to increase our Inventory Management Collection run to every 5 minutes (currently every hour). Can anyone forsee a problem with this or have experienced a problem
We have an Unserialized V3 update
Thanks

I do not see any issue. The LUW count of the records getting written to the delta queue might increase marginally, but that should not be an issue.

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

Urgent-Inventory Management in case of a glass or ply industry

A typical scenario.
I am facing a problem in inventory management for a client of mine who is into glass cutting and supply. The glass sheets are purchased in sheets from the vendor and is cut into various shapes and dimensions according to the order recieved by him. now in most of the cases the entire sheet is not used in a particular order. the remaining part which is not used goes to the inventory. Now for a next order all the remaining part may be used if it matches the lengthXBreadth specifications. So the inventory items should show the length X Width specification. The dimensions are not fixed and there may be "n" number of variables.
Example- A default sheets of sizes 10"X10" is purchased form vendor. Seperate shapes of 6"X4" and 4"X 4" is cut out from it. Then the remaining part will have a dimension of 6"X10", which goes to the inventory. Now whenever he will see te inventory report he should be able to see that 1qunty of 6"X10" is ther in the inventory. So that when if he recieves an order of 6"X8" or 6"X10" he can use that and save cutting a new sheet (10"X10"). This will minimise the wastages.
I had planed to do it by the area but then that does not solve the perpose as the inventory total will show the sum area of all the dimensions in the inventory in "sq@units". Makong item masters for different dimensions will involve a huge inventory management and the users may land up in making numerous masters evry day and also risk of the duplication of the same masters will prevail.
Please anyone who has done any implementation for such clients or of similar type or any one having a suitable solution to this issue........please help!!!

Debraj,
In that case the option you could try is to enable batches and store the size as a batch number
For example: The inventory could have 10 pieces of item A
Qty......Batch
..2.......6x10
..3.......6x8
..5.......6x6
Now when ever you want to add a cut piece of item A which is of size 6x10, you simply enter Batch 6x10 and this will not only increase stock by1 but also you now the visiblity of what the stock is made up of by running the Batch report.
If you want to do it in a much better way then you need to probably go with an AddOn
Suda

Serial Numbers in Inventory Management – Warehouse Managed storage location

Serial Numbers in Inventory Management u2013 Warehouse managed storage locations
We want to run inventory cycle at the warehouse for materials. These materials are u2018serial numberedu2019 in the material master. During the initial entry (say GR) of the materials, systems prompt for the serial numbers. At this point, system offers option of assignments of serial numbers automatically.
While running an inventory cycle for warehouse u2013 and posting difference at WM level (LI01), system is throwing error as u201Cmaintain serial number for totol quantityu201D. System does not promt me to enter the serial number for the materials (count) which are found excess/shortage duing the inventory cycle.
Is there any configuration where this scenario can be managed; system should prompt us to enter serial number while posting differenes at WM level (LI20).
The inventory cycle is -
1.     Create Physical Inventory Documents - LI01N
2.     Activate Physical Inventory Document -      LI02N
3.     Enter Count -     LI11N
4.     Post Differences at WM level -     LI20
5.     Post Differences at IM level(If Differences are posted at WM ) -     LI21

Curious to know: The WM Inventory transaction - LI11N - (where we enter physical count. )
1. Compared to MI04 - IM Inventory Transaction: where a pop-up window asks for serial number of the material.
2. We expect a similar pop-up at LI11N transaction- where the system should ask serial numbers.
Q.1 How can we achieve this?
Q.2 Will this be a standard SAP practice? (if we do customizing to get serial nos. pop-up window at LI11N)
thanks,

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

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

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

Wrong values for Total stock - Inventory managment ( negative values)

Hi,
I loaded inventory management load
2LIS_03_BF INIT 01.06.2009 - 06.7.2009 No Marker Update (compressed with check)
2LIS_03_UM INIT 01.06.2009 - 06.7.2009 No Marker Update (compressed with check)
the first quantity received is from 11.06.2009 and 0RECTOTSTCK is showing 300 which is correct.
on 10.06.2009 it is showing -300 for 0TOTALSTCK when it should be 0 since there hasn't been any data.
whats the right way to compress my cube if I don't want to load BX and how can I resolve this.
thanks

Hi,
The standard process to get correct values in report is
1. First u have to do init laod from 2LIS_03_BX and u have to compress the request with 'no marker update' chk box unselected.
2. Next u have to do init load from 2LIS_03_BF and u have to compress the request with 'no marker update' chk box selected.
3. Next u have to do init load from 2LIS_03_UM and u have to compress the request with 'no marker update' chk box selected.
4. Normally u can run delta loads from BX and BF data sources. ( Compression is not mandatory. Even if u compress it will improve the performance)
Regards,
Thilak

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

Inventory management problem with WS-C2950-24 on CWLMS 4.0

Hi Joe,
I have a problem with inventory management wiht 2950- 24 switches on which I am not able to capture inventory as well as the configurations. The IOS version is 121-22.EA13 and featureset is i6k2l2q4-mz. However, when I troubleshoot it, all the transport protocols (Telnet, ssh, tftp etc) shows success.
Thanks,
Best Regards // Rajiv

Inventory uses snmp to communicate to device. Please check you device has snmp configured and LMS has correct SNMP RO credentials added to it.
Please try to do a manual snmpwalk from LMS server (using device centre > tools) and see the walk succeeds.
Then again try to run the inventory from LMS server on this perticular device and if it fails, share the failure result/screenshot etc details. NMSROOT/log/ic_server.log as well.
-Thanks

Inventory Management 0IC_C03 customizations

Dear Experts,
I have a task in hand to implement Inventory Management in SAP BW 3.5. Now, this is the first time that we will be implementing anything related to Logistics and I havenu2019t done so earlier in my support projects. I have got 10 hrs of downtime.
I need to fetch the report for both Trading as of now.
The fields needed in the report by the customer are:
Plant
Plant Description
S. Loc.
S.Loc. Description
Opening Stock Qty,
Opening Stock Value,
Receipts against PO Qty,
        Value,
Receipt against STO Qty,
        Value,
Receipt against return SO Qty,
     Value,
All Other Receipts Qty,
      Value,
RevaluationValue,
Miro Differences,
Issue against SO Qty,
      Value,
Issue against STO Qty,
        Value,
All Other Issues Qty,
      Value,
Closing Stock Qty,
           Value,
Book Inv Qty,
Physical Inv Count.
I am planning to define these as Zkey-figures and write routines in update rules based on processing keys to capture each qty and value separately.
My questions are:
1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
2) For every above field, customer has given standard movement types.
For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
            for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
If you know which processing key can be used for above fields, please let me know.
3) What are the other fields that need to be considered in routines. If possible please specify field wise.
4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
Thanks friends.

BJ,
My questions are:
1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
~ You will get fields from the Cube only.
2) For every above field, customer has given standard movement types.
For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
~ Check this Table in Source system for BW Keys : TMCLVBW
But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
If you know which processing key can be used for above fields, please let me know.
Check this table
3) What are the other fields that need to be considered in routines. If possible please specify field wise.
That depends upon your requirement in the report or Check the standard Dcoument for Inv management in SDN search.
you will get lot of help.
4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
~Best Practice and even SAP Recommends Make a ZCUBE and then enhance or customize to fullfill your rek.
No impact follow IM steps for BW.
Make sure you keep these things in Mind:
There are 3 SAP delivered transactional data sources for stock management.
2LIS_03_BX : Always needed to carry the initialization of the stocks.
2LIS_03_BF : Initialize this in source if you need historical data else an empty init can be done for this to load only future delta records. If the Source system is new then no need to do an initialization.
2LIS_03_UM : Only needed if revaluations are carried out in Source. This data source is helpful if adjustment in material prices is done time to time otherwise it wonu2019t extract any data.
2. Check list for source system. Needs to be carried out before initialization of the above 3 data sources .
A.   Table TBE11 : Maintain Entry u2018NDIu2019 with text u2018New Dimension Integrationu2019 and activate the flag(Note 315880)
B.   Table TPS01 : Entry should be as below(Note 315880)
PROCS u2013 01010001
INTERFACE - SAMPLE_PROCESS_01010001
TEXT1 u2013 NDI Exits Active
C.   Table TPS31 : Entry should be as below(Note 315880)
PROCS u2013 01010001
APPLK - NDI
FUNCT u2013 NDI_SET_EXISTS_ACTIVE
D.   Tcode u2013   MCB_
In most cases you need to set the industry sector as u2018standardu2019. For more info please see Note 353042
E.    Tcode u2013 BF11
Set the indicator to active for the Business warehouse application entry. This entry may needs to be transported to the production system. (Note 315880)
3. After running the setup data, check the data for the fields BWVORG, BWAPPLNM, MENGE. If no data available in these fields then some setting mentioned in the above checklist are missing in R/3. Correct the issue and rerun the setup data.
4. Data staging with DSO for BX extractor is not allowed. Data should directly load from extractor to Cube only once. Choose the extraction mode as u2018Initial Non-cumulative for Non-cumulative valuesu2019 in the DTP.
5. DSO is possible for BF. If you are creating a standard DSO then choose the fields MJAHR,BWCOUNTER,MBLNR,ZEILE as key fields. Some of these fields wonu2019t be available in the standard data source but the data source can be enhanced using LO Cockpit (LBWE) to add these fields. In addition to these other fields depending upon the DSO structure is also possible.
Note 417703 gives more info on this.
6. Point-5 is valid for UM also. The Key fields could be a combination of MJAHR,MBLNR,ZEILE,BUKRS fields. Note 581778
7. Data load to the cube should follow the below process
A.      Load the BX data. Compress the request with stock marker(uncheck the marker option).
B.      Load the BF and UM init data. Compress the loads without the stock maker(Check the marker option).
C.      The future delta loads from BF and UM should be compressed with Stock marker(uncheck the marker option).
8. If in future the cube needs to be deleted due to some issues then the load process should also be carried out as above. (only init of BF and UM should be loaded first and then the deltas should be processed)
9. To check the data consistency of a Non cumulative cube the standard program SAP_REFPOINT_COMPLETE can be used. To check the compression status of the cube the table RSDCUBE can be refered. Before the compression of BX request, the u2018REFUPDATEu2019 field should be blank and after the compression the value should become u2018Xu2019. Check Note 643687 for more info.
10. After BX data load to cube the data wonu2019t be visible by LISTCUBE. Only after compression the data can be seen by running a query on the Non cumulative cube.
~AK

Inventory Management Collection run

Similar Messages

Maybe you are looking for