Results for “credit_method_for_rules”

50+ results




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

Overview

AR_CM_NET_REVENUE_ASSIGNMENTS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) module. Its documented purpose is to determine the credit memo lines that credit a given invoice line. In practice, the view functions as a reconciliation bridge between original invoice revenue distributions and the credit memo activity applied against them, exposing the net revenue assignment amount that results after credit memos are considered.

Because the object is a VIEW rather than a stored table, it does not hold data of its own. Instead, it derives its result set at runtime from a UNION of two queries: one branch that reads credit memo amounts applied to invoice lines, and a second branch that reads revenue assignments recorded directly against those invoice lines. This design allows downstream financial reporting, revenue recognition processing, and integration extracts to obtain a consolidated per-line net revenue figure without issuing separate queries against multiple base objects.

The view is available and VALID in both Oracle EBS 12.1.1 and 12.2.2. It is typically consumed by revenue recognition, general ledger reconciliation, and subledger accounting (SLA) related processes rather than being surfaced directly in standard Receivables forms.

Underlying Base Objects

The ETRM-documented base objects referenced by the view are:

The view joins these objects primarily on CUSTOMER_TRX_LINE_ID, PREVIOUS_CUSTOMER_TRX_LINE_ID, and PREVIOUS_CUSTOMER_TRX_ID, using the line-level "previous" reference columns to trace credit memo lines back to the invoice lines they credit. The join to FND_CURRENCIES uses the invoice currency code, and the join to GL_SETS_OF_BOOKS uses the set of books identifier on the transaction.

Key Columns

  • CUSTOMER_TRX_LINE_ID — the transaction line identifier to which the revenue or credit amount applies.
  • PREVIOUS_CUSTOMER_TRX_LINE_ID — the originating invoice line referenced by a credit memo line.
  • PREVIOUS_CUSTOMER_TRX_ID — the identifier of the original invoice transaction.
  • REQUEST_ID — the concurrent request identifier associated with the row.
  • GL_DATE — the accounting date for the amount.
  • AMOUNT — the revenue assignment amount, rounded according to currency precision or minimum accountable unit, and forced to zero where the transaction is incomplete (COMPLETE_FLAG = 'N').
  • QUANTITY — the quantity credited or assigned, defaulted to zero where null.
  • CREDIT_METHOD_FOR_RULES — the credit method rule configured on the transaction, used to drive credit memo behavior.
  • PERIOD_SET_NAME — the accounting period set name from the ledger.

Common Use Cases and Queries

Typical uses include reconciling invoice revenue against applied credit memos, validating rounding behavior per currency, and feeding revenue recognition or SLA reporting extracts.

To retrieve net revenue assignments for a specific invoice line:

  • SELECT customer_trx_line_id, previous_customer_trx_line_id, amount, quantity, gl_date FROM ar_cm_net_revenue_assignments WHERE previous_customer_trx_line_id = :line_id;

To summarize net revenue by ledger period:

  • SELECT period_set_name, gl_date, SUM(amount) FROM ar_cm_net_revenue_assignments GROUP BY period_set_name, gl_date;

Because the view is a UNION of credit memo and revenue assignment branches, consumers should expect one row per qualifying source line and should apply their own aggregation where a single net figure per invoice line is required.