Results for “okl_fmla_oprnds”

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

Overview

OKL_FMLA_OPRNDS is a transactional association table within the OKL (Leasing and Finance Management) module of Oracle E-Business Suite, validated in both 12.1.1 and 12.2.2. Its documented description, "Association of Formulae and Operands," identifies its role as the resolution layer that binds individual operands to the formulae in which they participate. In leasing calculation and pricing logic, formulae are composed trees whose leaves are operands; OKL_FMLA_OPRNDS records which operand occupies which position or label inside a given formula, enabling the calculation engine to evaluate a formula deterministically at contract, quote, or stream generation time.

From a Data Vault modeling perspective, the heuristic classification of this object is link. The classification is derived from its foreign key topology: the table carries the composite business key (OPD_ID, FMA_ID) which joins two independent hubs, OKL_OPERANDS_B and OKL_FORMULAE_B. This suggests a many-to-many resolution between operands and formulae, with the LINK, LABEL, and edition columns acting as descriptive attributes that could alternatively be modeled as a satellite on that link. The table is not a hub, since it owns no independent business entity of its own.

Key Information Stored

The following columns represent the substantive data content of the table; the remaining documented columns are standard EBS WHO-column audit and multi-tenant edition columns.

• ID — Surrogate primary key of the row, enforced by UK index OKL_FMLA_OPRNDS_U1 (with ZD_EDITION_NAME). Not a business identifier; used for row-level joins and concurrency.
• OPD_ID — Foreign key to OKL_OPERANDS_B. Identifies the operand assigned to the formula. Part of the business key.
• FMA_ID — Foreign key to OKL_FORMULAE_B. Identifies the parent formula. Part of the business key.
• (OPD_ID, FMA_ID) — The documented unique index OKL_FMLA_OPRNDS_U2 defines this pair, under edition, as the natural business key and enforces that a given operand appears at most once per formula per edition.
• LABEL — The symbolic name or position label by which the operand is referenced inside the formula expression. Unique index OKL_FOD_U3 (FMA_ID, LABEL, ZD_EDITION_NAME) enforces label uniqueness within a formula, preventing ambiguous operand references.
• OBJECT_VERSION_NUMBER — Optimistic locking token maintained by the ORM layer.
• ZD_EDITION_NAME — Editioning column supporting online patching in 12.2.x; participates in all three unique indexes and is the key mechanism allowing pre-patch, post-patch, and runtime editions to coexist.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard audit columns capturing creation and last modification context.

Common Use Cases and Queries

The primary use case is formula introspection and validation — resolving the complete operand set for a formula, or the reverse, finding every formula that consumes a given operand before that operand is modified or retired. Typical patterns include:

• Operands of a formula: SELECT OPD_ID, LABEL FROM OKL_FMLA_OPRNDS WHERE FMA_ID = :p_fma_id AND (ZD_EDITION_NAME = :edition) ORDER BY LABEL;
• Formulae referencing an operand: SELECT FMA_ID FROM OKL_FMLA_OPRNDS WHERE OPD_ID = :p_opd_id; — useful as an impact query before retiring or editing operands in OKL_OPERANDS_B.
• Duplicate label detection: aggregate on (FMA_ID, LABEL) to detect data anomalies where OKL_FOD_U3 was bypassed by direct DML.
• Formula expansion reporting: join to OKL_FORMULAE_B and OKL_OPERANDS_B to produce a flattened formula-to-operand dictionary for audit or documentation purposes.
• Edition-aware queries: any query executed during online patching must include ZD_EDITION_NAME or use AD_ZD views to avoid cross-edition row duplication.

Because this is an association table, reports should never aggregate it directly without joining to the hubs; the numeric meaning resides in OKL_OPERANDS_B and OKL_FORMULAE_B.

Related Objects

• OKL_FORMULAE_B — Referenced via OKL_FMLA_OPRNDS.FMA_ID; the parent formula definition (hub).
• OKL_OPERANDS_B — Referenced via OKL_FMLA_OPRNDS.OPD_ID; the operand definition (hub).
• OKL_FORMULAE_TL — Translation table providing user-facing formula names and descriptions.
• OKL_OPERANDS_TL — Translation table for operand names.
• OKL_FMLA_DTLS — Related formula detail structure used by the calculation engine; joins on formula identity rather than through this table.
• OKL_K_* contract objects — Stream and pricing tables that ultimately consume evaluated formulae and therefore depend transitively on this association.
• OKL_OKC_API / OKL_FMLA API — Public APIs that insert, update, and delete operand-to-formula associations; direct DML is discouraged because these APIs enforce label uniqueness and edition context.

In summary, OKL_FMLA_OPRNDS is the structurally critical but functionally silent link that allows Oracle Leasing and Finance Management formulae to be composed from reusable operands. Its business value is realized only through its two parent hubs, which is why it is classified heuristically as a link rather than a hub or satellite.