Search Results credit_memo




Overview
Explore in AI Chat

Overview

The APPS.OKL_CS_CREDIT_MEMO_REQUEST_UV view is a reporting and integration construct within the Oracle E-Business Suite (EBS) Lease and Finance Management (ETRM) module. It consolidates credit memo request records originating from the service or contract transaction flow, presenting them alongside their associated status descriptions and originating user information. Its primary role is to provide a unified, human-readable projection of credit memo requests without requiring callers to repeatedly join the underlying transaction request table to the FND lookup and user tables.

The view excludes requests whose status is ENTERED, effectively filtering out items still in an initial, unsubmitted state. This makes the view suitable for downstream reporting, workflow monitoring, and integration interfaces that need to reflect requests already actioned or otherwise progressed beyond entry. Because the user searched for okl_request_status, it is significant that this view derives its primary status value from the OKL_REQUEST_STATUS lookup type, while also exposing the transaction status of an associated AR invoice via the OKL_TRANSACTION_STATUS lookup.

Underlying Base Objects

The documented base objects referenced by this view are FND_LOOKUPS, FND_USER, OKL_TRX_AR_INVOICES_B, OKL_TRX_REQUESTS, and the FND_GLOBAL package. The definition is a UNION of two branches over the central OKL_TRX_REQUESTS table:

Both branches restrict to REQUEST_TYPE_CODE = 'CREDIT_MEMO'. The FND_GLOBAL package is referenced in the view metadata, typically supplying session context such as the effective responsibility or user for row-level security or defaulting within ETRM.

Key Columns

  • REQUEST_NUMBER — the user-facing identifier of the credit memo request.
  • ID — the primary key of the transaction request in OKL_TRX_REQUESTS.
  • OBJECT1_ID1 — in the invoice branch, the foreign key to the AR invoice (OKL_TRX_AR_INVOICES_B.ID).
  • DNZ_KHR_ID and LSM_ID — denormalized identifiers retained for ETRM processing context.
  • AMOUNT and CURRENCY_CODE — the credit memo value and its currency.
  • STATUS_CODE — the raw status value; sourced from REQUEST_STATUS_CODE in the first branch and from the invoice's TRX_STATUS_CODE in the second.
  • STATUS — the decoded meaning from the relevant FND lookup (OKL_REQUEST_STATUS or OKL_TRANSACTION_STATUS).
  • USER_NAME — the name of the creating user.
  • CREATION_DATE and REQUEST_TYPE_CODE — audit and classification details.

Common Use Cases and Queries

This view is commonly queried to report on outstanding or completed credit memo requests and to reconcile request status against invoice status. A typical query filters by status meaning or user:

  • Status monitoring: SELECT request_number, status, user_name, amount FROM okl_cs_credit_memo_request_uv WHERE status = 'APPROVED';
  • User workload: grouping by USER_NAME with counts of requests.
  • Reconciliation: joining or comparing STATUS values across the two UNION branches to detect credit memo requests whose invoice status (from OKL_TRANSACTION_STATUS) diverges from the request status (from OKL_REQUEST_STATUS).

Because the view pre-filters ENTERED requests, it should not be used when auditing the full lifecycle from initial entry; in those cases the base OKL_TRX_REQUESTS table is required.