Search Results freight_adjusted

Overview

ICX_AR_ADJUSTMENTS_V is a view registered under the ICX (Oracle iProcurement) product family and is documented with the description "Invoice Adjustments View." It exposes Oracle Receivables adjustment records — the transactions used to write off, discount, or otherwise modify an open invoice balance — in a form suitable for display and integration within the iProcurement self-service stack. The view is intended for reporting and integration consumption rather than for direct transactional DML; it surfaces adjustment header information together with selected payment schedule attributes (currency, due date, original and remaining amounts due) and lookup-derived meaning columns.

In the ETRM implementation metadata supplied for the 12.1.1 / 12.2.2 reference set, ICX_AR_ADJUSTMENTS_V is flagged as "Not implemented in this database." This is an important caveat: the view definition is preserved in the documentation, but the object may not be deployed in every environment, and dependent code should verify existence before selection.

Underlying Base Objects

The documented metadata lists no explicit base objects, and the view text shows the table aliases used in the definition (for example, ADJ for the adjustment row source, PS for the payment schedule source, and LK_STATUS / LK_TYPE for the lookup meaning joins). The adjustment columns (ADJUSTMENT_ID, ADJUSTMENT_NUMBER, AMOUNT, ACCTD_AMOUNT, ADJUSTMENT_TYPE, APPLY_DATE, APPROVED_BY, and the ATTRIBUTE1–ATTRIBUTE15 descriptive flexfield columns) correspond structurally to AR_ADJUSTMENTS_ALL. The payment schedule columns (INVOICE_CURRENCY_CODE, DUE_DATE, AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING) derive from AR_PAYMENT_SCHEDULES_ALL, joined on the customer transaction. MEANING columns for status and type are resolved from Receivables lookups, most likely AR_LOOKUPS. Because the authoritative join predicates are truncated in the supplied excerpt, consumers should treat column-to-table mapping as indicative rather than contractual.

Key Columns

• ADJUSTMENT_TYPE — the lookup code identifying the kind of adjustment (for example, write-off, discount, or chargeback). This is the column users most often filter on when reconciling adjustments.
• ADJUSTMENT_NUMBER / ADJUSTMENT_ID — the user-visible adjustment identifier and its internal primary key.
• AMOUNT, ACCTD_AMOUNT — the adjustment amount in the invoice currency and in accounted (ledger) currency respectively. AMOUNT is formatted through FND_CURRENCY.SAFE_GET_FORMAT_MASK, so it is returned as a formatted string rather than a raw number.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING — original and remaining amounts on the associated payment schedule, also currency-formatted.
• INVOICE_CURRENCY_CODE, DUE_DATE — currency context and schedule due date for the associated transaction.
• STATUS_MEANING, TYPE_MEANING — display-ready lookup meanings for adjustment status and type.
• CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, CHARGEBACK_CUSTOMER_TRX_ID — links to the invoice transaction, its line, and any chargeback transaction generated by the adjustment.
• APPLY_DATE, APPROVED_BY, AUTOMATICALLY_GENERATED, CREATED_FROM, COMMENTS — audit and origin attributes describing when, how, and by whom the adjustment was applied.

Common Use Cases and Queries

Typical uses include adjustment reconciliation reports, approval-audit extracts, and integration feeds that require the outstanding balance at the time an adjustment was applied. A representative query filters by adjustment type and restricts to a transaction:

SELECT adjustment_number,
       adjustment_type,
       type_meaning,
       amount,
       amount_due_remaining,
       apply_date
FROM   icx_ar_adjustments_v
WHERE  adjustment_type = :adjustment_type
AND    customer_trx_id = :customer_trx_id;

Because AMOUNT and the amount-due columns are returned pre-formatted by SAFE_GET_FORMAT_MASK, arithmetic on those columns should be performed against the base adjustment tables rather than the view. In environments where the ETRM metadata reports the view as not implemented, query AR_ADJUSTMENTS_ALL joined to AR_PAYMENT_SCHEDULES_ALL directly to obtain equivalent data with numeric columns intact.