Results for “okl_credit_requests_v”

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

Overview

OKL_CREDIT_REQUESTS_V is a reporting and integration view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. The view presents transaction-level credit request information, exposing the credit approval workflow that governs lease and finance transactions. In the OKL credit management model, a credit request is generated against a quote or contract to obtain authorization for extending credit to a customer before the transaction proceeds. This view supplies a denormalized, read-oriented projection of that data for use in custom reports, concurrent programs, Oracle Business Intelligence Publisher (BI Publisher) data templates, and outbound integrations to external credit or risk systems. The view is documented as "not implemented in this database" in the source metadata, meaning the view text is catalogued but no runtime object exists in that particular environment; where it is deployed, it acts as a lightweight abstraction over the underlying credit request entity rather than a stored materialization of data. Its naming follows the OKL convention whereby "_V" objects are views intended for inquiry and reporting rather than for direct transactional DML.

Underlying Base Objects

The view text identifies a single underlying base object: OKL_CREDIT_REQUESTS, aliased as CRQ in the defining SQL. Every column in the view is a direct, one-to-one projection of a column in that table, with no joins, unions, aggregations, or computed expressions present in the documented view definition. Consequently, OKL_CREDIT_REQUESTS_V inherits the grain of OKL_CREDIT_REQUESTS: one row per credit request record. The ETRM metadata records no additional referenced base objects, and the "Referenced base objects: none documented" annotation reflects the cataloguing scope rather than the underlying physical dependency, since the view text itself is explicit about OKL_CREDIT_REQUESTS as its source. No database links, synonyms, or external tables are documented in the extraction. Because the view performs a straight SELECT from a single table, query performance and filter pushdown characteristics are essentially identical to querying OKL_CREDIT_REQUESTS directly; the view adds semantic clarity and a stable interface rather than optimization.

Key Columns

• ID — The unique identifier of the credit request row (CRQ.ID).
• CREDIT_REQ_ID and CREDIT_REQ_NUMBER — The business key and human-readable request number used to track and reference the credit request.
• QUOTE_ID — Foreign reference to the originating quote, linking the credit request to its transaction context.
• CREDIT_AMOUNT and CURRENCY_CODE — The requested credit exposure and the currency in which it is denominated.
• REQUESTED_BY and REQUESTED_DATE — The user who initiated the credit request and the timestamp of submission.
• APPROVED_BY and APPROVED_DATE — The approver responsible for the credit decision and the date of approval; these are the columns most relevant to the "approved_by" search, enabling audit and aging analysis of credit approvals. A null APPROVED_BY generally indicates the request is pending or rejected.
• STATUS — The workflow or processing state of the request, driving filtering for outstanding, approved, or declined items.
• CREDIT_KHR_ID — Reference to the associated key credit history or credit check record.
• ORG_ID — The multi-organization operating unit identifier, essential for security and ledger-level reporting.
• OBJECT_VERSION_NUMBER — Optimistic locking version, useful for detecting concurrent updates in integrations.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard Oracle EBS descriptive flexfield columns for client-specific extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "who column" audit fields supporting change tracking.

Common Use Cases and Queries

The primary use cases are credit approval reporting, approval turnaround analysis, exposure aggregation by operating unit or currency, and extraction of credit request data into external workflow or risk systems. A typical report querying approvals within a date range follows:

• SELECT CREDIT_REQ_NUMBER, APPROVED_BY, APPROVED_DATE, CREDIT_AMOUNT, CURRENCY_CODE FROM OKL_CREDIT_REQUESTS_V WHERE APPROVED_BY = :p_approver AND APPROVED_DATE BETWEEN :p_from AND :p_to;
• Pending-request monitoring: SELECT CREDIT_REQ_NUMBER, REQUESTED_BY, REQUESTED_DATE, CREDIT_AMOUNT FROM OKL_CREDIT_REQUESTS_V WHERE APPROVED_BY IS NULL AND STATUS = :p_pending;
• Exposure by business unit: SELECT ORG_ID, CURRENCY_CODE, SUM(CREDIT_AMOUNT) FROM OKL_CREDIT_REQUESTS_V GROUP BY ORG_ID, CURRENCY_CODE;
• Joining to quotes using QUOTE_ID, and observing OBJECT_VERSION_NUMBER when preparing updates to the base table in integration logic.

Because the view is a direct projection, all filtering and aggregation are executed against OKL_CREDIT_REQUESTS; developers should confirm deployment in each environment before relying on the view in concurrent programs or interfaces.