Search Results access_template_entity_code

Overview

ICX_RA_CUSTOMERS_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that belongs to the ICX (Oracle iProcurement) product family. As its description ("Customer View") indicates, it provides a denormalized, read-only presentation of customer master records drawn from the Receivables customer model. The view is defined as a projection of the RA_CUSTOMERS table, exposing the full set of customer attributes — identifiers, classification codes, tax settings, sales and financial profiling columns, descriptive flexfields, and audit columns — through a single named object.

The view serves a bridging role between the Receivables (AR) customer data model and iProcurement's need to present and validate customer information. In this sense, ICX_RA_CUSTOMERS_V is best understood as an integration and reporting convenience layer rather than a distinct data store. It does not hold data of its own; every row and column is sourced directly from the underlying Receivables tables. The ETRM record notes that the view is "Not implemented in this database," which is a common ETRM annotation indicating that the object is defined in the release but not necessarily created in every environment.

Underlying Base Objects

According to the documented view text, ICX_RA_CUSTOMERS_V is defined over a single base table: RA_CUSTOMERS. The view text is a straightforward SELECT that enumerates individual columns from RA_CUSTOMERS without joins, filters, or aggregation, so the view is essentially a column-limited mirror of the base table. No additional referenced base objects are documented in the ETRM metadata, and the "Referenced base objects" field lists none.

Because RA_CUSTOMERS is the Receivables customer master and, in R12, is tightly coupled with the trading community model (HZ_PARTIES and related HZ tables), the attributes surfaced here originate in the customer record and cascade from the party model. However, the view itself does not expose those HZ joins — it presents only the RA_CUSTOMERS columns. Practically, this means the view offers a stable, AR-centric slice of customer data suitable for consumers that do not need the full trading community graph.

Key Columns

• CUSTOMER_ID — Primary identifier for the customer record; the principal join key to other customer-related objects.
• CUSTOMER_NAME / CUSTOMER_NUMBER / ORIG_SYSTEM_REFERENCE / ORIG_SYSTEM — Customer identity and source-system reference; ORIG_SYSTEM distinguishes records imported from external systems.
• STATUS / CUSTOMER_TYPE / CUSTOMER_CLASS_CODE / CUSTOMER_CATEGORY_CODE / CUSTOMER_GROUP_CODE / CUSTOMER_SUBGROUP_CODE — Classification and lifecycle attributes used for segmentation and eligibility logic.
• THIRD_PARTY_FLAG — Indicates whether the customer is a third-party entity. This column is the specific attribute matched by the user's search term. It is exposed directly from RA_CUSTOMERS and is commonly used to partition or filter customer populations in reporting and integration queries.
• TAX_EXEMPT, TAX_EXEMPT_NUM, TAX_EXEMPT_REASON_CODE, TAX_CODE, TAX_REFERENCE, JGZZ_FISCAL_CODE — Tax-related attributes for exemption handling and fiscal reporting.
• PRIMARY_SALESREP_ID, PRIMARY_SPECIALIST_ID, SECONDARY_SPECIALIST_ID, SALES_CHANNEL_CODE, PRICE_LIST_ID, ORDER_TYPE_ID, PAYMENT_TERM_ID, FREIGHT_TERM, SHIP_VIA, FOB_POINT, WAREHOUSE_ID — Commercial and fulfillment defaults associated with the customer.
• NET_WORTH, NUM_OF_EMPLOYEES, POTENTIAL_REVENUE_CURR_FY, POTENTIAL_REVENUE_NEXT_FY, RANK, YEAR_ESTABLISHED, ANALYSIS_FY, FISCAL_YEAREND_MONTH — Financial profiling and analytical attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments, providing extensibility for customer-defined data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard WHO and concurrent-program audit columns.
• DUNNING_SITE_USE_ID, STATEMENT_SITE_USE_ID — References to site-use records for dunning and statement purposes.

Common Use Cases and Queries

Because ICX_RA_CUSTOMERS_V mirrors RA_CUSTOMERS, it is most useful where a consumer needs customer attributes without depending directly on the base table name. Typical scenarios include iProcurement customer lookups, third-party customer segregation, and cross-module reporting. To retrieve third-party customers, for example:

• SELECT customer_id, customer_name, customer_number, third_party_flag FROM icx_ra_customers_v WHERE third_party_flag = 'Y';
• SELECT customer_id, customer_name, customer_class_code FROM icx_ra_customers_v WHERE status = 'A' AND customer_type = 'R';
• SELECT customer_id, attribute1, attribute2 FROM icx_ra_customers_v WHERE attribute_category = 'MY_CATEGORY';

Analysts should note that the view is not implemented in every database and that, where it is absent, queries can be rewritten against RA_CUSTOMERS directly. As with all customer reporting, joining to site-use and party tables may be required for address and contact detail not exposed here.