Code generation - foreign key relationships

I'm using the code/descriptor generation tab to generate classes from existing tables. It offers an option of choosing which relationships to generate, but seems to miss out some of the defined foreign key relationships in the database.
I have three tables, CLIENTS, TXNS and REG
The following constraints are defined in my database:
TXN Primary Key: (TXN_ID)
CLIENTS Primary Key :CLIENT_ID, TXN_ID)
CLIENTS Foriegn KEy : TXN_ID references TXNS
REG Primary Key: CLIENT_ID, TXN_ID
REG Foreign Key: CLIENT_ID, TXN_ID references CLIENTS
I select these three tables and choose generate classes and descriptors for selected tables. When the "Choose Relationships to generate" screen comes up, it only shows me the CLIENTS<-->TXNS relationship, but not the REG<-->CLIENTS relationship, even though the database foreign key constraints all look as though they've been defined in similar ways.
thanks for any help.

Hi Matt,
I'm not surprised that you have an issue with this. One bugbear I have with Gateway is that for some reason the designers don't think any context beyond the immediate preceding navigation node is important. They don't support this within the same service,so it's hardly likley to work in a service reference.
I may be wrong but I don't think GW is OData compliant in this respect. If I have the navigation path /blindservice/FromHereSet(1)/ToAPoints(22)/ToBPoints, it's rather restrictive to say I cannot see the initial key of '1' in the path when I am trying to resolve 'ToBPoints'. If that value - where I started - is key to the context, I have to know it.
Currently the only way to access this context is to embed the 'key history' in the intermediate entities, i.e. /blindservice/FromHereSet(1)/ToAPoints(1,22)/ToBPoints. In my view that is corrupting the URl to suit the limitations of the SAP OData implementation. What's even more confusing/frustrating is that the technical request context appears to be able to store the stacked navigation keys but doesn't make use of this design.
I feel your pain
Ron.

Similar Messages

Before delete trigger and foreign key relationship

Hi,
I am analysing one database for migration. On one parent table there is before delete trigger , to delete records from child. Also there is foreign key relationship on child table for this parent table.
When I am deleting a row from parent, message gets displayed as "there are child records found."
I would like to know, if there is foreign key relatioship then delete trigger on parent does't work, what is exactly happening?

Could you post that trigger code and the Oracle version as well?
With basic assumptions, I can't reproduce what you have stated here.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> create table parent (id number primary key);
Table created.
SQL> create table child (id number);
Table created.
SQL> alter table child add constraint fk_parent foreign key (id) references parent;
Table altered.
SQL> create or replace trigger bdr_parent
2 before delete on parent
3 for each row
4 begin
5 delete from child where id = :old.id;
6 end;
7 /
Trigger created.
SQL> insert into parent (id) values (1);
1 row created.
SQL> insert into child (id) values (1);
1 row created.
SQL> commit;
Commit complete.
SQL> delete from parent where id = 1;
1 row deleted.
SQL> select * from parent;
no rows selected
SQL> select * from child;
no rows selected
SQL> rollback;
Rollback complete.
SQL> alter table child drop constraint fk_parent;
Table altered.
SQL> alter table child add constraint fk_parent foreign key (id) references parent on delete cascade;
Table altered.
SQL> delete from parent where id = 1;
delete from parent where id = 1
ERROR at line 1:
ORA-04091: table SCOTT.CHILD is mutating, trigger/function may not see it
ORA-06512: at "SCOTT.BDR_PARENT", line 2
ORA-04088: error during execution of trigger 'SCOTT.BDR_PARENT'
SQL>

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

Maintenance View for custom table with foreign key relationship

Hi Folks,
I have created a custom table with foreign key relationship with other check tables. I want to create a maintenance view / tablemaintenance generator. What all things I need to take care for the foreign keys related fields while creating the maintenance view / tablemaintenance generator.
Regards,
santosh

