What is meant by referential integrity

hi
what is meant by referential integrity

Hi,
Referential integrity is the property that guarantees that values from one column depend on values from another column. This property is enforced through integrity constraints.
If you set this flag a check for referential integrity is performed for this InfoObject, against the master data table or ODS object. The InfoObject is checked for valid characteristic values.
It is used when v r doing Flexi update...
Prerequisites for checking for referential integrity:
Data is updated flexibly
You have activated error handling in the BW scheduler (Tab page Update)
On the Update tab page in the BW scheduler, you have selected the option Always update data, even when no master data exists for the data.
send ur id, i will send u screen shot of ref.integrity
regards
reena

Similar Messages

What is mean by Referential Integrity? Where do we use it and Why..?

Hi All,
Can anybody tell me, What is mean by Referential Integrity? Where do we use it and Why..?
Regards,
Kiran Telkar

Dear Kiran Telkar ,
you might be knowing that generally refrential integrity is concerned with nothing but primary key and foriegn key relationship. Generally we use to check uniqueness of records.
In sap we use it during flexible updation...to check the data records of transaction data and master data.
In other words, to check before loading of data, that whether loading will be properly or not.
we will check(tick) the option in the maintainance of the
<b>infosource--> communication structure</b>
it will be better if you clearly mention your problem, if further help is needed.
hope this will help you.
Regards
vinay
<i>please assign points to all who will help you.</i>

What is meant by seamless integration?

What is meant by Seamless Integration using XI ?
When we use BAPI technology for Integration between SAP and Non-SAP systems, the flat file concept comes into picture.
I do accept that the maintainance of this kind of point to point (BAPI) interface is pretty complex and labourious.
But how XI will comeover this issue....????
Can anyone explain me about this...????
Regards
Pavan

>>But how XI will comeover this issue....????
Designing Scenarios like.
IDoc -
> XI -
> IDOC
IDoc -
> XI -
> File
File -
> XI -
> IDOC
RFC -
> XI -
> File
File -
> XI -
> RFC
File -
> XI -
> File
Proxy -
> XI -
> File
File -
> XI -
> Proxy
Webservice -
> XI -
> IDoc.. Bla Bla Bla............ !!!
Regards
San

What is self referential integrity? How does it effect the Database?

Hello Gurus,
What is self referential integrity?
How could it is achieved and implemented?
and what is effect on the Database?
Thanks in advance.
~ SubbaReddy .M

Self referential integrity simple means that the parent end of a foreign key constraint is in the same table as the child end. Consider the SCOTT.EMP table. Every manager is also an employee. Hence there is a foreign key between the MGR column and the EMPNO column.
rgds, APC

Whats is referential integrity

Hi all,
What is referential integerity found in the communication structure ? what is it significance and when do you use in real time scenario. pls explain with an real time scenario.
what is cardinality ? and when shd u used cardinality and cardinality can be only defined in infocubes isnt it? can cardinality be defined in ods ?
thanxs in advance
hari

Hi Hari,
Referential Integrity: Its a DataBase concept which combines(logically) the data of multiple table with the master table. Here master table has the primary key and rest of the tables have the same key as forienkey.
Here we use the characteristic (or combinations of Chars) call as referential char.
check this.
you might be knowing that generally refrential integrity is concerned with nothing but primary key and foriegn key relationship. Generally we use to check uniqueness of records.
In sap we use it during flexible updation...to check the data records of transaction data and master data.
In other words, to check before loading of data, that whether loading will be properly or not.
we will check(tick) the option in the maintainance of the
infosource--> communication structure
it will be better if you clearly mention your problem, if further help is needed.
http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/14c43bb7137503e10000000a11402f/content.htm
Referential integrity is the property that guarantees that values from one column depend on values from another column.This property is enforced through integrity costraints....
see this link...
http://help.sap.com/saphelp_nw2004s/helpdata/en/6d/117c5fd14811d2a97400a0c9449261/content.htm
Please find the below url
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=referential%20integrity&cat=sdn_all
thanks
@jay

Maintaining referential integrity using MS SQL server

Some time ago I posted a question relating to the following extension:
<extension vendor-name="kodo" key="jdbc-delete-action" value="null"/>
Kodo generates a "on delete set null" constraint for this, however ms sql
server does not support this. Since I don't want to matain this referential
integrity in my java code (meaning as soon as an object is deleted, setting
all references to it to null), I tried to implement a custom dictionary with
the default ms sql server solution for this problem: creating a trigger by
overriding the "getAddForeignKeySQL" method. This works fine when creating a
database from scratch using the schema tool, however, when updating an
existing databasebase schema, this is ignored, thereby not solving the
problem of having the database maintenance automated. I suppose I have to
write code for checking whether the trigger already exists. Browsing through
the code, I couldn't figure out how this is done. Can someone give me
suggestions on how to do this (and if this takes a lot of effort).
I also would like to know whether solarmetric has intentions to deal with
this problem in their framework. To be honest, I was quite surprised that
Kodo doesnt take care of this, leaving my database in an inconsistent state.
kind regards,
Christiaan

