Results for “fee_purpose_code”

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

Overview

OKL_K_FEE_LINES_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management module. The view carries a VALID status in the ETRM data dictionary and is documented as the "user interface view for fee lines." Its purpose is to consolidate the discrete data elements required to render and process fee line information within the Lease and Finance Management application, exposing a flattened, denormalized projection of fee lines together with their associated contract line, item, party role, and lookup attributes.

Because the object name contains the suffix "_UV", it is understood to be a user-facing view rather than a purely internal technical construct. It presents business-meaningful labels, such as the FNDV.MEANING column sourced from FND_LOOKUPS, alongside raw identifiers, allowing forms, OAF pages, or concurrent programs to display a fee line with its human-readable fee type. The inclusion of the PARTY_RLE_CODE column, which is central to how the view surfaces party role information, makes it directly relevant to users who search on "party_rle_code."

Underlying Base Objects

The ETRM metadata for release 12.2.2 lists the following referenced base objects for APPS.OKL_K_FEE_LINES_UV: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), OKC_K_HEADERS_B (SYNONYM), OKC_K_ITEMS (SYNONYM), OKC_K_LINES_B (SYNONYM), OKC_K_PARTY_ROLES_B (SYNONYM), OKC_LINE_STYLES_B (SYNONYM), OKL_K_HEADERS (SYNONYM), and OKL_K_LINES (SYNONYM).

The view text confirms that the principal driving table is OKC_K_LINES_B, aliased CLEB, which supplies the core line identity and status columns such as LINE_ID, CLE_ID, STS_CODE, LINE_NUMBER, and DISPLAY_SEQUENCE. The OKL_K_LINES table, aliased KLEB, is joined to provide the OKL-specific fee attributes, including FEE_TYPE, FEE_PURPOSE_CODE, AMOUNT, CAPITAL_AMOUNT, and the ATTRIBUTE1 through ATTRIBUTE15 flexfield columns. OKC_LINE_STYLES_B (LSEB) contributes the line style and line type (LTY_CODE), OKC_K_ITEMS (ITEM) provides item-level identifiers, and OKC_K_PARTY_ROLES_B (CPLB) supplies the party role data, including the RLE_CODE column that is surfaced as PARTY_RLE_CODE. FND_LOOKUPS (FNDV) provides the lookup meaning for the fee type. OKC_K_HEADERS_B, OKL_K_HEADERS, and FND_GLOBAL are documented as referenced objects and are used within the view's join structure and function references.

Key Columns

The view exposes a broad set of columns organized by functional area. Fee header attributes include FEE_TYPE and the derived MEANING label, along with FEE_PURPOSE_CODE. Line-level attributes include LINE_ID, LINE_CLE_ID, LINE_STS_CODE, LINE_CURRENCY_CODE, LINE_LINE_NUMBER, LINE_DISPLAY_SEQUENCE, LINE_LSE_ID, LINE_START_DATE, and LINE_END_DATE. Financial values are presented as LINE_AMOUNT and LINE_CAPITAL_AMOUNT.

Item-related columns include ITEM_ID, ITEM_CLE_ID, ITEM_OBJECT1_ID1, ITEM_OBJECT1_ID2, ITEM_JTOT_OBJECT1_CODE, ITEM_UOM_CODE, ITEM_EXCEPTION_YN, and ITEM_NUMBER_OF_ITEMS. Line style and header context are represented by LS_LTY_CODE and LS_ID. Of particular interest given the search term, the party role block includes PARTY_ID, PARTY_RLE_CODE, PARTY_CLE_ID, PARTY_OBJECT1_ID1, PARTY_OBJECT1_ID2, and PARTY_JTOT_OBJECT1_CODE, mapping to the RLE_CODE of the associated party role record. The view also exposes CUST_ACCT_ID, QTE_ID, KHR_ID, placeholder columns ROLLOVER_QUOTE and CONTRACT_NUMBER, and the full ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 descriptive flexfield set from OKL_K_LINES.

Common Use Cases and Queries

Typical use cases include reporting on lease fee lines with their fee types, retrieving fee lines by party role, and building integration extracts that require both identifier and descriptive attributes. A representative query filtering on the party role code is shown below:

• SELECT fee_type, meaning, line_amount, party_rle_code, party_id, line_currency_code, line_sts_code FROM apps.okl_k_fee_lines_uv WHERE party_rle_code = '&role_code';
• SELECT line_id, line_number, fee_type, meaning, line_amount FROM apps.okl_k_fee_lines_uv WHERE line_cle_id = :cle_id ORDER BY line_display_sequence;
• SELECT party_id, party_rle_code, line_amount FROM apps.okl_k_fee_lines_uv WHERE fee_type = '&fee_type' AND line_sts_code = 'ACTIVE';

Because the view exposes descriptive columns such as MEANING and the DFF attributes, it is well suited to building BIPublisher or Oracle Reports data models and to OAF-based UI screens that must present fee lines in a single, queryable structure without requiring the developer to reassemble the underlying transactional tables manually.