Search Results ar_rct_cust_h_v




Overview
Explore in AI Chat

Overview

AR_RCT_CUST_H_V is a reporting 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 expose customer-level ("H" level, meaning header) information sourced from Receivables Subledger Accounting (XLA) extract data, joined to the corresponding customer records held in the Oracle Trading Community Architecture (TCA) tables. The view presents a denormalized, report-friendly projection of customer attributes — account number, party name, party number, address and demographic fields, tax and fiscal references — keyed by the accounting EVENT_ID and LEDGER_ID that originate from the XLA extract.

The view name prefix "RCT" reflects the Receivables extract convention, and the "_H_" suffix indicates header-level granularity. It is most relevant in the context of Subledger Accounting extraction, where downstream reporting, reconciliation, or data-warehouse loads need to associate accounting events with the paying customer's descriptive attributes. The presence of columns such as RCT_CUST_FISCAL_CODE reflects localization requirements (for example, fiscal code reporting), which is why users searching for the term "rct_cust_fiscal_code" will find this view to be the owning object.

Underlying Base Objects

Per the documented ETRM metadata, AR_RCT_CUST_H_V is defined over three referenced base objects, all exposed through synonyms in the APPS schema:

  • AR_XLA_LINES_EXTRACT (SYNONYM) — the Subledger Accounting extract lines that carry the EVENT_ID, LEDGER_ID, PAYING_CUSTOMER_ID, and LEVEL_FLAG used to scope the query.
  • HZ_CUST_ACCOUNTS (SYNONYM) — the TCA customer account records, aliased CA3, providing the account number, customer type, account name, and global attribute descriptive flexfields.
  • HZ_PARTIES (SYNONYM) — the TCA party records, aliased P3, supplying party name, party number, party type, and the address/demographic and fiscal attributes.

The view text joins CA3.CUST_ACCOUNT_ID to L.PAYING_CUSTOMER_ID, restricts rows to L.LEVEL_FLAG = 'H', and joins CA3.PARTY_ID to P3.PARTY_ID. A hint (INDEX(L AR_XLA_LINES_EXTRACT_N1)) directs the optimizer to drive the extract lines through their index, confirming that the extract line set is the primary driver and the customer tables are looked up.

Key Columns

The columns fall into three logical groups:

Common Use Cases and Queries

Typical uses include XLA extract validation, customer-level reconciliation of accounting events, and feeding downstream reporting or data-warehouse extracts where the fiscal code or party address is required alongside the event.

SELECT RCT_CUST_PARTY_NAME, RCT_CUST_ACCOUNT_NUMBER,
       RCT_CUST_FISCAL_CODE, RCT_CUST_TAX_REFERENCE,
       RCT_CUST_CITY, RCT_CUST_COUNTRY, EVENT_ID, LEDGER_ID
FROM   APPS.AR_RCT_CUST_H_V
WHERE  LEDGER_ID = :p_ledger_id
AND    EVENT_ID  = :p_event_id;

A second common pattern retrieves all customer-header rows for a ledger run:

SELECT EVENT_ID, LEDGER_ID, RCT_CUST_NPA_NUMBER,
       RCT_CUST_PARTY_NUMBER, RCT_CUST_GLOBAL_ATTR1
FROM   APPS.AR_RCT_CUST_H_V
WHERE  LEDGER_ID = :p_ledger_id
ORDER  BY EVENT_ID;

Because the view is a simple join with no aggregation, it can be safely queried with standard predicates on LEDGER_ID and EVENT_ID, which are the most selective access paths.