Cardinality and semantic attributes -foreign key-table

Does sematic attributes and Cardinality needs to be filled in while creating foreign key??
I find that Foreign key created without the above works fine..
whats the significance of them?
Edited by: ksiva on Aug 26, 2008 4:17 PM

Hi,
Its work fine,
cardinality: The cardinality (n : m) describes the foreign key relationship with
regard to the number of possible dependent records involved (records of
the foreign key table) or referred records (records of the check table).
e right side of the cardinality has the following significance:
o   m = 1
    For each record of the check table there is exactly one dependent
    record.
o   m = C
    For each record of the check table there is at most one dependent
    record.
o   m = N
    For each record of the check table there is at least one dependent
    record.
Forein key: The foreign key field category describes whether the foreign key field
identifies the foreign key table.
Regards
jana

Similar Messages

Hi guru's what is forign key , and what is foriegn key table

hi guru's what is forign key , and what is foriegn key table

hi...
Foreign key is nothing but simply we can say,
A field in one table related to field in another table..see the below example...
consider, there are two tables like emp_personal and emp_official .
In emp_personal table , the fields are empid,empname, dob for example. In this table, empid is the primary key field.
In emp_official table , the fields are empid,dept,designat ion for example. In this also, empid is the Primary key or may not be a Primary key field.
now we relate these two tables using the foreign key relationship. Foreign key relationship is used to avoid the redundancy mainly...
now, emp_personal is the Check table( Bcos it holds the empid field, which has the primary key...)
emp_official table is the Foreign key table (Bcos it holds the empid field, which may or may not be a Primary key).
now, we foreign key relationship is given. (click the KEY Like icon in ABAP Dict - Database Table : Emp Official )
Tables are ready to enter the records...for example create some 5 records in the emp_personal table .
Table : emp_personal :   Primary Key - empid
empid     empname    empdob             Status
   1            AAA          1.1.1990          Record saved successfully
   2            BBB          2.2.1990          Record saved successfully
   3            CCC          3.3.1990          Record saved successfully
   4            DDD          4.4.1990          Record saved successfully
   5            EEE          5.5.1990          Record saved successfully
records are saved in the table : emp_personal.
now, we are tryiing to create records in emp_official table.
Table : emp_official :   Primary Key or not a Primary Key - empid
empid          dept        designation             Status
   1            Dept1        S.E                 Record saved successfully
   2            Dept2       S.SE               Record saved successfully
now, if u try to create the record which is not in the table emp_personal , which has the empid = 6. but it'll not allow us to create the record 6, bcos of the foreign key relationship between these two tables....
   6            Dept6       P.M                Record doesn't exist......
now, the foreign key relationship helps us to avoid the duplicate entry......
Foreign key relationship is possbile between the tables having atleast one same type of field. Also the Technical characteristics of the fields should be same . this is done in the value table.....
this is the concept of Foreign key...I think this explantion is enough to describe the Foreign key....

FM8 and DITA: attribute "rotate" in table entries

Hi there,
I tried to add the attribute "rotate" for table entries. The Developer's guide and the additional reference guide were a good help here. Everything you need for your dtd and read/write rules is listed there.
<!ATTLIST entry
rotate %yesorno; #IMPLIED
>
element "entry"
attribute "rotate" is fm property rotate;
In the EDD, the attribute has not to be added, I think.
But anyway: I have added this attribute to some table entries. And now I always get the error message that the attribute 'rotate' was not declared for the element 'entry', when I open the xml-file in FrameMaker.
Does anyone know, what else I have to do?
Thanks in advance,
Anna

Hi Seth,
I just use the rotate attribute for some entries. I haven't tried until now to specify that the text should always be rotated for a special table/col.
I cannot image how this would work, though.
It's not possible with the template nor the EDD nor the r/w rules.
Perhaps it would be possible to use FrameScript for this. You might want to consult Russ Ward or Michael Müller-Hildebrand for this.

Parsing XML data stored as CLOB in DB and save attribute values in table

Hello,
I have a CLOB column in table that is holding XML data as follows,
<banners>
<banner-image id="0">
<type>BANNER</type>
<local-path>http.gif</local-path>
<click-through-url>www</click-through-url>
<make>Acura</make>
</banner-image>
<banner-image id="1">
<type>BANNER</type>
<local-path>http.gif</local-path>
<click-through-url>gfrty</click-through-url>
<make>BMW</make>
</banner-image>
</banners>
Now I need to parse thru the above XML data and pull the attribute values to store in another table as follows,
BANNER_IMAGE_ID | TYPE | LOCAL_PATH | CLICK_URL | MAKE
0 | BANNER | http.gif | www | Acura
1 | BANNER | http.gif | gfrty | BMW
And XML data doesn't always end up with 2 rows in this table....some times it may be 3 or 4 as well. It is just that in this example it ended up with 2 rows.
So, I would appreciate if someone can help me find a generic way of doing this,
Thank you in advance,
Madhu.

