This page (revision-40) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
40 26-Nov-2021 10:22 11 KB Karen Parrott to previous
39 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
38 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
37 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
36 26-Nov-2021 10:22 11 KB Karen Parrott to previous | to last
35 26-Nov-2021 10:22 11 KB rforbes to previous | to last
34 26-Nov-2021 10:22 11 KB jmyers to previous | to last
33 26-Nov-2021 10:22 11 KB jmyers to previous | to last
32 26-Nov-2021 10:22 11 KB jmyers to previous | to last
31 26-Nov-2021 10:22 11 KB RForbes to previous | to last
30 26-Nov-2021 10:22 11 KB RForbes to previous | to last
29 26-Nov-2021 10:22 11 KB RForbes to previous | to last
28 26-Nov-2021 10:22 11 KB RForbes to previous | to last
27 26-Nov-2021 10:22 11 KB RForbes to previous | to last
26 26-Nov-2021 10:22 11 KB RForbes to previous | to last
25 26-Nov-2021 10:22 11 KB RForbes to previous | to last
24 26-Nov-2021 10:22 11 KB JMyers to previous | to last NAMING CONVENTION ==> NAMING CONVENTION AND STANDARDS
23 26-Nov-2021 10:22 11 KB RForbes to previous | to last
22 26-Nov-2021 10:22 10 KB RForbes to previous | to last
21 26-Nov-2021 10:22 10 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
ERD
ERD

Version management

Difference between version and

