Results for “hxc_transactions”

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

Overview

HXC_TRANSACTIONS is the core transaction header table in the Oracle Time and Labor Engine (HXC) module, holding one row per time-related transaction processed by the engine. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, this table acts as the transactional anchor for time entry, retrieval, submission, and approval workflows generated through the Time and Labor Engine APIs and concurrent processes. It sits in the HXC schema alongside its dependent detail table and is referenced throughout the Time and Labor reporting and calculation stack.

Under the heuristic Data Vault classification derived from the mined foreign-key structure, HXC_TRANSACTIONS is assessed as hub-leaning. In Data Vault terms, a hub captures a unique business entity keyed by a surrogate identifier, and HXC_TRANSACTIONS fits this pattern: it is the parent of dependent child records and is not itself dependent on a higher-level transactional parent. Modeling this table as a hub keyed on TRANSACTION_ID, with the descriptive and status attributes treated as satellite data, is a reasonable design suggestion for customers building an analytical or integration layer.

Key Information Stored

The documented physical schema for 12.2.2 lists 14 columns. The most significant columns and their roles are as follows:

• TRANSACTION_ID — the surrogate primary key, enforced by the HXC_TRANSACTIONS_PK unique index. This is the single unique-index column documented and therefore the lone business-key candidate in the current metadata; it is the join key to child records.
• TRANSACTION_PROCESS_ID — associates the transaction with the processing run or batch context that produced it, supporting traceability of engine activity.
• TRANSACTION_DATE — the effective date of the transaction, used for period-based reporting, payroll cutoff logic, and ordering of events.
• TYPE and TRANSACTION_CODE — classify the nature of the transaction (for example, entry versus retrieval, or a specific engine operation), driving downstream processing rules.
• STATUS — the current lifecycle state of the transaction (submitted, processed, error, and similar), which is central to exception handling and workflow monitoring.
• EXCEPTION_DESCRIPTION — free-text or coded explanation populated when the engine encounters a failure or warning, making it the primary diagnostic field for operational support.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column, ensuring concurrency safety during updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns providing audit history and user attribution.
• DATA_SET_ID — identifies the data set or reference group context for the transaction, relevant in multi-set or legislative-data configurations.

Common Use Cases and Queries

HXC_TRANSACTIONS is routinely queried for engine monitoring, failed-transaction remediation, and reconciliation reporting. A typical operational query joins the header to its details and filters on status and date range:

• SELECT t.transaction_id, t.transaction_date, t.type, t.status, t.exception_description FROM hxc_transactions t WHERE t.status = 'ERROR' AND t.transaction_date >= :start_date ORDER BY t.transaction_date DESC;
• SELECT t.transaction_id, d.* FROM hxc_transactions t JOIN hxc_transaction_details d ON d.transaction_id = t.transaction_id WHERE t.transaction_process_id = :process_id;
• Aggregate throughput reporting by process: SELECT transaction_process_id, status, COUNT(*) FROM hxc_transactions GROUP BY transaction_process_id, status;

Reconciliation reports compare transactions created within a period against the expected timecard volume, while integration extracts use TRANSACTION_ID, TRANSACTION_DATE, and STATUS to feed downstream systems.

Related Objects

• HXC_TRANSACTION_DETAILS — the principal dependent child table; joined on HXC_TRANSACTION_DETAILS.TRANSACTION_ID = HXC_TRANSACTIONS.TRANSACTION_ID. This is the only foreign-key relationship documented in the metadata and represents the header-to-detail backbone.
• HXC_TRANSACTIONS_PK — the primary-key constraint on TRANSACTION_ID, governing uniqueness and index access paths.
• HXC_TIME_ENTRY / HXC_TIME_ATTRIBUTE style core HXC tables — related time-recording objects that supply the source data feeding transaction generation.
• Time and Labor Engine APIs — the HXC public APIs that create and update these transaction rows during processing.
• Payroll and OTL reporting views — reporting layer objects that reference transaction headers to surface processing outcomes.

Because the documented relationship data is limited to a single child FK, integration and reporting designs should confirm any additional dependencies against the live system dictionary before finalizing join logic.