This is not a reply.. sorry.
I took have a similar problem only..
can you pls help me
XML structure.
<PODetails>
<POHeader>
<CurrencyID>INR</CurrencyID>
<ExchangeRate>1</ExchangeRate>
<RefNo>0080000110</RefNo>
<VendorID>1200</VendorID>
<TransDate>2006-12-20</TransDate>
<DocRelationshipId>PURCHASE</DocRelationshipId>
<LocationID>0000102327</LocationID>
</POHeader>
<POItemDetails>
<ItemID>ARSH1332</ItemID>
<Size>L HS</Size>
<Quality>Q1</Quality>
<CustPO>rush order</CustPO>
<UOM>PC</UOM>
<Quantity>3.000</Quantity>
<PriceValue>2509.5</PriceValue>
<TaxAmount>0.00</TaxAmount>
</POItemDetails>
<POItemDetails>
<ItemID>ARSH1332</ItemID>
<Size>M HS</Size>
<Quality>Q1</Quality>
<CustPO>rush order</CustPO>
<UOM>PC</UOM>
<Quantity>2.000</Quantity>
<PriceValue>1673</PriceValue>
<TaxAmount>0.00</TaxAmount>
</POItemDetails>
<POItemDetails>
<ItemID>ARSH1556</ItemID>
<Size>39FS</Size>
<Quality>Q1</Quality>
<CustPO>rush order</CustPO>
<UOM>PC</UOM>
<Quantity>1.000</Quantity>
<PriceValue>836.5</PriceValue>
<TaxAmount>0.00</TaxAmount>
</POItemDetails>
</PODetails>
The DB is ORACLE 9i
This is stored in a XML table of type XMLTYPE.
THIS I USED THE .extract function to get the values of the nodes.
POHeader details are working fine. But when i get the POItemDetails i am getting 'ARSH1332ARSH1332ARSH1556' when i issue the command
select a.extract('/PODetails/POItemDetails/ItemID/text()').getStringVal() ItemID
FROM xmltable a
WHERE a.existsnode('//POItemDetails/ItemID')=1
Pls Help..
Regds,
Santhoshkumar.G.

Foreign keys in SCD2 dimensions and fact tables in data warehouse

Hello.
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.

>
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
>
Are you still designing your system? Why did you choose NOT to use a Star schema? Star schema's are simpler and have some performance benefits over snowflakes. Although there may be some data redundancy that is usually not an issue for data warehouse systems since any DML is usually well-managed and normalization is often sacrificed for better performance.
Only YOU can determine what foreign keys you need. Generally you will create foreign keys between any child table and its parent table and those need to be created on a primary key or unique key value.
>
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.
>
I have no idea what that means. There isn't any way to tell from just the DDL for one dimension table that you provided.
It is not clear if you are saying that your fact table will have a direct relationship to the star-flake dimension tables or only link to them through the top-level dimensions.
Some types of snowflakes do nothing more than normalize a dimension table to eliminate redundancy. For those types the dimension table is, in a sense, a 'mini' fact table and the other normalized tables become its children. The fact table only has a relation to the main dimension table; any data needed from the dimensions 'child' tables is obtained by joining them to their 'parent'.
Other snowflake types have the main fact table having relations to one or more of the dimensions 'child' tables. That complicates the maintenance of the fact table since any change to the dimension 'child' table impacts the fact table also. It is not recommended to use that type of snowflake.
See the 'Snowflake Schemas' section of the Data Warehousing Guide
http://docs.oracle.com/cd/B28359_01/server.111/b28313/schemas.htm
>
Snowflake Schemas
The snowflake schema is a more complex data warehouse model than a star schema, and is a type of star schema. It is called a snowflake schema because the diagram of the schema resembles a snowflake.
Snowflake schemas normalize dimensions to eliminate redundancy. That is, the dimension data has been grouped into multiple tables instead of one large table. For example, a product dimension table in a star schema might be normalized into a products table, a product_category table, and a product_manufacturer table in a snowflake schema. While this saves space, it increases the number of dimension tables and requires more foreign key joins. The result is more complex queries and reduced query performance. Figure 19-3 presents a graphical representation of a snowflake schema.

