Results for “fee_type_code”

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

Overview

The OKL_PYMTS_FEE_INSTS_UV view is a user-interface (UI) view owned by the APPS schema within the OKL – Lease and Finance Management product of Oracle E-Business Suite. Its documented purpose is to supply the Fee Line instance List of Values (LOV) rendered on the Payments Page of the Lease and Finance Management application. In EBS 12.1.1 and 12.2.2, the object is reported with a status of VALID and is defined as a VIEW over a combination of OKL, OKC, and FND foundation objects.

Because the view is designed explicitly for a UI LOV rather than for transactional processing, it materializes only a narrow slice of fee line data: the identifiers, descriptive attributes, and fee type code/meaning required to populate a selection list. The view enforces a lookup-type filter against OKL_FEE_TYPES and restricts results to a fixed set of fee type codes: MISCELLANEOUS, PASSTHROUGH, SECDEPOSIT, INCOME, FINANCED, and ROLLOVER. It also excludes fee lines whose status sits in HOLD, EXPIRED, TERMINATED, or CANCELLED, ensuring that only active, selectable fee lines are offered to the user. The search term "fee_type_code" corresponds directly to a column projected by this view, FEE_TYPE_CODE, which is sourced from the FND_LOOKUPS lookup code.

Underlying Base Objects

The documented base objects referenced by OKL_PYMTS_FEE_INSTS_UV are:

• FND_LOOKUPS (VIEW) — supplies the fee type lookup code and its meaning, filtered to lookup_type = 'OKL_FEE_TYPES'.
• OKC_K_ITEMS (SYNONYM) — the contract item association joining structured instrument types to contract lines.
• OKC_K_LINES_B (SYNONYM) — the base contract line table, providing LINE_ID and DNZ_CHR_ID.
• OKC_LINE_STYLES_B (SYNONYM) — line styles, filtered to LTY_CODE = 'FEE'.
• OKC_STATUSES_B (SYNONYM) — status codes and sub-status codes used to exclude held, expired, terminated, or cancelled lines.
• OKL_K_LINES (SYNONYM) — the OKL line extension carrying FEE_TYPE and the LSE_ID linkage.
• OKL_STRMTYP_SOURCE_V (VIEW) — provides the structured instrument/service type name and description.
• FND_GLOBAL (PACKAGE) — the standard EBS foundation package invoked in the runtime context (for example, for organization and user context).

The joins are driven from OKC_LINE_STYLES_B (LTY_CODE = 'FEE') through OKC_K_LINES_B, then correlated to OKL_K_LINES by ID, to OKC_K_ITEMS by JTOT_OBJECT1_CODE = 'OKL_STRMTYP', and finally to OKL_STRMTYP_SOURCE_V for the descriptive text. FND_LOOKUPS supplies the code-to-meaning translation.

Key Columns

• LINE_ID — Contract line identifier from OKC_K_LINES_B.ID; the primary selection key for the fee line instance.
• KHR_ID — The contract header identifier (DNZ_CHR_ID), linking the fee line to its parent lease/contract.
• LSE_ID — The lease identifier, joining the line to the OKL lease structure.
• SERVICE_INST_NAME — The structured instrument/service type name from OKL_STRMTYP_SOURCE_V, presented as the LOV display value.
• SERVICE_INST_DESC — The descriptive text associated with that structured instrument.
• FEE_TYPE_MEANING — The translated meaning of the fee type from FND_LOOKUPS; used for display alongside the code.
• FEE_TYPE_CODE — The lookup code (for example, MISCELLANEOUS, PASSTHROUGH) that drives fee type classification; this is the column most commonly filtered or joined by downstream queries.

Common Use Cases and Queries

Typical usage centres on retrieving the selectable fee line instances for a given lease and classifying them by fee type. A representative query filtered on the search term is:

• SELECT line_id, khr_id, lse_id, service_inst_name, fee_type_code, fee_type_meaning FROM apps.okl_pymts_fee_insts_uv WHERE fee_type_code = 'MISCELLANEOUS';
• SELECT line_id, service_inst_name, fee_type_code FROM apps.okl_pymts_fee_insts_uv WHERE khr_id = :p_contract_id ORDER BY service_inst_name;
• SELECT fee_type_code, COUNT(*) FROM apps.okl_pymts_fee_insts_uv GROUP BY fee_type_code;

The first two scenarios support LOV rendering and fee-line selection on the Payments Page and in custom extensions; the third supports reporting distributions across permitted fee types. Because the view embeds status and fee-type restrictions, consumers should treat it as a presented, filtered dataset rather than as a complete inventory of contract fee lines; queries requiring inactive or excluded lines must address OKC_K_LINES_B and OKL_K_LINES directly.