Results for “okc_outcomes_s1”

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

Overview

OKC_OCE_PVT is a private PL/SQL package in the APPS schema that implements the core runtime logic for Oracle Contract Management outcomes. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, the OKC module uses the "outcome" concept to record the eventual result or disposition of a contract, a contract line, or a contract-related action. The OKC_OCE_PVT package body supplies the low-level, non-public data manipulation and versioning routines that the public OKC_OCE API and other OKC packages call. Its classification as a private (PVT) API indicates that it is not intended for direct invocation by customer code; instead, it acts as the internal engine behind the publicly exposed outcome interfaces. The persistent entity managed by this package is the outcome definition stored in the OKC_OUTCOMES tables, together with its translated (language) rows and history records. The package also participates in the OKC versioning framework, so outcome definitions can be versioned, copied, and restored consistently with other contract objects.

Key Procedures and Functions

The documented interface exposes 17 procedures and functions. Their purposes are as follows. QC performs the package-level quality or consistency check used during installation and upgrade validation. CHANGE_VERSION switches the working context to a different version of the outcome entity, supporting the OKC version model. API_COPY creates a new outcome definition by copying an existing one, which is the basis for reuse of standard outcomes. ADD_LANGUAGE inserts translated (TL) rows so that outcome descriptions are available in additional installed languages. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW provide the standard transactional data manipulation operations on the outcome base and translation tables, with LOCK_ROW enforcing concurrency control on a selected outcome record. VALIDATE_ROW applies the business validation rules required before an outcome may be saved or committed. INSERT_ROW_UPG is the upgrade-specific variant of INSERT_ROW, used by the upgrade driver to migrate pre-existing outcome data into the current schema. CREATE_VERSION and RESTORE_VERSION integrate outcomes with the OKC versioning engine, creating a new version snapshot and restoring a prior version respectively. Together these routines implement the complete lifecycle of an outcome definition, from creation and translation through validation, versioning, and deletion.

Tables Accessed

The package reads and writes the OKC_OUTCOMES base table (OKC_OUTCOMES_B), its history table (OKC_OUTCOMES_BH), the translation table (OKC_OUTCOMES_TL) and its translation history table (OKC_OUTCOMES_TLH), and the intersection table OKC_OUTCOMES_S1 that relates outcomes to other entities. It also queries the OKC views OKC_OUTCOMES_V, OKC_ACTIONS_V, OKC_CONDITION_HEADERS_V, OKC_PROCESS_DEFS_V, and OKX_RESOURCES_V for validation and lookup purposes. FND_APPLICATION and FND_LANGUAGES supply application and language reference data, while DUAL and the PLITBLM PL/SQL table type support internal utility logic. The package additionally depends on shared OKC infrastructure packages such as OKC_API, OKC_UTIL, OKC_P_UTIL, OKC_DATATYPES, and OKC_VERSION_PVT for error handling, versioning, and common services.

Usage Notes

OKC_OCE_PVT is never called directly by end users. It is invoked indirectly through the public OKC_OCE API, from Oracle Forms that maintain outcome definitions, from concurrent programs that load or migrate outcome data, and from the OKC upgrade driver during patching. Because it is referenced by ten other packages and references none of them in return, it sits low in the OKC dependency hierarchy. Customizations should target the public OKC_OCE API rather than this private package, since its signature and behavior may change between releases and it is not part of the supported customer integration surface.