Creating Column in table or use Foreign Key

I have a bunch of tables that are year specific, so I need to store the year in the record. I'm not sure if I should create a column in each table called 'year' or create a master 'Year' table and use a foreign key to it in all my other tables. Any advice?
PK_ID NUMBER Constraint pk1
PRIMARY KEY
YEAR VARCHAR2(4)
--- or----
PK_ID NUMBER Constraint pk1
PRIMARY KEY
FK_YEAR NUMBER Constraint fk_year
REFERENCES year_table(PK_ID)

Does your "year" entity have any attributes ?
Why do you have a year, which to most people seems to be a number, stored as a varchar2(4) ? And what are you going to do about the Y10K problem ?
How about making the ID of year the numeric value of the year you are storing - then you have eat your cake and have it ;)
Seriously, though, why do you want a table to say that the year 2008 is the year identified by a meaningless unique number ?
Regards
Jonathan Lewis
http:/jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

How to create a Foreign key relationship between 2 user defined tables...

Hi Folks,
I have created two user defined tables... Where in i want to create foriegn key relationship between the 2 tables.... Can anyone guide the step by step procedure to do this scenario...
Any help would be highly appreciated...
Thanks

Hi
1. In the 2nd table call the field of the 1st table which is a primary key.
2. Give the same field and dataelement name.
3. Select that field and then click on the foreign key field icon which is beside Search Help button.
4. Then give short text, and the 1st table name.
5. Then in the below box give the 2nd table name and 2nd table field name which you have called from 1st table.
6. Then click on copy, then u will be able to see Check table name and check table field name beside foreign key table name.
7. Then again click on copy.
Regards
Haritha.

Is it possible to create foreign key from composite key in other table.

SQL> desc PRODUCT_CONFIG_OPTION;
Name Null? Type
CONFIG_ITEM_ID NOT NULL VARCHAR2(20) --composite primary key
CONFIG_OPTION_ID NOT NULL VARCHAR2(20) --composite primary key
CONFIG_OPTION_NAME VARCHAR2(100)
DESCRIPTION VARCHAR2(255)
SEQUENCE_NUM NUMBER(18)
LAST_UPDATED_STAMP TIMESTAMP(6)
LAST_UPDATED_TX_STAMP TIMESTAMP(6)
CREATED_STAMP TIMESTAMP(6)
CREATED_TX_STAMP TIMESTAMP(6)
SQL> DESC PRODUCT_CONFIG_ITEM;
Name Null? Type
CONFIG_ITEM_ID NOT NULL VARCHAR2(20)
CONFIG_ITEM_TYPE_ID VARCHAR2(20)
CONFIG_ITEM_NAME VARCHAR2(100)
DESCRIPTION VARCHAR2(255)
LONG_DESCRIPTION CLOB
IMAGE_URL VARCHAR2(255)
LAST_UPDATED_STAMP TIMESTAMP(6)
LAST_UPDATED_TX_STAMP TIMESTAMP(6)
CREATED_STAMP TIMESTAMP(6)
CREATED_TX_STAMP TIMESTAMP(6)
SQL> desc product;
Name Null? Type
PRODUCT_ID NOT NULL VARCHAR2(20)
PRODUCT_TYPE_ID VARCHAR2(20)
PRIMARY_PRODUCT_CATEGORY_ID VARCHAR2(20)
MANUFACTURER_PARTY_ID VARCHAR2(20)
FACILITY_ID VARCHAR2(20)
INTRODUCTION_DATE TIMESTAMP(6)
SUPPORT_DISCONTINUATION_DATE TIMESTAMP(6)
SALES_DISCONTINUATION_DATE TIMESTAMP(6)
SALES_DISC_WHEN_NOT_AVAIL CHAR(1)
INTERNAL_NAME VARCHAR2(255)
BRAND_NAME VARCHAR2(100)
COMMENTS VARCHAR2(255)
=========
CREATE TABLE PROD_CONFIG_PROD_CONFIG_OPTION (
PRODUCT_ID VARCHAR2(20),
CONFIG_ITEM_ID VARCHAR2(20),
CONFIG_OPTION_ID VARCHAR2(20),
PAGE_NUM_TO NUMBER(18),
ALTERNATE_PAGE_NUM_TO1 NUMBER(18),
ALTERNATE_PAGE_NUM_TO2 NUMBER(18),
ALTERNATE_PAGE_NUM_TO3 NUMBER(18),
LAST_UPDATED_STAMP TIMESTAMP(6),
LAST_UPDATED_TX_STAMP TIMESTAMP(6),
CREATED_STAMP TIMESTAMP(6),
CREATED_TX_STAMP TIMESTAMP(6),
CONSTRAINT PK_PROD_CAT_CONFIG_MOD PRIMARY KEY (PRODUCT_ID),
CONSTRAINT FK_PRODUCT_ID FOREIGN KEY (PRODUCT_ID) REFERENCES PRODUCT(PRODUCT_ID),
CONSTRAINT FK_CONFIG_ITEM_ID FOREIGN KEY (CONFIG_ITEM_ID) REFERENCES PRODUCT_CONFIG_ITEM(CONFIG_ITEM_ID),
CONSTRAINT FK_CONFIG_OPTION_ID FOREIGN KEY (CONFIG_OPTION_ID) REFERENCES PRODUCT_CONFIG_OPTION(CONFIG_OPTION_ID) )
TABLESPACE DATA_SMALL
i try to create this table if i omit 3rd foreign key constraint then table successfully created.but including trd foreign key constraint it return error "ORA-02270: no matching unique or primary key for this column-list"
i checked everything is it possible to create foreign key from composite key in other table.