Hi,
You do not have to do anything explicitely for the foreign key relationships in the table maintainance generator.
Create the table maintainance generator via SE11 and it will take care of all teh foreign key checks by itself.
Regards,
Ankur Parab

Mapping in OWB with primary key and foreign key relationship

Hi all,
I am new to this datawarehousing field. I have just started my career. I have to now create a mapping in owb where a table has a field which is a primary key of another table in the same staging area. If you guys could help me out with the a method it can be created that would be very helpful to me.
I thought of 2 ideas,
1. If I can use a look up, but then I am not sure if i can use a lookup for primary key, foreign key relationship. If I can use also, I do not know how to use that.
2. What if I can directly take that the first table and link the primary key of that table to the second table which uses that primary key of the first table as one of its fields.
I do not know how feasible these methods are. Please guys help me out.
Thanks in advance.

I have a similar case where table a and table b having relation but table a got inserted with data and table b is empty so there no values for foriegn key column in table b to realte with table a.
Now i want to load table b foriegn key with primary key column values of table a.
how can we do this in owb
thanks
kumar

Composite Foreign Key Relationships

I'm having problems defining relationships that are using the same set of fields in a composite primary key and a composite foreign key. Are there any examples for doing this kind of thing. I think I have the primary keys set up correctly but the foreign key defs aren't working yet. From the spec it looks ike it should be something like this:
@ManyToOne
     @PrimaryKeyJoinColumns({
     @PrimaryKeyJoinColumn(name="CGMTI_ID"),
     @PrimaryKeyJoinColumn(name="MISSION_REF_DATE")})
     CgmtiHeader cgmtiHeader;
Also, the composite foreign keys seem to make Dali's entity generation blow up.