"Abe White" <[email protected]> schreef in bericht
news:caaunu$ecj$[email protected]..
>
I also would like to know whether solarmetric has intentions to dealwith
this problem in their framework. To be honest, I was quite surprisedthat
Kodo doesnt take care of this, leaving my database in an inconsistentstate.
>
Well, I would say that you're the one leaving the database in an
inconsistent state by not keeping your object model consistent :)From the manual:
6.2.2.12. jdbc-delete-action
If a field holds a relation to another object, you can use the
jdbc-delete-action field extension to control the delete action of the
database foreign key that models this relation. Possible values are:
null: Null the column(s) of this foreign key when the related record is
deleted.
It does mean that if the primary key record is deleted, all foreign keys to
the record are set to null, right? Since the jdo framework is about database
independence, not writing sql code (and of course lots more;) and Kodo
supports ms sql server, I would have expected that kodo to set the foreign
key to null if the object is deleted. Even if I do know sql server supports
does not support a 'on delete set null' sql statement;)
>
We have no plans to create triggers at this time.
What do you mean when you say "it is ignored" when you're updating?
Exactly what tool are you running, what actions are you running with, is
the foreign key extension present, and what is the outcome?Like I said, I wrote code in the "getAddForeignKeySQL" in the dictionary, so
a trigger is created when creating the database in the workbench (by running
the schematool). However, if the table already exists, but not the trigger,
refreshing the database from the workbench does not call the
getAddForeignKeySql to add the trigger to the table.

I have been interested in how lightroom uses the catalog so was poking around a backup of the catalog. I found it rather concerning that although the database (catalog) is pretty well designed, there is no referential integrity defined or enforced.

I have been interested in how lightroom uses the catalog so was poking around a backup of the catalog. I am a database administrator and I found it rather concerning that although the database (catalog) is pretty well designed, there is no referential integrity defined or enforced. This is non-standard practice and could well be the source of corrupt catalogs I have seen many people complain about. I would strongly recommend the developers modify the catalog and adopt best practices if they want to improve the stability of Lightroom and the catalog.

I would imagine that data integrity is not enforced for performance reasons. In a closed environment like LR where the application has complete control over the data, enforcing data integrity may not be worth the performance hit. Often what is done in an environment like this is to have data integrity on in test environments which would expose data integrity bugs but where the impact of performance is low. In "production" it is then turned off to get as much performance as possible. I would say there are many more complaints about performance than corrupt catalogs. And corrupt catalogs are more likely due to interruptions in writing to the catalog (like crashes, backups or dropbox activity while LR is running, etc). Data integrity would not help in these cases as they are outside the databases control.

CDG-01141 ERROR: Module Component Table Usage ... Table usage ... requires primary key column for referential integrity

For some strange reason when I modified a form, (commented out some code in a when-window-activated trigger) I now get the following error.
CDG-01141 ERROR: Module Component Table Usage GR1130A.CUSTOMER.GR_CUSTOMER.GC: Table usage GR_CUSTOMER requires primary key column for referential integrity
I am sure this is not related to my change, but do not know what may have caused this or how to fix it.
Anyone seen this error before? been able to fix it?
Thanks!
Windows 7
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
Designer Version 6.5.95.4.8

You know that Developer/Designer 6i is not certified for Windows 7, right? Also, your version is not the latest one, so you can try to install the latest patch set first.
>Table usage GR_CUSTOMER requires primary key column for referential integrity
Check if there is a PK in the table definition (not in the database, but in Designer).

Self Referential integrity constraint?

What is self-referential integrity constraint? Is it a foreign key where the same column acts as the parent key too.

The good old EMP table in the SCOTT schema is one example. Managers are employees, so the MGR column refers back to the EMPNO primary key. If I wanted to create my own table...
1 create table emp2 (
2 empno number primary key,
3 mgr number references emp2( empno )
4* )
SCOTT @ hp92 Local> /
Table created.Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

What is meant by cost element

hi
what is meant by cost element

HI.
Differentiation of Cost Elements
Use
In call management, it is necessary to differentiate cost elements further for the settlement of orders in profitability analysis. Both the costs incurred and the sales deductions are classified according to their source, and assigned to the appropriate cost elements. For example, the following costs are differentiated:
Sales costs
Warranty costs
Good will costs
Sales deductions due to warranty
Sales deductions due to good will
The differentiation of costs and sales deductions enables you to assess more accurately the profitability of your products.
Integration
The differentiation of cost elements is only of use if the service orders are settled in profitability analysis.
Prerequisites
Resource-related billing must be performed for service orders.
You must have defined the accounting indicator in Customizing for Plant Maintenance.
When you create a service order, you define the accounting indicator in the header, under administrative data. Currently it is only possible to have one accounting indicator per order.
Once the order is released, the accounting indicator can no longer be changed in the order header.
Features
When actual postings are made for a service order, the system creates CO single records and a CO totals record. When doing this, it copies the accounting indicator defined in the order header, and enters it in the origin of the totals or single records.
In addition to the variance class and the cost element, the accounting indicator is a further characteristic of the PA transfer structure.
The transfer of the accounting indicator to the origin also makes it possible during the settlement of a service order in profitability analysis, to navigate more specifically in the PA transfer structure. The costs and sales deductions for warranty, good will, and sales are entered in the respective value fields.
Reward all helpfull answers.
Regards.
Jay

