Validity table

hi experts , what is validity in BW it is created when we use non cumulative key figures but what is the purpose of it
Please search the forum. Also, Please read rules of engagement
Edited by: Pravender on May 21, 2010 10:53 AM

I am not sure I understood your question.
Are you saying 'country' is also a characteristic and you are getting additional data to the cube for these new countries? Or just that more data is now being added to the cube?
If the plants are more or less defined for similar date range, or are defined for the period for which typical reporting would happen -
Say plant 1 is valid from June 1999, Plant 2 from Apr 2001 .... and so on. This would be the situation where you need plant in the validity table.
However, if your users are typically reporting over last two years, and not many plants have been added in this period, and not many are likely to be added later, you can remove plant from validity table. This should generally not impact query performance. Only if users frequently report on the overlapping period (when the plant existed, and not existed) would there be some performance difference. Unless the no of plants is high (say 100 ) the difference in performance either way should be minimal.
This is my limited understanding ( ie to say do not go solely by it ).

Similar Messages

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

Validity Table not updating for 0IC_C03 while updating data

Hi,
1.Validity table not updating for 0IC_C03 while updating data in my BW 7.4 With HANA data base?
Key fields : 0Plant
0Calday
if you run this programe after loading data - RSDG_CUBE_VALT_MODIFY it is updating.
2. I am not getting no marker update option in non-cumulative Info cube 0ic_c03 manage tab or in DTP tabs check as per 7.4 modifications?
and 2LIS_03_BX in DTP I am getting below this option only
Can you please give me solution for this issues.
Regards
Umashankar

Hi Uma,
Please go through the below link which might be helpful.
Not able to Edit Validity Table : RSDV
Marker Update Option is available under Collapse tab of Info cube.
Thanks,
Karan

Validity table for a Non-Cumulative key figure

Hi,
I need to make changes to a validity table for a Non-Cumulative key figure.
I know initially it is done thru Extras- > Maintain Non-Cumulative value but subsequently how to change the parameters ?
Best Regards,
-Anurag Dev

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.

Validity table for stock cube

hi,
I am designing a stock cube with non-cumulative values.
Data for amounts of stock movements I plan to get from Transfer Order documents.
Data will be extracted on daily basis and in cube I want to have among others following chars: quant, storage bin, storage type and warehouse nr.
I would like to include in validity table such all of chars mentioned above (i.e. quant, storage bin, storage type, warehouse nr and date).
I am wondering is it ok to include so many chars in this table. Are there any guidelines for designing this table?
Can you suggest any documentation?
Regards,
Andrzej

You can use RSDG_CUBE_VALT_MODIFY report for this.
See:
http://help.sap.com/saphelp_bw31/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/content.htm
Also take a look on notes:
360249
534865
419490
Regards

Validity Table in Non cumulative cube

Hi Friends,
What is the use of validity table in Non cumulative cube?
I have already studied the document 'How to Inventory
Please can any one explain me with example.
Thanks & Regards,
Ramnaresh.P.

Hi,
Validity table is created for non-cumulative key values.
Non cumulative key figures are one which are not possible to cumulate such as head count, inventory amount, these are always in relation to a point in time.
Regards,
Shiva.

FK01: Vendor Master Record Validation Table is not maintained

Hi Experts,
Appreciate your help on this matter: I have created a new Vendor Account Group and tried to used it. However, upon saving I encountered problem: error message Vendor Master Record Validation Table is not maintained. Do I missed some configuration?
Thank you very much!

Hi,
STEP 3 : In Financial accounting > A/R A/P > Business Transactions > Outgoing payments > Manual Outgoing payments >
Define Tolerance (Vendors)
STEP 4 : Create a GL A/c Creditors in FS00 as a balance sheet a/c and in control tab give reconciliation type as Vendors
and Field Status Group G067. Assign this account in company code data in FK02.
Regards,
Sadashivan

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.

APP-FND-01444 additional columns in "validation table information"

I have the following ERROR, when add additional columns in validation table information.
Table Name: “oe_order_headers_all oea, HZ_CUST_ACCOUNTS hca, hz_parties hp”
Table Columns:
Name
Type
Size
Value
OEA.ORDER_NUMBER
Number
10
Meaning
ID
OEA.HEADER_ID
Number
10
Where/Order By: OEA.SOLD_TO_ORG_ID = HCA.CUST_ACCOUNT_ID
AND HCA.PARTY_ID = HP.PARTY_ID
AND OEA.FLOW_STATUS_CODE= 'BOOKED'
Aditional Columns: HP.PARTY_NAME"Customer"(50)

the problem was the following space were not there.
Aditional Columns: HP.PARTY_NAME "Customer" (50)
before and after "Customer" there were no space. so we need spaces before and after the column name.

Validity Table Question - 0CALDAY and 0PLANT

Hi, I have an Inventory InfoCube 0IC_C03 and I noticed that the validity table has both 0CALDAY and 0PLANT checked.
I read the documentation that it's best to have just 0CALDAY.
http://help.sap.com/scenarios_bus2004/helpdata/en/42/266241fe918347e10000000a1550b0/content.htm
The document does mention a 0PLANT scenario, but I'm not quite understanding it.
1. Will it hurt to have 0CALDAY and 0PLANT?
2. What would be the consequences from a reporting perspective if I have 0PLANT in the Validity Table?
Thanks!

