Search Results amw_process_locks_n1

Overview

AMW.AMW_PROCESS_LOCKS is a transactional table owned by the AMW schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. As its name and the ETRM documentation indicate, the object "stores information about process locks," functioning as a coordination mechanism that governs which concurrent AMW processes may execute against a given organization. The AMW schema underlies the Oracle Assets (formerly Fixed Assets) mass-additions and mass-transfers functionality, and process-level locking is essential in that context to prevent two concurrent requests from mutating the same fixed asset data set at the same time.

At runtime the table behaves as a directed dependency record: each row names one process that currently holds a lock (the locking process) and one process that is prevented from proceeding (the locked process), scoped by organization and security group. The heuristic Data Vault classification mined from the foreign-key structure is standalone, and no satellite hub-link pattern is implied; the table is best modeled as a simple operational state or junction table rather than a conformed dimension or fact. The single documented foreign key, on SECURITY_GROUP_ID to FND_SECURITY_GROUPS, is a Multi-Org/hosted-environment artifact rather than a true business relationship. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is indexed by AMW_PROCESS_LOCKS_N1 in APPS_TS_TX_IDX.

Key Information Stored

Ten columns are documented in the ETRM metadata. The most significant are:

• ORGANIZATION_ID (NUMBER) — stores the organization identifier, anchoring every lock record to a specific inventory organization and serving as the leading column of the non-unique index.
• LOCKING_PROCESS_ID (NUMBER) — the process identifier that currently holds the lock; this is the column surfaced by the user search term "locking_process_id".
• LOCKED_PROCESS_ID (NUMBER) — the process identifier that is blocked from proceeding while the lock is held.
• SECURITY_GROUP_ID (NUMBER) — used in hosted environments; the sole documented foreign key, referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER (NUMBER) — the optimistic-locking column used by the Oracle Application Framework/ADF business components to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard Who columns that record audit and provenance information for each row.

No primary-key constraint is documented in the ETRM extract, and the only index (AMW_PROCESS_LOCKS_N1) is non-unique across ORGANIZATION_ID, LOCKING_PROCESS_ID, and LOCKED_PROCESS_ID. Consequently no surrogate primary key is published, and the composite (ORGANIZATION_ID, LOCKING_PROCESS_ID, LOCKED_PROCESS_ID) is the closest business-key candidate for unique identification of a lock relationship; ROWID remains the only physical row identifier. Because the table carries standard Who and OVN columns, it is maintained by the EBS framework rather than by direct user entry.

Common Use Cases and Queries

Operational DBAs and AMW developers query this table to diagnose stuck or contended mass-addition and mass-transfer processes. A typical diagnostic retrieves all locks for an organization:

• SELECT locking_process_id, locked_process_id, last_update_date FROM amw.amw_process_locks WHERE organization_id = :org_id;
• SELECT * FROM amw.amw_process_locks WHERE locking_process_id = :locking_process_id; — the pattern implied by the searcher's term, returning every process blocked by a given locker.
• SELECT l.* FROM amw.amw_process_locks l, fnd_security_groups g WHERE l.security_group_id = g.security_group_id; — joins to resolve hosted-environment context.
• Aggregate reporting on lock frequency by organization to identify serialization hot spots, and joins to concurrent-request tables (FND_CONCURRENT_REQUESTS) via the process IDs to map locks to request names and phases.

Because rows accumulate with standard audit columns, retention or purge analysis should filter on CREATION_DATE and LAST_UPDATE_DATE.

Related Objects

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; the only documented FK relationship.
• APPS.AMW_PROCESS_LOCKS — the APPS-layer synonym/view through which the table is normally accessed by concurrent programs and forms.
• FND_CONCURRENT_REQUESTS — join source for resolving LOCKING_PROCESS_ID and LOCKED_PROCESS_ID to submitted concurrent requests.
• Other AMW process and mass-addition tables in the AMW schema, which rely on this lock table to serialize execution per organization.

The table references no other database objects beyond FND_SECURITY_GROUPS, confirming its narrow, operational role within the AMW locking framework.