Results for “bill_to_site_use_name”

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

Overview

The view APPS.OKL_SEC_INVESTORS_UV is a user interface view within the Oracle Leasing and Finance Management (OKL) module, part of the E-Business Suite 12.1.1 and 12.2.2 code lines. It presents securitization investor data by joining contract header, contract line, party role, status, and lookup information into a single denormalized row per investor–contract line relationship. Its name suffix _UV indicates a User interface View, and it is used primarily to drive the investor-related pages and inquiries in the OKL Securitization flow. Because it exposes both the coded value and the translated meaning for payout frequency and payout event, it is particularly relevant to searches such as pay_investor_event, since that column and its decoded meaning are surfaced directly by this view.

The view is owned by the APPS schema and is documented as VALID in the ETRM repository. It is not a transactional table; it is a read-only projection intended for reporting, form population, and integration queries that must show securitization investor terms in a business-friendly form.

Underlying Base Objects

The view is defined over a fixed set of documented base objects, joined on contract, party, status, and lookup keys:

• OKL_K_LINES (SYNONYM) — the OKL contract line extension table (aliased KLEB), supplying the securitization-specific attributes such as PAY_INVESTOR_EVENT, PAY_INVESTOR_FREQUENCY, PAY_INVESTOR_REMITTANCE_DAYS, AMOUNT, AMOUNT_STAKE, and DATE_PAY_INVESTOR_START.
• OKC_K_LINES_B (SYNONYM) — the core contract line table (CLEB), providing CHR_ID, line ID, status code, start date, bill-to site use, and customer account references.
• OKC_K_HEADERS_B (SYNONYM) — the contract header (KHRB), supplying the currency code.
• OKC_LINE_STYLES_B (SYNONYM) — restricts rows to line style INVESTMENT (LTY_CODE = 'INVESTMENT').
• OKC_STATUSES_B and OKC_STATUSES_TL (SYNONYMS) — supply the status code and its language-specific meaning.
• OKC_K_PARTY_ROLES_B (SYNONYM) — the party role table, filtered to RLE_CODE = 'INVESTOR'.
• OKX_PARTIES_V (VIEW) and OKX_CUST_SITE_USES_V (VIEW) — party and site name/description lookups.
• FND_LOOKUPS (VIEW) — used twice, once for the payout event (LOOKUP_TYPE = 'OKL_SEC_PAYOUT_EVENT') and once for frequency (LOOKUP_TYPE = 'OKL_FREQUENCY').
• HZ_CUST_ACCOUNTS (SYNONYM) — the Receivables customer account, joined via an outer join.
• ARP_ADDR_LABEL_PKG and FND_GLOBAL (PACKAGES) — supporting packages referenced in the compilation context.

Key Columns

• CHR_ID / TOP_LINE_ID — contract header identifier and top-level contract line identifier, the primary linkage keys.
• STS_CODE / STS_MEANING — status code and its translated meaning.
• K_ROLE_ID, NAME, ID1, ID2 — party role identifier and investor party name/identifiers.
• DATE_PAY_INVESTOR_START — the date on which investor payout begins.
• PAY_INVESTOR_FREQUENCY / PAY_INVESTOR_FREQUENCY_MEANING — frequency code and decoded meaning for investor payments.
• PAY_INVESTOR_EVENT / PAY_INVESTOR_EVENT_MEANING — the payout event code and its decoded meaning, looked up from OKL_SEC_PAYOUT_EVENT. This is the column directly associated with the pay_investor_event search term.
• PAY_INVESTOR_REMITTANCE_DAYS, AMOUNT, AMOUNT_STAKE — remittance lag in days and monetary amounts (total and stake portion).
• START_DATE, CURRENCY_CODE — contract line start date and contract currency.
• BILL_TO_SITE_USE_ID / BILL_TO_SITE_USE_NAME, CUST_ACCT_ID / CUST_ACCT_NO / CUST_ACCT_NAME — bill-to and customer account details.

Common Use Cases and Queries

The view is commonly queried to report securitization investor payment terms, to reconcile investor stake amounts, and to drive Pay Investor setup and inquiry forms. A typical query returns investor names alongside their payout event and frequency for a given contract:

• Investor payout schedule listing: SELECT CHR_ID, NAME, PAY_INVESTOR_EVENT_MEANING, PAY_INVESTOR_FREQUENCY_MEANING, DATE_PAY_INVESTOR_START, AMOUNT_STAKE FROM APPS.OKL_SEC_INVESTORS_UV WHERE CHR_ID = :p_chr_id;
• Filter by payout event: SELECT NAME, CHR_ID, PAY_INVESTOR_EVENT FROM APPS.OKL_SEC_INVESTORS_UV WHERE PAY_INVESTOR_EVENT = :p_event_code;
• Currency and stake reconciliation: SELECT CURRENCY_CODE, CUST_ACCT_NAME, SUM(AMOUNT_STAKE) FROM APPS.OKL_SEC_INVESTORS_UV GROUP BY CURRENCY_CODE, CUST_ACCT_NAME;

Because the underlying OKL_K_LINES record is joined to the core contract line and filtered to the INVESTMENT line style and the INVESTOR role, results are already scoped to securitization investors. No additional role filtering is required, and consumers should treat all columns as read-only projections.