Search Results previous_customer_trx_line_id




Overview
Explore in AI Chat

Overview

APPS.AR_NET_REVENUE_ASSIGNMENTS is a reporting view in the Oracle Receivables (AR) module of Oracle E-Business Suite. It presents a consolidated, net-oriented picture of revenue assignments by normalizing the relationship between an originating transaction line and any line that supersedes it. Revenue assignments in Receivables record how revenue is recognized across accounting periods for a given customer transaction line, and the base table AR_REVENUE_ASSIGNMENTS can contain chained or re-assigned rows in which a later assignment points back to the line it replaces through the PREVIOUS_CUSTOMER_TRX_LINE_ID attribute.

The view exists to collapse that chain into a single net view: for each revenue assignment, it returns either the line's own CUSTOMER_TRX_LINE_ID (when the assignment represents an original line) or the PREVIOUS_CUSTOMER_TRX_LINE_ID (when the assignment replaces an earlier line). This makes it possible to report revenue at the level of the "net" line rather than at the level of individual reassignment rows. It is used in reporting and integration scenarios where downstream consumers need a stable line identifier after credits, adjustments, or line reassignments have occurred.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: AR_REVENUE_ASSIGNMENTS (itself implemented as a view). The definition of AR_NET_REVENUE_ASSIGNMENTS is a set operation over that object:

  • A first branch selects rows where ACCOUNT_CLASS = 'REV' and PREVIOUS_CUSTOMER_TRX_LINE_ID IS NULL, returning the line's own CUSTOMER_TRX_LINE_ID.
  • A second branch selects rows where PREVIOUS_CUSTOMER_TRX_LINE_ID IS NOT NULL and ACCOUNT_CLASS = 'REV', returning the PREVIOUS_CUSTOMER_TRX_LINE_ID instead of the current line identifier.
  • The two branches are combined with UNION, so the result set contains no duplicate rows and preserves only revenue-class assignments (ACCOUNT_CLASS = 'REV').

Because both branches project the same five columns in the same order — CUSTOMER_TRX_LINE_ID, REQUEST_ID, GL_DATE, AMOUNT, PERIOD_SET_NAME — the union is type-consistent. The view therefore inherits the filtering already applied by AR_REVENUE_ASSIGNMENTS and adds the 'REV' account-class restriction plus the line-identifier normalization.

Key Columns

  • CUSTOMER_TRX_LINE_ID — The effective (net) transaction line identifier. For original assignments this is the row's own line ID; for reassignments it is the earlier line ID drawn from PREVIOUS_CUSTOMER_TRX_LINE_ID. This is the primary join key to transaction line reporting.
  • REQUEST_ID — The concurrent request identifier associated with the assignment record, useful for tracing batch revenue recognition runs.
  • GL_DATE — The accounting date on which the assignment amount is recognized in the general ledger.
  • AMOUNT — The revenue amount assigned to the line for the period. Because rows are unioned, callers should be aware that the view does not aggregate amounts.
  • PERIOD_SET_NAME — The accounting period set name governing the GL date, tying the assignment to a specific calendar.

Common Use Cases and Queries

The view is most often used to report recognized revenue against the correct originating line once reassignments have occurred, and to reconcile Receivables revenue assignments with GL postings by request. A representative query follows:

  • Join to transaction lines: SELECT n.CUSTOMER_TRX_LINE_ID, n.GL_DATE, n.AMOUNT, n.PERIOD_SET_NAME FROM APPS.AR_NET_REVENUE_ASSIGNMENTS n WHERE n.GL_DATE BETWEEN :start_date AND :end_date ORDER BY n.CUSTOMER_TRX_LINE_ID, n.GL_DATE;
  • Trace by concurrent request: SELECT CUSTOMER_TRX_LINE_ID, GL_DATE, AMOUNT FROM APPS.AR_NET_REVENUE_ASSIGNMENTS WHERE REQUEST_ID = :request_id;
  • Aggregate net revenue by line: SELECT CUSTOMER_TRX_LINE_ID, SUM(AMOUNT) FROM APPS.AR_NET_REVENUE_ASSIGNMENTS GROUP BY CUSTOMER_TRX_LINE_ID;

When searching for previous_customer_trx_line_id, users should note that this view deliberately hides that raw column and instead substitutes it into the CUSTOMER_TRX_LINE_ID output column where applicable. To inspect the unmodified predecessor attribute directly, query the base AR_REVENUE_ASSIGNMENTS view. In both 12.1.1 and 12.2.2 the definition is unchanged, and the view remains a lightweight, non-materialized reporting layer over the base revenue assignments object.