Search Results ar_rct_cust_l_v




Overview
Explore in AI Chat

Overview

AR_RCT_CUST_L_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and is documented as an AR XLA Extract view. Its purpose is to denormalize and expose customer-level descriptive attributes alongside the Subledger Accounting (XLA) extract line data generated during Receivables accounting events. The suffix "_L_V" indicates a view defined at the line level ("L"), filtering the underlying extraction table on LEVEL_FLAG = 'L'.

The view plays a supporting role in the Accounting Methods Builder (AMB) and the Subledger Accounting extract architecture. When Receivables creates accounting events, XLA stores transactional and reference data in staging tables such as AR_XLA_LINES_EXTRACT. AR_RCT_CUST_L_V enriches those records with customer and party information (account number, category, address, tax reference, global attributes) by joining to the Trading Community Architecture (TCA) tables HZ_CUST_ACCOUNTS and HZ_PARTIES. This enables subledger accounting rules, diagnostics, and reporting to reference customer context without writing custom joins to TCA directly.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

  • AR_XLA_LINES_EXTRACT — the XLA extract staging table holding accounting event lines. The view selects EVENT_ID, LINE_NUMBER, LEDGER_ID, and PAYING_CUSTOMER_ID from this table and applies the LEVEL_FLAG = 'L' predicate.
  • HZ_CUST_ACCOUNTS — the TCA customer account table, aliased CA3, joined on CA3.CUST_ACCOUNT_ID = L.PAYING_CUSTOMER_ID.
  • HZ_PARTIES — the TCA party master table, aliased P3, joined on CA3.PARTY_ID = P3.PARTY_ID.

The definition carries an inline hint, /*+INDEX(L AR_XLA_LINES_EXTRACT_N1)*/, directing the optimizer to use the AR_XLA_LINES_EXTRACT_N1 index when scanning the extract table. A GROUP BY clause on all selected columns effectively enforces a distinct result set, preventing row duplication introduced by the join.

Key Columns

The column names are prefixed with RCT_CUST_ (Receivables Customer) to align with the XLA extract column-naming convention. Principal columns include:

Common Use Cases and Queries

Typical usages include diagnosing XLA extract contents for a given customer, validating customer attributes captured during accounting rule processing, and building reconciliation reports between Receivables transactions and their accounting events.

Example — retrieve extract lines for a specific customer account:

  • SELECT rct_cust_account_number, rct_cust_party_name, rct_cust_city, event_id, line_number, ledger_id FROM apps.ar_rct_cust_l_v WHERE rct_cust_account_id = :cust_account_id ORDER BY event_id, line_number;

Example — count distinct customers appearing in extract data for a ledger:

  • SELECT ledger_id, COUNT(DISTINCT rct_cust_account_id) cust_count FROM apps.ar_rct_cust_l_v GROUP BY ledger_id;

Because the view is a reporting and extraction artifact rather than a transactional interface, it should not be updated or used as an integration target. Its result set depends on the content of AR_XLA_LINES_EXTRACT, so it should be queried only after accounting extraction has been performed.