Search Results frequency_code




Overview
Explore in AI Chat

Overview

OKL_CS_PPD_PAYMENTS_UV is a reporting view owned by the APPS schema within the Oracle Leasing and Finance Management (OKL) module. It presents a flattened, denormalized projection of planned payment and cash flow data associated with lease and financial asset contracts, joining cash flow headers, cash flow levels, stream types, contract header and line information, and frequency lookups into a single queryable structure. The _UV suffix identifies it as a user-facing validation or presentation view, intended to be consumed by concurrent programs, Oracle Reports, Business Intelligence Publisher layouts, and integration extracts rather than by transactional forms. In Oracle EBS 12.1.1 and 12.2.2, this view supports forecast-style reporting where payment schedules must be displayed in a human-readable form — most notably by resolving coded values such as FREQUENCY_CODE into descriptive meanings through the FND_LOOKUPS table.

Underlying Base Objects

The view is defined over a mix of OKL transactional tables, OKC contract objects, and an FND lookup view:

FND_GLOBAL is referenced by the underlying objects for session context rather than by this view directly.

Key Columns

  • REQUEST_ID — the source ID from OKL_CASH_FLOW_OBJECTS, typically the concurrent request or source transaction identifier.
  • DNZ_KHR_ID — the contract header ID linking the cash flow to its lease or finance agreement.
  • KLE_ID — the base source (contract line) identifier; the result set is ordered by this column first.
  • ASSET — the descriptive asset or line name.
  • STREAM_TYPE — the decoded stream type code, used for ordering and categorization.
  • FREQUENCY_CODE — the raw frequency code from OKL_CASH_FLOW_LEVELS (for example, monthly, quarterly, annual). This is the column most frequently searched, as it drives grouping and cycle analysis.
  • FREQUENCY — the FND lookup meaning corresponding to the frequency code, suitable for direct display.
  • ARREARS — indicates whether payments are due in arrears; NULL implies advance.
  • NUMBER_OF_PERIODS, AMOUNT, STUB_DAYS, STUB_AMOUNT — the schedule shape and monetary detail.
  • START_DATE — the commencement date of the payment schedule.
  • ADVANCE_PAYMENTS — the number of advance periods.
  • CURRENCY_CODE — contract currency, drawn from OKC_K_HEADERS_B.

Common Use Cases and Queries

The view is most often used to produce payment schedules, verify frequency assignments, and reconcile stub periods during conversion or audit. Because FREQUENCY and ASSET are resolved inline, no additional joins are required for display reports.

Identify schedules by frequency:

SELECT kle_id, asset, stream_type, frequency_code, frequency,
       number_of_periods, amount, start_date
  FROM apps.okl_cs_ppd_payments_uv
 WHERE frequency_code = 'MONTHLY'
 ORDER BY kle_id, start_date;

Summarize planned payments per contract line:

SELECT kle_id, stream_type, frequency, sum(amount)
  FROM apps.okl_cs_ppd_payments_uv
 GROUP BY kle_id, stream_type, frequency;

Audit frequency codes that fail to resolve to a lookup meaning:

SELECT DISTINCT frequency_code
  FROM apps.okl_cs_ppd_payments_uv
 WHERE frequency IS NULL;

These patterns support lease schedule validation, cash forecasting, and migration reconciliation within the OKL module on both EBS 12.1.1 and 12.2.2.