Tables relations

[ESSO]

You can add an article in P41026 application only if you previusly add the same article in P4101 application, jde controls parent relationship, but if we see the tables F4101 and F4102 we don't see any constraint that indicates the relationship, only can see the primary key. is this correct?

 

[craig_welton]

If you are referring to a foreign key/primary key relationship between tables, this is not done at the database level through constraints (from what I have seen). This is maintained through the applications/functions etc.

Craig

 

[eydeak]

In the future, please include your system information with your post.



I think the short answer to your question is, yes. But, I'm going to
expand on an answer to make sure I really understand your question.



When you say constraint, I believe you are referring to database table
level constraints which can be used to enforce referential integrity
between tables. JDE does not provide you with a way of doing this in TDA
(Table Design Aid), so I don't believe they use constraints at all.



They enforce their table relationships programmatically by using Master
Business Functions to do all of the heavy transactional processing. So,
P41026 is designed to not allow you to add an Item Branch Plant for an
Item that doesn't already exist.



You can infer the table relationships by studying the table layouts. If
you look at the table layout for F4101 - Item Master, you can infer from
the name that it is a master table. Look at the primary key and it is a
unique Short Item Number (ITM). Next, look at the layout for F4102 -
Item Branch. Its primary key is a combination of Short Item Number (ITM)
and Business Unit (MCU). So, you can infer that there is a one-to-many
relationship between F4101 and F4102.



Ellen Deak

Senior Systems Developer

Cooper Standard Automotive

JDE EnterpriseOne (OneWorld XE Update 7 SP23_M1), AS400 DB2 V5R3M0,
Citrix Clients

 

[ESSO]

Re: RE: Tables relations

thanks for the aclarations, we have clear now!.