Results for “receipt_method_code”

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

Overview

OKL_SUBSIDIES_V is an entity view owned by the APPS schema within the OKL (Leasing and Finance Management) product of Oracle E-Business Suite. It is a VALID database object in both 12.1.1 and 12.2.2. The view presents the complete set of subsidy setup data maintained for leasing and finance agreements, exposing the header-level attributes stored in OKL_SUBSIDIES_B together with the translatable descriptive columns held in OKL_SUBSIDIES_TL. Because it consolidates the base and translation tables into a single denormalized row, it is the standard reporting and integration surface for subsidy configuration.

In the ETRM documentation, the object is described as an entity view whose purpose is to return all subsidy setup data. This makes it the appropriate source for operational reports, subsidy validation queries, and outbound interfaces that need to read subsidy definitions without joining multiple tables. It also underpins the OAF-based maintenance pages that display subsidy records to end users.

Underlying Base Objects

The view is defined over two documented base objects:

• OKL_SUBSIDIES_B — the base table holding subsidy header attributes, prefixed as SUBB in the view text. This supplies the identifying and business columns such as ID, ORG_ID, NAME, currency, calculation basis, amounts, dates, formula references, and the descriptive flexfield attributes.
• OKL_SUBSIDIES_TL — the translation table, prefixed as SUBT, which supplies SHORT_DESCRIPTION, DESCRIPTION, and the SFWT_FLAG. A join between the two on the subsidy ID and language columns produces the fully described subsidy row.

Both base tables are referenced as SYNONYMs in the documented metadata, meaning the view resolves them through the APPS synonyms. The view also preserves a ROW_ID derived from the base table ROWID and the OBJECT_VERSION_NUMBER for optimistic locking during DML.

Key Columns

The view exposes an extensive column list. Notable columns include:

• ID and ORG_ID — the primary identifier and operating unit of the subsidy.
• NAME, SHORT_DESCRIPTION, DESCRIPTION — the descriptive identity of the subsidy, the latter two sourced from the translation table.
• EFFECTIVE_FROM_DATE / EFFECTIVE_TO_DATE — the active date range, complemented by EXPIRE_AFTER_DAYS.
• CURRENCY_CODE, AMOUNT, PERCENT, RATE_POINTS — the calculation inputs, governed by SUBSIDY_CALC_BASIS.
• FORMULA_ID — the primary calculation formula reference.
• REFUND_FORMULA_ID — the formula applied when a refund is calculated, tied to TERMINATION_REFUND_BASIS. This is the column most relevant to users searching for refund formula configuration.
• TERMINATION_REFUND_BASIS, RECOURSE_YN, ACCOUNTING_METHOD_CODE — termination and accounting treatment attributes.
• VENDOR_ID, STREAM_TYPE_ID, RECEIPT_METHOD_CODE, TRANSFER_BASIS_CODE — operational links.
• MAXIMUM_TERM, MAXIMUM_FINANCED_AMOUNT, MAXIMUM_SUBSIDY_AMOUNT — cap constraints.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield content.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns.

Common Use Cases and Queries

The view is typically queried to list active subsidies, to inspect calculation configuration, or to trace which subsidies reference a given refund formula. A representative query returns active subsidies for an operating unit filtered by effective dates:

• SELECT id, name, currency_code, subsidy_calc_basis, amount, percent FROM okl_subsidies_v WHERE org_id = :org_id AND sysdate BETWEEN effective_from_date AND NVL(effective_to_date, sysdate + 1);
• SELECT id, name, refund_formula_id, termination_refund_basis FROM okl_subsidies_v WHERE refund_formula_id IS NOT NULL; — isolates subsidies configured with a refund formula.
• SELECT name, formula_id, refund_formula_id FROM okl_subsidies_v WHERE formula_id = :formula_id OR refund_formula_id = :formula_id; — reverses the relationship to find subsidies using a particular formula.

These patterns support subsidy auditing, formula impact analysis, and reconciliation of setup data prior to contract origination.