Results for “previous_customer_trx_id”

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

Overview

AR_CM_NET_REVENUE_FORM is a reporting view owned by the APPS schema within the Oracle Receivables (AR) product module. Its documented purpose is to determine the uncredited amount associated with credit memo processing and revenue assignment. The view is registered as VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2, and its structure and behavior are consistent across these releases because it is defined purely as a SQL view over an existing assignments table rather than as a physical object subject to editioning changes.

In the broader context of Oracle EBS reporting and integration, this view exposes net revenue figures and net unit prices at the level of previous customer transaction lines. It is typically consumed by Receivables credit memo workflows, AutoInvoice-related logic, and downstream reporting that needs to resolve how much revenue remains uncredited after credit method rules are applied. Because it consolidates and aggregates AMOUNT and QUANTITY by transaction line, general ledger date, and accounting period, it is suited to reconciliation and period-based analysis rather than to transactional data entry.

Underlying Base Objects

The view is defined over a single documented base object, AR_CM_NET_REV_ASSIGNMENTS_FRM, which is itself a view. AR_CM_NET_REVENUE_FORM performs no joins to additional tables; instead it aggregates the rows retrieved from that underlying assignments view. This layered design means the view inherits any filtering, security, or derivation logic embedded within AR_CM_NET_REV_ASSIGNMENTS_FRM.

The aggregation applies GROUP BY over PREVIOUS_CUSTOMER_TRX_LINE_ID, TRUNC(GL_DATE), PREVIOUS_CUSTOMER_TRX_ID, and PERIOD_SET_NAME. Consequently, each output row represents a distinct combination of prior transaction line, prior transaction, GL date (normalized to the day), and accounting period set, with revenue and quantity totals summed across matching assignment records. All columns are sourced from the base view; no external tables are referenced in the documented view text.

Key Columns

• PREVIOUS_CUSTOMER_TRX_LINE_ID — Identifier of the earlier customer transaction line to which the credit or revenue assignment relates.
• PREVIOUS_CUSTOMER_TRX_ID — Identifier of the earlier customer transaction header referenced by the assignment.
• GL_DATE — The general ledger date, returned as TRUNC(GL_DATE), so reporting is performed at day-level granularity.
• AMOUNT — Summed monetary amount for the grouped records.
• NET_UNIT_PRICE — A derived value calculated as the sum of non-unit and non-LIFO amounts divided by a quantity denominator. The denominator sums QUANTITY only for records where CREDIT_METHOD_FOR_RULES is empty, with a DECODE guard returning 1 when the denominator is zero to avoid division errors.
• PERIOD_SET_NAME — The accounting period set name associated with the grouped records, enabling period-based classification.

Common Use Cases and Queries

Because the user search term credit_method_for_rules maps directly to the DECODE logic within the view text, this view is the natural starting point for investigating how credit method rules affect net revenue and net unit price calculations. Typical scenarios include auditing the net unit price applied to previously invoiced lines, reconciling uncredited revenue by period, and tracing revenue adjustments back to prior transaction lines.

A representative query retrieving net revenue by prior transaction line is shown below:

• SELECT previous_customer_trx_id, previous_customer_trx_line_id, gl_date, amount, net_unit_price, period_set_name FROM apps.ar_cm_net_revenue_form WHERE previous_customer_trx_id = :trx_id ORDER BY gl_date;

This query returns the aggregated amount and derived net unit price for a specific previous transaction, allowing an analyst to verify that unit and LIFO credit methods are correctly excluded from the net unit price numerator and that quantities are included only when no credit method rule is present. Restricting by PERIOD_SET_NAME supports period-close reconciliation across ledger configurations.