Search Results okc_rld_pvt




Overview
Explore in AI Chat

Overview

OKC_RLD_PVT is a private (PVT-classified) PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the Contracts (OKC) module family. Its name follows the OKC_RLD convention associated with rule definitions, and the dependency metadata confirms this: the package operates directly against the OKC_RULE_DEFS_B, OKC_RULE_DEFS_TL, and OKC_RULE_DEFS_V objects, which store the base, translated, and validated representations of contract rule definitions. Rather than exposing a public API surface, OKC_RLD_PVT functions as the internal implementation layer that encapsulates the low-level row manipulation, concurrency control, and multi-language maintenance logic required to persist and retrieve contract rules and their associated descriptive flexfield (DFF) metadata.

The package is declared VALID in the ETRM repository for both 12.1.1 and 12.2.2, and its dependency graph shows it straddling two concerns: core contract rule data management and Oracle Application Object Library infrastructure such as FND_API, FND_DESCRIPTIVE_FLEXS, and FND_LANGUAGES. This positioning makes it a foundational utility rather than a standalone business service.

Key Procedures and Functions

The documented interface comprises 21 procedures and functions, of which the following are explicitly catalogued. The CRUD family — INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW — provides the primitive persistence operations against the rule definition tables, with LOCK_ROW supplying the standard SELECT ... FOR UPDATE concurrency guard used throughout EBS private packages. VALIDATE_ROW enforces the business and column-level integrity rules a rule definition must satisfy before it can be saved.

ADD_LANGUAGE manages the translation rows held in OKC_RULE_DEFS_TL, ensuring that non-base languages are created or maintained consistently with the base record. API_COPY performs rule definition duplication, supporting the common Contracts requirement of cloning a rule set when copying a contract. CHANGE_VERSION participates in the versioning model, allowing the package to create a new revision of an existing rule definition when version-controlled edits occur. QC is an internal quality-check routine, typically used to assert data consistency after a write operation.

The remaining documented utilities, GET_APPL_ID and GET_DFF_NAME, resolve descriptive flexfield configuration metadata — the application identifier and the DFF name — from the FND_DESCRIPTIVE_FLEXS and FND_DESCR_FLEX_CONTEXTS foundation tables, allowing OKC_RLD_PVT to attach and validate DFF segments when rule definitions are created or updated.

Tables Accessed

The primary data tables are OKC_RULE_DEFS_B (base, language-independent columns), OKC_RULE_DEFS_TL (translated columns), and the view OKC_RULE_DEFS_V, which exposes the joined result for read access. Oracle Applications foundation tables referenced through APPS synonyms include FND_APPLICATION, used to validate the owning application; FND_DESCRIPTIVE_FLEXS and FND_DESCR_FLEX_CONTEXTS, used to resolve DFF definitions and context information; FND_LANGUAGES, used by ADD_LANGUAGE to determine installed and base languages; and PLITBLM, the standard PL/SQL integer-table utility. The package also calls FND_API for its standard return-status conventions and OKC_API for shared contract business logic, reinforcing its role as an internal collaborator within the OKC code base.

Usage Notes

OKC_RLD_PVT is not intended for direct invocation by end users or external integrations. It is referenced by seven other packages — OKC_COPY_CONTRACT_PVT, OKC_QA_DATA_INTEGRITY, OKC_RDS_PVT, OKC_RULE_PUB, OKC_RULE_PVT, OKC_RUL_PVT, and OKC_TIME_UTIL_PVT — and it also references itself, indicating internal recursive or helper-call patterns. Forms-based maintenance of contract rules, contract copy operations, and rule-set creation flows within the Contracts workbench ultimately reach this package through the public OKC_RULE_PUB and OKC_RULE_PVT wrappers. The presence of OKC_QA_DATA_INTEGRITY in the caller list shows it is additionally exercised by data-integrity diagnostic programs. Customizations should route through the public OKC packages rather than calling OKC_RLD_PVT directly, since private packages offer no guarantee of interface stability across patches or upgrades.