Search Results tloc_expiry_date

Overview

The OKL_CREDIT_REQUESTS_UV view (owner: APPS, status: VALID) is a user-facing reporting construct within the Oracle E-Business Suite OKL – Leasing and Finance Management module. It consolidates credit request data originating from leasing quotes with the corresponding credit management records held in Oracle Receivables, and enriches that data with contract, customer, party, and lookup information. The view exposes a single denormalized row per credit request, combining identifiers, monetary amounts, workflow milestones, and descriptive attributes.

The view is primarily intended for reporting, inquiry, and integration scenarios. Because it joins across credit management (AR_CMGT_CREDIT_REQUESTS), leasing contracts (OKC_K_HEADERS_ALL_B), receivables customer data (HZ_CUST_ACCOUNTS), and trading partners (HZ_PARTIES), it removes the need for consumers to reconstruct these relationships manually. The view is defined in both Oracle EBS 12.1.1 and 12.2.2 with the same column set and join semantics.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_CREDIT_REQUESTS (synonym) — primary source of credit request rows (aliased CRQ).
• AR_CMGT_CREDIT_REQUESTS (synonym) — the Receivables credit management request record (ACR), joined on CREDIT_REQ_ID = CREDIT_REQUEST_ID.
• OKC_K_HEADERS_ALL_B (synonym) — joined twice: once as KHR for the quote contract and once as CHR for the credit contract.
• HZ_CUST_ACCOUNTS (synonym) — provides the customer account number and name (CAT).
• HZ_PARTIES (synonym) — provides the party name (PTY).
• FND_LOOKUPS (view) — supplies the lookup meaning for the credit request status, filtered on lookup type OKL_REQUEST_STATUS.
• FND_GLOBAL (package) — used by the organization context referenced in the view metadata.

Outer joins are applied to CHR (credit contract), CAT (customer account), and PTY (party), so credit requests remain visible even when those references are absent. The joins to KHR, ACR, and FND_LOOKUPS are inner joins.

Key Columns

The view exposes the following notable columns:

• ID, QUOTE_ID, QUOTE_NUMBER — the credit request identifier and the associated leasing quote.
• CREDIT_REQ_NUMBER, CREDIT_REQ_ID — the credit request number and its cross-reference into AR credit management.
• CREDIT_AMOUNT, CURRENCY_CODE — the requested credit value and its currency.
• REQUESTED_BY, REQUESTED_DATE — who submitted the request and when.
• APPROVED_BY, APPROVED_DATE — the approver and approval timestamp; these are the columns most commonly targeted by users searching for "approved_by".
• STATUS, MEANING — the status code and its FND_LOOKUPS meaning (e.g., approved, pending).
• CREDIT_KHR_ID, CONTRACT_NUMBER — the credit contract header and its number.
• CUST_ACCOUNT_ID, ACCOUNT_NUMBER, ACCOUNT_NAME, PARTY_NAME — customer and party identification.
• ORG_ID — the operating unit, for multi-org security.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• TLOC_EXPIRY_DATE — exposed as NULL in the current view text.

Common Use Cases and Queries

Typical uses include reporting on approval turnaround, listing pending requests per customer, and exposing credit data to downstream integrations. A query to list requests and their approvers follows:

SELECT credit_req_number,
       quote_number,
       party_name,
       approved_by,
       approved_date,
       meaning
FROM   apps.okl_credit_requests_uv
WHERE  status = 'APPROVED';

To identify open requests by customer, restrict on MEANING and ACCOUNT_NUMBER. Because the view performs multi-table joins, filtering on indexed columns such as ORG_ID and CREDIT_REQ_ID improves performance.