Search Results hxt_errors

Overview

HXT_ERRORS is an APPS-owned database view in Oracle EBS Release 12.1.1 and 12.2.2, belonging to the HXT (Time and Labor) product family. The object is registered in ETRM with a status of VALID and is classified as a date-effective, session-filtered view. Its purpose is to expose error records generated during Time and Labor processing activities, such as timecard validation, rule execution, and payroll-related transactions, in a form that respects the application's effective-date security model.

Unlike a simple reporting view, HXT_ERRORS applies a WHERE predicate against FND_SESSIONS, comparing the view's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns to the EFFECTIVE_DATE of the current user session. This ensures that only error rows valid as of the session's effective date are returned, which is essential in an environment where historical and future-dated corrections coexist.

Underlying Base Objects

The view is defined over two documented base objects:

• HXT_ERRORS_F (SYNONYM) — the primary base table holding the actual error rows, including all data columns and the effective date range.
• FND_SESSIONS (SYNONYM) — the session table used in the WHERE clause to retrieve the EFFECTIVE_DATE for the current SESSION_ID via USERENV('SESSIONID').

HXT_ERRORS is therefore a filtered projection of HXT_ERRORS_F: every column in the view maps directly to a column in the base table, and the only transformation applied is the date-effective session filter. Because HXT_ERRORS_F is referenced through a synonym, the view resolves to the underlying APPS table at runtime, and no joins or aggregations alter the row shape.

Key Columns

The view exposes nineteen columns. The most significant include:

• ID — primary identifier for the error record.
• ERROR_MSG — the human-readable error description presented to users or logged for diagnostics.
• ORA_MESSAGE — the underlying Oracle database error text, where applicable.
• LOCATION — the point in processing where the error was raised.
• ERR_TYPE — classification of the error, used to distinguish severity or category.
• TIM_ID, HRW_ID, PTP_ID, PPB_ID, PAYROLL_ID, PERSON_ID — foreign-key references to the timecard, retrieved/processed time, payroll, and person contexts associated with the error.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range controlling visibility through the session filter.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

HXT_ERRORS is typically queried to investigate timecard submission failures, rule-processing exceptions, and payroll transfer errors. Because the view is session-filtered, queries executed directly in SQL*Plus or another client outside a properly initialized EBS session may return no rows or unexpected results, especially where FND_SESSIONS lacks a matching SESSION_ID entry. A representative query follows:

• SELECT id, error_msg, ora_message, person_id, tim_id, creation_date FROM hxt_errors WHERE person_id = :person_id ORDER BY creation_date DESC;
• SELECT err_type, COUNT(*) FROM hxt_errors GROUP BY err_type;
• SELECT e.id, e.error_msg, e.tim_id FROM hxt_errors e WHERE e.tim_id = :timecard_id;

Integrations and concurrent programs should generally read from HXT_ERRORS_F directly when session context is unavailable, or rely on the view within an authenticated EBS session. The view remains the documented, supported access path for effective-dated error reporting within Time and Labor.