And
CONSTRAINT FK_CONFIG_OPTION_ID FOREIGN KEY (CONFIG_ITEM_ID,CONFIG_OPTION_ID) REFERENCES PRODUCT_CONFIG_OPTION(CONFIG_ITEM_ID,CONFIG_OPTION_ID)
?

Foreign keys to same table / Who columns in User table???

Hi All,
We are designing a database for our client and we are using common columns in all tables like CreatedBy and UpdatedBy which are foreign keys to USER table. My question is can we use these two columns in USER table and have the foreign key constraints to the same tables?
USER table script will look like following..
CREATE TABLE XX_USER
     User_ID                              VARCHAR2(10)
,     CreatedBy                         NUMBER(10)
,     UpdatedBy                         NUMBER(10)
,     User_Name                         VARCHAR2(100)     NOT NULL
,     Designation                         VARCHAR2(100)     NOT NULL
,     CONSTRAINT USER_ISACTIVE_CHECK CHECK (Is_Active in ('Y', 'N'))
,     CONSTRAINT USER_KEY PRIMARY KEY (User_ID),
,     CONSTRAINT USER_CREATED_BY FOREIGN KEY (CREATED_BY)
     REFERENCES XX_USER (USER_ID)
,     CONSTRAINT USER_UPDATED_BY FOREIGN KEY (UPDATED_BY)
     REFERENCES XX_USER (USER_ID)
);I think what I am doing (the above script) is not correct. Could someone please suggest me how can solve this issue?
Thanks in advance,
Oraebs

user8644385 wrote:
We are designing a database for our client and we are using common columns in all tables like CreatedBy and UpdatedBy which are foreign keys to USER table. My question is can we use these two columns in USER table and have the foreign key constraints to the same tables?You can. After fixing synatx errors:
SQL> CREATE TABLE XX_USER
2 (
3   User_ID        VARCHAR2(10)
4 , CreatedBy     NUMBER(10)
5 , UpdatedBy     NUMBER(10)
6 , User_Name     VARCHAR2(100) NOT NULL
7 , Designation   VARCHAR2(100) NOT NULL
8 , Is_Active     VARCHAR2(1)
9 , CONSTRAINT USER_ISACTIVE_CHECK CHECK (Is_Active in ('Y', 'N'))
10 , CONSTRAINT USER_KEY PRIMARY KEY (User_ID)
11 , CONSTRAINT USER_CREATED_BY FOREIGN KEY (CreatedBy)
12       REFERENCES XX_USER(USER_ID)
13 , CONSTRAINT USER_UPDATED_BY FOREIGN KEY (UpdatedBy)
14       REFERENCES XX_USER(USER_ID)
15 )
16 /
Table created.
SQL> Now USER_ID is a string while CreatedBy/UpdatedBy is a number. Even though it is allowed, it limits USER_ID to numeric strings and causes implicit conversions while validating. So I would change CreatedBy/UpdatedBy data type to VARCHAR2(10).
SY.

Why can't global temporary tables have foreign keys?

