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

Similar Messages

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

Validity table--how

hi gurus,
i am loading data for Inventory management.
in the document how to manage inventory management i read about validity table....r time reference characters, somebody kindly explain me the link between reference point and validity table and plz explain what is validity table with examples.
any help will be appreciated.
thanks and regards
neelkamal

Hi neelkamal
Look at this previous threads
Inventory Management: Validity Table
Validity table for stock cube
and these links
http://help.sap.com/saphelp_nw04/helpdata/en/67/86b264415811d1893d0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/7e/c81e6d52c511d182c50000e829fbfe/frameset.htm
Regards
Naalla

Set up validity table for inventory management

Hi all,
somebody know if it is necessary reload the infocube 0IC_C03 every time that change the transfer method with the Tx. RSDV?
Thanks in advance.
Facundo Romero.

Hi,
If you decide later that you require more validity-determining characteristics, you can modify the selection using the report RSDG_CUBE_VALT_MODIFY. In this report, the non-cumulative InfoCube is only changed to the extent that the new validity-determining characteristics are selected and the validity table is reconstructed. The structure of the non-cumulative InfoCube remains the same. You do not have to reload the transaction data for it.
I hope this helps.

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

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

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

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

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

Define the Characteristics of the validity table for non-cumulatives

Hi Friends,
Here I am designing MultiProvider ( ZCA_M01), based on the Two Business content info cubes (0IC_C03 & 0SD_C03 ) & one customized info cube (ZPUR_C01).
I done Identification for char & keyfigures also.
When i trying to activating the Multiprovider, here i am getting the error , error message is : Define the Characteristics of the validity table for non-cumulatives.
Even here I am attaching the error message help also.
Message no. R7846
Diagnosis
The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube).
Besides the most detailed time characteristic, additional characteristics for the InfoCube can be included in the validity table:
Examples of such characteristics are:
A "plan/actual" indicator, if differing time references exist for plan and actual values (actual values for the current fiscal year, plan values already for the next fiscal year),
the characteristic "plant", if the non-cumulative values are reported per plant, and it can occur that a plant already exists for plant A for a particular time period, but not yet for plant B.
Procedure
Define all additional characteristics that should be contained in the validity table by selecting the characteristics.
In the example above, the characteristics "plan/actual" and "plant" must be selected.
The system automatically generates the validity table according to the definition made. This table is automatically updated when data is loaded.
Please take as a high priority.
Thanks & Regards,
Vanarasi Venkat.

Hi Venkat,
If you want to include 0IC_C03 cube in your multi provider the you must make sure that the time characterestics ( 0CALDAY, 0CALMONTH ....) are present in all of the other info providers which you are including in the MP. The Time char to choose depends upon the Inventory cube in which you have mentioned during the definition. As you are using the standard cube 0IC_C03 it has the time char as 0CALDAY. Try to include this in all the other info providers and dont include more tha one Non-cumulative in the MP.
Try this and see if it helps....

Inventory Management: Validity Table

Similar Messages

Maybe you are looking for