Results for “hxc_transaction_details”

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

Overview

HXC_TRANSACTION_DETAILS is a transactional table within the HXC – Time and Labor Engine product of Oracle E-Business Suite. It stores the individual retrieval transaction details generated by the Time and Labor processing engine, capturing the outcome of time retrieval runs against time building blocks. Each row represents a discrete detail record associated with a parent HXC_TRANSACTIONS entry, providing the granular audit trail and error context required for timecard processing, payroll transfer, and downstream cost allocation.

In Data Vault modeling terms, the mined foreign key structure suggests this object is best classified as a link table. It resolves many-to-many and dependent associations between two principal entities — HXC_TRANSACTIONS (the transaction header) and HXC_TIME_BUILDING_BLOCKS (the retrieved time measurements) — while retaining descriptive attributes such as STATUS and EXCEPTION_DESCRIPTION. This positional role makes it a natural integration point between retrieval execution and the underlying time data model.

Key Information Stored

The table is documented with thirteen physical columns. The most operationally significant are summarized below.

• TRANSACTION_DETAIL_ID — Surrogate primary key, enforced by the unique index HXC_TRANSACTION_DETAILS_PK. This is the sole documented business-key candidate and is referenced by dependent tables.
• TRANSACTION_ID — Foreign key to HXC_TRANSACTIONS; identifies the parent retrieval transaction header to which the detail belongs.
• TIME_BUILDING_BLOCK_ID — Foreign key to HXC_TIME_BUILDING_BLOCKS; links the detail to the specific time building block consumed during retrieval.
• TIME_BUILDING_BLOCK_OVN — Object version number of the referenced time building block, supporting optimistic concurrency and consistency checks against the source row.
• STATUS — Processing status of the detail line, used to distinguish successful retrievals from failures or partial outcomes.
• EXCEPTION_DESCRIPTION — Free-text description of any error or exception raised while processing the detail, supporting troubleshooting.
• DATA_SET_ID — Identifier partitioning the record within a logical data set, relevant to multi-tenant or multi-group processing contexts.
• OBJECT_VERSION_NUMBER — Standard EBS optimistic locking column for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when, along with the last login session.

Common Use Cases and Queries

The table is typically queried to trace retrieval outcomes for a given transaction, to identify failing detail lines, and to reconcile retrieved time against source building blocks. A representative join retrieves status and error context for a transaction:

• SELECT d.transaction_detail_id, d.transaction_id, d.status, d.exception_description FROM hxc_transaction_details d WHERE d.transaction_id = :transaction_id ORDER BY d.transaction_detail_id;
• Joining to HXC_TIME_BUILDING_BLOCKS via TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN to obtain the underlying measured time.
• Aggregating details by STATUS to produce retrieval success/failure dashboards for Time and Labor administrators.
• Driving exception reports that surface EXCEPTION_DESCRIPTION rows for correction before payroll transfer.

Related Objects

Significant objects that reference or depend on HXC_TRANSACTION_DETAILS, with actual join columns, include:

• HXC_TRANSACTIONS — parent transaction header, joined on TRANSACTION_ID.
• HXC_TIME_BUILDING_BLOCKS — source time measurements, joined on TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN.
• HXC_ERRORS — stores processing errors, referencing TRANSACTION_DETAIL_ID.
• HXC_TRANSACTION_DETAILS_AR — archive counterpart referencing TRANSACTION_DETAIL_ID.
• HXC_RPT_TC_DETAILS_ALL — reporting detail table referencing TRANSACTION_DETAIL_ID.