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

Similar Messages

Inventory Management (0IC_C03) Business Content queries

I have the following queries which are delivered when I activate 0IC_C03. The queries below have also been activated as part of the model.
Is there any additional queries which should/can be activated against this InfoProvider and of the list below are any redundant? Thanks
Blocked Stock
Consignment Stock at Customer
Inventory Turnover
Quantities of Valuated Project Stock (as of 3.1 Content)
Quantities of Valuated Sales Order Stock (as of 2.1 Cont.)
Receipt and Issue Customer Consignment Stock
Receipt and Issue of Blocked Stock
Receipt and Issue Quality Inspection Stock
Receipt and Issue Stock in Transit
Receipt and Issue Vendor Consignment Stock
Scrap
Stock in Quality Inspection
Stock in Transit
Stock Overview
Stock Overview (as of 3.1 Content)
Stock Range of Coverage
Valuated Stock
Valuated Stock (as of 3.1 Content)
Vendor Consignment Stock

hi Niten,
by choosing that 0IC_C03 and using grouping 'in dataflow afterward' in business content activation, you should get all the queries.
you can cross check in rsa1->metadata repository->local object (business content).
in sap help
http://help.sap.com/saphelp_nw2004s/helpdata/en/77/65073c52619459e10000000a114084/frameset.htm
(expand left node)
hope this helps.

Inventory Management Extractors via DSO to Cube 0IC_C03

Dear experts,
to fulfill the requirements of DataWarehouse spirit using Entry-, Harmonization- and Reporting-Layer I want to use for Inventory Management a Data Flow from extractors 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM via DSO/DSOs and later on to Cube 0IC_C03.
In this forum there are some opened threads about this issue, but none has been resolved! Many hints are about the "How to Inventory Management..." - some other say: "You can use DSO's!" - others say: "Don't use DSOs!". So: Where is the truth? Is there anybody who can provide a really praticable way to implement the above mentioned data flow?
I'm so excited about your suggestions and answers.
Thanks in advance and regards
Patrick
--> Data Flow has to be in BW 7.0

Hi Patrick,
Yes indeed there is.
Using DSOs in inventory flow is absolutely possible. Here's what you need to know and do:
1 - Firstly don't be apprehensive about it. Knowledge is power! We know that inventory uses ABR delta update methodology and that is supported by DSOs so no doubt abt it.
2 - Secondly Inventory is special because of non-cumulative and several rule group at cube level for BX and BF.
3 - Now as you want to use a DSO and I am presuming that this will be used for staging purpose, use a write optimized DSO as the first layer. While mapping from DS to this DSO, keep one to one mapping from field to Info-objects.
4- Keep in mind that from Infosource to 0IC_C03 there would be multiple rule groups present in transformations.
These rule groups will have different KPIs mapped with routines. The purpose is that from ECC only 1 field for quantity (BWMNG) and one field for value (BWGEO) is coming but from Infosource to 0IC_C03 the same fields in different rule groups are mapped to different KPIs (Stock in transit, vendor consignment, valuated stock etc) based on stock category, stock type and BW transaction keys.
5- So create a write optimized DSO. map it one to one from datasource fields. create/copy transformations from this DSO to cube maintaining the same rule groups and same logic.
6- you can also use standard DSO and create rule groups and logic at DSO level and then do one to one from DSO to Cube.
Keep in mind that these rule groups and logic in them should be precisely the same as in standard flow.
This should work.
Debanshu

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 and physical inventory data transfer

hi all,
can anyone plz povide me with inventory management and physical inventory data transfer tutorial or link.
points are guarented.
rgds

The information behind the blue-button for MI34, MI38 (as you mentioned) does not have enough detail. It's basically one-page. Is there another instructional source available? How is the logical file MMIM_PHYSICAL_INVENTORY_DOCUMENTS tied to the physical, can you clarify? Not sure how to determine where the sequential file being processed needs to be located. Thanks!

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

Inventory management

Hi,
In Inventory management ...for reports i am using standard queries taken from metadata repository but i am not using the standard cube instead using a custom cube and copied all those queries on to custom cube...since for all figures routines have been written in update rules...
please tell me wheather i need to test them with R/3 to know whether data flow or data entries are right or no...
if i have to test from BW to R/3 then i need to test them in Standard reports of R/3 not using RSA3 becoz the values of key figures are calculated during runtime and i dnt get them in RSA3 m i right?
please suggest me where i can search the standard reports in R/3...which transactions i need to use...
e.g.Receipt quantity :Blocked stock(0RECBLOSTC)
WHERE can i get the values for this in R/3?
thanks in advance,
Vijaya

Hi,
The information on "how to validate" given in the note 586163:
<i>TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
Note 766622 provides you with the option
of creating a LOG file for the extraction.</i>
With rgds,
Anil Kumar Sharma .P

Inventory Management - 0IC_C03 InfoCube Partitioning (Recommendations)