This mapping is missing the referencedcolumn definition, and because it is a composite pk, it cannot figure out a default value. So it should similar to:
@ManyToOne
@PrimaryKeyJoinColumns({
@PrimaryKeyJoinColumn(name="CGMTI_ID", referencedColumnName="CGMTI_ID),
@PrimaryKeyJoinColumn(name="MISSION_REF_DATE", referencedColumnName="MISSION_REF_DATE)})
CgmtiHeader cgmtiHeader;
Similar discussions exist in threads:
Extra Columns in ManyToMany table workaround
and
http://forums.java.net/jive/thread.jspa?threadID=2564&messageID=36441
both of which list blogs showing examples.
Best Regards,
Chris

Foreign Key Relationships to external associations - Is it really this dodgy or is there a better way?

Hi All,
Let's picture that I have a GW service called Search Helps and within that service I have a PersonalAreas Entity Set which acts as a search help for drop down fields effectively that need to select a Personal Area. I have 3 properties, with Personal Area Id and Company Code being the keys, and the text for Personal Area being the 3rd and last property. You really need to filter PersonalAreas by Company Code otherwise it's a fairly useless result set.
Now within a different GW service, I have an entity called Position which has a single key of PositionId. There is also a a property of company code on this Position.
Now rather than asking the UI developer to get the Company code value and filter PersonalAreas with it directly, I thought it would be nicer for the UI developer just to use the navigation from a specific Position to PossiblePersonalAreas. e.g. Positions('123')/PossiblePersonalAreas returns the entity set of PersonalAreas filtered by the Position's Company Code.
So with that in mind, I add the external model reference pointing at the search helps service; then create an external association via the sneaky External Associations Editor button (that doesn't appear on the Wizard just to confuse you), and set up my Dependent entity to point at the Search Helps PersonalAreas entity.
At this point I really want to tie the Position's Company Code to the PersonalAreas Company Code, but all I can do is set up a referential constraint of PositionId to CompanyCode or have no referential constraint at all (note - in my example I added the referential constraint as there is an issue with navigation keys being provided to external associations from what I can tell - more about this below).
So, without any other option, I go into my GetEntitySet method of PersonalAreas and write something like the following:
CASE iv_source_name.
    WHEN 'Position'.
      READ TABLE it_filter_select_options ASSIGNING <filter> INDEX 1.
      CHECK sy-subrc = 0.
      READ TABLE <filter>-select_options assigning <select_option> INDEX 1.
      CHECK sy-subrc = 0.
      position_id = <select_option>-low.
*     Get company code for position
      TRY.
          CREATE OBJECT o_position
            EXPORTING
              i_position_id = position_id.
          o_position->get_cost_centre_information(
            IMPORTING
              e_company_code = company_code
        CATCH zcx_hr_object.
      ENDTRY.
endcase.
* Continue with retrieving PersonalAreas for given Company Code
<Remaining code not shown>
e.g. I have to assume CompanyCode is actually "Position Id" when the source of this call is from Position (I could also look at the navigation to find this has come from Position but if you're wondering, unfortunately for external associations, the key is not included in this for some reason but the same followup logic of reloading the object would be required).
So the question I'm hoping the answer to is Yes is: Am I missing something in my understanding here?
Thanks,
Matt
Edit since posting and playing around a bit more: Thinking about this further - it's unfortunate, but the navigation property in odata really implies the dependent entity has knowledge of the principal entity and realistically must know how to instantiate it if it needs to get data based on one of the properties.
Now while I'm fine with that (sort of) I think it's wrong that the dependent entity needs to have the required key properties to hold the principal entities as it makes something like a generic search help impossible to do with navigation - Maybe I just need to be done with that and expect filters to be used by UI programmers to find foreign key'ed entities....

Hi Matt,
I'm not surprised that you have an issue with this. One bugbear I have with Gateway is that for some reason the designers don't think any context beyond the immediate preceding navigation node is important. They don't support this within the same service,so it's hardly likley to work in a service reference.
I may be wrong but I don't think GW is OData compliant in this respect. If I have the navigation path /blindservice/FromHereSet(1)/ToAPoints(22)/ToBPoints, it's rather restrictive to say I cannot see the initial key of '1' in the path when I am trying to resolve 'ToBPoints'. If that value - where I started - is key to the context, I have to know it.
Currently the only way to access this context is to embed the 'key history' in the intermediate entities, i.e. /blindservice/FromHereSet(1)/ToAPoints(1,22)/ToBPoints. In my view that is corrupting the URl to suit the limitations of the SAP OData implementation. What's even more confusing/frustrating is that the technical request context appears to be able to store the stacked navigation keys but doesn't make use of this design.
I feel your pain
Ron.

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.

Query Builder - foreign key relationships not showing automatically

Is it standard functionality in APEX that foreign key to primary key relationships are not shown in Query Builder when choosing related tables? Do you always have to join FKs to PKs manually (i.e. using control click) whenever you create joins in queries? In Oracle forms and SQL Developer the foreign key constaints are always draw in automatically. Any reason why this is not part of APEX's query builder as well? It's such a hassel to have to put them in each time when the relationships could easily be read directly from the data dictionary constraints.
regards
Paul P

bump...

SQL Developer Data Modeler not drawing foreign key relationships

I'm having trouble with SQL Developer Data Modeler when I importa a DDL that has foreign keys. I export DDL files from SQL developer and choose various subsets of files. Sometimes Data Modeler will not recognize a foreign key if I include say a dozen files in the DDL file, but it will if I include just a few. Worse, even if the foreign key is recognized, sometimes it is not drawn in the Data Modeler and I have no way to make it be drawn. To be specific, I import a file containing the DDL for just two tables -- I see the foreign key! I import a file containing the DDL for a dozen tables including the two, I don't! Is there something I am not understanding about when Data Modeler will draw foreign keys or is the tool simply quite buggy?
Much thanks!
-ttamon

Hi Philip,
I believe I have isolated the problem. Apparently if a field is named "FOREIGN..." it interferes with the tool recognizing foreign keys. Try to import a DDL file containing the following text:
CREATE TABLE "SAMPLE"."SAMPLE_ONE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_TWO"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "FOREIGN_NAME" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_THREE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "ALT_ID" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ENABLE,
     CONSTRAINT "FK6DF8294F2288190D" FOREIGN KEY ("ALT_ID")
     REFERENCES "SAMPLE"."SAMPLE_ONE" ("ID") ENABLE
TABLESPACE "SAMPLE_DATA" ;
You will discover the foreign key is not recognized or drawn! Now, if you swap the location of the third table (put it up first) everything works fine. This is how I discovered the problem, various subsets would work, others would not. To confirm the problem is with the field named "FOREIGN_NAME" use the DDL as specified above but change the first letter in the word "FOREIGN" to something else, and it will recognize the foreign key. Looks like a bug to me (took me about 4 hours to isolate this!). I am using Oracle SQL Developer Data Modeler version 2.0.0 Build 584.
-ttamon

Primary Key / Foreign Key relationship

Hi Folks,
I have a MASTER_TABLE which has master values . This table has two fields, STATUS & STATUS_TEXT, Key field is STATUS.
This is a check table for another table INSTANCE_TABLE which also has field STATUS; this is not a key field though.
The requirement is: If I attempt to delete a STATUS value from MASTER_TABLE, it should not allow me if there is any record in INSTANCE_TABLE which has the same STATUS value. Is there a way to establish such a relationship between the two tables?
Thank you for the help!
Sid

Hi Friend,
Only through table Maintaince only it can be acheived , by table relatio it can not be .
because as you know the non primary key cannot be be check table field .means
In Mater table STATUS is primary key so you are making it as check table field to Insance table STATUS Field.
But in Instance table is not a primary key so , without primary key you will not be able to do the foriegn key relation to the master table ,so that it will not be check table becs of that they check will not happen for your scenario . to acheieve this you need to either make your STATUS field in Instance table also as primary key and do the foerign key relationship with Master table .
Or else write an event in the table maintainance .
Regards,

How to represent foreign key relationship between entity services

Hi All,
I have two entity services sbu and lob with remote persistensy(web service).In the sql database also i have these two tables.
lob table attributes: lobId and lobName.
sbu table attributes:sbuId,sbuName,and lobId.Here lobId a is foreign key referring to primary key of lob table.
I want to represent this in the entity services.
Can you plz tell me how can i do this?.
Thanks
Sampath.G

Hi Sampath,
to avoid creating a lob entity set the lobId and the timestamp attributes. because this is not smoothly done in the service browser, continue writing your UI.
in old caf implementation this blog serie gives you a short overview...
/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-i
/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-ii
/people/raphael.vogel/blog/2006/05/19/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-iii
/people/raphael.vogel/blog/2006/05/21/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-iv
Regards, Jens

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

Foreign key relationship between vbrp and j_1iexchdr

Hi folks,
Which field links vbrk and j_1iexchdr tables.
Thanks.
Sai.

Hi Raj.
I tried it using rdoc but i'm not getting, to retrive bukrs (company code) can i use ekko table, Right now I am developing excise invoice.
Thanks.
Sai.

Integration Object - Setting parent/child (Foreign Key) relationship

Hi all -
I have what I think is a very basic question but I cannot seem to get it right. I am using Siebel EAI Adapter with two IO where the source is a template and the second is the instances of the template. The structure is parent/children for both. I am also using a data map to transform the data. My assumtion is that I can insert a template record and all of its children with one message/insert command. My question is how do I set the FK value on the children to the parent id? The parent id is not known at the time of data mapping because the record has not yet been created.
I would think that the link between the two objects would handle this but I cannot get it to work. Any help is appreciated!
Siebel 8.1 using Siebel EAI Adapter in WF with data map.
Kind Regards,
Chad

One Siebel Adapter Upsert operation should be sufficient to insert the parent and child. In the Integration object definition, you define the Template child instances with the Parent of Template. i.e
You define Template first as an Integration Component and then define
Template child instances to have a Parent as Template.
Thanks
Swarna

Code generation - foreign key relationships

Similar Messages

Maybe you are looking for