Results for “okc_subclasses”

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

Overview

OKL_BPD_AP_DISBURS_SMRY_UV is a read-only supplementary view owned by the APPS schema in Oracle E-Business Suite, registered in FND design data as OKL.OKL_BPD_AP_DISBURS_SMRY_UV. It belongs to the Oracle Lease and Finance Management (OKL/ETRM) product family and is documented as a "View TypeA" supplementary view whose stated purpose is to simplify forms coding. Oracle explicitly warns that this view should not be queried or modified directly, since its definition may change dramatically between minor or major releases.

The view presents a consolidated summary of accounts payable disbursements tied to investor agreements and lease contracts. It joins AP invoice and vendor data with OKL contract and transaction lines to expose, at the invoice grain, the investor identity, the source invoice details, the currency, and the subclass of the associated contract.

Underlying Base Objects

The view is defined over a mixture of AP, PO, and OKL objects. The documented dependencies are: AP_INVOICES_ALL (SYNONYM), FND_APPLICATION (SYNONYM), OKC_K_HEADERS_B (SYNONYM), OKL_ACCOUNTING_UTIL (PACKAGE), OKL_CNSLD_AP_INVS_ALL (SYNONYM), OKL_STRM_TYPE_V (VIEW), OKL_TRX_AP_INVOICES_V (VIEW), OKL_TXL_AP_INV_LNS_V (VIEW), and PO_VENDORS (VIEW).

• AP_INVOICES_ALL supplies the base invoice header records (invoice number, date, currency).
• PO_VENDORS resolves the supplier/investor name.
• OKC_K_HEADERS_B anchors the contract header, linking the invoice to a contract and its subclass.
• OKL_CNSLD_AP_INVS_ALL and the OKL transaction/invoice line views (OKL_TRX_AP_INVOICES_V, OKL_TXL_AP_INV_LNS_V) drive the consolidated investor disbursement amounts.
• OKL_STRM_TYPE_V and the OKL_ACCOUNTING_UTIL package carry stream type and accounting logic.
• FND_APPLICATION is referenced for application context.

Notably, the view is not referenced by any other database object — it is a leaf reporting construct.

Key Columns

• INVOICE_ID (NUMBER) — AP invoice identifier, the primary join key.
• INVESTOR_AGREEMENT (VARCHAR2 120) / INVESTOR_NAME (VARCHAR2 240) — the agreement and vendor/investor identity.
• INVOICE_NUMBER (VARCHAR2 240), INVOICE_CURRENCY_CODE (VARCHAR2 15), and INVOICE_DATE (DATE, "Date of the invoice") — core invoice attributes.
• ORG_ID (NUMBER) — Operating Unit Identifier, essential for multi-org security.
• INVESTOR_AMOUNT and TOTAL_TRANSACTION_AMOUNT (both VARCHAR2 4000) — aggregated amounts exposed as character strings.
• SCS_CODE (VARCHAR2 30) — "Indicates subclass of the Contract. Refers to code in okc_subclasses." This column is directly why the search term okc_subclasses surfaces this view; SCS_CODE maps to the subclass lookup populated by OKC_SUBCLASSES.

Common Use Cases and Queries

Because it summarizes investor disbursements in a single, denormalized row set, the view supports operational reporting on lease investor payouts and subclass analysis. A typical query, respecting the ORG_ID for multi-org filtering, is:

SELECT invoice_id, investor_name, invoice_number,
invoice_currency_code, invoice_date, org_id,
investor_amount, total_transaction_amount, scs_code
FROM apps.okl_bpd_ap_disburs_smry_uv
WHERE org_id = :p_org_id
AND scs_code = :p_subclass;

Common scenarios include reconciliation of investor disbursements against AP invoices, grouping totals by SCS_CODE to compare contract subclasses, and validating amounts against OKC_K_HEADERS_B subclasses via the OKC_SUBCLASSES lookup. Where rigorous summing is required, the VARCHAR2 amount columns should be cast to NUMBER. Given Oracle's advisory against direct querying, supported form or reporting interfaces are preferable for production use, and any dependency on this view should be treated as version-sensitive across 12.1.1 and 12.2.2.