At line 1 changed 5 lines
%%center
||[ERDs by Module:|ERD] | [AM|ERD-AM] | [AT|ERD-AT] | [BE|ERD-BE] | [CM|ERD-CM] |[FC|ERD-FC] | [HR|ERD-HR] | [LR|ERD-LR] | [PR|ERD-PR] | [RE|ERD-RE] | [RX|ERD-RX] | [SA|ERD-SA] | [SH|ERD-SH] | [TD|ERD-TD] | [TS|ERD-TS] | [UT|ERD-UT]
%%
----
!!!ENTITY-RELATIONSHIP DIAGRAMS
%%(color:red)Latest ERD [Manual|ERD/ERD_Manual.pdf]%\\
At line 7 removed 10 lines
%%warning
\\
__ATTENTION:__
*The ERDs in the Knowledge Base are updated as of the 5.04 Release. They will not be updated to reflect any changes done in the 5.05 Release\\
\\
%%
At line 19 changed one line
The modules in the application are comprised of many different tables, such as ‘Identity’ or ‘Assignment’. The tables within the system interact with one another and share information. Through these associations, ‘relationships’ form and tables can become dependent on others. The Entity Relationship Diagrams (ERDs) in this manual will explain the interaction that tables in the application have with one another.
The modules in the application are comprised of many different tables, such as the ‘Identity’ or ‘Assignment’. The tables within the system interact with one another and share information. Through these associations, ‘relationships’ form and tables can become dependant on others. The Entity Relationship Diagrams (ERDs) in this manual will explain the interaction that tables in the application have with one another.
At line 21 removed 3 lines
[{TableOfContents }]
At line 32 changed one line
This basic box will display only the entity name (ALIAS) and entity alias (EAL). Please note that the entity name will eventually be used in the table [Naming Convention|NAMING CONVENTION AND STANDARDS]. (e.g. The ‘Alias’ entity name will be referenced in the table name ‘P2K_HR_ALIASES‘.)
This basic box will display only the entity name (ALIAS) and entity alias (EAL). Please note that the entity name will eventually be used in the table [Naming Convention]. (e.g. The ‘Alias’ entity name will be referenced in the table name ‘P2K_HR_ALIASES‘.)
At line 44 changed one line
The shaded background indicates that the table is [date sensitive|DATE SENSITIVE]. These tables will always have Effective (date) and Expiry (date) columns, although not shown on the ERD.
The shaded background indicates that the table is [date sensitive]. These tables will always have Effective (date) and Expiry (date) columns, although not shown on the ERD.
At line 48 changed one line
The shading will appear gray on a black and white printout; however, it may appear yellow if the ERD is brought up on a computer.
The shading will appear grey on a black and white printout; however, it may appear yellow if the ERD is brought up on a computer.
At line 51 changed one line
A table may also appear on an ERD with a bold border. This border indicates that the information in this table is provided as part of the [seed data|SEED DATA].
A table may also appear on an ERD with a bold border. This border indicates that the information in this table is provided as part of the [seed data].
At line 56 changed one line
[{Image src='ERD_Dotted.JPG' width='244' align='center' link='attach/ERD/ERD_Dotted.JPG'}]
[{Image src='ERD_Dotted.JPG' width='101' align='center' link='attach/ERD/ERD_Dotted.JPG'}]
At line 62 changed one line
[{Image src='ERD_Italic.JPG' width='115' align='center' link='attach/ERD/ERD_Italic.JPG'}]
[{Image src='ERD_Italic.JPG' width='101' align='center' link='attach/ERD/ERD_Italic.JPG'}]
At line 64 changed 2 lines
!!Lines
!Solid Line Vs. Broken Line
!Lines
Solid Line Vs. Broken Line
At line 68 changed one line
[{Image src='ERD_BrokenLine1.JPG' width='382' align='center' link='attach/ERD/ERD_BrokenLine1.JPG'}]
The solid line indicates that the Parent table (EID) is MANDATORY for the Dependant table (ECT). This means that the Parent table must be filled BEFORE the Dependant table can be completed. A broken line indicates that the Dependant table (ECT) is OPTIONAL for the Parent table (EID). This means that the Parent table can be completed WITHOUT the Dependant table having been filled.
At line 70 removed 4 lines
The solid line indicates that the Parent table (EID) is MANDATORY for the Dependent table (ECT). This means that the Parent table must be filled BEFORE the Dependent table can be completed. A broken line indicates that the Dependent table (ECT) is OPTIONAL for the Parent table (EID). This means that the Parent table can be completed WITHOUT the Dependent table having been filled.
[{Image src='ERD_BrokenLine2.JPG' width='400' align='center' link='attach/ERD/ERD_BrokenLine2.JPG'}]
At line 76 removed 2 lines
[{Image src='ERD_BrokenLine3.JPG' width='378' align='center' link='attach/ERD/ERD_BrokenLine3.JPG'}]
At line 80 removed 3 lines
[{Image src='ERD_Written.JPG' width='391' align='center' link='attach/ERD/ERD_Written.JPG'}]
At line 92 removed 3 lines
[{Image src='ERD_Dependent.JPG' width='350' align='center' link='attach/ERD/ERD_Dependent.JPG'}]
At line 67 added one line
In this instance, the line starts as a single line at the Entity table and ends in many lines at the Unit table. This means that the entity may have many units associated with it, however, the unit cannot belong to more than one entity. Another way this can be expressed is that the Entity table is the PARENT of the Unit table and the Unit table is the DEPENDANT of the Entity table.
At line 97 changed one line
In this instance, the line starts as a single line at the Entity table and ends in many lines at the Unit table. This means that the entity may have many units associated with it, however, the unit cannot belong to more than one entity. Another way this can be expressed is that the Entity table is the PARENT of the Unit table and the Unit table is the DEPENDENT of the Entity table.
There can be a situation where two tables are parents to each other, which will be explained further on in this manual.
At line 99 removed 10 lines
There can be a situation where two tables are parents to each other, which will be explained further on.
!Foreign Keys
Dependent tables will always have a [Foreign Key|FOREIGN KEY] that identifies its parent table.
The presence of the "many" branch (also known as crow's feet) indicates this foreign key.
For instance, within the Alias table, there will be a foreign key column (EID_ID) for the parent table, Identity.
Parent tables do not keep foreign keys and therefore their dependent tables can only be traced within the Oracle Data dictionary as referential constraints
At line 112 changed 4 lines
__Parent/Dependent Relationship__
In the first scenario, one table is the parent with two lines moving towards a dependent table.
[{Image src='ERD_Parent1.JPG' width='228' align='center' link='attach/ERD/ERD_Parent1.JPG'}]
__Parent/Dependant Relationship__
In the first scenario, one table is the parent with two lines moving towards a dependant table.
*** PICTURE ***
At line 122 changed 2 lines
[{Image src='ERD_Parent2.JPG' width='160' align='center' link='attach/ERD/ERD_Parent2.JPG'}]
*** PICTURE ***
At line 128 changed 3 lines
A bold line between two tables indicates that if you delete the record in the parent table, the associated record in the dependent table will be deleted. This is know as a Cascade Delete.
[{Image src='ERD_BoldLine.JPG' width='446' align='center' link='attach/ERD/ERD_BoldLine.JPG'}]
A bold line between two tables indicates that if you delete the record in the parent table, the associated record in the dependant table will be deleted. This is know as a Cascade Delete.
***PICTURE ***
At line 135 changed 2 lines
[{Image src='ERD_CurvedLine.JPG' width='306' align='center' link='attach/ERD/ERD_CurvedLine.JPG'}]
*** PICTURE ***
At line 146 changed one line
The dependent records (subsidiaries) will refer back to the parent record in the DEN_ID key.
The dependant records (subsidiaries) will refer back to the parent record in the DEN_ID key.
At line 149 changed one line
|Dependent| 10 |D Corp| 1
|Dependant| 10 |D Corp| 1
At line 155 changed 7 lines
[{Image src='ERD_ExclusiveJoin1.JPG' width='361' align='center' link='attach/ERD/ERD_ExclusiveJoin1.JPG'}]
This exclusive join means that the contact table may be tied to either the User table or the Identity table, but not both. These tables cannot have the same contact.
Occasionally you will see an exclusive join that isn’t connected to multiple tables. This simply means that for brevity sake, not all dependent tables are displayed on the chart
[{Image src='ERD_ExclusiveJoin2.JPG' width='272' align='center' link='attach/ERD/ERD_ExclusiveJoin2.JPG'}]
*** PICTURE ***
This exclusive join means that the contact table may be tied to either the User table or the Identity table, but not both. These tables
cannot have the same contact.
Occasionally you will see an exclusive join that isn’t connected to multiple tables. This simply means that for brevity sake, not all dependant tables are displayed on the chart
*** PICTURE ***
At line 166 changed 3 lines
This diamond means the parent table cannot be changed on the dependent record. This indicates a [non-transferable|NON-TRANSFERABLE] constraint.
[{Image src='ERD_Transferable.JPG' width='323' align='center' link='attach/ERD/ERD_Transferable.JPG'}]
This diamond means the parent table cannot be changed on the dependant record.
*** PICTURE ***
At line 170 removed 5 lines
----
![Notes|Edit:Internal.ERD]
[{InsertPage page='Internal.ERD' default='Click to create a new notes page'}]
This page (revision-40) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop