Results for “next_payment_date”

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

Overview

OKL_CS_PRINCIPAL_PAYDOWN_UV is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema within the OKL – Leasing and Finance Management module. Its documented purpose is to present a list of principal paydown requests associated with lease and finance contracts. The "UV" suffix conventionally denotes a user-facing or validation view intended for inquiry, reporting, and integration rather than for direct transactional update.

The view consolidates core request data from OKL_TRX_REQUESTS together with decoded lookup meanings and user identity information, producing a single denormalized result set suitable for concurrent programs, OAF/Forms inquiry pages, BI Publisher reports, and inbound/outbound interface logic. Because it joins transactional request rows to FND_LOOKUPS and FND_USER, it delivers both machine codes (e.g., REQUEST_STATUS_CODE, REQUEST_TYPE_CODE) and human-readable equivalents (REQUEST_STATUS, REQUEST_TYPE, REQUESTED_BY) without requiring downstream consumers to perform their own decoding. The view is documented as VALID and is available under the same definition across EBS 12.1.1 and 12.2.2, which supports migration and cross-release reporting consistency.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_TRX_REQUESTS (SYNONYM) — the primary transactional source, aliased TRQ, supplying request header, amount, currency, payment, status, and principal-balance columns.
• FND_USER (SYNONYM) — aliased USR, joined on TRQ.CREATED_BY = USR.USER_ID to resolve the user name exposed as REQUESTED_BY.
• FND_LOOKUPS (VIEW) — joined twice, aliased TYPE and STAT, to translate REQUEST_TYPE_CODE and REQUEST_STATUS_CODE into their display meanings.
• FND_GLOBAL (PACKAGE) — referenced by the view definition, typically for session context established by FND_GLOBAL.USER_ID and related calls used in the runtime SQL predicate context.

The relationship is essentially a star-style lookup join: OKL_TRX_REQUESTS is the fact source, while the two FND_LOOKUPS aliases and FND_USER provide dimensional decoding. Users searching by "requested_by" should note that this attribute is not stored on the base request table but is derived through the CREATED_BY join to FND_USER.USER_NAME.

Key Columns

• REQUEST_NUMBER / REQUEST_ID — the externally visible request identifier and the internal primary key.
• REQUEST_STATUS_CODE / REQUEST_STATUS — coded status and its OKL_REQUEST_STATUS lookup meaning.
• REQUEST_TYPE_CODE / REQUEST_TYPE — coded type and its OKL_REQUEST_TYPE lookup meaning.
• REQUESTED_BY — the FND_USER.USER_NAME of the user who created the request; this is the column targeted by the "requested_by" search.
• CREATED_BY — the numeric FND_USER.USER_ID behind REQUESTED_BY.
• REQUEST_DATE — mapped to TRQ.LAST_UPDATE_DATE, reflecting the last update of the request row.
• AMOUNT (RENT), CURRENCY_CODE, PAYMENT_DATE, PAYMENT_AMOUNT — monetary and scheduling attributes of the paydown request.
• KHR_ID, PARENT_KHR_ID, PAYDOWN_TYPE, YIELD_TYPE — contract/asset identifiers and paydown classification attributes.
• NEXT_PAYMENT_DATE — mapped from TRQ.START_DATE.
• RECEIPT_ID, TCN_ID, CUR_PRINCIPAL_BALANCE, CUR_ACCUM_INTEREST — links to receipt and transaction context plus current principal and accrued interest balances.

Common Use Cases and Queries

Typical uses include paydown request monitoring, status dashboards, reconciliation of principal balances, and integration extracts. A common pattern retrieves requests by requester:

• SELECT REQUEST_NUMBER, REQUEST_STATUS, REQUEST_TYPE, REQUESTED_BY, PAYMENT_AMOUNT, CUR_PRINCIPAL_BALANCE FROM APPS.OKL_CS_PRINCIPAL_PAYDOWN_UV WHERE REQUESTED_BY = :p_user_name;
• SELECT REQUEST_ID, REQUEST_NUMBER, REQUEST_STATUS, PAYMENT_DATE, RENT, CURRENCY_CODE FROM APPS.OKL_CS_PRINCIPAL_PAYDOWN_UV WHERE REQUEST_STATUS IN ('APPROVED','PENDING') ORDER BY REQUEST_DATE DESC;
• SELECT REQUESTED_BY, COUNT(*), SUM(PAYMENT_AMOUNT) FROM APPS.OKL_CS_PRINCIPAL_PAYDOWN_UV GROUP BY REQUESTED_BY;

Because REQUESTED_BY derives from CREATED_BY, filtering on it is case-sensitive against FND_USER.USER_NAME; letter-case or inactive-user variations should be handled in the query layer. No DML should be issued against this view.