Search Results oke_k_standard_notes_s

Overview

OKE_NOTE_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Knowledge Exchange (OKE) module, which supports procurement and projects contract terms, deliverables, and associated notes. The package encapsulates the low-level data manipulation and validation logic for the OKE standard notes entity, a repository of reusable text blocks that can be attached to headers, lines, and deliverables within OKE-managed documents.

As a PVT-classified API, OKE_NOTE_PVT is not intended for direct invocation by external callers or customer extensions. It exists to provide a controlled, reusable layer beneath the public OKC_API and OKE_API surfaces, centralizing row-level operations, concurrency locking, validation, and multi-language translation handling for standard notes. The package reports a VALID status in the data dictionary and depends on foundational EBS infrastructure including FND_API, FND_GLOBAL, FND_LANGUAGES, APP_EXCEPTIONS, and OKC_API, confirming that it conforms to the standard EBS API programming conventions.

Key Procedures and Functions

The documented interface exposes thirteen procedures and functions that cover the complete lifecycle of a standard note record:

• INSERT_ROW — Creates a new standard note record, populating the base table and associated translation rows.
• UPDATE_ROW — Modifies an existing standard note record, including its translatable attributes.
• DELETE_ROW — Removes a standard note record and its dependent translation data.
• VALIDATE_ROW — Applies business-rule validation to note attributes before persistence.
• LOCK_ROW — Acquires a row-level lock to enforce concurrency control during update or delete operations.
• ADD_LANGUAGE — Inserts translation rows for an additional installed language, supporting the multi-language (_TL) architecture.

These routines are typical of an EBS private table-handler package, providing the atomic operations that public APIs invoke through their own higher-level interfaces. No parameter signatures are asserted here beyond what the documented procedure names imply.

Tables Accessed

The package reads and writes the standard notes entity and its associated reference data through APPS synonyms:

• OKE_K_STANDARD_NOTES_B — the base table holding standard note records; written by INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
• OKE_K_STANDARD_NOTES_TL — the translation table storing language-specific note text.
• OKE_K_STANDARD_NOTES_BH and OKE_K_STANDARD_NOTES_TLH — the history tables that preserve audit trails of base and translation changes.
• OKE_K_STANDARD_NOTES_S — a sequence used to generate primary keys for new note records.
• FND_LANGUAGES — the installed-language repository, consulted by ADD_LANGUAGE to determine valid translation targets.
• OKE_K_HEADERS, OKE_K_LINES, and OKE_K_DELIVERABLES_B — parent OKE entities to which notes may be associated or validated against.
• DUAL and PLITBLM — used for PL/SQL expression evaluation and index-by-table handling respectively.

Usage Notes

OKE_NOTE_PVT is invoked indirectly through the public OKC_API and OKE_API packages, which are themselves called by OKE forms, concurrent programs, and integration code responsible for creating and maintaining standard notes. Because the package is documented as referenced by only two other packages and is itself a private body, customization or direct calls should be avoided. Customers requiring standard note maintenance should use the supported public API surface or the relevant OKE application screens, leaving OKE_NOTE_PVT to perform the underlying DML, validation, locking, and translation management on their behalf.