Search Results gsa_indicator_flag




Overview
Explore in AI Chat

Overview

APPS.AR_RCT_CUST_L_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module that exposes receiving customer (RCT, i.e., "Receipt Customer") attributes in a denormalized, report-ready form. The view flattens data from the Receivables Subledger Accounting extract line table and joins it to the Trading Community Architecture (TCA) customer model, presenting a single row per extract line at the "L" (Line) level. The naming convention reflects its purpose: AR (Receivables), RCT (receipt / receiving customer), CUST (customer), L (line level), and _V (view).

In Oracle EBS 12.1.1 and 12.2.2, this view sits within the Subledger Accounting (SLA) and Receivables extract pipeline, where XLA extract lines are populated for downstream processing, including receipt-related accounting and reporting. It is principally used for reporting, diagnostics, and integration where the line-level receipt customer context must be combined with TCA party and customer account attributes. Notably, the user-searched term gsa_indicator_flag is exposed by this view as the alias rct_cust_gsa_flag, sourced from HZ_PARTIES.GSA_INDICATOR_FLAG. This flag identifies parties associated with the U.S. General Services Administration (GSA) schedule, a mandatory attribute for government-commercial reporting in Oracle Receivables and Order Management.

Underlying Base Objects

Per the documented ETRM metadata, APPS.AR_RCT_CUST_L_V is defined over three referenced base objects, each represented as a synonym under the APPS schema:

  • AR_XLA_LINES_EXTRACT — the Receivables Subledger Accounting extract line table (aliased l). Drives the view's grain and restricts rows to line-level entries via l.level_flag = 'L'.
  • HZ_CUST_ACCOUNTS — the TCA customer accounts table (aliased ca3). Joined on ca3.cust_account_id = l.paying_customer_id.
  • HZ_PARTIES — the TCA parties table (aliased p3). Joined on ca3.party_id = p3.party_id.

The view text applies the hint /*+INDEX(l ar_xla_lines_extract_n1)*/ to drive access to the extract line table via its N1 index, and terminates with an explicit GROUP BY across all projected columns to eliminate duplicate rows arising from multi-join fan-out. A supporting index on AR_XLA_LINES_EXTRACT (AR_XLA_LINES_EXTRACT_N1) is therefore expected to exist for optimal plan selection.

Key Columns

Columns fall into three logical groups reflecting their source tables and reporting intent:

Common Use Cases and Queries

Typical uses include reconciling extract lines to customer identity, validating GSA party configuration for government reporting, and building custom receipt-customer datasets for integration or analytics. A simple diagnostic query isolating the search term follows:

SELECT rct_cust_account_number, rct_cust_party_name, rct_cust_gsa_flag FROM apps.ar_rct_cust_l_v WHERE rct_cust_gsa_flag = 'Y';

To join extract lines back to their ledger context for a specific ledger:

SELECT event_id, line_number, ledger_id, rct_cust_account_number, rct_cust_gsa_flag FROM apps.ar_rct_cust_l_v WHERE ledger_id = :p_ledger_id ORDER BY event_id, line_number;

Because the view spans TCA and SLA schema objects, query performance depends on the AR_XLA_LINES_EXTRACT_N1 index and on the selectivity of level_flag and customer joins. Filtering by ledger, event, or account number before aggregation is recommended; avoid unrestricted full-view scans on large extract populations.