Results for “arfv_ar_customer_trans_lines”

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

Overview

The ARFV_AR_CUSTOMER_TRANS_LINES view is a reporting and integration construct owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes customer transaction line information in a denormalized, user-friendly form, joining transactional line data with descriptive flexfield references, transactional context, unit of measure descriptions, accounting rule names, and operating unit names. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is commonly consumed by reports, concurrent programs, and interface extracts that require a consolidated line-level view of customer transactions without the multiple joins that the base tables would otherwise demand.

Because the view is defined WITH READ ONLY, it is designed strictly for querying and cannot be used as an updateable entity. It is frequently leveraged in extracts destined for general ledger, revenue recognition, or downstream data warehousing processes, especially where accounting rule attributes and flexfield descriptors must be surfaced alongside standard transaction line attributes.

Underlying Base Objects

The view is defined over the following documented base objects in the APPS schema:

• RA_CUSTOMER_TRX_LINES — the primary line-level transaction table, aliased as CTL.
• RA_CUSTOMER_TRX — the transaction header table, aliased as CT, providing transaction number, date, and completion status.
• RA_RULES — the accounting rule definition table, aliased as RUL, providing the accounting rule name.
• MTL_UNITS_OF_MEASURE — the unit of measure table, aliased as UOM, providing the UOM description.
• HR_ALL_ORGANIZATION_UNITS — the organization units table, aliased as AOU, providing the operating unit name.

Additional self-joins to RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES retrieve previous and initial transaction references, exposing original and prior credit transaction numbers and line numbers. All joins (other than the driving CTL-to-CT join) are outer joins, ensuring lines are returned even where related lookup data is absent.

Key Columns

The view exposes several columns of particular interest to reporting and integration:

• TRANSACTION_LINE_ID and TRANSACTION_LINE_NUMBER — the surrogate and user-visible line identifiers.
• AMOUNT, UNIT_PRICE, QUANTITY_ORDERED, QUANTITY_CREDITED, QUANTITY_INVOICED — core monetary and quantity attributes.
• ACCOUNTING_RULE_ID and ACCOUNTING_RULE_DURATION — the accounting rule reference and its duration, critical for revenue recognition queries.
• RUL — the accounting rule name resolved through RA_RULES.
• "_LA:REASON" — a flexfield-style descriptor for the reason code, resolved via AR_LOOKUPS.
• RUL_START_DATE — the accounting rule start date governing revenue scheduling.
• SALES_ORDER_NUMBER, SALES_ORDER_LINE, SALES_ORDER_DATE — order-referencing attributes.
• ITEM_DESCRIPTION and the UOM code — descriptive item and UOM information.
• ORG_ID, LAST_UPDATE_DATE, CREATED_BY and related audit columns — multi-org and audit tracking fields.

Common Use Cases and Queries

A frequent requirement is identifying invoice lines that carry an accounting rule, for example when auditing revenue recognition setup or extracting rule-driven lines. A representative query is:

• SELECT TRANSACTION_LINE_NUMBER, AMOUNT, ACCOUNTING_RULE_DURATION, RUL FROM ARFV_AR_CUSTOMER_TRANS_LINES WHERE ACCOUNTING_RULE_DURATION IS NOT NULL;
• SELECT TRANSACTION_LINE_NUMBER, AMOUNT, UNIT_PRICE, QUANTITY_INVOICED FROM ARFV_AR_CUSTOMER_TRANS_LINES WHERE ORG_ID = :p_org_id;
• SELECT TRANSACTION_LINE_NUMBER, AMOUNT, RUL_START_DATE, RUL FROM ARFV_AR_CUSTOMER_TRANS_LINES WHERE RUL IS NOT NULL ORDER BY RUL_START_DATE;

Because the view already resolves lookups, UOM, organization, and rule names, it eliminates the need for repetitive joins in custom reports, reconciliation extracts, and data warehouse staging. Query performance depends on the underlying base tables, so filtering by ORG_ID, transaction date, or line identifiers is recommended.