Search Results hxc_transactions

Overview

The HXC_TRANSACTIONS table is a core data object within the Oracle E-Business Suite (EBS) Time and Labor Engine (HXC). It serves as the primary transactional repository for timecard entries. Each row in this table represents a distinct time entry transaction, such as the initial submission, a correction, or an approval action for a specific time period. Its role is to act as the master header record, capturing the essential metadata of a time transaction, which is then detailed in related child tables. The existence of the primary key HXC_TRANSACTIONS_PK underscores its fundamental role as the unique identifier source for all time transactions in the system.

Key Information Stored

While the provided metadata does not list specific columns, the primary key column is documented as TRANSACTION_ID. Based on its role as a header table, it typically stores high-level attributes for each time transaction. Common columns in such a structure include:

• TRANSACTION_ID: The system-generated unique identifier (PK) for the transaction.
• RESOURCE_ID: Identifier linking to the person (employee or contingent worker) who performed the work.
• TIMECARD_ID: Reference to the overarching timecard to which this transaction belongs.
• TRANSACTION_TYPE: Indicates the nature of the transaction (e.g., 'CREATE', 'UPDATE', 'APPROVE', 'REJECT').
• TRANSACTION_DATE: The date and time when the transaction was recorded in the system.
• APPROVAL_STATUS: The current approval state of the transaction (e.g., 'WORKING', 'SUBMITTED', 'APPROVED').
• START_TIME and STOP_TIME: The date/time boundaries for the period of work this transaction covers.

Common Use Cases and Queries

This table is central to auditing time entry history, troubleshooting submission issues, and building custom time and labor reports. A typical use case involves tracing the complete lifecycle of a time entry. For example, to find all transactions for a specific employee within a date range, one might query:

SELECT transaction_id, transaction_type, transaction_date, approval_status
FROM hxc_transactions
WHERE resource_id = :emp_id
AND start_time >= :date_from
ORDER BY transaction_date;

Another common pattern is joining to the HXC_TRANSACTION_DETAILS table (via the documented foreign key relationship) to retrieve both header and detailed line information, such as hours and cost codes, for reporting or data validation purposes.

Related Objects

The primary documented relationship is with the HXC_TRANSACTION_DETAILS table, which holds the granular details (like hours, earning policies, and segments) for each transaction header. The foreign key HXC_TRANSACTION_DETAILS.TRANSACTION_ID references HXC_TRANSACTIONS.TRANSACTION_ID. This table is also intrinsically linked to key Time and Labor base tables such as HXC_TIMECARDS (for the timecard structure) and HXC_TIME_BUILDING_BLOCKS (for the atomic time data). Programmatically, data in this table is typically created and managed via the Time and Labor public APIs rather than through direct DML.