Search Results okc_aav_pvt




Overview
Explore in AI Chat

Overview

OKC_AAV_PVT is the private implementation package body for the Action Attribute Values (AAV) subsystem within Oracle E-Business Suite's Enterprise Contracts (OKC) module. In the ETRM architecture, packages with the "_PVT" suffix carry the actual procedural logic for a business entity, while the corresponding public "_PUB" or API wrapper exposes a controlled interface to external callers. OKC_AAV_PVT supports the storage, validation, and lifecycle management of action attributes—the discrete data values that qualify a contract action (such as a deliverable, clause, or term) against the attributes defined in the contract's action-attribute framework.

This object is VALID in the APPS schema and is documented in ETRM release 12.2.2. It is classified as an API package of the PVT type, indicating that it is invoked internally by other OKC components rather than directly by end users. The package underpins the multi-row persistence of action attribute values and provides the low-level data access used by higher-level contract authoring and versioning flows.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions within this package. The core procedures include:

  • INSERT_ROW — Creates a new action-attribute-value record in the underlying AAV table, establishing the linked attribute value for a given action.
  • UPDATE_ROW — Modifies an existing action-attribute-value record.
  • DELETE_ROW — Removes an action-attribute value from persistence.
  • LOCK_ROW — Acquires a row-level lock to preserve transactional consistency during concurrent updates.
  • VALIDATE_ROW — Performs attribute-value validation, ensuring the supplied value conforms to the data type and constraint rules defined by the action attribute.
  • API_COPY — Duplicates action-attribute values, typically used when copying a contract, action, or template to a new context.
  • CHANGE_VERSION — Manages version transitions for action-attribute values, supporting the EBS versioning model where edits create new effective-dated rows.
  • QC — A quality-control / consistency check procedure that verifies the integrity of action-attribute values.
  • INSERT_ROW_UPG — A dedicated insert routine used during upgrade or data-migration processing.

The package depends on OKC_API, OKC_DATATYPES, OKC_P_UTIL, OKC_UTIL, FND_API, FND_GLOBAL, and FND_PROFILE, confirming that it adheres to the standard EBS API discipline of returning status, messages, and using the FND_GLOBAL profile and application context.

Tables Accessed

The primary documented table is OKC_ACTION_ATT_VALS, which stores the action attribute value rows managed by this package. It is accessed through the APPS synonym and supports the standard INSERT/UPDATE/DELETE/LOCK operations described above. The package also references PLITBLM, the PL/SQL index-by table (associative array) type, indicating internal use of collection structures to batch or stage attribute values. Through its view dependencies and SQL statements, the package additionally interacts with OKC_ACTION_ATTRIBUTES_V, OKC_ACTION_ATT_VALS_V, and OKC_CONDITION_OCCURS_V, which supply read-only attribute definitions and conditional occurrence data required for validation and versioning.

Usage Notes

OKC_AAV_PVT is not referenced by any database object directly and is therefore considered a private implementation layer. It is called by the public OKC API stack and by at least seven other EBS packages, most likely the OKC_ACTIONS and contract-authoring APIs. Typical invocation occurs during contract creation, action amendment, template application, and contract copy operations, as well as during EBS upgrade scripts via INSERT_ROW_UPG. Customizations should avoid calling this package directly; instead, extend behavior through the officially documented OKC public APIs, since the private routines may change between EBS 12.1.1 and 12.2.2 patch levels. Because it relies on FND_API and FND_GLOBAL, any direct call must establish the correct application context and handle the standard API return codes.