Hi,
I have a forms module which shows two blocks. The first block is based on a normal database table EMP and the second one is based on a global temporary table SAL_TEMP. There is a master-detail relation between the two blocks. So far, in Designer I created two normal database tables EMP and SAL_TEMP and created a foreign key with validation level "none" from the table SAL_TEMP to the table EMP. By creating the foreign key, Designer generates code to automatically synchronize the data between the master and the detail block in my form.
In the latest version of Designer it is finally possible to indicate a table as a global temporary table. But when I try to change my table SAL_TEMP to a global temporary table (session) I get an error that this is not allowed because my table contains foreign keys. So the Designer team finally implemented this feature but it is useless to me.
Can someone explain to me the reason of this restriction?
Vincent

Just out of curiosity - which version of Designer supports the creation of global temp tables? We are running version 9.0.2.80.6 and, as far as I am award, this does not support it (unless I am being really thick!) - is this new 10g Dev. Suite functionality?
thanks,
Pete

How we relate two tables using foreign key(fk)?

hi to all,
what are the conditions has to follow to relate two tables.I.e.,
the two tables have same primary keys(pk). if we relate these two tables in one table the pk and fk will be the same then how that table in active.

Hi
To relate two tables..we have foreign key relationship.
In one table v have primary key and in the second table, the same key is foreign key for that table..
To relate two tables, we can use JOINS
If there is already a suitable foreign key between two tables used in the view, these tables can be linked with a join condition from this foreign key.
Create a view on tables TAB1 and TAB2. TAB1 is the primary table of the view. TAB2 is the secondary table of the view. TAB1 is the check table for TAB2. The foreign key fields are assigned to the check table fields as follows:
TAB1-FIELD_A assigned to TAB2-FIELD_1
TAB1-FIELD_A assigned to TAB2-FIELD_1
The join condition of the view generated from the foreign key is then:
CREATE VIEW ... AS SELECT ... WHERE TAB2-FIELD_1 = TAB1-FIELD_A AND TAB2-FIELD_2 = TAB1-FIELD_B.
Join conditions can also be copied from generic and constant foreign keys. If a constant is assigned to a field in the foreign key, it is also assigned to the field in the join condition. There is no join condition for a generic relationship in the foreign key.
The foreign key between tables TAB1 (check table) and TAB2 (foreign key table) is defined as follows:
TAB1-FIELD_A assigned to TAB2-FIELD_1
TAB1-FIELD_B generic
TAB1-FIELD_C assigned to constant C
The join condition for the view generated from the foreign key is in this case:
CREATE VIEW ... AS SELECT ... WHERE TAB2-FIELD_1 = TAB1-FIELD_A AND TAB2-FIELD_2 = C.
Hope it helps
Reward if useful.

How to identify tables use currency as foreign keys?

Currently we have identified some currencies that needed to updated to ISO values and others as obsolete(eg. some EURO countiries set to EUR) in ECC
So my question is how to efficiently locate those foreign keys tables in ECC?
Thx and Best Grds
David

I do not think I fully understand your question but I will give it a shot.
If you are trying to locate a foreign key, then proceed as follows.
1. Transaction Code: SE11
2. Enter the table in question. For example BSEG
3. Select a table. For example BUKRS or KUNNR
4. Click on Foreign Keys. The symbol or icon is a key with an arrow pointing down. It is before Srch Help.
5. A screen will pop-up with the foreign key fields and tables where you can you the CHECKTABLE.
Or enter table using SE11: GLPCT
2. Select RTCUR
3. Click on Foreign Keys
3. In the pop-up screen, double click on TCURC in the check table field.
Hopes the above provides you with a clue.
Elias
Edited by: Elias Akorli on Dec 7, 2009 2:29 PM

Foreign key dependency checking

Dear all:
I have a question about foreign key checking.
Let's say I have two Z table, one is master table and one is transaction table.
The master table contains a primary key named CustNo.
The transaction table have two primary keys named CustNo and OrderNo.
The CustNo has foreign key (mandt + CustNo) point to master table, with setting
"Key fields/candidates 1:N"
I expected that, delete record in master table should check if there is any dependency in the transaction table,
but I am wrong. I am able to delete anything in master table even there are records in transaction table using the same CustNo.
My question is, how can I make the dependency check?
Thanks in advance.
Edited by: Hung Kai, Michael Cheng on Nov 3, 2008 5:29 AM

