Search Results follow_up_code_last

Overview

ICX_AR_PAYMENT_SCHED_INV_V is a reporting view shipped with Oracle iProcurement (product code ICX) that presents invoice and debit memo payment schedules. It consolidates payment schedule information from Oracle Receivables into a single, denormalized structure that can be consumed by iProcurement-related inquiry pages, reporting extracts, and integration interfaces. The view exposes one row per payment schedule line, joined to transaction header and freight/ship-via reference data, and it formats monetary amounts according to the invoice currency so that downstream consumers receive presentation-ready values rather than raw numerics.

Per the ETRM metadata for this object, the description is "Invoice and Debit Memos Payment Schedules View." In the 12.2.2 documentation the view is not implemented in the database, and no base objects are formally documented. Consequently, the view text itself is the authoritative specification of its structure and behavior. Its currency-formatting approach—calling FND_CURRENCY.SAFE_GET_FORMAT_MASK with the invoice currency code and a 30-character mask—means amount columns are returned as character strings rather than numbers, a design choice that favors display but requires care in any programmatic reuse.

Underlying Base Objects

The documented base objects are listed as none; however, the view text identifies the principal source objects unambiguously. The central source is the payment schedule table, aliased PS, which supplies PAYMENT_SCHEDULE_ID, TRX_NUMBER, TRX_DATE, currency, amounts, due date, terms sequence, exchange rate, and the full attribute column set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15). A transaction header source, aliased CT, contributes PURCHASE_ORDER, WAYBILL_NUMBER, and SHIP_VIA. A reference table aliased FRT supplies ATTRIBUTE14 as SHIP_VIA_URL and DESCRIPTION as SHIP_VIA_MEANING, and AL_CLASS supplies the transaction class meaning through its MEANING column.

Because inventory (amount) columns are passed through FND_CURRENCY.SAFE_GET_FORMAT_MASK, the view depends on the Oracle Application Object Library currency formatting function at runtime, and the row identity is exposed through PS.ROWID as ROW_ID. Any custom SQL should therefore be written against the view's own column names rather than assuming the names or semantics of the underlying tables.

Key Columns

• ROW_ID — the payment schedule ROWID, useful as a stable row identifier in extracts.
• PAYMENT_SCHEDULE_ID — the primary key of the payment schedule line.
• TRX_NUMBER, TRX_DATE — transaction number and date of the invoice or debit memo.
• AL_CLASS_MEANING — the transaction class meaning derived from AL_CLASS.
• INVOICE_CURRENCY_CODE — the currency used to format all amount columns.
• AMOUNT_DUE_ORIGINAL, TAX_ORIGINAL, FREIGHT_ORIGINAL — original amounts, formatted as strings.
• AMOUNT_DUE_REMAINING — the remaining open balance of the schedule line.
• AMOUNT_ADJUSTED, AMOUNT_CREDITED, AMOUNT_APPLIED — activity amounts against the schedule.
• DUE_DATE, GL_DATE, TERMS_SEQUENCE_NUMBER, EXCHANGE_RATE — payment terms and accounting context.
• CT_PURCHASE_ORDER, WAYBILL_NUMBER, SHIP_VIA, SHIP_VIA_URL, SHIP_VIA_MEANING — procurement and shipment descriptors sourced from CT and FRT.
• CUSTOMER_ID and attributes 1–15 — party identifier and the standard DFF column set.

Common Use Cases and Queries

Typical uses include iProcurement payment schedule inquiries, supplier-facing balance reporting, and reconciliation extracts where the formatted currency strings can be published directly. A straightforward query returning open schedules is:

SELECT payment_schedule_id, trx_number, trx_date, al_class_meaning, invoice_currency_code, amount_due_remaining, due_date, ct_purchase_order FROM icx_ar_payment_sched_inv_v WHERE invoice_currency_code = 'USD' ORDER BY due_date;

For a party-specific extract, filter on customer_id and aggregate by currency, remembering that the amount columns are character-formatted and must be cast before arithmetic. All access should be through the view's exposed columns, as the underlying implementation is not documented and should not be relied upon.