Search Results rule_end_date

Overview

RA_CUSTOMER_TRX_LINES_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It presents transaction line information from RA_CUSTOMER_TRX_LINES_ALL, joining to customer, site, location, tax, and memo line sources to expose a denormalized, reporting-friendly projection of a Receivables transaction line. Status is VALID and the object is documented from Release 11.5 onward, remaining valid through EBS 12.1.1 and 12.2.2.

The view is commonly used in Receivables reporting, extracts, and downstream integration. Because it resolves customer language, tax override behavior, and revenue scheduling attributes, it is a convenient source for invoice line analytics where the base table would otherwise require numerous joins. The presence of the RULE_START_DATE column, together with ACCOUNTING_RULE_ID and ACCOUNTING_RULE_DURATION, means the view is frequently queried when users investigate revenue recognition rule dates — including the search term rule_end_date, which conceptually corresponds to the end of the revenue recognition schedule derived from the rule start date plus duration.

Underlying Base Objects

The primary base object is the synonym RA_CUSTOMER_TRX_LINES_ALL, aliased CTL in the view text. The view also references AR_CUSTOMER_TRX, RA_CUST_TRX_TYPES_ALL, RA_RULES, AR_VAT_TAX, AR_MEMO_LINES, and AR_LOOKUPS, together with HR and HZ synonyms such as HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. Organization and unit-of-measure context come from ORG_ORGANIZATION_DEFINITIONS and MTL_UNITS_OF_MEASURE.

PL/SQL packages referenced include ARP_TRX_LINE_UTIL, ARP_BAL_UTIL, ARPT_SQL_FUNC_UTIL, ARH_ADDR_PKG, FND_DATE, FND_GLOBAL, HR_GENERAL, HR_SECURITY, and MO_GLOBAL. These packages supply derived values such as secured customer access, date formatting, and multi-org context, which explains why the view is heavier than a simple join but yields richer output.

Key Columns

• CUSTOMER_TRX_LINE_ID / CUSTOMER_TRX_ID — primary line and parent transaction identifiers used for joins to RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL.
• LINE_NUMBER, LINE_TYPE, DESCRIPTION — line ordering, line classification, and descriptive text.
• QUANTITY_ORDERED, QUANTITY_INVOICED, QUANTITY_CREDITED — quantity metrics; QUANTITY_CREDITED is NVL'd against QUANTITY_INVOICED for reporting.
• UNIT_SELLING_PRICE, EXTENDED_AMOUNT, REVENUE_AMOUNT, GROSS_EXTENDED_AMOUNT — pricing and revenue amounts, with NVL fallbacks to the standard selling price and extended amount.
• ACCOUNTING_RULE_ID, ACCOUNTING_RULE_DURATION, RULE_START_DATE, AUTORULE_COMPLETE_FLAG, AUTORULE_DURATION_PROCESSED — revenue recognition scheduling information; RULE_START_DATE is the anchor from which rule end dates are computed.
• TAXABLE_FLAG, TAX_RATE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, VAT_TAX_ID, SALES_TAX_ID — tax determination attributes.
• SALES_ORDER, SALES_ORDER_LINE, SALES_ORDER_SOURCE, MOVEMENT_ID — order management lineage.
• SET_OF_BOOKS_ID and audit columns (CREATED_BY, LAST_UPDATE_DATE, etc.) — multi-org and audit context.

Common Use Cases and Queries

Typical usage includes invoice line extracts, revenue schedule analysis, and tax exception reporting. Because rule end dates are not stored directly, analysts combine RULE_START_DATE with ACCOUNTING_RULE_DURATION to derive them.

SELECT customer_trx_line_id,
       customer_trx_id,
       line_number,
       accounting_rule_id,
       rule_start_date,
       ADD_MONTHS(rule_start_date, accounting_rule_duration - 1) AS rule_end_date
FROM   apps.ra_customer_trx_lines_v
WHERE  rule_start_date IS NOT NULL
AND    accounting_rule_id IS NOT NULL;

The view is also useful for joining transaction headers to line-level revenue and tax attributes:

SELECT v.customer_trx_id, v.line_number, v.extended_amount, v.tax_rate
FROM   apps.ra_customer_trx_lines_v v
WHERE  v.set_of_books_id = :sob
AND    v.creation_date >= :start_date;

Integration and reconciliation scripts frequently read this view rather than RA_CUSTOMER_TRX_LINES_ALL directly, since the derived columns reduce application-side logic. Any derived rule end date should always be validated against AR revenue recognition setup and RA_RULES.