Results for “payment_term”

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

Overview

AR_LINE_REVENUE_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Receivables. It presents revenue information at the customer transaction line level for transactions that carry a revenue scheduling rule, including the associated accounting distributions, contract references, and reason-code driven adjustments. The view is a purpose-built reporting surface for the Revenue Recognition and line-level collections review processes; it consolidates data that would otherwise require joining RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, and Receivables reason-code audit records.

The object is a VIEW with VALID status and is classified under the AR – Receivables product. Because it exposes the MANUAL_OVERRIDE_FLAG column from the underlying audit trail, it is frequently queried when users investigate why a line's revenue or collection attributes differ from the values defaulted by the revenue scheduling rule. The view performs aggregation (MAX and SUM) over the base tables, so each row represents a single transaction line rather than an individual distribution line.

Underlying Base Objects

The view is defined over the following documented base objects:

• AR_RAMC_AUDIT_TRAIL (synonym) — the source of line-level reason and override flags, including LINE_COLLECTIBLE_FLAG, MANUAL_OVERRIDE_FLAG, and the reason flags for credit, payment term, forfeiture, refund, acceptance, cancellation, and fiscal adjustments.
• RA_CUSTOMER_TRX (synonym) — supplies transaction header attributes such as TRX_NUMBER, TRX_DATE, PRIMARY_SALESREP_ID, and ORG_ID.
• RA_CUSTOMER_TRX_LINES_ALL (synonym) — supplies the line-level descriptive and reference data, including LINE_NUMBER and DESCRIPTION.
• RA_CUST_TRX_LINE_GL_DIST_ALL (synonym) — provides the GL distribution rows and ACCOUNT_CLASS values; the view sums account-class-specific amounts and surfaces GL_DATE and GL_DATE2.
• RA_RULES (synonym) — the revenue scheduling rule name exposed as RULE_NAME.
• GL_SETS_OF_BOOKS (view) — the set of books name, identifier, and currency used for the transaction.
• HZ_CUST_ACCOUNTS (synonym) and HZ_PARTIES (synonym) — customer name and account number.
• OKC_K_HEADERS_B (synonym) — the contract number associated with the transaction line.
• ARPT_SQL_FUNC_UTIL (package) — provides GET_REFERENCE for the document reference number and GET_SALESREP_NAME_NUMBER for the salesperson name.
• ARP_BAL_UTIL (package) — provides GET_LINE_CM, used to compute credit memos applied against the line, which feeds the UNSCHEDULED_REVENUE calculation.
• MO_GLOBAL (package) — supports multi-org security on the row set.

Key Columns

• TRX_NUMBER, TRX_DATE, GL_DATE, GL_DATE2 — transaction identification and the accounting dates of the associated distributions.
• CUSTOMER_NAME, CUSTOMER_NUMBER, SET_OF_BOOKS_NAME, SET_OF_BOOKS_ID, CURRENCY_CODE — the customer and ledger context for the line.
• REFERENCE_NUMBER — the document reference derived via ARPT_SQL_FUNC_UTIL.GET_REFERENCE.
• LINE_COLLECTIBLE_FLAG and MANUAL_OVERRIDE_FLAG — flags read from AR_RAMC_AUDIT_TRAIL indicating whether the line is collectible and whether a manual override was applied during revenue or collections review.
• CREDIT and PAYMENT_TERM — decoded values from REASON_CREDIT_FLAG and REASON_PAYMENT_TERM_FLAG.
• LINE_AMOUNT, SCHEDULED_REVENUE, CREDIT_MEMOS, UNSCHEDULED_REVENUE — the revenue position of the line; UNSCHEDULED_REVENUE is computed as LINE_AMOUNT plus CREDIT_MEMOS less SCHEDULED_REVENUE.
• RULE_NAME, LINE_NUMBER, DESCRIPTION, CONTRACT_NUMBER, SALES_ORDER, SALESREP_NAME — descriptive and reference attributes of the transaction line.
• FORFEITURE_EXPIRATION, REFUND_EXPIRATION, ACCEPTANCE_EXPIRATION, CANCELLATION_EXPIRATION, FISCAL_EXPIRATION — conditional expiry dates emitted only when the corresponding reason flag is set to 'Y'.

Common Use Cases and Queries

The view supports revenue review, collections analysis, and audit of manual overrides. A common query identifies lines where the defaulting logic was overridden:

• Manual override audit: SELECT TRX_NUMBER, LINE_NUMBER, CUSTOMER_NAME, MANUAL_OVERRIDE_FLAG FROM AR_LINE_REVENUE_DETAILS_V WHERE MANUAL_OVERRIDE_FLAG = 'Y';
• Unscheduled revenue exposure: SELECT TRX_NUMBER, LINE_NUMBER, LINE_AMOUNT, SCHEDULED_REVENUE, UNSCHEDULED_REVENUE FROM AR_LINE_REVENUE_DETAILS_V WHERE UNSCHEDULED_REVENUE <> 0;
• Non-collectible line review: SELECT TRX_NUMBER, CUSTOMER_NAME, LINE_NUMBER FROM AR_LINE_REVENUE_DETAILS_V WHERE LINE_COLLECTIBLE_FLAG = 'N';
• Expiry monitoring: query REFUND_EXPIRATION and FORFEITURE_EXPIRATION for lines where the corresponding reason flag is enabled.

Because the underlying query applies aggregation with MAX and SUM and calls ARP_BAL_UTIL.GET_LINE_CM and ARPT_SQL_FUNC_UTIL functions per line, queries against this view can be expensive on high-volume installations. Predicates on TRX_NUMBER, TRX_DATE, or SET_OF_BOOKS_ID generally reduce the result set most effectively. The view is intended for reporting and integration rather than for transactional update; all columns are derived or read-only.