Search Results rct_cust_state




Overview
Explore in AI Chat

Overview

APPS.AR_RCT_CUST_H_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema. It is classified as an internal Oracle view (FND Design Data: AR.AR_RCT_CUST_H_V) and carries the standard Oracle Internal Use Only warning: Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. The view presents a horizontal (denormalized) projection of customer attribute data associated with Receivables tax and extract processing, exposing customer account, party, address, and fiscal identifiers alongside the EVENT_ID and LEDGER_ID context columns. Its name and column set indicate it is a horizontal "customer header" view designed to supply Receivables tax calculation and reporting extracts with the customer attributes required for jurisdiction determination, fiscal reporting, and reconciliation.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, AR_RCT_CUST_H_V is defined over the following referenced base objects:

  • AR_XLA_LINES_EXTRACT (referenced through a synonym) — the Subledger Accounting (XLA) lines extract, which supplies the EVENT_ID and LEDGER_ID context that links each row to an accounting event and ledger.
  • HZ_CUST_ACCOUNTS (referenced through a synonym) — the Trading Community Architecture customer accounts table, source of customer account number, account identifier, and category/group attributes.
  • HZ_PARTIES (referenced through a synonym) — the TCA parties table, source of party name, party number, and party type, along with person and organization attributes.

The published query text confirms this lineage by exposing the view over the AR_RCT base object family, with the columns drawn from the Receivables customer/tax structures joined to the underlying TCA customer and party entities.

Key Columns

The view exposes 27 columns. The most significant are:

Common Use Cases and Queries

Because the view is internal, it is intended primarily for Oracle Applications programs performing Receivables tax and extract processing. Analysts nevertheless query it for reconciliation and audit of customer attributes against the XLA lines extract. The most common scenarios involve retrieving the customer type and party classification for a given event, and joining the extract context back to the accounting event and ledger. A representative query is:

  • SELECT rct_cust_type, rct_cust_account_number, rct_cust_party_name, rct_cust_party_type, rct_cust_country, rct_cust_tax_reference, event_id, ledger_id FROM apps.ar_rct_cust_h_v WHERE rct_cust_type = :p_cust_type;
  • SELECT event_id, ledger_id, COUNT(*) FROM apps.ar_rct_cust_h_v GROUP BY event_id, ledger_id;
  • SELECT rct_cust_account_id, rct_cust_party_id, rct_cust_cat_code, rct_cust_group_type FROM apps.ar_rct_cust_h_v WHERE rct_cust_party_number = :p_party_number;

Given the Oracle Internal Use Only designation, any direct querying should be confined to read-only diagnostics and reporting, and should not be embedded in custom production code that Oracle support would not cover.