Hello,
For this u need to change the cardinality.
Below are the list of cardinalities and their functionality.Chack it and use the proper one.
The left side (n) of the cardinality is defined as follows:
n=1: There is exactly one record assigned to the check table for each record of the foreign key table.
n=C: The foreign key table may contain records which do not correspond to any record of the check table because the foreign key field is empty. This can occur for example if the field of the foreign key table is optional, in which case it does not have to be filled.
The right side (m) of the cardinality is defined as follows:
m=1: There is exactly one dependent record for each record of the check table.
m=C: There is at most one dependent record for each record of the check table.
m=N: There is at least one dependent record for each record of the check table.
m=CN: There may be any number of dependent records for each record of the check table.
Shafi

Foreign Key Relationship.

Hi,
I asked a question in the link below(which I solved).
https://social.msdn.microsoft.com/Forums/en-US/514a4f48-b1fa-4fe7-bc2b-4c252b34cf50/insertion-of-null-value?forum=vbgeneral
Here my question is that:
We make relation of foreign keys to enforce user for accurate data insertion, but sometime we do need null values to be passed to attribute that is used as
Foreign key. We studied and know that Foreign keys are meant to except null values, which it doesn't(In simple way. I mean when we select an attribute as foreign key and check it to except nulls, then it should.)
As I explained in the upper link how I solved the problem, if similar problems have to be solved like that then,
Why we define Foreign Key over there, i mean it could be done without defining the Foreign key?
If it is necessary in any meaning then why we Enforce Foreign
Key Constraint as No,
to except nulls from user?
What effects does Enforce Foreign Key Constraint as No
gives to Foreign Key Constraints?
Thnx in advance.
Habib Ur Rehman

Hello Habib,
I do not think what you are seeing is normal and without having the exact DDL it will be hard to comment.
I suspect, you may had "NOT NULL" constraint on the foreign key column. thats why it is not allowing NULLs.
By definition, Foreign Key maintains(enforces) referential integrity and does allows NULLs. So, you should be able to enter nulls without having to disable the foreign key enforcement.
by setting
Enforce Foreign Key Constraint to NO, you are effectively disabling the enforcement. you are invalidating the whole purpose of the constraint.
The purpose of having that option(disabling foreign key) is to fasten the data load process bypassing the check(extra work) to make sure the value exists in the primary key table when importing large amounts of data. But to maintain the referential
integrity you should have that enabled.
I am not sure without having the ddl, where you did wrong.PLEASE POST YOUR DDL and it should be clear where it went wrong for you. but i hope this script below should help you understand...
CREATE TABLE [dbo].[Make]([sid] [int] NULL unique,[sname] [varchar](50) NULL)
go
CREATE TABLE [dbo].[Make_FK]([sno] [int] NULL unique,[sname] [varchar](50) NULL,[sid] [int] NULL
CONSTRAINT FK_MAKE FOREIGN KEY (sid) REFERENCES dbo.make (SID))
insert into make(sid,sname)
values(1,'sam')
insert into dbo.Make_FK(sno,sname,sid)
values(100,'somename',null)
select * from Make
--sid is null. SID is the foreig n key referring to sid in MAKE table.
select * from Make_FK
Hope it Helps!!

Problem with Foreign Key relationships in SAP R/3 4.7

Hi Experts,
I am trying to create a foreign key relationship between 2 transparent tables in SAP R/3 4.7
Table 1:ZAAVNDR (MANDT (pk), VENDORNO (pk), NAME, REGION, COUNTRY (fk)) Foreign Key Table
Table 2: ZAAVNDRREF(MANDT(pk), COUNTRY (pk)) ---Check table
I have added few valid countries in check table but when I am adding some records in foreign key table with invalid countries these records are not being restricted and are still successfully going into the table.
Could any one please help in this.
Thanks in anticipation.
-Amit

Hi Sandra,
Many thanks for your response and providing time of yours.
Now, I have done exactly the same thing, but still it is the same.
I have created two new tables as below:
ZAAVREF (Check table)
MANDT (PK)
COUNTRY (PK) Domain:ZAACOUNT (CHAR 10)
ZAAV1 (Foreign key table)
MANDT (PK)
COUNTRY (PK) Domain:ZAACOUNT (CHAR 10)
Then I have created FK on country of foreign key table ZAAV1 and then SE16 (for table ZAAVREF)->Create Entries-> Entered values for Country only->Save....Records entered with valid Country values.
After that SE16 (for table ZAAV1)->Create Entries-->Entered an Invalid country->Save->Still the record entered to the Database successfully....
Could you please let me know where I am going wrong.
I am using SAP R/3 4.7 and creating tables using Tools->ABAP Workbench->Development->ABAP dictionary

Cardinality and semantic attributes -foreign key-table

Similar Messages

Maybe you are looking for