*copy paste from some other forum*
Validity table defines the range of the characteristic values for which the non-cumulative KF is valid.
Let us say your cube has 0calday, and it has data from 01/01/1999 to 12/31/2000. If you run a query and check (say its stock cube) stock balance per day per plant, it will calculate balances for each plant and show starting from 01/01/1999 onwards.
However, if you had a plant that became operational on 06/01/2000, you wouldn't want to see a 0 stockbalance for it starting from 01/01/1999 (or say when calculating the average, take as if stock existed from 01/01/1999) but from the date the plant actually existed ie 06/01/2000.
In this case, if your validity table had only 0calday, your report would show 0 stock for each day from 01/01/1999 to 06/01/2000 for this new plant (not a good idea), while if you defined it at plant level, you will see the report starting at 06/01/2000 while it will start from 01/01/1999 for other plants. This is what you want
see this http://forums.sdn.sap.com/thread.jspa?threadID=318570
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204a99c7-b3c5-2e10-f18f-e3ddb6ec6ad3?QuickLink=index&overridelayout=true

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

MySQL connectivity problem: no validation table provided

hi there,
As a superbeginner, on my Mac G4 OSX 10.4 I am trying to add a MySQL database in Sun JSC 2.1, following the tutorial:
Creating Database Server Types and Data Sources
So far I have managed to
-install mysql 3.1.14 and
-add this as a new database server
When I try to add a data source, I cannot select a validation table (message: No Tables were found. Check your connection information), and I cannot find in the manuals how to make one. When I test the connection the connection status is succeeded, but the validation table status is failed (No validation table provided...)
In a seccond attempt, I also installed MySQL 4.1.21 and navicat (in which the connection seems to be good), but I cannot figure out how to connect this version 4.1.21 to the JSC, because 4.1.21 differs in installation (it uses an installation package in stead of a zipped folder) which is not covered by the tutorial.
Any hints on one of the two attempts, or a suggestion for a database which might give a beginner like me less problems to connect? Thanks a lot.
[email protected]

I think the simplest way is:
create a table:if you have mysql 5.x you can di it with mysql tools (mysql administrator or mysql query browser), if you have a non graphical version of mysql you have to create the table with prompt.
Create table Paziente (
     codice_fiscale_paziente Char(20) NOT NULL,
     nome Char(20),
     cognome Char(20))
     ENGINE = MyISAM;
than open JSC (it doesn't have a jdbc driver installed to work with mysql, you have to download from mysql website and install in jsc)
servers--> right click -->add data source
than :
data source name : the name you want to use
server type: mysql
database name : your's database name
if you have user autentication in your db, set user and password
set the correct db url
and... test connection
it should work

How to insert a value in the Validity Table with Report ABAP

Hi,
I should insert in the validity table in the field "To Mode" the value "R" through a report ABAP.
Is possible? Have I seen that the exist FM RSDV_INSERT_VALID_TAB. Is possible to use ? As?
Thanks.

Hi, thanks the same to everybody. I have already resolved.
Regards.
Charly1

How to setup a validation table in the IBM AS400 ?????

I am trying to use the Java studio creator with the IBM AS400
and I am having difficulty setting up a validation table.
I created a totally new DB2 SQL table, with just a couple of columns.
However, when I use it as the validation table to setup the Datasource, I get the following message:
[SQL5016] Qualified object name PMABR not valid.
The ideal validation table exists only for connection validation purposes. Do not use an existing table that has a large number of rows or a table that will be frequently accessed.
any ideas?
thanks a lot

Thanks for rectifying me Howard.
I just read your full article on this too and its very well explained here:
http://www.dizwell.com/prod/node/357
Few lines from your article
It is true, of course, that since Version 8.0 Oracle has provided the ability to create a Keep Pool in the Buffer Cache, which certainly sounds like it can do the job... especially since that word 'keep' is used again. But a keep pool is merely a segregated part of the buffer cache, into which you direct blocks from particular tables (by creating them, or altering them, with the BUFFER POOL KEEP clause). So you can tuck the blocks from such tables out of the way, into their own part of the buffer cache... but that is not the same thing as guaranteeing they'll stay there. If you over-populate the Keep Pool, then its LRU mechanism will kick in and age its contents out just as efficiently as an unsegregated buffer cache would.
Functionally, therefore, there can be no guarantees. The best you can do is create a sufficiently large Keep Pool, and then choose the tables that will use it with care such that they donâ€™t swamp themselves, and start causing each other to age out back to disk.
Thanks and Regards

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

Validation Tables and Constraints

Ok, here is an interesting question. If you had validation tables such as building codes with their translations, or person type codes, or sorority codes, or anything that has changing codes that are valid and invalid over the years --- that your database application used with data this person lives in this building code and it goes to get the long translation from the validation table ( a whole bunch of them) and you wanted to increase the efficiency of such validation tables so that you could put a STATUS (old do not use now but valid for old data, active use now for new data), how would you go about doing this en masse for the whole database and all of the validation tables?
Would a constraint work, user defined? And how? Or how would you most efficiently go about this?

Ability to deactivate old values in validation tables but leave them for integrity of historical data
VALIDATION - include the ability to inactivate old values in the validation tables so that these values can be in the database for old rows (records) but cannot be used for new rows (records).
The fact to leave the old value in there is for referential integrity for the old data values but show they are inactive and to only allow new data to be added with CURRENT valid values. No matter what you tell the people entering the data, if a value is valid for entry they will enter even if it has not been used for years
How to do this most efficiently with constraints now or will we have to add triggers to every piece of update and insert code?

Validity table

Similar Messages

Maybe you are looking for