Inventory Management - SnapShot Cube
Why am I not able to load the Stock Init extractor 2LIS_03_BX into the SnapShot Cube? Thanks
Hi,
The Diagnosis says:
This InfoSource is specifically set for the initial run of non- cumulatives. Only certain non-cumulative key figures are therefore displayed in the update rules.
If you donot have any Non Cumulative KF in the cube you can not use 2LIS_03_BX.
With rgds,
Anil Kumar sharma .P
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? ThanksHello 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 -
Inventory management snapshot model using Datamart Interface
Hi,
We have implemented Inventory management NON-CUMULATIVE scenario.
Now for reporting needs we are adding snapshot model and trying to use datamart interface to fill up snapshot cube.
But how to get value of KF say "ZTOTALST" becuase NON-*** cube has only changes stored as "0RECTOTSTCK" and "0ISSTOTSTK". If anyone has implemented or has any ideas on using snapshot model with datamart interface , please help .
regards,
Daljit BoparaiTry out with this
http://help.sap.com/bp_biv335/BI_EN/index.htm
Regards
Kumar -
Business Content Inventory Management (0IC_C03) Cube
I am thinking of adding a data staging ODS to our Inventory Management model. However, I wanted to check whether the delivered cube 0IC_C03 is aggregated or whether it is a representation of the R3 extraction. If the latter is the case I do not see the purpose of an additional ODS layer. Could anyone pass their thoughts? Thanks
hi Niten,
check oss note 581778-ODS capability of extractors from Inventory Management
Symptom
Data is not updated into the ODS when you load certain data records of the 2LIS_03_BF extractor.
Other terms
ODS, 2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 0STORNO, ROCANCEL, RODMUPDMOD, 0RECORDMODE, Inventory Management, 0IC_C03,
Application 03, Logistics Extraction Cockpit, LBIW
Reason and Prerequisites
The 2LIS_03_BF extractor does not return any "connected" after and before images, as in the SD extraction, for example.
Originally, the extractor was only designed for updating into an InfoCube. The extraction method was converted from the "D" delta process to "ABR1" with PI 2000.1 patch 4, or PI-A 2000.1 patch 4 so that it could be updated into an ODS object (see notes 322303, 385703 and 323811).
If documents are canceled in Inventory Management, a new document is generated (new document and item number).
This type of operation is transferred into BW with the "ROCANCEL" field set to 'X'. This results in the necessary inversion of quantities or value key figures. A new record is generated for this in the ODS (the "preceding document" has another key).
Example:
ODS key: Doc.
Movement data:
Document Item Document year Movement type Qty ROCANCEL
4711 1 2002 101 +100
4712 1 2002 102 -100 X
ODS contents:
Document Item. Document year Movement type Quantity
4711 1 2002 101 +100
4712 1 2002 -100
The "Movement type" field was set to "initial" in the data record for document "4712" by the processing during the ODS update.
Document 4712 is a before image (0RECORDMODE = 'X') for the ODS. Therefore, this data does not arrive in the ODS. Nevertheless, the before image (document 4712) does not have any context with the after image (document 4711) because there are different keys (document/item/document year). The SAP R/3 inventory management controls these activities with new material documents and (reversal) movement types.
BW technology note no. 747037 provides more information.
Solution
You have two options to evaluate cancellations or operations which contain reversal movement types and ROCANCEL = "X" in the ODS:
1. Implement a start routine
Insert the following code into the start routine of your update:
ODS key: Material doc.|Item number|Calendar year
BEGIN******************************
LOOP AT DATA_PACKAGE.
if DATA_PACKAGE-recordmode eq 'X'.
DATA_PACKAGE-recordmode = ''.
modify DATA_PACKAGE.
endif.
endloop.
END********************************
2. Change the transfer rules
With the transfer rules, do not assign the "ROCANCEL" DataSource field to the "0RECORDMODE" InfoObject in the InfoSource. As a result, only records with "0RECORDMODE" = ' ' are transferred to the ODS. For the ODS, the after images whose characteristics or key figures that are set to overwrite, are not deleted.
Other special features when updating the extractors of the inventory management into ODS objects:
1. 2LIS_03_BF and 2LIS_03_UM
a) ODS capability
For more information, see notes 322303, 323811 and 385703.
b) Key creation
For 2LIS_03_BF, see note 417703.
The following keys are available for 2LIS_03_UM:
1. MCMSEG-BUKRS
2. MCMSEG-BELNR
3. MCMSEG-GJAHR
4. MCMSEG-BUZEI
Field no. 4 is not delivered as standard in the extract structure, but it can be added using the Logistics extract structures Customizing Cockpit.
Field no. 1 may not be included in the relevant organizational structure.
2. 2LIS_03_BX (up to and including 3.0B 2LIS_40_S278)
The dynamic stock calculation from stocks (2LIS_03_BX) and movements (2LIS_03_BF) is only possible with (non-cumulative) InfoCubes.
Using ODS technology is only useful in this context for:
- an Enterprise DataWarehouse layer
- the realization of a snapshot scenario:
See the How to paper for this topic at:
-> http://service.sap.com/bw
-> left navigation area: SAP BW InfoIndex
-> info index: N ("Non-cumulatives") ->
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Use note 773823 to update the 2LIS_03_BX InfoSource into an ODS.
Note also that you cannot update any key figures into an ODS object (see notes 752492 and 782314). -
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
RKI 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. -
Inventory Management SnapShot ODS
What is the purpose of the SnapShot ODS, in the sense that why can I not just load directly to the SnapShot cube, my understanding is that if I look at the logic for say the total quantity and value key figures in the update rules to the cube this should be able to give me an upto date scenario or am I mistaken? Thanks
Hi Niten,
I am not sure if you are referring to any standard content ODS. But, generally speaking about snapshot scenarios, the advantages of introducing an ODS layer are:
- Overwrite feature
- you can keep data at a very granular level in ODS and create different cubes for different reporting scenarios or aggregation levels.
- additional flexibilty in loading data to cubes due to the introduction ODS.
Hope this helps. If you are looking at any specific case, do write back with details. -
Inventory Management Info Cube Compression!
Hi Experts!
Anybody please let me know the use of 'No Marker Update' while compressing the request in an infocube of inventory management.
Best Regards
Snuil.Hello Sunil,
Three datasources that are mainly involved :2lis_03_BX, BF & UM.
BX is used to load the opening balance. This request (for opening balance using BX) when compressed uses the marker update( i.e the No marker update is NOT checked).
This will update the marker and set a reference points that will be used to determine the stock figures.
BF is used to load the actual material documents. First load using BF when compressed need not update the marker( i.e the No marker update is Checked!!). Here the historic documents(for which the opening balance is already loaded) are loaded but the marker need not be updated.
Then onwards the delta loads the marker needs to be updated( i.e the No marker update is NOT checked).
Follow the same strategy for UM as in case for BF!!
Please also refer to
how to inventory management
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Hope it helps..
thanks, -
Inventory Management (0IC_C03) cube
When I carry out delta loads to the Inventory Management (0IC_C03) InfoCube do I need to compress these delta loads with No Marker Update? Thanks
hi Nitish,
1. Compressing the request containing the opening stock that was just uploaded. Make
sure the "No marker update" indicator is not set. Please consider note very carefully
643687 before you carry out the compression of requests in stock InfoCubes!
2. Loading the historical movements into the InfoCube 0IC_C03 via the DataSource /
InfoSource 2LIS_03_BF. Choose the upload mode "Initializing the delta process"
here.
3. After successfully uploading the historical material movements, the associated
request has to be compressed. You must make sure the "No marker update"
indicator is set. This is necessary because the historical material movements are
already contained in the opening stock. Well look more closely at markers later on. -
Inventory Management SnapShot model
In the How to guide it discusses on how to create a SNAPSHOT model for monthly loads.
Can I create a SNAPSHOT ODS and eliminate the Cube as part of my Data Flow and if so I believe the only change that I need to make is to check the BEx reporting flag in the ODS. Is this correct and are there any possible limitations with this approach? ThanksHi Niten,
I read in the document...
"If the SnapShot Scenario is chosen to reduce the Query-Runtime it should be taken in account that for recovery reason and for the ability to retrace the data it is only advisable to run an InfoCube with non-cumulative keyfigures with all the movements in parallel for a certain timeframe. For the administrator it is much easier to avoid, find and repair inconsistencies in the data. Inconsistencies could happen if data in the PSA is deleted and the update-/ transferrules do not fulfill all the EndUser requirements or the coding is just wrong. A reinitialization of all the past data could be necessary. In the SnapShot Scenario the past data is nowhere stored."
Hope it helps!
Bye,
Roberto -
Inventory Management: Snapshot ODS 2LIS_03_UM
In the How to guide the Update rule from 2LIS_03_UM for the Key Figure refers to:
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
ELSE.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 4.
ENDIF.
Is there only an error in the comment (duplicated) or is it that we only need one of the statements? Thankshi Niten,
returncode = 0 will update, returncode = 4 not update,
seems duplicated, comment will impact nothing to the program/routine.
hope this helps. -
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
ThanksHello 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 -
Snapshot scenario or non cumulative key figure in inventory management
Hi
We are currently using Inventory Management with non-cumulative key figures but we get very high performance problems due to so big number of lines in info cube.
We are analyzing the other scenario with snapshot and I am asking if it would be very realistic to use it to satisfy our requirement: to be able to get inventory management at day level for about 2 000 000 combinations article-site and about 100 000 stock movement lines per day (we are retailer!).
Is there somebody to give me advice about it?
Tanks a lot
AnneBeing a non-cumulative KF, total stock is automatically takes care of that.
Try putting all the restrictions which you have included for total receipts and total issues, for eg, restrict Total Stock with the movement types used in Receipts as well as Issues.
Check and revert.
Regards
Gajendra -
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 MenezesHi 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 -
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 -
Inventory Management Cube 0ic_c03, 0StockType
In the Inventory Management Cube 0ic_c03 queries,I've found that 0StockType has descriptions that are misleading because of the way they are written in domain bstaus (R3 side), especially when seeing the key and SHORT description (truncated beyond meaning).
OK I can correct these by changing BStaus 's texts.
The main changes I'd do are for the Customer Consigment, Customer Return Packaging and Material Provided to Vendor descriptions.
But what does 0StockType 'blank' (or #) mean ?
(It seems to mean something like Valuated Stock Valuation and 'Not Defined' is not very good in a Query result)Well, no one replied, but I got feedback from OSS. So just in case anyone is interested.....
I had to use r3 > se11 to change the domain descriptions myself.
Bstaus 'blank' I put as 'Valuation'
I also improved some of the Bsttyp descriptions whilst there
Maybe you are looking for
-
Remote Desktop and Brother MFC-6490CW not working
I have installed a Brother MFC-6490CW on my iMac 20" Intel with Leopard 10.5.6 and have had no problems getting to work using local mac programs printing through the USB cable. I cannot get it to work correctly when I log into my Windows 2003 Termina
-
Ddeleting the Second Row tag in XML output
Hi All, When I run the following query: select dbms_xmlgen.getxml('select wo.work_order_no, cursor(select regacc.work_order_no, regacc.work_order_task_no, regacc.regulatory_account_no from sa_work_orde_reg regacc where regacc.work_order_no = wo.work_
-
Is this only a one-way sync?
It doesn't seem like the edits I make in either Illustrator or Indesign gets sent back to the app? That would really be ideal. Maybe I'm not saving correctly? Anyway, looks very promising! J.
-
I would like to sell my G4. But first I would like to erase any information on the computer. How do I wipe it clean before selling?
-
OSX 10.4.11 (Tiger) and newest MacBook Pro - is it possible ?
Hello, I have just bought the latest high end MacBook Pro 2.5GHz and it came with Leopard. I would still like to work with Tiger. Is there a way I can boot with 10.4.11 despite it might (or it is not) be supported by Apple? I have am older MacBook pr