Results for “okc_oce_pvt”

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

Overview

OKC_OCE_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, residing in the APPS schema. The suffix "PVT" indicates that the package contains internal implementation logic intended to be invoked by other packages rather than being called directly from forms, concurrent programs, or customer code. The package governs the "Outcome" entity within the Contracts Core schema, as evidenced by its global record type oce_rec_type and its primary dependency on the OKC_OUTCOMES_B, OKC_OUTCOMES_TL, OKC_OUTCOMES_BH, and OKC_OUTCOMES_TLH tables.

Within the Contracts application, outcomes represent the results or deliverables associated with a contract line, such as fulfillment of a term, condition, or entitlement. The package maintains the full lifecycle of these outcome records, including multilingual translation rows, versioning, row-level locking, and upgrade-specific data handling. In the context of Oracle EBS 12.1.1 and 12.2.2, the package remains structurally consistent, though the file header reflects an original creation around the 11.5.10 era (version 120.0, dated 2005). The "OCARA team" reference likely aligns with internal Oracle development or support naming conventions for the Contracts (OKC) and related AP/AR functional groups, as OKC_OCE_PVT is widely catalogued in ETRM documentation under that team's scope.

Key Procedures and Functions

The documented API surface of OKC_OCE_PVT comprises 17 procedures and functions, the majority of which follow the standard Oracle EBS Private API convention for CRUD and multi-language operations:

• QC — Quality control/consistency check routine used to validate internal invariants before or after data operations.
• CHANGE_VERSION — Alters the version number of an outcome record, supporting the Contracts versioning framework.
• API_COPY — Copies outcome data from one record context to another, typically used in duplication or cloning scenarios.
• ADD_LANGUAGE — Inserts translation rows into the _TL table for additional installed languages.
• INSERT_ROW — Inserts a new outcome record into OKC_OUTCOMES_B and corresponding translation rows.
• LOCK_ROW — Acquires a row-level lock to prevent concurrent modification.
• UPDATE_ROW — Updates an existing outcome record.
• DELETE_ROW — Deletes an outcome record and its dependent translation rows.
• VALIDATE_ROW — Applies business-rule validation before persistence.
• INSERT_ROW_UPG — Upgrade-specific insertion path used during patch or upgrade processing.
• CREATE_VERSION — Creates a new version of an existing outcome.
• RESTORE_VERSION — Restores a record to a prior version state.

Tables Accessed

The package operates primarily on the Contract Outcomes tables:

• OKC_OUTCOMES_B — Base table storing outcome definitions and the ENABLED_YN flag, object_version_number, WHO columns, and DFF attributes (attribute_category, attribute1 through attribute15).
• OKC_OUTCOMES_TL — Translation table holding language-specific descriptions.
• OKC_OUTCOMES_BH and OKC_OUTCOMES_TLH — History tables supporting versioning and audit of the base and translated rows.
• OKC_OUTCOMES_S1 — A secondary index or seed table used by the outcome setup.
• FND_APPLICATION and FND_LANGUAGES — Oracle Application Object Library lookups to resolve application identifiers and installed language codes during language-row insertion.
• DUAL and PLITBLM — Utility references; PLITBLM is a standard PL/SQL index-by table type used internally.

Usage Notes

Because OKC_OCE_PVT is a Private package, it should not be called directly by customer extensions. Its documented procedures are referenced by 10 other packages, which act as the public interface (for example, corresponding OKC_OCE_GRP or OKC_API packages) that Forms, concurrent programs, and OAF pages invoke. Multi-language support requires that ADD_LANGUAGE be paired with INSERT_ROW, and callers should honor LOCK_ROW before UPDATE_ROW or DELETE_ROW in concurrent sessions. The presence of INSERT_ROW_UPG indicates use during Oracle Applications upgrade or patch application, where direct table DML must respect the same validation and versioning logic. Custom integrators extending Contracts Outcome functionality should call the public wrappers rather than OKC_OCE_PVT predicates to preserve supportability across 12.1.1 and 12.2.2.