What is meant by administered objects in jms

what is meant by administered objects in jms..
and
is this Analogy true : JMS Provider like JDBC Driver
or JMS Provider like DBMS(IBM MQ)
what that provider is.....

In my previous job I was developer/administrator etc for the was environment and although I don't know if there are any hard and fast rules to what administered objects are I classed anything that get created in WAS as adminstered objects so that would be the likes of:
JMS Queues
JMS Queue Connection Factories
Datasources
J2C Aliases
JDBC Providers e.g. Sybase driver
In the case of WAS 6+ then that would also include your service integration buses, foreign MQ buses etc.
Basically anything that you can script using wsadmin
Hope that helps.
Matt

Referential Integrity

Hi,
Is there a way to ensure semantic consistency of the ontology stored in Oracle 11g at insert/update/delete time? This would be equivelant to referential integrity in the relational model.
Thanks,
Essam

Reponse to Essam: One possibility is to call the validation procedure via a trigger on inserts. But of course that would be computationally intensive. But perhaps there are only some situations that could lead to semantic inconsistency, and the trigger could be used for only those situations (and not on every insert)?
Response to Christian: This is something we can look at in the future. If you have more detailed feedback on what you like to see do write to me at melliyal <dot> annamalai <at> oracle <dot> com
Melli

Foreign Key or Referential Integrity

Hi All,
I would like to know whether Sun Java System Directory Server supports the concept of foreign key or referential integrity? I would like to have LDAP entries point to other LDAP entries in a different subtree of the same DIT. Is this possible?
Please help.
Rgds,
anna
(http://missingrainbow.blogspot.com)

What you're asking is called Aliases in the LDAP terminology.
Sun Directory Server does support creating alias objects, but does not support dereferencing them during searches or reads.
Referential Integrity is about removing or changing attributes with the DN syntax when the entry they reference is deleted or renamed. Sun DS does support referential integrity via a plugin. The list of attributes for which it's enforced is configurable (and should be indexed).
Regards,
Ludovic.

What is meant by costing key?

Dear Experts ,
while releasing the billing document to accounts , i am getting error like
Valuation with material cost estimate: error, The system looked for the material cost estimate using costing key "002", as defined in the Customizing settings for CO-PA, incomplete due to FI/CO interface
what is meant by costing key?
regards
rajakarthik

Hi,
In Costing based Profitability analysis you define costing keys. A costing key is a set of access parameters which are used in valuation to determine which data in Product cost planning should be read. In the costing key you attach the costing variant.
In the costing key you specify whether the system should read the current standard cost estimate, the previous standard cost estimate or the future standard cost estimate or a saved cost estimate.
The configuration settings to determine this costing key is as follows:
Assign costing keys to the products u2013 Three costing keys can be attached to a single product for a specific point of valuation, record type, plan version.
Assign costing keys to Material types
Assign costing keys to any characteristics u2013 You can use your own strategy to determine the costing keys. This is through user defined assignment tables.
regards,
Santosh kumar

Issue with Referential Integrity check in Oracle VPD Policy

Hi,
Lets assume I have two tables - Customer and Order, with cust_id in Order table referring to primary key of Customer table.
Example Data;
Customer
cust_id Name
1 abc
2 def
3 ghi
Order
Order_id cust_id Order_type
1 1 A
2 2 A
3 1 B
Now I have policies defined on both the tables;
- for "Select, Insert, Update" queries on Customer table.
- for "Select" queries on Order Table.
Policy 1 on Order Table;
Irrespective of the user, predicate = 'Order_type = ''A'''
Policy 2 on Customer Table;
Irrespective of the user, predicate = '(select count(1) from order o where o.cust_id = customer.cust_id and o.order_type = ''B'') > 0'
My intention is to show only those customers who have atleast one order of type 'B'. And this policy works fine in case a user tries to read data from customer table. (for example, record for cust_id = 2 will not be returned as it don't have any orders of type "B")
However, when a user tries to insert record in Order Table, because of the existing referential integrity constraint, the Policy on Customer table is also getting triggered. And an exception is being raised "ORA-28113: policy predicate has error".
Could someone please explain why this is happening ?

I'm afraid, there is no such a mean.
At least I do not know about it.

What is meant by referential integrity

Similar Messages

Maybe you are looking for