Search Results commitment_line_number




Overview

ARFV_TAXES is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema. In the ETRM metadata for 12.1.1 and 12.2.2 the object is reported with a status of VALID and is provisioned in every standard Oracle EBS environment under APPS. The view presents tax lines associated with customer transactions: specifically, rows drawn from RA_CUSTOMER_TRX_LINES_ALL where the line type is 'TAX'. It aggregates descriptive attributes of the tax line, resolves foreign key lookups to the parent transaction, the credited (previous) transaction, the initial (original) transaction, the associated revenue line, and the operating unit, and exposes both business-facing names and the underlying surrogate identifiers.

Because the view is not a base table, it should be treated strictly as a reporting and integration access point. It supplies a denormalized, read-only projection of tax line data that would otherwise require joining RA_CUSTOMER_TRX_LINES_ALL to its transaction header and to reference tables for lookup meanings. It is used by Receivables inquiry and reporting functionality, and it is a common source for reconciliation extracts and data-warehouse staging of tax detail.

The naming convention follows ETRM standards: the "_LA" prefixed columns carry the lookup meaning for a corresponding code column (for example, REASON_CODE resolved against the AR_LOOKUPS view with the INVOICING_REASON lookup type), while the "_DF" columns record the descriptive flexfield context for the relevant entity. The "_LA" and "_DF" identifiers are presented as literal strings in the view text, an indication of how the view was generated from a data-model definition rather than hand-written SQL.

Underlying Base Objects

According to the documented 12.2.2 metadata, ARFV_TAXES is defined over the following referenced base objects, all of which are accessed through APPS synonyms:

  • RA_CUSTOMER_TRX_LINES_ALL — the primary driver, aliased CTL, restricted to LINE_TYPE = 'TAX'.
  • RA_CUSTOMER_TRX_ALL — the transaction header, accessed multiple times: aliased CT for the owning transaction, CRCT for the prior/credited transaction, and COCT for the initial transaction.
  • RA_CUSTOMER_TRX_LINES_ALL — accessed again as CRCTL and COCTL for the previous and initial transaction lines, and as ASCTL for the associated (link-to) line.
  • HR_ALL_ORGANIZATION_UNITS — aliased AOU, providing the operating unit name.

The joins are predominantly outer joins (denoted by the (+) operator) on PREVIOUS_CUSTOMER_TRX_ID, PREVIOUS_CUSTOMER_TRX_LINE_ID, INITIAL_CUSTOMER_TRX_LINE_ID, INITIAL_CUSTOMER_TRX_ID, and ORG_ID. The link from CTL.LINK_TO_CUST_TRX_LINE_ID to ASCTL.CUSTOMER_TRX_LINE_ID is an inner join, so a tax line that is not linked to a transaction line is excluded from the view. This structure makes the view useful for tracing credit, rebill, and adjustment chains around tax lines.

Key Columns

The view exposes the following principal columns (noting that several source columns are renamed in the projection):

Common Use Cases and Queries

Typical scenarios include reconciling tax amounts on invoices and credit memos, tracing credit chains for a tax line, and matching tax lines back to sales-order commitments for order-to-cash reporting.

SELECT t.transaction_number,
       t.transaction_date,
       t.transaction_line_id,
       t.tax_amount,
       t.tax_rate,
       t.commitment_line_num
FROM   appsfnd.arfv_taxes t
WHERE  t.transaction_number = '100045'
ORDER  BY t.transaction_line_id;

Tax lines that were subsequently credited can be retrieved by filtering on the credited transaction columns. To isolate tax associated with a specific commitment line, filter on COMMITMENT_TRANSACTION_NUMBER and COMMITMENT_LINE_NUM, which is where the COMMITMENT_LINE_NUMBER search term entered by the user becomes relevant. Because these columns are derived from the link-to and initial transaction joins, ensure the link-to exists (the inner join requirement) or the row will not appear.

The COMMITMENT_TRANSACTI… and COMMITMENT_LINE_NUM columns provide the direct path from a tax line to the commitment/order line, while the initial and credited transaction columns describe the invoice lifecycle around it. All queries should be issued in a read-only context, as the view is a reporting projection only.