Results for “locker_type_id”

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

Overview

HXC_LOCKER_TYPES is a reference table in the HXC (Time and Labor Engine) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The table stores the components that define "locker types", which are the classification records that govern how the Time and Labor Engine assigns and manages locks against concurrent processing, concurrent time entry, and other timecard-related operations. Locking rules and active locks both point back to this table to identify which type of lock is being applied, making it a small but structurally central lookup within the HXC schema.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as hub-leaning. HXC_LOCKER_TYPES behaves like a hub because it holds a single, stable business concept (a locker type) identified by a surrogate key, and it is the target of multiple foreign keys from surrounding tables rather than itself containing many foreign keys. This classification is a modeling suggestion only; the physical object remains a conventional relational table with nine documented columns and a unique index.

Key Information Stored

The most significant columns documented for HXC_LOCKER_TYPES are:

• LOCKER_TYPE_ID — the surrogate primary key, defined by the HXC_LOCKER_TYPES_PK constraint. It uniquely identifies each locker type row and is the column referenced by all three documented foreign keys.
• LOCKER_TYPE — the business-meaningful code or name describing the locker type.
• PROCESS_TYPE — indicates the processing context or category in which the locker type applies.
• CREATED_BY, CREATION_DATE — standard EBS WHO columns capturing row creation audit information.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing the most recent modification, including the login/session that performed it.
• ZD_EDITION_NAME — the editioning column introduced with the EBS 12.2 online patching architecture, used to resolve a row to the correct edition of the application code. This column also participates in the unique index HXC_LOCKER_TYPES_PK (LOCKER_TYPE_ID, ZD_EDITION_NAME).

The business-key candidate is the uniqueness enforced through HXC_LOCKER_TYPES_PK on the combination of LOCKER_TYPE_ID and ZD_EDITION_NAME, distinguishing the identity of the row from the surrogate identifier alone.

Common Use Cases and Queries

Typical usage involves resolving a locker type ID produced by locking rules or lock records into a human-readable description, and validating that a given locker type is configured before it is referenced.

• Lookup resolution: join HXC_LOCKS or HXC_LOCKING_RULES to HXC_LOCKER_TYPES on LOCKER_TYPE_ID to report the locker type description alongside active locks or rules.
• Configuration review: list all locker types and their PROCESS_TYPE to confirm which processing contexts have locking configured.
• Audit reporting: extract CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace who set up or changed locker type definitions and when.
• Integrity checks: identify orphaned lock records by left-joining HXC_LOCKS to HXC_LOCKER_TYPES and selecting rows where LOCKER_TYPE_ID does not resolve.

A representative query pattern is a join from HXC_LOCKS l to HXC_LOCKER_TYPES t on l.LOCKER_TYPE_ID = t.LOCKER_TYPE_ID, filtered by PROCESS_TYPE or by LAST_UPDATE_DATE for change tracking. In 12.2 environments, queries that must return only the current edition should account for ZD_EDITION_NAME.

Related Objects

• HXC_LOCKS — references HXC_LOCKER_TYPES via HXC_LOCKS.LOCKER_TYPE_ID; the primary consumer of locker type definitions.
• HXC_LOCKING_RULES — references HXC_LOCKER_TYPES twice, through HXC_LOCKING_RULES.LOCKER_TYPE_OWNER_ID and HXC_LOCKING_RULES.LOCKER_TYPE_REQUESTOR_ID, defining owner and requestor locker types for each rule.
• HXC_LOCKER_TYPES_PK — the unique index/constraint on LOCKER_TYPE_ID and ZD_EDITION_NAME that anchors row identity.
• HXC_LOCKING_RULES (as rule owner) — the governing rules table that drives which locker types apply to a given locking scenario and is the principal join partner in Time and Labor locking analysis.