Search Results hr_incompatibility_rules_fk2

Overview

The HR_INCOMPATIBILITY_RULES table is a core data structure within the Oracle E-Business Suite Human Resources (HRMS) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical application control function by storing business rules that define incompatible navigation units. These rules are used to enforce restrictions within the application's user interface, preventing users from accessing or navigating to specific units or pages when they are in a particular context. The table's sole purpose is to maintain a paired list of unit identifiers where a relationship of incompatibility exists, thereby governing permissible application flows and data access.

Key Information Stored

The table is structurally simple, containing only two significant columns, both of which are mandatory foreign keys. It does not store descriptive text or rule metadata; it solely captures the incompatible relationship itself.

• FROM_NAV_UNIT_ID (NUMBER): A foreign key referencing the HR_NAVIGATION_UNITS table. This column identifies the source or current navigation unit from which the restriction applies.
• TO_NAV_UNIT_ID (NUMBER): A foreign key referencing the HR_NAVIGATION_UNITS table. This column identifies the target navigation unit that is deemed incompatible and should be restricted when accessed from the FROM_NAV_UNIT_ID.

The combination of these two columns forms the table's unique primary key (HR_INCOMPATIBILITY_RULES_UK), ensuring that no duplicate incompatible pairings are stored. The presence of a non-unique index on TO_NAV_UNIT_ID (HR_INCOMPATIBILITY_RULES_FK2) facilitates efficient reverse lookups.

Common Use Cases and Queries

This table is primarily referenced by the application's underlying logic to dynamically enable or disable menu options, buttons, or navigation paths. A common use case is preventing a user from initiating a specific transaction (TO_NAV_UNIT_ID) while another related transaction is in progress or a particular form is open (FROM_NAV_UNIT_ID). For reporting and analysis, administrators may query the table to audit or verify configured restrictions.

A basic query to retrieve all defined incompatibility rules is the standard SELECT statement provided in the ETRM:

SELECT FROM_NAV_UNIT_ID, TO_NAV_UNIT_ID FROM HR.HR_INCOMPATIBILITY_RULES;

A more practical query joins to the HR_NAVIGATION_UNITS table to translate the numeric IDs into meaningful unit names for review:

SELECT fnu.NAME AS FROM_UNIT, tnu.NAME AS TO_UNIT
FROM hr.hr_incompatibility_rules ir,
hr.hr_navigation_units fnu,
hr.hr_navigation_units tnu
WHERE ir.from_nav_unit_id = fnu.nav_unit_id
AND ir.to_nav_unit_id = tnu.nav_unit_id;

Related Objects

The HR_INCOMPATIBILITY_RULES table has a singular, critical dependency on the HR_NAVIGATION_UNITS table, which provides the master list of navigable application components. The relationships are explicitly defined by the following foreign key constraints, as documented in the provided metadata:

• Foreign Key Reference 1 & 2: HR_INCOMPATIBILITY_RULES.FROM_NAV_UNIT_ID references HR_NAVIGATION_UNITS (likely the NAV_UNIT_ID column).
• Foreign Key Reference 3 & 4: HR_INCOMPATIBILITY_RULES.TO_NAV_UNIT_ID references HR_NAVIGATION_UNITS (likely the NAV_UNIT_ID column).

These relationships ensure referential integrity, meaning that a rule cannot be defined for a navigation unit that does not exist in the master table. The table is also referenced by public and APPS schema synonyms (HR_INCOMPATIBILITY_RULES), which are the standard access points for EBS application code.