Results for “payment_cross_rate_type”

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

Overview

AP_APPLY_PREPAYS_FR_PREPAY_V is an APPS-owned, VALID Oracle E-Business Suite view in the Payables (AP) module. It is a reporting and integration object designed to expose the list of non-prepayment invoices that remain eligible for applying or offsetting against an existing prepayment. In the Payables workflow, a prepayment is a special invoice type used to advance funds to a supplier; subsequently, a standard invoice is entered and applied against that prepayment so the actual liability is settled. This view supplies the candidate invoices that the "Apply Prepayments" form and its associated programmatic logic can present to a user, from which the prepayment is then matched and applied.

Because the view already filters for eligible records and pre-computes unpaid amounts, it functions as a convenience data source that shields callers from the complex joins and subqueries otherwise required to determine which invoices are open and available. It is therefore useful both to interactive users and to internal Payables programs that drive prepayment application.

Underlying Base Objects

The view is defined over several AP and PO base objects. Its primary FROM clause joins AP_INVOICES (synonym) to PO_VENDORS (view) and PO_VENDOR_SITES_ALL (view) on VENDOR_ID and VENDOR_SITE_ID respectively. Eligibility is established through correlated subqueries against AP_PAYMENT_SCHEDULES_ALL (which must carry a positive AMOUNT_REMAINING) and AP_SELECTED_INVOICES_ALL (an invoice is excluded if a matching selected-invoice row exists, i.e., it is already queued for payment). The view also invokes package functions AP_PREPAY_UTILS_PKG.GET_INVOICE_UNPAID_AMOUNT and GET_INCLUSIVE_TAX_UNPAID_AMT to derive unpaid and tax amounts. Documented referenced objects additionally include AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_LINES (synonym) and FND_GLOBAL (package), the latter typically supplying the runtime organization context.

Note that PO_VENDORS and PO_VENDOR_SITES_ALL are supplied as views in this release, so supplier name, number, and site code are sourced through those supplier-model abstractions rather than directly from base tables.

Key Columns

• ROW_ID / INVOICE_ID / INVOICE_NUM — Identifier, surrogate row identifier, and user-visible invoice number.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_CODE — Supplier identification and site detail.
• INVOICE_CURRENCY_CODE / PAYMENT_CURRENCY_CODE — Invoice and payment currencies, relevant when the two differ.
• INVOICE_DATE — Date of the candidate invoice.
• PAYMENT_CROSS_RATE_DATE — The date of the cross rate used when the invoice and payment currencies differ; this is the column most closely associated with the "payment_cross_rate_date" search term. It governs the conversion rate effective date applied during application.
• PAYMENT_CROSS_RATE_TYPE — The rate type (for example, Corporate or Spot) paired with the cross rate date.
• SET_OF_BOOKS_ID, ORG_ID, DESCRIPTION — Ledger, operating unit, and invoice description context.
• AMOUNT_UNPAID — Derived via AP_PREPAY_UTILS_PKG.GET_INVOICE_UNPAID_AMOUNT; the outstanding liability.
• TAX_AMOUNT_UNPAID — Derived via GET_INCLUSIVE_TAX_UNPAID_AMT and returned as NULL when zero.

Common Use Cases and Queries

The principal use case is retrieving open, unselected invoices available for prepayment application, frequently filtered by supplier or by the cross-rate date. A typical query selects the paying invoice details alongside the cross rate date:

• SELECT invoice_id, invoice_num, vendor_name, payment_currency_code, payment_cross_rate_date, payment_cross_rate_type, amount_unpaid, tax_amount_unpaid FROM ap_apply_prepays_fr_prepay_v WHERE vendor_id = :p_vendor_id;
• Filtering by rate date: ... WHERE payment_cross_rate_date BETWEEN :p_from AND :p_to ORDER BY payment_cross_rate_date;
• Reconciliation of applied versus unpaid balances by selecting SUM(amount_unpaid) grouped by vendor or org_id.

Because the view enforces eligibility via the payment schedule and selected-invoice subqueries, no additional filtering for open status is required from the caller, which reduces the risk of double-applying an invoice already queued for payment.