Results for “reference_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IRC_REFERENCES is a table owned by the HR schema within the PER (Human Resources) product family of Oracle E-Business Suite. In the documented ETRM metadata for both release 12.1.1 and 12.2.2, the object is registered as VALID, yet its official description states "Not currently used." This designation reflects the object's status as a reserved or legacy structure within the Oracle iRecruitment data model, rather than an actively maintained transactional table. It exists in the physical schema and is subject to standard EBS dictionary management, but Oracle does not expose it as a supported functional entity.

From a data modeling perspective, the ETRM metadata classifies IRC_REFERENCES as standalone using a heuristic Data Vault assessment mined from foreign key structure. As a modeling suggestion, this would place the table as an isolated hub-like or reference structure with no incoming or outgoing link dependencies. The absence of documented foreign key relationships reinforces that it does not participate in the referential fabric of the HR schema in the same manner as core iRecruitment tables such as IRC_CANDIDATES or IRC_ASSIGNMENTS. Any integration work should treat it as an inert container whose population, if any, is not governed by documented EBS application logic.

Key Information Stored

The physical schema documents eleven columns. The most significant are summarized below, distinguishing the surrogate key from business-key candidates:

• REFERENCE_ID — The surrogate primary key, enforced through the unique index IRC_REFERENCES_PK. This is the column referenced by the user search term "irc_references_pk."
• PARTY_RELATIONSHIP_ID — A relationship identifier, presumably associating a reference with a party relationship record in the TCA (Trading Community Architecture) model. This is the strongest business-key candidate in the table, though no unique constraint is documented on it.
• REFERENCE_STATUS — The current lifecycle state of the reference record.
• REFERENCE_STATUS_DATE_CHANGED — The date the status was last modified.
• COMMENTS — Free-text remarks; this column is associated with the supplemental index SYS_IL0000202722C00005$$, indicating a LOB or large-column segment.
• OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column used for concurrent update control (OAF/BC4J).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — WHO-column audit triad identifying when and by whom the row was last changed.
• CREATED_BY, CREATION_DATE — WHO-column creation pair recording insert audit information.

Only REFERENCE_ID is documented as a unique business-key candidate via IRC_REFERENCES_PK; PARTY_RELATIONSHIP_ID functions as a probable logical foreign key without a documented unique index.

Common Use Cases and Queries

Because the table is documented as "Not currently used," practical reporting scenarios are limited to schema auditing, data migration analysis, and discovery. A typical catalog query confirms the primary key and structure:

SELECT uc.constraint_name, ucc.column_name
FROM   user_constraints uc
JOIN   user_cons_columns ucc ON uc.constraint_name = ucc.constraint_name
WHERE  uc.table_name = 'IRC_REFERENCES'
AND    uc.constraint_type = 'P';

A row-count and null-profile check is useful before any migration or cleanup decision: SELECT COUNT(*) FROM hr.irc_references;. Where rows exist, a join to TCA party relationships on PARTY_RELATIONSHIP_ID can reveal legacy reference data, for example joining HR.IRC_REFERENCES.PARTY_RELATIONSHIP_ID to HZ_RELATIONSHIPS.PARTY_RELATIONSHIP_ID. Auditing queries using LAST_UPDATE_DATE and LAST_UPDATED_BY support change-tracking reports. Given the "Not currently used" status, no supported concurrent program, OAF page, or API is expected to reference this table, so query development should be treated as investigative rather than operational.

Related Objects

The metadata documents no foreign keys, consistent with the standalone classification. The following objects are the most significant likely point of interaction, inferred from column naming and the surrounding iRecruitment schema:

• HZ_RELATIONSHIPS — Potential join on PARTY_RELATIONSHIP_ID, if populated.
• IRC_CANDIDATES — Adjacent iRecruitment entity; may share the reference concept via person/party identifiers.
• IRC_ASSIGNMENTS — Recruitment assignment context potentially referencing reference records.
• PER_ALL_PEOPLE_F — Underlying person records for reference subjects where they correspond to employees.
• HR_LOOKUPS / FND_LOOKUP_VALUES — Source of allowed values for REFERENCE_STATUS where lookups are used.
• IRC_REFERENCES_PK (index) — The unique index enforcing the primary key on REFERENCE_ID.
• SYS_IL0000202722C00005$$ (index) — Supplemental LOB index supporting the COMMENTS column.

Because no formal referential constraints are documented, these relationships should be validated empirically in each environment before being relied upon.