Search Results okc_inst_cnd_pvt




Overview
Explore in AI Chat

Overview

OKC_OAT_PVT is a private PL/SQL package in the APPS schema that implements the outcome and argument layer of Oracle Contract Management (OKC), the contracts module of Oracle E-Business Suite. The suffix PVT identifies it as an internal, non-public API component: it is not intended for direct invocation by external integrations but instead supplies the procedural foundation on which public contract APIs and the contract authoring forms rely. Its principal subject area is contract outcomes and their associated arguments — the user-defined result records that capture values produced when a contract clause, condition, or deviation is evaluated, along with the parameter structure that describes each outcome.

The object is documented in ETRM as VALID and is present in both the 12.1.1 and 12.2.2 releases. Its dependency list identifies FND_API (the standard EBS API utility package), OKC_API (the public contract application programming interface), and the outcome argument tables OKC_OUTCOME_ARGUMENTS and OKC_OUTCOME_ARGUMENTS_V as direct references. It is referenced by ten other packages, including OKC_CONDITIONS_PVT, OKC_OUTCOME_PVT, OKC_OUTCOME_PUB, OKC_VERSION_PVT, OKC_COPY_CONTRACT_PVT, OKC_DELETE_CONTRACT_PVT, OKC_INST_CND_PUB, OKC_INST_CND_PVT, OKS_COPY_CONTRACT_PVT, and OKS_COVERAGES_PVT, confirming its role as a shared lower-level service.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. They fall into three functional groups.

  • Row-level data manipulation: INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, and VALIDATE_ROW perform the standard insert, update, delete, pessimistic lock, and validation operations against the outcome argument entity, applying the calling convention required by the OKC private API layer.
  • Versioning and lifecycle: QC (a query/cursor helper), CHANGE_VERSION, CREATE_VERSION, and RESTORE_VERSION manage transition between contract versions, allowing outcome argument records to be copied forward into a new version and reinstated from a prior one. CREATE_VERSION and RESTORE_VERSION are the core primitives used by the contract versioning framework.
  • Copy and upgrade: API_COPY replicates outcome argument data, typically as part of contract duplication or template instantiation, while INSERT_ROW_UPG supports the upgrade path used when migrating data between schema releases.

Tables Accessed

Access is performed through APPS synonyms. OKC_OUTCOME_ARGUMENTS is the base transactional table holding outcome argument rows; OKC_OUTCOME_ARGUMENTS_H is the corresponding history table maintained for versioned records; OKC_OUTCOME_ARGUMENTS_S1 is a supporting index or sequence-backed structure associated with the entity; OKC_OUTCOME_ARGUMENTS_V is a view exposing the arguments for read access. FND_APPLICATION supplies application identifier and name lookups for multitenant and localization handling, DUAL is used for single-row evaluations, and PLITBLM is the standard EBS PL/SQL index-by table used for bulk processing.

Usage Notes

OKC_OAT_PVT is invoked indirectly. Contract forms in Oracle Contracts and the Service (OKS) contract modules call the public wrappers OKC_OUTCOME_PUB and OKC_INST_CND_PUB, which in turn delegate to this package. Concurrent programs that copy, delete, or version contracts reach it through OKC_COPY_CONTRACT_PVT, OKC_DELETE_CONTRACT_PVT, and OKC_VERSION_PVT. Custom development should not call OKC_OAT_PVT directly; the supported entry points are the public APIs, which enforce validation, security, and message handling. The frequent appearance of OKC_INST_CND_PVT in the reference list confirms a close coupling with the instantiated-conditions processing path. Because the package is marked VALID and carries private classification, its signature is not part of Oracle's committed public interface and may change between patch levels, so any custom dependency on it should be replaced with a public API where possible.