Results for “refund_type_meaning”

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

Overview

The view OKL_CURE_RFND_VND_DTLS_UV is an Oracle E-Business Suite database object owned by the APPS schema within the OKL – Leasing and Finance Management product family. Its documented purpose is to present vendor-level refund details, aggregating refund amounts due that arise from cure processing. In the leasing lifecycle, a cure event occurs when a delinquent or defaulted contract is brought back into good standing, and a refund may become payable to a vendor. This view consolidates that refund exposure so that it can be reported and reviewed by vendor and vendor site.

The view is constructed as a UNION ALL of two grouped result sets derived from OKL_CURE_REFUNDS_DTLS_UV. The first branch produces one row per vendor site, labelled VENDOR_SITE / VENDOR SITE, with the sum of REFUND_AMOUNT_DUE grouped by currency, vendor, vendor site, and cure due attributes. The second branch produces an aggregate "across sites" row, labelled ACROSS_SITES / INCLUDE ALL SITES, which collapses the vendor site dimension and reports the total refund amount due for the vendor. The result is a two-tier presentation that supports both site-detail and vendor-total reporting from a single query.

Underlying Base Objects

The documented referenced base objects for this view are:

• OKL_CURE_REFUNDS_DTLS_UV (VIEW) – the primary source of refund detail rows, queried twice and aggregated.
• FND_GLOBAL (PACKAGE) – the standard EBS package that supplies session context such as USER_ID, RESP_ID, and ORG_ID, typically used to enforce organization-level security.
• OKC_UTIL (PACKAGE) – the Contracts utility package, providing shared helpers for contract-related derivation and currency or lookup handling.
• OKL_BILLING_UTIL_PVT (PACKAGE) – the Leasing billing utility package, used for billing-related logic such as amount computation or currency handling.

These references indicate that the view is a reporting layer rather than a base table, layering aggregation and presentation logic over the underlying refund detail view while relying on EBS utility packages for security and currency context.

Key Columns

The view exposes the following columns, which combine literal descriptor columns with aggregating monetary columns:

• REFUND_TYPE – literal indicator distinguishing the row scope, either VENDOR_SITE or ACROSS_SITES.
• REFUND_TYPE_MEANING – user-facing label: "VENDOR SITE" or "INCLUDE ALL SITES".
• CURRENCY_CODE – the contract currency code for the refund amounts. This column is central to the view's grouping and is the object the user searched for under the term "contract_currency_code"; it is derived from CONTRACT_CURRENCY_CODE in the underlying detail view and ensures refunds are never summed across currencies.
• VENDOR_NAME and VENDOR_ID – vendor identification attributes.
• VENDOR_SITE_ID – the vendor site identifier; set to TO_NUMBER(NULL) on the across-sites row.
• VENDOR_CURE_DUE and VENDOR_SITE_CURE_DUE – cure-due flags or indicators at vendor and site level; the site column is rendered as a blank string on the aggregate row.
• REFUND_AMOUNT_DUE – the summed refund amount payable, grouped by currency and vendor scope.

Common Use Cases and Queries

This view is typically consumed by cure and refund reporting, vendor exposure analysis, and payables reconciliation in Leasing and Finance Management. A common query retrieves vendor-level totals in a single currency:

• Site-level refund review: SELECT vendor_name, vendor_site_id, currency_code, refund_amount_due FROM okl_cure_rfnd_vnd_dtls_uv WHERE refund_type = 'VENDOR_SITE' AND currency_code = :p_currency ORDER BY vendor_name;
• Vendor total exposure: SELECT vendor_name, currency_code, refund_amount_due FROM okl_cure_rfnd_vnd_dtls_uv WHERE refund_type = 'ACROSS_SITES' ORDER BY vendor_name;
• Currency-specific filtering: Because grouping includes CURRENCY_CODE, always filter or group by currency when consolidating totals to avoid mixing amounts denominated in different currencies.

Because the view depends on FND_GLOBAL through its base objects, queries are normally executed under a valid EBS responsibility so that organization and user context are applied correctly. Practitioners should treat the view as read-only and reference it from concurrent programs, BI Publisher reports, or custom inquiry pages rather than attempting DML.