Results for “net_worth”

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

Overview

OE_RA_CUSTOMERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Order Management (ONT) product family. Its name follows the OE_RA convention, indicating a reporting and integration ("RA") view associated with Order Entry, and it is documented as VALID in the ETRM dictionary. The view exposes a consolidated, denormalized projection of customer account and party information, joining account-level attributes from HZ_CUST_ACCOUNTS with party-level attributes from HZ_PARTIES. It is intended primarily for reporting, concurrent program output, and inbound/outbound integration where a flattened customer record is required without directly joining the Trading Community Architecture (TCA) tables.

Because it resolves against HZ_CUST_ACCOUNTS and HZ_PARTIES through synonyms, OE_RA_CUSTOMERS_V provides a stable interface that shields downstream consumers from schema-level detail while preserving standard TCA semantics such as account number, party name, customer class, and tax attributes.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 lists two referenced base objects:

• HZ_CUST_ACCOUNTS (SYNONYM)
• HZ_PARTIES (SYNONYM)

The view joins these on the party identifier, with the account table supplying account-centric columns (customer account ID, account number, status, customer class, sales channel, price list, order type, attribute flexfields, and audit/WHO columns) and the party table supplying name, category, reference flags, tax reference, and assigned organization-specific fields. Many party columns are wrapped in DECODE expressions so that values such as SIC_CODE, ANALYSIS_FY, FISCAL_YEAREND_MONTH, EMPLOYEES_TOTAL, and potential revenue values are returned only when the party type is 'ORGANIZATION', and otherwise return NULL. Several positional columns (for example CUSTOMER_GROUP_CODE, CUSTOMER_SUBGROUP_CODE, RANK, NET_WORTH, ACCESS_TEMPLATE_ENTITY_CODE) are exposed as literal NULL placeholders, preserving column positions expected by legacy reports and interfaces even though the underlying data is not populated.

Key Columns

The view exposes the following significant columns, among others:

• CUST_ACCOUNT_ID — primary account identifier from HZ_CUST_ACCOUNTS.
• CUSTOMER_NAME / CUSTOMER_NUMBER — party name (SUBSTRB limited to 50 bytes) and account number.
• ORIG_SYSTEM_REFERENCE — source system reference for the account, used in integration matching.
• STATUS, CUSTOMER_TYPE, CUSTOMER_CLASS_CODE — account lifecycle and classification attributes.
• TAX_CODE, TAX_REFERENCE — tax classification and tax registration values. Note that the metadata does not expose a TAX_EXEMPT_NUM column; tax exemption data resides in other TCA entities (for example HZ_CUST_ACCOUNTS.TAX_CODE and related exempt handling), so searches on tax_exempt_num against this view will not resolve.
• PRIMARY_SALESREP_ID, SALES_CHANNEL_CODE, PRICE_LIST_ID, ORDER_TYPE_ID — default ordering and pricing context.
• ATTRIBUTE1 – ATTRIBUTE15 — the account descriptive flexfield segments.
• PARTY.CATEGORY_CODE, PARTY.CUSTOMER_KEY, PARTY.REFERENCE_USE_FLAG, PARTY.THIRD_PARTY_FLAG, PARTY.COMPETITOR_FLAG — party-level flags and categorization.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID.

Common Use Cases and Queries

Typical usages include reporting on customer accounts for a given sales channel, validating account setup for inbound order interfaces, and enriching extracts with party classification. A basic query is:

• SELECT cust_account_id, customer_name, customer_number, status, customer_class_code, tax_code, tax_reference FROM oe_ra_customers_v WHERE status = 'A' ORDER BY customer_number;
• SELECT cust_account_id, customer_number, category_code FROM oe_ra_customers_v WHERE orig_system_reference = :p_source_ref; — used to resolve an external account reference to a TCA account.
• SELECT customer_number, customer_name, primary_salesrep_id, price_list_id, order_type_id FROM oe_ra_customers_v WHERE customer_class_code = 'RETAIL'; — order defaulting and pricing review.

Consumers should treat the view as read-only. Where tax exemption numbers are required, a direct query to the appropriate TCA exemption tables is necessary, since the view does not expose a tax_exempt_num column.