Search Results transaction_detail_id

Overview

The HXC_DEP_TRANSACTION_DETAILS table is a core transactional entity within the Oracle E-Business Suite Time and Labor Engine (HXC). It functions as a detailed ledger, recording the individual time building blocks that constitute a deposit transaction. A deposit transaction represents a batch of timecard data submitted for processing into the payroll or project accounting systems. This table provides the critical link between the high-level deposit transaction header and the atomic units of time data, enabling detailed audit trails, error reconciliation, and the processing of timecard information from submission through to final import.

Key Information Stored

The table's primary purpose is to associate time entries with their parent deposit transaction. Its key columns, as defined by the provided metadata, are the foreign keys that establish these essential relationships. The TRANSACTION_DETAIL_ID column serves as the table's unique primary key. The TRANSACTION_ID column is a foreign key linking each detail record to its parent header in the HXC_DEP_TRANSACTIONS table. The TIME_BUILDING_BLOCK_ID and its corresponding TIME_BUILDING_BLOCK_OVN (Object Version Number) are foreign keys that precisely identify the specific time entry, stored in the HXC_TIME_BUILDING_BLOCKS table, that is included within the deposit. This structure ensures each time building block's inclusion in a deposit is tracked and version-controlled.

Common Use Cases and Queries

This table is central to troubleshooting and reporting on timecard deposit processes. A common use case involves identifying all time entries contained within a specific failed or problematic deposit transaction for error analysis. Another key scenario is tracing the deposit history of a particular time entry to confirm its successful submission and processing. A fundamental query pattern joins this table to both its parent transaction and the time building block details:

• Sample Query: To retrieve all time building blocks for a given transaction ID, a developer or analyst might use: SELECT hdt.transaction_id, hdtb.* FROM hxc_dep_transaction_details hdtd JOIN hxc_time_building_blocks hdtb ON hdtd.time_building_block_id = hdtb.time_building_block_id WHERE hdtd.transaction_id = :p_transaction_id;
• Reporting Use Case: Generating a report showing the volume and status of time entries deposited per payroll period or by a specific user, which requires joining HXC_DEP_TRANSACTION_DETAILS to HXC_DEP_TRANSACTIONS and HXC_TIME_BUILDING_BLOCKS.

Related Objects

The table's integrity and utility are defined by its documented foreign key relationships, which integrate it into the broader Time and Labor data model.

• HXC_DEP_TRANSACTIONS: This is the parent header table. The relationship is maintained via the HXC_DEP_TRANSACTION_DETAILS.TRANSACTION_ID column referencing HXC_DEP_TRANSACTIONS.
• HXC_TIME_BUILDING_BLOCKS: This is the master table for all timecard entries. The relationship is a composite foreign key, where HXC_DEP_TRANSACTION_DETAILS.TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN reference the corresponding columns in HXC_TIME_BUILDING_BLOCKS, ensuring the correct version of the time entry is linked to the deposit.