Search Results adjustment_date




Overview

ARBV_ADJUSTMENT_DISTRIBUTIONS is a read-only Oracle EBS view owned by the APPS schema in the Receivables (AR) product. It presents the accounting distributions generated for Receivables adjustments, joining adjustment header information from AR_ADJUSTMENTS to the corresponding Subledger Accounting (SLA) distribution lines and their accounting event headers. Because Receivables adjustments are accounted through the SLA engine in Release 12, the actual debit and credit lines are not stored directly on AR_ADJUSTMENTS; this view reconciles the adjustment and its resulting journal distributions into a single reporting structure.

The view carries a WITH READ ONLY clause and is intended purely for query, reporting, and integration purposes. It exposes functional and accounted amounts, the general ledger date, the posting status derived from the accounting header, and the adjustment reason. For the user searching on adjustment_date, note that the view surfaces the adjustment date column (mapped to ADJ.GL_DATE) as ADJUSTMENT_DATE, in addition to the APPLY_DATE from the underlying adjustment. This makes the view valuable for date-driven analysis of adjustment activity and its ledger impact.

Underlying Base Objects

The view is defined over three documented base objects:

  • AR_ADJUSTMENTS (SYNONYM) — aliased as ADJ, the primary source of adjustment attributes: adjustment identifier, GL date, apply date, reason code, status, org, set of books, payment schedule, and transaction identifiers.
  • AR_XLA_ARD_LINES_V (VIEW) — aliased as DIST, a Receivables subledger accounting distributions view supplying the amount and account columns and the linking keys.
  • XLA_AE_HEADERS (SYNONYM) — aliased as HED, the Subledger Accounting event headers, used to derive the posted flag from GL_TRANSFER_STATUS_CODE.

The join is established on ADJUSTMENT_ID, SOURCE_TABLE = 'ADJ', and SOURCE_TYPE = 'ADJ', with DIST.AE_HEADER_ID linking to HED.AE_HEADER_ID. This confirms that only adjustment-sourced SLA distributions are returned.

Key Columns

Common Use Cases and Queries

Typical uses include reconciliation of adjustment accounting to the general ledger, audit of adjustment distributions by date, and extraction for downstream reporting.

  • List adjustments occurring within a date range:
    SELECT adjustment_id, adjustment_date, transaction_id,
           debit_amount, credit_amount, posted_flag
    FROM   apps.arbv_adjustment_distributions
    WHERE  adjustment_date BETWEEN :from_date AND :to_date
    ORDER  BY adjustment_date;
  • Identify unposted adjustment distributions:
    SELECT adjustment_id, code_combination_id,
           functional_debit_amount, functional_credit_amount
    FROM   apps.arbv_adjustment_distributions
    WHERE  posted_flag = 'N';
  • Summarize adjustment activity by reason and date:
    SELECT adjustment_reason, adjustment_date,
           SUM(NVL(functional_debit_amount,0)) dr,
           SUM(NVL(functional_credit_amount,0)) cr
    FROM   apps.arbv_adjustment_distributions
    GROUP  BY adjustment_reason, adjustment_date;

All queries should reference the APPS schema and account for the read-only nature of the view.