Results for “amount_mode”

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

Overview

AR_REVENUE_ADJUSTMENTS_ALL is an Oracle Receivables (AR) base table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores information about specific revenue adjustments. It records the instructions and resulting allocations used to redistribute revenue across sales representatives, sales groups, categories, inventory items, and transaction lines on a customer transaction. A single revenue adjustment row defines the source ("from") and destination ("to") attributes together with the adjustment amount or percentage and the sales credit type, providing the transactional basis for revenue reallocation and the associated accounting distribution.

Under the Data Vault classification heuristic mined from its foreign key structure, AR_REVENUE_ADJUSTMENTS_ALL is best modeled as a link. Its structure is dominated by foreign key references to master and transaction entities—customer transactions, transaction lines, sales representatives, sales groups, inventory categories, applications, concurrent requests, and users—rather than descriptive or time-variant attributes. In Data Vault terms it should be considered a link connecting these hubs, with the adjustment-specific descriptive columns treated as link-level satellite attributes. This classification is a modeling suggestion only; in native EBS terms the object is a standard transactional table owned by the AR schema with status VALID.

Key Information Stored

The table contains 50 documented columns. The most significant are:

• REVENUE_ADJUSTMENT_ID — surrogate primary key, enforced by AR_REVENUE_ADJUSTMENTS_PK and the unique index AR_REVENUE_ADJUSTMENTS_U1. This is the only documented unique business-key candidate.
• REVENUE_ADJUSTMENT_NUMBER — user-facing identifier for the adjustment.
• CUSTOMER_TRX_ID — the customer transaction to which the adjustment applies, joining to RA_CUSTOMER_TRX_ALL.
• APPLICATION_DATE and GL_DATE — the effective date and accounting date of the adjustment.
• TYPE, REASON_CODE, STATUS, COMMENTS — classification, justification, workflow state, and free-text notes.
• AMOUNT_MODE, AMOUNT, PERCENT — whether the adjustment is expressed as an absolute amount or a percentage, and its value.
• LINE_SELECTION_MODE — determines how transaction lines are selected for adjustment.
• FROM_SALESREP_ID / TO_SALESREP_ID, FROM_SALESGROUP_ID / TO_SALESGROUP_ID — source and destination sales representatives and sales groups.
• SALES_CREDIT_TYPE — the sales credit basis affected by the adjustment.
• FROM_CATEGORY_ID / TO_CATEGORY_ID, FROM_INVENTORY_ITEM_ID / TO_INVENTORY_ITEM_ID — category and item redirection targets.
• FROM_CUST_TRX_LINE_ID / TO_CUST_TRX_LINE_ID — source and destination transaction lines.
• ORG_ID — operating unit identifier (multi-org).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_APPLICATION_ID — audit and concurrent program context. Fifteen ATTRIBUTE columns provide descriptive flexibility.

Common Use Cases and Queries

Typical scenarios include reconciliation of revenue adjustments per transaction, analysis of sales credit redistribution, audit of adjustments that redirect categories or items, and reporting on adjustments generated by concurrent programs.

Adjustments for a given transaction:

SELECT revenue_adjustment_number, application_date, amount, percent,
       status, reason_code
FROM   ar.ar_revenue_adjustments_all
WHERE  customer_trx_id = :p_trx_id
ORDER  BY application_date;

Sales representative redistribution:

SELECT a.revenue_adjustment_number, a.sales_credit_type,
       fr.salesrep_name  from_salesrep,
       tr.salesrep_name  to_salesrep,
       a.amount, a.percent
FROM   ar.ar_revenue_adjustments_all a,
       ar.ra_salesreps_all fr,
       ar.ra_salesreps_all tr
WHERE  a.from_salesrep_id = fr.salesrep_id
AND    a.to_salesrep_id   = tr.salesrep_id
AND    a.status = 'COMPLETE';

Adjustments by operating unit and date range:

SELECT org_id, COUNT(*), SUM(NVL(amount,0))
FROM   ar.ar_revenue_adjustments_all
WHERE  gl_date BETWEEN :start_date AND :end_date
GROUP  BY org_id;

Because RA_CUST_TRX_LINE_GL_DIST_ALL and RA_CUST_TRX_LINE_SALESREPS_ALL reference this table via REVENUE_ADJUSTMENT_ID, reconciliation queries commonly join those distributions and sales credits back to the originating adjustment.

Related Objects

• RA_CUSTOMER_TRX_ALL — referenced through CUSTOMER_TRX_ID; the invoice, debit memo, or credit memo being adjusted.
• RA_CUSTOMER_TRX_LINES_ALL — referenced twice through FROM_CUST_TRX_LINE_ID and TO_CUST_TRX_LINE_ID.
• RA_CUST_TRX_LINE_GL_DIST_ALL — references AR_REVENUE_ADJUSTMENTS_ALL.REVENUE_ADJUSTMENT_ID; holds resulting accounting distributions.
• RA_CUST_TRX_LINE_SALESREPS_ALL — references REVENUE_ADJUSTMENT_ID; holds resulting sales credits.
• RA_SALESREPS_ALL — referenced through FROM_SALESREP_ID and TO_SALESREP_ID.
• JTF_RS_GROUPS_B — referenced through FROM_SALESGROUP_ID and TO_SALESGROUP_ID.
• MTL_CATEGORIES_B — referenced through FROM_CATEGORY_ID and TO_CATEGORY_ID.
• FND_CONCURRENT_REQUESTS, FND_APPLICATION, FND_USER — referenced through REQUEST_ID, PROGRAM_APPLICATION_ID, and LAST_UPDATED_BY for audit and process tracking.