Search Results ra_customers_view




Overview
Explore in AI Chat

Overview

RA_CUSTOMERS_VIEW is a dictionary view in the Oracle E-Business Suite Receivables (AR) module, documented in the E-Business Suite Technical Reference Manual (ETRM) as a SINGLE_ORG view. Its purpose is to expose a focused, single-organization projection of the underlying RA_CUSTOMERS base table, presenting the core customer identity attributes required by most reporting, integration, and lookup scenarios without the full breadth of the customer master record. In EBS 12.1.1 and 12.2.2, the multi-org architecture separates customer information across organization contexts; a SINGLE_ORG view such as this eliminates the need for callers to apply operating unit or organization security predicates themselves, and instead returns the customer records associated with a single organization. This makes the view suitable as a stable, simplified interface for concurrent programs, Oracle Reports, OBIEE extracts, and custom PL/SQL that need a consistent customer identifier and name.

Underlying Base Objects

The ETRM documentation for this object lists the source as the RA_CUSTOMERS base table and records that no other base objects are referenced. The view text confirmed in the metadata is:

RA_CUSTOMERS is the Receivables customer master entity that stores bill-to and ship-to customer records, with CUSTOMER_ID as its primary key. Because RA_CUSTOMERS_VIEW projects only four columns from that single table, it introduces no joins or aggregations. The documented metadata notes that the view is "Not implemented in this database" for the excerpted environment, meaning the view may be created conditionally during the SINGLE_ORG view generation process. In environments where multi-org (Multiple Organization) is enabled and the single-org views are built, RA_CUSTOMERS_VIEW is instantiated by the corresponding SINGLE_ORG view creation scripts; where it is not implemented, queries against it will fail until the view is generated. This behavioral characteristic should be validated per instance before the view is used in production code.

Key Columns

The view exposes four columns, each inherited directly from RA_CUSTOMERS:

  • CUSTOMER_ID — The unique numeric identifier of the customer record; the primary key of RA_CUSTOMERS and the surrogate used in foreign key relationships across AR tables such as RA_CUSTOMER_PROFILES and RA_SITE_USES.
  • CUSTOMER_NAME — The customer's display name, the primary human-readable identifier used in invoices, statements, and reports.
  • CUSTOMER_NUMBER — The assigned customer number, which is the business-facing unique identifier (frequently used for cross-referencing and data conversion).
  • STATUS — The customer record status, indicating whether the customer is active or inactive for transaction processing.

Because the view exposes no organization or operating-unit column, callers relying on it in a multi-org context should confirm which organization's data the underlying single-org definition returns.

Common Use Cases and Queries

Typical uses include customer validation lookups, report parameter lists, extracts for downstream systems, and reconciliation of customer identifiers between interfaces and Receivables. A representative query retrieves active customer records by number:

  • SELECT customer_id, customer_name, customer_number FROM ra_customers_view WHERE status = 'A' ORDER BY customer_name;
  • SELECT customer_id, customer_name FROM ra_customers_view WHERE customer_number = :p_customer_number;

For integration, the view is commonly used to resolve a CUSTOMER_NUMBER supplied by an external system into the internal CUSTOMER_ID needed when inserting Receivables transactions. For reporting, it serves as a lightweight dimension source where only customer identity is required. Before deployment, confirm the view exists in the target instance, since the metadata indicates it may not be implemented in every database, and verify the STATUS value semantics against the operational lookup codes.