Search Results credit_method_for_rules




Overview
Explore in AI Chat

Overview

APPS.AR_CM_NET_REVENUE is a reporting view in the Oracle E-Business Suite Receivables module that consolidates net revenue assignment data used by the Credit Memo against Revenue (CM) processing flow. Its principal function is to aggregate the underlying assignment records produced during revenue adjustment and credit memo application, exposing a grouped result set keyed by the originating transaction line, GL date, concurrent request, and accounting period set. In EBS 12.1.1 and 12.2.2 the view is delivered under the APPS schema and is treated as a read-only reporting object rather than a transactional entity.

The view is of particular relevance to implementers investigating the credit_method_for_rules attribute, since that column governs how amounts and quantities are weighted in the view's aggregation logic. It therefore appears in troubleshooting and diagnostic contexts whenever revenue credit methods such as UNIT, LIFO, and unpriced or quantity-based allocations are reconciled.

Underlying Base Objects

The view is defined over a single documented base object: AR_CM_NET_REVENUE_ASSIGNMENTS, itself a view. No additional base tables are referenced in the documented metadata; all columns projected by APPS.AR_CM_NET_REVENUE originate from that assignment view.

Because the layer beneath is already an assignment view, AR_CM_NET_REVENUE acts as a summarization layer, applying GROUP BY and aggregate functions over records that have already been assembled by the assignments logic. It does not introduce new joins, filters, or derivations beyond the decode-based conditional aggregation described below.

Key Columns

  • PREVIOUS_CUSTOMER_TRX_LINE_ID — Identifier of the originating transaction line to which the net revenue assignment relates; part of the grouping key.
  • PREVIOUS_CUSTOMER_TRX_ID — Header-level identifier of the prior transaction; also part of the grouping key.
  • REQUEST_ID — Concurrent request that generated the assignment records, allowing results to be isolated by program run.
  • GL_DATE — General Ledger date associated with the assignment, used in accounting-period grouping.
  • PERIOD_SET_NAME — Accounting period set, completing the grouping key.
  • SUM(AMOUNT) — Total assigned amount for the grouped records.
  • Derived weighted rate — Computed as the sum of amounts excluding UNIT and LIFO credit methods, divided by the sum of quantities where the credit method is null. The denominator uses DECODE(...,0,1,...) to prevent division by zero.

The treatment of CREDIT_METHOD_FOR_RULES is central: UNIT and LIFO amounts are excluded from the numerator, while only records with a blank credit method contribute quantity to the denominator. This yields a unit-based net revenue rate for quantity-driven allocations.

Common Use Cases and Queries

Typical usage includes reconciliation of credit memo revenue adjustments, verification that UNIT and LIFO methods are excluded from weighted-rate calculations, and auditing output by request or accounting period.

SELECT previous_customer_trx_id,
       previous_customer_trx_line_id,
       gl_date,
       period_set_name,
       request_id
FROM   apps.ar_cm_net_revenue
WHERE  request_id = :p_request_id;

Filtering by GL_DATE and PERIOD_SET_NAME supports period-close analysis, while joining the view back to AR_CM_NET_REVENUE_ASSIGNMENTS at the same grouping key allows the aggregated net revenue result to be traced to its individual assignment rows, including the underlying CREDIT_METHOD_FOR_RULES values.