Results for “original_amount”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_INVOICE_COMMITMENT_INFO_V is a Receivables (AR) view owned by the APPS schema and marked VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose, per the ETRM metadata, is to "collect information about commitments" — that is, to consolidate, for a given invoice line, the commitment invoice it originated from together with the amounts committed, the amounts already recognized against that commitment, the amounts still uninvoiced, and a computed commitment balance.

The view joins customer transaction header and line data with the transaction type definitions and the INV/CM lookup to expose commitment details on a per-line basis. It is typically surfaced through an Oracle Reports or OAF page attached to the Transactions window and is the source of the commitment details block. It is read-only and derives all calculated values through calls to the AR_INVOICE_SQL_FUNC_PUB package, so its output is consistent with the PL/SQL logic used elsewhere in Receivables for commitment accounting.

Underlying Base Objects

The documented base objects are:

The join is driven from RA_CUSTOMER_TRX (TRX) restricted to COMPLETE_FLAG = 'Y', joining RA_CUST_TRX_TYPES on CUST_TRX_TYPE_ID, then AR_LOOKUPS on LOOKUP_TYPE = 'INV/CM', then RA_CUSTOMER_TRX_LINES on CUSTOMER_TRX_ID. The CHILD transaction is linked by the predicate CHILD.INITIAL_CUSTOMER_TRX_ID = TRX.CUSTOMER_TRX_ID. Credit memos are filtered so that a CM is only returned when TRX.CUSTOMER_TRX_ID equals NVL(TRX.PREVIOUS_CUSTOMER_TRX_ID, -1).

Key Columns

  • CUSTOMER_TRX_ID — the child transaction being reported.
  • PREVIOUS_CUSTOMER_TRX_ID — the transaction that preceded the commitment, if any.
  • COMMITMENT_CUSTOMER_TRX_ID / COMMITMENT_TRX_NUMBER — the commitment transaction's ID and number.
  • START_DATE_COMMITMENT and END_DATE_COMMITMENT — the commitment validity window. The user search term "end_date_commitment" identifies this column, which carries the commitment end date sourced from RA_CUSTOMER_TRX.END_DATE_COMMITMENT.
  • CLASS / CLASS_NAME — the INV/CM lookup code and its translated meaning.
  • ORIGINAL_AMOUNT — the commitment line's REVENUE_AMOUNT.
  • THIS_INVOICE_AMOUNT — amount committed by this specific invoice.
  • TOTAL_ACTIVITY_AMT — total activity on the commitment for this class.
  • UNINVOICED_AMOUNT — commitment amount not yet invoiced.
  • COMMITMENT_BALANCE — the aggregate of ORIGINAL_AMOUNT, THIS_INVOICE_AMOUNT, TOTAL_ACTIVITY_AMT, and UNINVOICED_AMOUNT, treating nulls as zero.

Common Use Cases and Queries

Typical use cases include reporting commitment consumption against an invoice, auditing remaining commitment balances, and identifying commitments nearing expiry via END_DATE_COMMITMENT.

SELECT commitment_trx_number,
       start_date_commitment,
       end_date_commitment,
       class_name,
       original_amount,
       this_invoice_amount,
       uninvoiced_amount,
       commitment_balance
FROM   apps.ar_invoice_commitment_info_v
WHERE  customer_trx_id = :invoice_id;

To list commitments expiring within 30 days:

SELECT commitment_trx_number,
       end_date_commitment,
       commitment_balance
FROM   apps.ar_invoice_commitment_info_v
WHERE  end_date_commitment BETWEEN SYSDATE AND SYSDATE + 30
ORDER  BY end_date_commitment;

Because the amount columns are populated by AR_INVOICE_SQL_FUNC_PUB, queries against this view invoke PL/SQL per row and should be filtered before aggregation in high-volume reporting.