Results for “okl_operands_v”

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

Overview

OKL_OPERANDS_V is a VALID Oracle EBS view owned by the APPS schema within the OKL - Leasing and Finance Management product (Oracle Lease and Finance Management). The view presents the operands required by the Formulae used in lease and finance calculations. In Oracle Lease Management, a formula is composed of operands (variables, constants, or derived values) that feed pricing, yield, and amortization computations. This view exposes those operand definitions in a language-specific, user-facing form, making it suitable for reporting, integration, and inquiry against the operand setup.

Because it is a view rather than a table, it provides no independent storage; it is a read-only projection intended for query and reporting purposes. It is commonly consumed by concurrent programs, custom reports, and integration extracts that need to enumerate the operands available to the formula engine without accessing the underlying partitioned base and translation tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• OKL_OPERANDS_B — the base (transaction) table holding the operand records, aliased as OPDB. It supplies identifying, versioning, and audit attributes.
• OKL_OPERANDS_TL — the translation table holding language-specific descriptive text, aliased as OPDT. It supplies the SFWT_FLAG and DESCRIPTION columns.

The join is OPDB.ID = OPDT.ID AND OPDT.LANGUAGE = USERENV('LANG'). This combines each operand's base record with its translation in the session's current language, ensuring that the returned DESCRIPTION reflects the user's language environment. The _B and _TL suffix conventions confirm the standard Oracle multi-language support (MLS) pattern.

Key Columns

• ROW_ID — the ROWID of the base-table row, useful for direct row addressing.
• ID — the primary identifier of the operand, used to join to related formula objects.
• OBJECT_VERSION_NUMBER — optimistic locking / version control column.
• SFWT_FLAG — the "Seed/Formulae Workbench Translation" indicator sourced from the translation table.
• FMA_ID — foreign key to the formula to which the operand belongs.
• DSF_ID — identifier linking the operand to its data source definition.
• NAME / DESCRIPTION — the operand's name and its language-specific description.
• VERSION, START_DATE, END_DATE — effective-dating and versioning of the operand definition.
• SOURCE — indicates the origin of the operand (e.g., seeded versus user-defined).
• OPD_TYPE — the operand type classification.
• ORG_ID — the operating unit (multi-org) discriminator.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include listing all operands belonging to a given formula, extracting operand metadata for integration, and auditing seeded versus user-defined operands within an operating unit.

To list operands for a specific formula:

• SELECT id, name, description, opd_type, source, version FROM okl_operands_v WHERE fma_id = :p_fma_id ORDER BY name;

To find seeded operands in an operating unit:

• SELECT id, name, description, start_date, end_date FROM okl_operands_v WHERE org_id = :p_org_id AND source = 'SEEDED' ORDER BY name;

Because the view resolves DESCRIPTION through OKL_OPERANDS_TL using USERENV('LANG'), reports automatically return descriptions in the session language, making it well suited for multilingual deployments on both EBS 12.1.1 and 12.2.2.