Search Results surrogate_id

Overview

HR.HR_STU_EXCEPTIONS is an Oracle E-Business Suite HRMS diagnostic table residing in the HR schema. Its purpose is narrowly scoped: it captures any error conditions encountered during the installation or application of HRMS seed data (startup data). The table functions as a staging and audit surface for the seed data load process. Under normal operating conditions, the table remains empty; the presence of rows signals that one or more validation checks failed during a seed data operation and that corrective action may be required before the affected setup data can be relied upon.

The object is registered in FND Design Data as PER.HR_STU_EXCEPTIONS and holds a status of VALID in both 12.1.1 and 12.2.2. It is stored in the APPS_TS_INTERFACE tablespace with a PCT Free of 10. The ETRM metadata classifies this object as a standalone entity based on its foreign key structure. In Data Vault modeling terms, this is a satellite-style diagnostic record: it is not a master or reference entity, and it does not participate in hub or link relationships. The primary key itself, HR_STU_EXCEPTIONS_PK, combines the startup table name, the surrogate identifier of the failing record, and the exception text, which means the table records one row per distinct validation failure rather than one row per source record.

Key Information Stored

The documented physical schema contains four columns. The most significant are as follows:

• TABLE_NAME (VARCHAR2, 30, mandatory) — the name of the startup table in which the error was detected. This identifies which seed data entity failed.
• SURROGATE_ID (NUMBER, 15) — the identifier of the specific record that failed the validation check within that startup table.
• EXCEPTION_TEXT (VARCHAR2, 240) — human-readable help text describing the validation check that failed. This is the primary diagnostic payload.
• TRUE_KEY (VARCHAR2, 240) — additional help text identifying the name of the item that failed validation, supporting more precise root-cause analysis.

The primary key HR_STU_EXCEPTIONS_PK spans TABLE_NAME, SURROGATE_ID, and EXCEPTION_TEXT. Because this composite key is the sole unique index documented, those three columns also serve as the business-key candidates for the table. There is no separate meaningless system-generated key; the natural combination of source table, source record, and failure message uniquely identifies each exception row.

Common Use Cases and Queries

The principal operational use case is post-installation verification of HRMS seed data loads. After running a seed data installation or upgrade, DBAs and functional consultants query this table to confirm success or to enumerate failures. An empty result set confirms that no validation errors were logged. When rows are present, the standard review pattern lists the affected startup table and the corresponding error text:

• Retrieve all logged exceptions: SELECT TABLE_NAME, SURROGATE_ID, EXCEPTION_TEXT, TRUE_KEY FROM HR.HR_STU_EXCEPTIONS;
• Group failures by source table to gauge impact, for example with a GROUP BY TABLE_NAME aggregate over the surrogate identifiers.
• Isolate all exceptions for a specific entity, adding a predicate such as WHERE TABLE_NAME = :startup_table.

Because the table is populated only during seed data operations, it also serves as a lightweight audit trail for installation history. Support and implementation teams use the combination of SURROGATE_ID and TRUE_KEY to trace a failure back to a specific configuration record, then correct the underlying setup data and re-run the affected seed process. Reporting is typically ad hoc rather than scheduled, given the table's normally empty state.

Related Objects

The metadata documents that HR.HR_STU_EXCEPTIONS does not reference any database object through foreign keys — consistent with its standalone classification. It is, however, referenced by the following synonyms, which are the primary access paths used by application code and support tooling:

• APPS.HR_STU_EXCEPTIONS — the APPS-owned synonym used by application and concurrent program code under the APPS schema, the standard access point during EBS runtime.
• PUBLIC.HR_STU_EXCEPTIONS — the public synonym available to any database session with appropriate privileges, frequently used in diagnostic and support scripts.

Beyond these synonyms, the object carries no documented FK dependencies in either direction. Related dependencies in practice include the HRMS seed data loading framework and the various startup tables whose names appear in the TABLE_NAME column, since each row in HR_STU_EXCEPTIONS points back to a seed data table by name rather than by a formal foreign key relationship.