Search Results okc_oat_pvt




Overview
Explore in AI Chat

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

Overview

OKC_OAT_PVT is a private (PVT-classified) PL/SQL package body in the APPS schema that supports Oracle E-Business Suite's Contract Terms and Conditions (OKC) module, specifically the outcome and argument framework underlying Outcome Attribute Translation (OAT). The package functions as the internal engine for creating, versioning, validating, and maintaining rows in the OKC_OUTCOME_ARGUMENTS family of tables. It is not a public API offered directly to external consumers; instead, it is invoked by the broader OKC_API and OKC_VERSION_PVT layer to implement outcome argument behavior during contract authoring, contract versioning, and upgrade operations.

The business purpose is to ensure that outcome arguments — the structured parameters attached to contract outcomes defined in the Process Definition repository — are correctly persisted, copied across business object versions, validated against their governing attribute definitions, and migrated during application upgrades. Because outcomes drive downstream contract term generation and rule evaluation, the integrity maintained by OKC_OAT_PVT is critical to correct contract lifecycle behavior.

Key Procedures and Functions

  • QC — A quality-control or quick-check utility that validates the internal consistency of outcome argument data before or after processing.
  • CHANGE_VERSION — Handles the version-change transition for outcome argument records, allowing them to be associated with the correct contract version.
  • API_COPY — Copies outcome argument data, typically during copy operations such as contract duplication or template application.
  • INSERT_ROW — Inserts a new outcome argument row with standard WHO columns and validation checks.
  • LOCK_ROW — Issues a row-level lock on a specific outcome argument record, enforcing concurrency control during updates.
  • UPDATE_ROW — Updates an existing outcome argument, preserving audit columns and revalidating dependent attributes.
  • DELETE_ROW — Logically or physically removes an outcome argument row.
  • VALIDATE_ROW — Performs business rule validation on an outcome argument before persistence, ensuring required attributes and value constraints are satisfied.
  • INSERT_ROW_UPG — A variant of INSERT_ROW used specifically during upgrade processing to migrate legacy outcome argument data into the current structure.
  • CREATE_VERSION — Creates a new version of an outcome argument or its associated entity, capturing the version baseline for history tracking.
  • RESTORE_VERSION — Restores a prior version of an outcome argument, supporting revert functionality within the versioning model.

Tables Accessed

  • OKC_OUTCOME_ARGUMENTS — The primary entity table for outcome argument definitions; the package reads, inserts, updates, and deletes records here.
  • OKC_OUTCOME_ARGUMENTS_H — The history table capturing version snapshots of outcome arguments for audit and version restoration.
  • OKC_OUTCOME_ARGUMENTS_S1 — A sequence used to generate primary key values for new outcome argument rows (the object referenced by the search term okc_outcome_arguments_s1).
  • OKC_OUTCOME_ARGUMENTS_V — A view providing a join- or translation-enhanced read of outcome arguments for use in i18n and attribute display.
  • FND_APPLICATION and DUAL — Standard Oracle Application Object Library utility objects and PL/SQL pseudo-tables used for identity and control logic.
  • PLITBLM — The standard PL/SQL Internal Table of Long/Binary Messages used for dynamic SQL and error handling.

The package also references OKC_OUTCOMES_V, OKC_ACTION_ATTRIBUTES_V, OKC_PROCESS_DEFS_V, and OKC_PROCESS_DEF_PARAMETERS_V to resolve the outcome and process definition context in which arguments exist.

Usage Notes

OKC_OAT_PVT is not intended for direct invocation by custom code. It is called internally by OKC_API, OKC_VERSION_PVT, and related OKC packages during contract generation, copying, and upgrade operations. The presence of dependent packages such as FND_API, FND_GLOBAL, FND_PROFILE, and OKC_UTIL indicates adherence to the standard EBS API framework, including relational API savepoints, LOCK/UPDATE/DELETE row sequencing, and error stack propagation through FND_API.G_EXC_ERROR.

The upgrade-specific procedures (INSERT_ROW_UPG, CREATE_VERSION, RESTORE_VERSION) are typically executed by Oracle-supplied upgrade drivers during patch application from 12.1.1 to 12.2.2 or during internal version migrations. The object is referenced by ten other database packages, confirming its role as a shared internal dependency rather than a stand-alone interface. Customization should be avoided; any extension to outcome argument behavior should be pursued through supported OKC_API entry points.