Results for “rhx_dp_l_customer_v”

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

Overview

RHX_DP_L_CUSTOMER_V is a custom database view registered against the MRP (Master Scheduling/MRP) product family in Oracle E-Business Suite. Its description in the ETRM repository is marked as "Retrofitted," indicating that the object was introduced or re-created by a customer-specific or partner-specific extension (a "RHX" custom prefix) rather than by standard Oracle-delivered functionality. The ETRM documentation for 12.2.2 further states "Not implemented in this database," meaning that the view is catalogued as documented metadata but was not physically present in the reference environment from which the ETRM extract was generated. It therefore exists in customer instances only where the corresponding customization has been deployed.

Functionally, the view presents a de-normalised, list-of-values (LOV) style representation of customer records. Its naming convention (L for List, plus the RHX_DP custom prefix) suggests it is consumed by an Oracle Data Provider or custom form/report element requiring a simple key-flex value pair. Its role in EBS reporting and integration is to supply a curated set of customer identifiers alongside a composite display value, suitable for parameter prompts, concurrent program LOVs, or downstream extracts.

Underlying Base Objects

The only documented referenced base object is RA_CUSTOMERS, the Receivables customer master table that stores customer identity, numbering, and classification data. The view selects exclusively from this table, applying a SELECT DISTINCT to eliminate duplicate rows arising from the customer/party model. No joins to HZ_PARTIES, HZ_CUST_ACCOUNTS, or other Trading Community Architecture (TCA) tables are documented, and the ETRM record lists "none documented" for additional base objects. This makes the view a thin projection over RA_CUSTOMERS rather than a multi-entity consolidation. Because RA_CUSTOMERS is largely a compatibility synonym into the TCA/Receivables model in 12.1.1 and 12.2.2, administrators should verify how the view behaves against the actual deployment patch level.

Key Columns

• CUSTOMER_ID — The numeric primary key of the customer record in RA_CUSTOMERS; serves as the returned (hidden) value of the LOV.
• CUSTOMER_NUMBER — The human-readable customer account number, useful for search and reconciliation.
• CUSTOMER_TYPE — The classification of the customer record (for example, an internal or external designation as held on RA_CUSTOMERS).
• CUSTOMER — A concatenated display column built as RC.CUSTOMER_NAME joined by a configurable delimiter to RC.CUSTOMER_ID. Because it appends the ID, it does not always show a plain name; consumers should be aware of this formatting when using the column for matching or display.

The composite CUSTOMER column derives its separator from RHX_DP.GET_PARAMETER('RHX_DP_P_DELIMITER'), a custom parameter lookup function. The delimiter is therefore configurable per environment and may differ between instances.

Common Use Cases and Queries

The view is typically used to populate LOVs, report parameters, and integration staging tables where a single customer identifier and a readable label are required. The delimiter function must be resolvable at runtime, or the query will fail; this dependency is the most common cause of errors when deploying the view.

A representative query retrieving a filtered customer list is:

SELECT customer_id,
       customer,
       customer_number,
       customer_type
FROM   rhx_dp_l_customer_v
WHERE  UPPER(customer) LIKE UPPER(:p_search || '%')
ORDER  BY customer;

To validate the effective delimiter and resulting labels:

SELECT rhx_dp.get_parameter('RHX_DP_P_DELIMITER') AS delimiter
FROM   dual;

Because the view is marked as not implemented in the reference database and carries only RA_CUSTOMERS as a documented source, implementers should confirm object existence, grants, and the availability of the RHX_DP package and its parameter before relying on it. It should not be treated as an Oracle-standard interface; it is a retrofit artifact subject to the supporting customization's lifecycle.