Search Results ar_adjustments_v




Overview
Explore in AI Chat

Overview

AR_ADJUSTMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes adjustment activity recorded against customer transactions and their payment schedules within the Oracle Receivables module. Adjustments represent changes to the amount owed by a customer that are not directly associated with a receipt or credit memo, such as write-offs, discounts, small balance write-offs, claims, and other manual or automatic modifications to an invoice balance. The view allows technical consultants and developers to query adjustment data without navigating the underlying transaction and scheduling tables directly.

The ETRM documentation notes that the object was originally described as "(Release 11.5 Only)" in earlier documentation sets, which reflects the historical origin of the view. Despite that annotation, the view remains present and valid in the APPS schema in 12.1.1 and 12.2.2, and the documented metadata for 12.2.2 confirms the expanded set of base objects it references. The view is primarily used in reporting, reconciliation, and integration scenarios where adjustment detail must be combined with customer, transaction, lookup, and accounting context.

Underlying Base Objects

The 12.2.2 metadata documents AR_ADJUSTMENTS_V as being defined over a substantial set of base objects. The core transactional source is AR_ADJUSTMENTS (accessed via its synonym), which stores the adjustment rows themselves. Supporting tables include AR_PAYMENT_SCHEDULES_ALL, which links adjustments to installment-level balances; RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL, which provide the invoice and line context; and AR_RECEIVABLES_TRX_ALL, which describes the receivables activity used to classify the adjustment. RA_CUST_TRX_TYPES_ALL supplies transaction type information, while RA_BATCH_SOURCES_ALL identifies the batch source for adjustments created through AutoAdjustment or batch processes.

Customer-side context is drawn from HZ_CUST_ACCOUNTS and HZ_PARTIES. Reference and control data come from AR_LOOKUPS (the standard Receivables lookup view) and FND_USER (for the creating and approving user). FND_ATTACHMENT_UTIL_PKG is referenced as a package, typically for functions that resolve attachment or descriptive flexfield information used within the view definition. Because the view joins across these objects, it presents a denormalized picture of each adjustment, combining transaction, schedule, activity, batch, customer, and audit information in a single row.

Key Columns

  • ADJUSTMENT_ID / ADJUSTMENT_NUMBER — Primary identifier and user-facing number for the adjustment.
  • ADJUSTMENT_TYPE — Classifies the adjustment (for example, write-off, discount, or chargeback), derived in conjunction with AR_RECEIVABLES_TRX_ALL and AR_LOOKUPS.
  • AMOUNT / ACCTD_AMOUNT — Entered adjustment amount and the accounted amount in ledger currency.
  • CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID — The transaction and line against which the adjustment was applied.
  • PAYMENT_SCHEDULE_ID — The installment to which the adjustment relates, linking to AR_PAYMENT_SCHEDULES_ALL.
  • APPLY_DATE / GL_DATE / GL_POSTED_DATE — Application date and the accounting date, with the posted date indicating whether the adjustment has been transferred to the general ledger.
  • POSTABLE / POSTING_CONTROL_ID — Flags governing whether the adjustment is eligible for posting to GL.
  • CODE_COMBINATION_ID — The accounting flexfield combination used for the adjustment distribution.
  • BATCH_ID — Ties the adjustment to a batch created via a batch source.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard audit columns, with FND_USER providing the user names.
  • ORG_ID — Operating unit identifier for multi-org security and filtering.

Common Use Cases and Queries

Typical scenarios include reconciling adjustment activity to the general ledger, reporting write-offs and discounts by customer or transaction, auditing automatically generated adjustments, and extracting adjustment data for a data warehouse or integration feed. A common query retrieves adjustments for a specific transaction:

  • SELECT adjustment_number, adjustment_type, amount, acctd_amount, apply_date, gl_posted_date, postable FROM ar_adjustments_v WHERE customer_trx_id = :trx_id AND org_id = :org_id;
  • SELECT adjustment_type, SUM(amount) FROM ar_adjustments_v WHERE apply_date BETWEEN :from_date AND :to_date AND org_id = :org_id GROUP BY adjustment_type;
  • SELECT automatically_generated, COUNT(*) FROM ar_adjustments_v WHERE gl_posted_date IS NULL AND org_id = :org_id GROUP BY automatically_generated;

Because the view resolves customer, party, lookup, and user descriptions through its joins, it is well suited for ad hoc reporting and for building concurrent programs that export adjustment detail without requiring custom joins against the base tables.