Results for “opd_type”

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

Overview

OKL_OPERANDS_B is a core configuration table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its documented description is "Operands required by the Formulae," identifying it as the repository that stores the individual operand definitions — the variable inputs, constants, or data-source references — that Oracle Leasing formulae consume when computing values such as payment amounts, residual values, interest calculations, and amortization schedules. Because leasing calculations are essentially rule-driven expressions, the operand records held here supply the operands that the formula engine resolves at runtime against a contract's terms and attributes.

The table resides in the OKL schema and is marked VALID in both the 12.1.1 and 12.2.2 releases. It carries 17 documented columns in the 12.2.2 physical schema and is scoped by the ORG_ID and ZD_EDITION_NAME columns, consistent with EBS Multi-Org access control and the editioning (ZD_EDITION_NAME) pattern applied to upgrade-safe tables. The primary key is OKL_OPERANDS_B_PK on the ID column.

From the heuristic Data Vault classification derived from the foreign-key structure, OKL_OPERANDS_B is satellite-leaning. In Data Vault modeling terms this suggests the table behaves primarily as a descriptive, attribute-bearing satellite attached to one or more parent hubs — in this case the formula hub (OKL_FORMULAE_B) and the data-source function hub (OKL_DATA_SRC_FNCTNS_B). It is not a pure reference hub, since it carries descriptive and linkage attributes rather than acting solely as a business-key registry.

Key Information Stored

The most significant columns documented for OKL_OPERANDS_B include:

• ID — surrogate primary key (OKL_OPERANDS_B_PK), uniquely identifying each operand row.
• NAME — the operand name; a documented business-key candidate via the unique index OKL_OPD_U2 (NAME, VERSION, ZD_EDITION_NAME).
• VERSION — version discriminator, part of the same business-key candidate.
• FMA_ID — foreign key to OKL_FORMULAE_B, tying the operand to its parent formula.
• DSF_ID — foreign key to OKL_DATA_SRC_FNCTNS_B, identifying the data-source function that supplies the operand value.
• OPD_TYPE — the operand type or category, distinguishing how the operand is resolved or used.
• ORG_ID — operating unit / Multi-Org identifier.
• START_DATE and END_DATE — effective dating for the operand definition.
• SOURCE — origin indicator for the operand record.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ZD_EDITION_NAME — editioning column, part of both unique indexes (OKL_OPD_U2 and OKL_OPERANDS_B_U1).

The unique index OKL_OPERANDS_B_U1 (ID, ZD_EDITION_NAME) supports the editioning model, while OKL_OPD_U2 (NAME, VERSION, ZD_EDITION_NAME) is the candidate natural business key.

Common Use Cases and Queries

Typical reporting scenarios include listing all operands belonging to a given formula, tracing which data-source function supplies a particular operand, and auditing the effective dates of operand definitions. A representative query joins operands to their parent formula:

SELECT o.ID, o.NAME, o.OPD_TYPE, o.START_DATE, o.END_DATE
FROM OKL.OKL_OPERANDS_B o, OKL.OKL_FORMULAE_B f
WHERE o.FMA_ID = f.ID AND o.NAME = :operand_name;

To resolve the source function for an operand, join through DSF_ID to OKL_DATA_SRC_FNCTNS_B. Because the table is build/scratch-oriented configuration data, queries should generally filter on ORG_ID and use NVL(END_DATE, SYSDATE) checks for currently active records.

Related Objects

• OKL_FORMULAE_B — parent formula table; joined via FMA_ID = OKL_FORMULAE_B.ID.
• OKL_DATA_SRC_FNCTNS_B — data-source function table; joined via DSF_ID = OKL_DATA_SRC_FNCTNS_B.ID.
• OKL_FMLA_OPRNDS — mapping table that references operands via OKL_FMLA_OPRNDS.OPD_ID = OKL_OPERANDS_B.ID.

These three objects form the immediate dependency neighborhood for formula and operand configuration in the Leasing module.