Hello Everyone,
I have gone through most of the postings available on SDN and other white papers related to Inventory management implementation.
I did not get enough information and most of the information has given me both yes and no answers for partioning of the InfoCube.
I am looking for,
Can you please recommend what is the best practice for Physical and logical partitioning of 0IC_C03 InfoCube.
We have Calendar Day, Calendar Month, Calendar year in time characteristics and plant as the validity characteristic.
I have gone through couple of white papers which recommend avoid using the time characteristics for partitioning and rather use plant or territory grouping as applicable.
But some forum postings I have gone through mention that the partitioning has been done on time characteristics.
What is the impact of marker update and the paritioning being done on the time characteristics.
So, can you please let me know what the best practice would be and the reason for partitioning in the way whichever you recommend.
I really appreciate your input.
Thanks
Dharma.

Hello Naveen,
Thanks for the prompt response.
I understand that the partitioning by time characteristics is not useful because of how the data is accessed.
When I mentioned that the partitioning is considered on Plant or Territory.
I mean to use the logical partitioning where I am thinking of loading in my data based on the territory field which would then be grouped into regions.
In this case it can be Region 1, Region 2 and Region 3
Where
Region 1 --> Data from Territories 1,2,3
Region 2 --> Data from Territories 4,5,6
Region 3 --> Data from Territories 7,8,9
Once this has been done, I am planning of implementing the entries in RRKMULTIPROVHINT table to accordingly split the queries from Multiprovider.
The reason being most of the reporting is done at the territory level which in turn would help re-route the queries to appropriate part provider.
I am more worried about the physical partitioning for an InfoCube in order to have good database breakdown.
Thanks
Dharma.

Analysis Process Designer and Inventory Management

In the How to guide for Inventory Management it mentions that you can you can intialise stock in the Snap shot Cube using the Analysis Process Designer (APD). Has anyone done this and if so can you explain how or outline some steps? Thanks

Hallo,
the APD does`nt be a useful tool for modeling a performant
data flow. A lot of SAP BW user think so.
The performance problems are given by the ddic intern table, using to uploading the extracted data into the apd used wa_table and structures.
To have the best performance on your scenario, please use the following scenario as possible.
Step 1.
upload the extracted data from the psa into a data layer
there you can reduce and harmonize the data by using a transactional ods
Step 2.
build a infoset that joins the data
Step 3.
build one query to reducing data and make two copies of ist
Step 4.
build a useful data mining model
Step 5.
upload the results of the data mining model into a transactional ods
Step 6.
link the uploaded data into a infoset ore write back into a standard ods
Step 7.
query the data
If you use this scenario you have a lot of benefits. Better performance, better quality of persistent data and actual and traininged data.
The recommend next step (if you want a alerting) is to build a reporting agent report - if you have usefull processes in the query.
There are a workshop for Data mining and APD, named BW380.
I hope I helped you.
Otherwise give me a message.
[email protected]

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

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

Print Smartforms in Inventory Management

Dear Sappers,
My client requires a lot of samrtform in INventory Management including SC DC, Stock Transfer DC, GR etc.GR Smartform is coming as per my configuration.But other smartforms are not coming as per y configuration.
When I see the material documnet in MB02.I saw all the o/p types are coming for the respective transaction.Foe ex: If i'm going for Stock Transfer Smartform Print, I can see all the O/P types in the material document.So when I'm going to Print in MB90, the smartform is not triggering and system is giving one message.
Output could not be displayed (it may not be complete) Message no. VN069
Same thing applicable to S/C DC and other smartforms.
Is there any link between movement types and O/P types with access sequence??
Is there any other settings are there to take print????
Our client requires a smartform for Sub Contract DC.It's developed.In Inventory management I've assigned the programme name and smartform name and made the necessary settings.Even though I made the print is not coming.
Can anybody tell me where I've done the mistake?
I've created my o/p copying the standard WLB3 and created my own.
IN general data I put access sequence as 0004 & in default value I put dispatch time as 3 and transmission medium as 1.I made Print parameter as 7 plant/ storage location.
In processing routine I put the necessary programme name and smartform name.
In NACE, I've taken ME - Inventory Management.Out O/P type and Trans/Event Type as WA, print Version 3, Print Item 3 and debit/Credit Indicator as H (Credit).
I assigned the Printer name there.
Apart from that I made the goods movement respect to plant and storage location as well as movement type.
Still my print is not coming.
Any suggestions.
Thanks & Regards
PKB
Edited by: Pranaya Barik on Oct 13, 2009 1:48 PM

Hi
I'm waiting for the reply still I'm not getting any suggestions from.
We've developed smart form for Sub Contract DC.I've made the necesssary settings for this. Still Smartform print is not coming.If anyone works on Smartform for S/C DC, tell me how to do the necessary settings to get print preview of S/C DC.
Waiting for the respond??
Thanks & Regards
PKB

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, New Snapshot Scenario

We are planning to implement the New Snapshot scenario for Inventory Management. This is based on the "How to...." document. As per what is shown in the document, all the 3 extractors feed into the same DSO. However, when I try to create the Update Rules for <b>BX</b>, I get a error that there is no key figure. However, the DSO (Standard) has the Key figures. These are cummulative. Maybe, because of that I get the error when I create update rules for BX. But then, in the document the key figures appear. How is this possible.
Has anyone tried this and has been successful. If so, I'd appreciate if you could send some tips.
Thanks

hello
can you please take a screenshot of your data model and update rules (inside) and send me to (see email in card)
It will really help me!
Alex

Inventory management: Validy dates in queries???

Similar Messages

Maybe you are looking for