Results for “so_customers_cr_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The SO_CUSTOMERS_CR_V view is an Order Entry (OE) module database object delivered within the Oracle E-Business Suite 12.1.1 and 12.2.2 release stack. It presents a consolidated, query-ready projection of active customer records alongside their associated relationship rows, enabling forms, concurrent programs, and integration interfaces to retrieve customer and related-customer information without encoding the join logic and status filtering directly into application code. The view name suffix "CR_V" indicates a customer relationship view, distinguishing it from the broader customer master views used elsewhere in the Receivables and Order Management schemas. In Oracle EBS reporting and integration contexts, this view serves as a lightweight access layer that masks the underlying join between the customer entity and the customer relationship entity, exposing only those customers whose status is active and whose prospect classification resolves to a true customer rather than a prospect. The documentation notes that the view is not implemented in the target database, meaning the definition is shipped as part of the application tier metadata and is created conditionally when the relevant product schema is installed. This distinction is important for DBAs and technical consultants validating object availability during an implementation or upgrade.

Underlying Base Objects

The view text joins two base tables from the Receivables schema:

• RA_CUSTOMERS — the primary customer entity, aliased as RC, providing the customer identity, name, number, and prospect classification.
• RA_CUSTOMER_RELATIONSHIPS — the relationship entity, aliased as RCR, providing the RELATED_CUSTOMER_ID and the relationship status used for filtering.

The join is expressed as an outer join: RC.CUSTOMER_ID = RCR.CUSTOMER_ID(+). This preserves customer rows that have no corresponding relationship record, so a customer appearing only in RA_CUSTOMERS is still returned with a NULL RELATED_CUSTOMER_ID. Two active-status predicates restrict the result set: RCR.STATUS(+) = 'A' applies the outer-join side so that inactive relationship rows are excluded without eliminating the parent customer, and RC.STATUS = 'A' restricts the customer itself to active records only. The final predicate, NVL(CUSTOMER_PROSPECT_CODE, 'CUSTOMER') = 'CUSTOMER', ensures that null prospect codes are treated as customers while explicit prospect classifications are filtered out. The ETRM metadata documents no separately registered base objects beyond these two tables.

Key Columns

• CUSTOMER_NAME — the display name of the customer, sourced from RA_CUSTOMERS, used in order entry forms and customer lookup lists.
• CUSTOMER_NUMBER — the unique customer number, commonly used in reporting joins and for reference in order headers and interfaces.
• CUSTOMER_ID — the primary key identifier of the customer record, the standard foreign key used throughout Order Management and Receivables tables.
• RELATED_CUSTOMER_ID — the identifier of the related customer established through RA_CUSTOMER_RELATIONSHIPS; NULL when no active relationship exists for the customer.

Common Use Cases and Queries

Because the user search referenced the "oe customer opening form," the most frequent application of this view is populating customer selection lists, validation logic, and opening-form lookups in Order Entry, where only active, non-prospect customers should be selectable. A typical query to drive such a form is:

SELECT CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_ID, RELATED_CUSTOMER_ID FROM SO_CUSTOMERS_CR_V WHERE CUSTOMER_NUMBER = :P_CUSTOMER_NUMBER;

For relationship-aware reporting, a join back to the customer master can resolve the related customer's name:

SELECT V.CUSTOMER_NUMBER, V.CUSTOMER_NAME, R.CUSTOMER_NAME AS RELATED_NAME FROM SO_CUSTOMERS_CR_V V, RA_CUSTOMERS R WHERE V.RELATED_CUSTOMER_ID = R.CUSTOMER_ID;

Integration interfaces commonly use the view to stage active customer extracts for downstream order import or master data synchronisation, relying on the built-in status and prospect filters to avoid inactive or prospect records. When the view is not implemented in a given database, the DBA should create it from the documented view text prior to deploying dependent customisations.