Search Results oks_interaction_hist_pvt




Overview
Explore in AI Chat

Overview

OKS_INTERACTION_HIST_PVT is a private (PVT) PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the Service Contracts (OKS) module family. It implements the internal application logic layer for Service Interaction History records, providing the row-level operations and validation routines that sit beneath the public API surface. In the standard Oracle EBS layered API architecture, a PVT package is never intended to be called directly by external code; it is invoked exclusively by its corresponding public wrapper, in this case OKS_INTERACTION_HIST_PUB. The package therefore encapsulates the physical data manipulation against the OKS_INTERACTION_HISTORY table, allowing the public API to enforce interface rules, security, and business policy while the private package concentrates on persistence and record consistency.

Key Procedures and Functions

The package exposes eighteen documented program units, of which the following core routines form the operational backbone:

  • INSERT_ROW — Creates a new interaction history record, populating the target table with the supplied attribute values and system-derived columns such as WHO columns and object version number.
  • UPDATE_ROW — Modifies an existing interaction history record identified by its primary key, applying the changed attributes while preserving audit information.
  • DELETE_ROW — Removes an interaction history record from the underlying table.
  • LOCK_ROW — Obtains a pessimistic lock on the target row, typically used to serialize concurrent modifications before an update or delete.
  • VALIDATE_ROW — Performs entity-level validation on the inbound record, checking mandatory attributes and referential consistency before a write operation is permitted.
  • API_COPY — Duplicates an existing interaction history record, supporting scenarios where history must be replicated across related entities.
  • CHANGE_VERSION — Manages the object version number, ensuring optimistic locking semantics are honoured across concurrent transactions.
  • QC — A quality-control routine used internally for consistency checking of the processed record.

Each routine follows the standard EBS API conventions, returning a PL/SQL boolean or status indicator and populating an error message table rather than raising uncontrolled exceptions.

Tables Accessed

The package operates primarily against OKS_INTERACTION_HISTORY, the base table storing interaction history records, accessed through an APPS synonym. It also references OKS_INTERACTION_HIST_V, the corresponding view used for read operations and validation lookups, and PLITBLM, the standard EBS PL/SQL table type used for array-based batch processing of rows. No other application tables are documented as direct dependencies.

Usage Notes

OKS_INTERACTION_HIST_PVT is referenced by exactly one other package, OKS_INTERACTION_HIST_PUB, which acts as the supported entry point for all interaction history maintenance. The private package is not directly callable from forms or concurrent programs in a supported configuration; it also declares an internal self-reference, reflecting nested calls within the package body. It depends on FND_API and OKC_API for shared API utilities and error handling. Customisations requiring interaction history manipulation should always target the public API, because the private layer carries no guarantee of interface stability across patch levels and is subject to change without notice in Oracle EBS 12.1.1 and 12.2.2.