There are hundreds of tables in Oracle E-Business Suite HRMS, but some are used more frequently than others. When querying, it is important to not only know the common tables that are used, but also to understand how the tables link together. Some of the common tables are listed below.
Common HRMS Tables
The chart above shows some of the most common tables that are used in Oracle HRMS. Often, a column in one table will link to a column in a different table. For example, the primary key PERSON_ID in the PER_ALL_PEOPLE_F table will link to the foreign key PERSON_ID in the PER_ALL_ASSIGNMENTS_F table to connect people to their appropriate assignments. The Entity Relationship Diagram (ERD) below reflects Oracle’s Logical Data Model which illustrates the connections between each table (Click to enlarge).
Here are a few examples of interpretations:
- “A person may have one or many assignments, but an assignment must be assigned to a person”
- “A position must have only one organization, but an organization has one or many positions”
- “A position may be in many assignments, but an assignment be only be linked to one position”
ERD Key
Contact Us[/message_box]
3 Comments on “Understanding the Core Oracle E-Business Suite HRMS Tables”
Working out which tables are relevant to your requirement is challenging when there are so many tables – particularly if you don’t have intimate knowledge of E-Buisness Suite. We sell a product called Safyr that gets a ‘logical’ representation of the tables in an EBS system and then has a set of features for working out ‘meaningful’ groupings of those tables and relationships, allowing the user to get to a data model like the one you show very quickly.
Thanks a Lot for this valuable information
This is great information. I am looking at using HCM to replace PeopleSoft. I have a need to know what foundation code tables or relationship tables are required. Example; Employee, Department, Jobcode, Location, as so on. Is that an E/R diagram available?