Search Results hxc_transaction_details_pk




Overview
Explore in AI Chat

Overview

The HXC_TRANSACTION_DETAILS table is a core data object within the Oracle E-Business Suite Time and Labor Engine (HXC). It functions as a detailed audit and retrieval log for time entry transactions. Its primary role is to store a granular, historical record of the specific time building blocks that were submitted, approved, or otherwise processed within a given transaction. This table is essential for maintaining data integrity, enabling traceability from a high-level transaction record back to the individual timecard components, and supporting complex retrieval operations within the Time and Labor application.

Key Information Stored

The table's structure centers on linking transaction headers to the underlying time data. Its primary key is TRANSACTION_DETAIL_ID. The most critical columns are the foreign keys that establish these relationships: TRANSACTION_ID links to the HXC_TRANSACTIONS table to identify the parent transaction event, while TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN (Object Version Number) together form a composite foreign key to the HXC_TIME_BUILDING_BLOCKS table. This link precisely identifies the specific version of a time entry (e.g., a day, an hour segment, or an attribute) that was included in the transaction. The table essentially acts as a junction, recording which building blocks were part of which transactional process.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting timecard submission or approval flows. Support personnel can trace a failed process back to the exact time entries involved. Another key use is for historical reporting on time entry changes, allowing analysts to see what data was modified in a batch. A typical query pattern involves joining HXC_TRANSACTION_DETAILS to both HXC_TRANSACTIONS for transaction metadata (type, date, status) and HXC_TIME_BUILDING_BLOCKS for the actual time entry details.

SELECT htd.transaction_id,
       ht.transaction_type,
       ht.date_from,
       htd.time_building_block_id,
       hbb.building_block_type
FROM   hxc_transaction_details htd,
       hxc_transactions ht,
       hxc_time_building_blocks hbb
WHERE  htd.transaction_id = ht.transaction_id
AND    htd.time_building_block_id = hbb.time_building_block_id
AND    htd.time_building_block_ovn = hbb.object_version_number
AND    ht.resource_id = 12345;

Related Objects

  • HXC_TRANSACTIONS: The parent table containing header information for each transaction (e.g., transaction type, resource, process date). HXC_TRANSACTION_DETAILS.TRANSACTION_ID is a foreign key to this table.
  • HXC_TIME_BUILDING_BLOCKS: The foundational table storing all timecard entries. HXC_TRANSACTION_DETAILS links to it via the composite foreign key on TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN.
  • HXC_TRANSACTION_DETAILS_PK: The primary key constraint on the TRANSACTION_DETAIL_ID column, ensuring uniqueness for each detail record.