Search Results discount_amount_taken

Overview

The AMS_AP_INVOICES_V view is a marketing-module reporting object that presents a vendor invoice record as sourced from Oracle Payables. Despite being cataloged under the AMS - Marketing product family, its definition is entirely composed of Payables and Purchasing base tables, meaning it surfaces accounts payable invoice data to marketing-facing reporting and integration layers without requiring those consumers to join the underlying AP and PO entities directly. In Oracle EBS 12.1.1 and 12.2.2, this kind of cross-module view is typically used to feed marketing accrual, trade-promotion settlement, or vendor-spend analysis processes that need invoice-level financial data.

The specific column the user searched for, PAYMENT_CROSS_RATE_TYPE, is exposed directly from AP_INVOICES. It carries the cross-rate conversion type used when the invoice payment currency differs from the invoice currency, enabling consumers to report on the rate type applied during settlement rather than merely the invoice-level exchange rate.

Underlying Base Objects

The view is defined over the following documented objects:

• AP_INVOICES (AI) — the driving table supplying all invoice-level attributes.
• AP_LOOKUP_CODES (ALC1, ALC2, ALC3) — outer-joined three times to resolve the invoice type, payment status, and payment method lookup codes into displayed values.
• AP_TERMS (AT) — outer-joined on TERMS_ID to bring the payment term name.
• GL_DAILY_CONVERSION_TYPES (GDCT) — outer-joined on EXCHANGE_RATE_TYPE to resolve the user conversion type.
• PO_VENDORS (PV) and PO_VENDOR_SITES (PVS) — inner-joined on VENDOR_ID and VENDOR_SITE_ID to supply vendor and vendor-site identifiers.

Per the ETRM metadata, no additional base objects are documented, and the object is not implemented in every database. Inclusion therefore depends on whether the Marketing application objects are installed in the target instance.

Key Columns

• INVOICE_ID / INVOICE_NUM / INVOICE_DATE — invoice identity and date.
• INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE — the two currencies governing conversion behavior.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE — invoice-level conversion.
• PAYMENT_CROSS_RATE, PAYMENT_CROSS_RATE_TYPE, PAYMENT_CROSS_RATE_DATE — the cross-rate and rate type applied for the payment currency.
• AMOUNT_PAID, PAYMENT_AMOUNT_TOTAL, PAYMENT_STATUS_FLAG — settlement state and amounts.
• VENDOR_NAME, SEGMENT1, VENDOR_SITE_CODE — vendor identity.
• APPROVAL_STATUS, APPROVAL_DESCRIPTION — workflow approval state.

Common Use Cases and Queries

A frequent requirement is to extract invoices where a cross-rate type was applied, which indicates a payment in a currency other than the invoice currency:

• Cross-rate audit: SELECT INVOICE_NUM, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, PAYMENT_CROSS_RATE_TYPE, PAYMENT_CROSS_RATE FROM AMS_AP_INVOICES_V WHERE PAYMENT_CROSS_RATE_TYPE IS NOT NULL;
• Vendor spend reporting: aggregate BASE_AMOUNT and AMOUNT_PAID by VENDOR_NAME for a date range.
• Settlement analysis: compare EXCHANGE_RATE against PAYMENT_CROSS_RATE to validate conversion consistency.

Queries should account for the outer joins resolving lookups and the inner joins on vendor tables, which will exclude invoices lacking a valid vendor or vendor site.