Results for “lock_control”

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

Overview

AMW_CONTROL_PVT is a private PL/SQL package body in the APPS schema that encapsulates the business-level validation and persistence logic for Control entities within the Oracle Enterprise Asset Management (eAM) / Enterprise Technical Reference Model (ETRM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. The package name uses the _PVT suffix, which by EBS convention denotes a private API intended for internal consumption rather than direct customer extension. It sits beneath the public control API layer and above the table handlers (AMW_CONTROL_PVT's internal table manipulation routines) that perform the physical DML against the underlying control tables. Its stated purpose, per embedded comments, is to validate business-level logic before calling table handlers to load rows. Based on the source excerpt, it is also the layer exposed to callers searching for validate_control, a dedicated validation routine invoked before commits are attempted.

Key Procedures and Functions

The package exposes nine documented procedures and functions, consistent with the PL/SQL API standard that groups load, create, update, delete, lock, and validate operations:

• LOAD_CONTROL — the primary entry point. Accepts API version, initialization, and validation-level parameters, plus a control_rec_type record, and returns return status, message count, and message data along with control revision and control identifiers. It orchestrates validation and table handler calls to persist a control.
• LOAD1_CONTROL — an alternate/overload load routine, likely supporting a different control mode or revision path.
• CREATE_CONTROL — inserts a new control record, typically delegating to table handlers after validation.
• UPDATE_CONTROL — modifies an existing control record.
• DELETE_CONTROL — removes a control record (or logically deactivates it).
• LOCK_CONTROL — obtains a lock on a control row to serialize concurrent modifications.
• VALIDATE_CONTROL — the routine surfaced by the user's validate_control search. Performs business-rule validation on a control record independently of persistence.
• CHECK_CONTROL_ITEMS — validates associated control items, ensuring child rows are consistent before the parent operation completes.
• VALIDATE_CONTROL_REC — validates the inbound control_rec_type record structure, checking required attributes and field-level integrity.

All routines follow the FND_API convention, accepting p_api_version_number, p_init_msg_list, and p_commit, and returning x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• AMW_CONTROLS_B — base table storing control header attributes.
• AMW_CONTROLS_S — the corresponding translated/summary table.
• AMW_CONTROLS_TL — the translation table holding language-specific control text.
• AMW_CONTROL_REV_S — stores control revision records referenced by control revision identifiers.
• PER_JOBS — HR jobs table, referenced for validation of job-related control attributes.
• DUAL — used for single-row lookups such as sequence or lookup meaning resolution.

Usage Notes

AMW_CONTROL_PVT is invoked indirectly. It is referenced by three other packages, indicating it is called by the public control API or eAM forms and concurrent programs rather than by end users. In EBS 12.1.1 and 12.2.2, form-based control maintenance (likely via an eAM setup form) and concurrent programs loading control data would call this private layer. Custom code should not call it directly; instead, use the public API wrapper. The global g_user_id and g_login_id are initialized from FND_GLOBAL at package load, enforcing standard EBS audit and security context.