Results for “okl_sec_payout_event”

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

Overview

APPS.OKL_SEC_INVESTORS_UV is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Lease and Finance Management (OKL) module — also referenced as the Enterprise Contracts and Telesales/Contract Terms Management (ETRM) stack. The view consolidates contractual and party information related to investors participating in securitization contracts. Its defining purpose is to expose, in a single denormalized SELECT, the linkage between an investor party and the underlying lease funding line, including the payout schedule, remittance terms, and currency parameters that govern how investor distributions are calculated under a securitization arrangement.

The object is exposed under the APPS schema and is primarily consumed in reporting, inquiries, and integration extracts rather than by direct transactional entry. It is especially relevant when investigating investor payout configurations, since it resolves the payout event code against the OKL_SEC_PAYOUT_EVENT lookup and the payment frequency against the OKL_FREQUENCY lookup.

Underlying Base Objects

The view is defined over a mix of operational OKC/OKL contract tables, reference views, and lookup views. The documented base objects include: OKL_K_LINES (the lease line carrying investor terms), OKC_K_LINES_B (the contract line), OKC_K_HEADERS_B (the contract header), OKC_STATUSES_B and OKC_STATUSES_TL (status code and its translated meaning), OKC_LINE_STYLES_B (line style, filtered to 'INVESTMENT'), OKC_K_PARTY_ROLES_B (party roles), OKX_PARTIES_V (party master), FND_LOOKUPS (twice, for payout event and frequency), HZ_CUST_ACCOUNTS (customer account), and OKX_CUST_SITE_USES_V (bill-to site). Supporting packages ARP_ADDR_LABEL_PKG and FND_GLOBAL are referenced for address labels and the USERENV session language.

Joins connect the contract header (KHRB.ID = CLEB.DNZ_CHR_ID) to the contract line, which further links to the lease line via CLEB.ID = KLEB.ID. Investor identity is resolved by pairing OKX_PARTIES_V to OKC_K_PARTY_ROLES_B on object1_id1/id2 where the role code is 'INVESTOR' and the object code is 'OKX_PARTY'. The line style filter (lty_code = 'INVESTMENT') restricts output to investment-type contract lines. Bill-to and customer account joins are outer joins, so lines without a bill-to site or customer account still appear.

Key Columns

• chr_id / top_line_id — Contract header (DNZ_CHR_ID) and the top contract line identifier.
• sts_code, ste_code, sts_meaning — Contract line status code, status-code extension, and the language-dependent status meaning.
• k_role_id, name, description, id1, id2 — Party role identifier and investor party attributes resolved from OKX_PARTIES_V.
• date_pay_investor_start, pay_investor_frequency, pay_investor_frequency_meaning — Start date for investor payments, the frequency lookup code, and its FND_LOOKUPS meaning.
• pay_investor_event, pay_investor_event_meaning — Payout event code and its decoded meaning from the OKL_SEC_PAYOUT_EVENT lookup; this is the value most closely tied to the search term okl_sec_payout_event.
• pay_investor_remittance_days — Number of remittance days applied to investor disbursements.
• amount, amount_stake, currency_code — Payout amount, stake amount, and the contract header 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 identifiers and descriptive names.

Common Use Cases and Queries

Typical reporting scenarios include listing all investors per securitization contract, reviewing payout events and frequencies for audit, and extracting investor remittance schedules for treasury or finance reconciliation. The view is also useful in diagnosing configuration errors where a payout event or frequency code is missing from its lookup.

A representative query retrieves investor payout configuration for a contract:

• SELECT chr_id, top_line_id, name, pay_investor_event_meaning, pay_investor_frequency_meaning, date_pay_investor_start FROM apps.okl_sec_investors_uv WHERE chr_id = :contract_id;
• SELECT name, amount, amount_stake, currency_code FROM apps.okl_sec_investors_uv WHERE pay_investor_event = :event_code;

Because the view joins translated status and lookup views, results are returned in the session language as resolved via USERENV('LANG').