Results for “hxc_locks”

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

Overview

HXC_LOCKS is a table owned by the HXC schema within the Oracle EBS Time and Labor Engine (HXC) product module. As its name and documentation description indicate, it holds the locks components used by the Time and Labor Engine to coordinate and serialize access to time building data during processing. The table exists in both Oracle EBS 12.1.1 and 12.2.2, and its ETRM status is VALID, confirming it is a live, supported object in the application data model.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure positions HXC_LOCKS as a link table. This classification suggests that HXC_LOCKS functions primarily as an associative or relationship entity, resolving and connecting references between locker types, resources, and time building blocks rather than acting as an independent hub of business entities or a pure descriptive satellite. The strong dependency on multiple parent tables via foreign keys reinforces this associative role in the Time and Labor Engine's processing flow.

Key Information Stored

The documented physical schema for HXC_LOCKS in ETRM 12.2.2 consists of 40 columns. The most significant columns for understanding and querying the table include:

• LOCKER_TYPE_ID — Foreign key to HXC_LOCKER_TYPES, identifying the category of lock being applied.
• TIME_BUILDING_BLOCK_ID — Foreign key to HXC_TIME_BUILDING_BLOCKS, identifying the time building block that is being locked.
• TIME_BUILDING_BLOCK_OVN — Object version number for the referenced time building block, used for optimistic concurrency control.
• RESOURCE_ID — Identifies the resource (typically a person or resource entity) associated with the lock.
• START_TIME and STOP_TIME — Define the effective interval during which the lock applies.
• TRANSACTION_LOCK_ID — Identifies the transaction-level lock context.
• LOCK_DATE — The date the lock was created or recorded.
• PROCESS_ID — Identifies the concurrent process or job that owns the lock.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — Descriptive flexfield (DFF) columns supporting extensible, customer-defined locking attributes.

The surrogate primary key is not separately documented under a distinct ID column name in the excerpt, but the unique business-key candidates center on the pairing of LOCKER_TYPE_ID with TIME_BUILDING_BLOCK_ID and the associated resource/time interval, since these combinations define the scope of an individual lock. The foreign key columns are explicitly documented, while the descriptive flexfield columns follow the standard EBS convention for extensibility.

Common Use Cases and Queries

HXC_LOCKS is most commonly queried when diagnosing concurrency, deadlock, or lock-contention issues in Time and Labor processing. Typical scenarios include identifying which process holds a lock on a given time building block, auditing resource-level locking during time entry or approval, and reconciling orphaned locks after failed concurrent programs.

A representative query to find active locks for a specific time building block might join HXC_LOCKS to HXC_TIME_BUILDING_BLOCKS on TIME_BUILDING_BLOCK_ID. Another common pattern joins to HXC_LOCKER_TYPES on LOCKER_TYPE_ID to resolve the human-readable lock type name. Reporting use cases include analyzing lock duration using START_TIME and STOP_TIME, and correlating locks to concurrent processes using PROCESS_ID for performance tuning of the Time and Labor Engine.

Related Objects

• HXC_LOCKER_TYPES — Referenced by HXC_LOCKS.LOCKER_TYPE_ID; provides the lock type definition.
• HXC_TIME_BUILDING_BLOCKS — Referenced by HXC_LOCKS.TIME_BUILDING_BLOCK_ID and HXC_LOCKS.TIME_BUILDING_BLOCK_OVN; the primary time building entity being locked.
• HXC_TIME_BUILDING_BLOCK_OVN relationship — supports version-aware locking on the parent block.

Together, these relationships define HXC_LOCKS as a dependent, link-style table whose integrity depends on valid references to locker types and time building blocks within the HXC module.