Search Results okl_fod_pvt




Overview
Explore in AI Chat

Overview

OKL_FOD_PVT is a private (PVT classification) PL/SQL package body in the APPS schema that supports the Oracle Lease and Finance Management (OLFM) module of Oracle E-Business Suite. In ETRM terminology, the "FOD" component relates to formula and operand definitions, which are the building blocks used by the lease pricing and accounting engines to compute values such as interest rates, residual amounts, and payment streams. The OKL_FOD_PVT package provides the low-level, internal data manipulation and validation services that maintain the OKL_FMLA_OPRNDS records — the association between formulas and their operands.

Because this is a private package, its procedures are not intended for direct external invocation by customer code. Instead, it acts as the implementation layer behind a public API or a higher-level package that manages formula and operand configuration. The package is recorded as VALID and is widely reused: it is referenced by eight other packages, and it in turn depends on shared services including FND_API, FND_GLOBAL, OKC_API, OKC_P_UTIL, OKL_ACCOUNTING_UTIL, and OKL_FMLA_OPRNDS. This dependency profile confirms its role as a supporting utility embedded in the broader OLFM formula infrastructure rather than a standalone business service.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions. The central public operations are:

  • INSERT_ROW — creates a new formula/operand association record in the underlying table.
  • UPDATE_ROW — modifies an existing association record, applying the values supplied by the caller.
  • DELETE_ROW — removes an association record, typically after the parent formula or operand is retired.
  • LOCK_ROW — places a logical lock on a row to serialize concurrent maintenance of the same formula definition.
  • VALIDATE_ROW — performs the business-rule checks that must pass before insert, update, or delete is committed.
  • API_COPY — duplicates an existing formula/operand configuration, supporting versioning and template-based setup.
  • CHANGE_VERSION — advances the version identifier on a record, consistent with ETRM's versioning model for setup data.
  • LOAD_SEED_ROW — inserts the seed (reference) data rows that Oracle ships with the application, used during installation and patching.
  • QC — a query/check helper used to retrieve or verify a row before processing.

Together these procedures implement the standard Oracle object API pattern of insert, update, delete, lock, validate, copy, and seed load, with validation centralised in VALIDATE_ROW so that all maintenance paths enforce the same constraints.

Tables Accessed

The package reads and writes the APPS synonym OKL_FMLA_OPRNDS, which stores the mapping between formulas and the operands they consume. It also queries the OKL_FMLA_OPRNDS_V and OKL_FORMULAE_V views, together with OKL_OPERANDS_V, to present descriptive and validated data during row processing.

Standard Oracle infrastructure objects are referenced as well. DUAL is used for single-value lookups and sequence-style checks, while PLITBLM is the PL/SQL table type used internally for array handling. The dependency list also cites OKL_FMLA_OPRNDS directly and the PL/SQL and public synonyms required by the package. No tables outside the OLFM formula domain are touched.

Usage Notes

OKL_FOD_PVT is invoked indirectly. Configuration forms in the OLFM Setup responsibility for formula, variable, and operand definitions call the associated public API, which delegates row-level maintenance to this private package. Concurrent programs that load or upgrade formula seed data use LOAD_SEED_ROW, and patching or cloning operations rely on the same routine to install reference tuples.

Because the metadata shows no database object referencing OKL_FOD_PVT directly and eight packages calling into it, custom development should not call it directly; callers should use the supported public API instead. Custom code that must interact with formula operands should treat VALIDATE_ROW's rules as authoritative and expect LOCK_ROW to be used for concurrency control. This behaviour is consistent across EBS 12.1.1 and 12.2.2, where the OLFM formula architecture is unchanged.