Results for “ar_customers”

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

Overview

The AR_CUSTOMERS view is a reporting and integration construct in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema. It presents a consolidated, denormalized representation of customer information by joining customer account records to their associated party records. As indicated in the documentation, the view is designated as Release 11.5 only, meaning it reflects the pre-multi-org-access (MOAC) and pre-Trading Community Architecture (TCA)-complete data model of the earlier release. In practice, the surviving 11.5-era definition is retained as a valid APPS object and is exposed for backward compatibility, particularly for custom reports, interfaces, and legacy code that reference the historical AR_CUSTOMERS interface.

Because the view is defined over the TCA base objects HZ_CUST_ACCOUNTS and HZ_PARTIES, it functions as an abstraction layer that shields callers from the underlying normalized structure. It is principally used in reporting and inbound/outbound integrations where a flattened customer record is required.

Underlying Base Objects

The documented base objects for AR_CUSTOMERS are:

• HZ_CUST_ACCOUNTS (accessed via a synonym) — the TCA customer account entity, supplying account number, status, orig system reference, class, type, salesrep, tax code, price list, freight terms, order type, sales channel, warehouse, and descriptive flexfield attributes.
• HZ_PARTIES (accessed via a synonym) — the TCA party entity, supplying party name, customer key, category, party type, tax reference, taxpayer ID, SIC code, GSA indicator, and various organization-level attributes such as mission statement, employee totals, potential revenue, fiscal year-end, and competitor/reference/third-party flags.

The join is anchored on the customer account's party relationship, with organization-specific attributes conditionally projected using DECODE on PARTY_TYPE. The view text confirms that the two TCA tables are the sole documented base objects.

Key Columns

• CUSTOMER_ID — sourced from CUST_ACCOUNT_ID; the primary identifier for the customer account.
• CUSTOMER_NAME — SUBSTRB of PARTY_NAME, truncated to 50 bytes for legacy width constraints.
• CUSTOMER_NUMBER — the account number from HZ_CUST_ACCOUNTS.
• CUSTOMER_KEY — the party customer key.
• STATUS / ORIG_SYSTEM_REFERENCE — account status and the originating system reference for imported records.
• CUSTOMER_PROSPECT_CODE — a literal 'CUSTOMER' constant in this view.
• CUSTOMER_CATEGORY_CODE, CUSTOMER_CLASS_CODE, CUSTOMER_TYPE — TCA classification attributes.
• PRIMARY_SALESREP_ID, PRICE_LIST_ID, FREIGHT_TERM, ORDER_TYPE_ID, SALES_CHANNEL_CODE, WAREHOUSE_ID — commercial and order-default attributes.
• SIC_CODE, GSA_INDICATOR, MISSION_STATEMENT, NUM_OF_EMPLOYEES, POTENTIAL_REVENUE_CURR_FY/NEXT_FY, FISCAL_YEAREND_MONTH, YEAR_ESTABLISHED, ANALYSIS_FY — organization-only attributes, returned as NULL for non-organization party types.
• TAX_REFERENCE, TAX_CODE, TAXPAYER_ID (JGZZ_FISCAL_CODE), COMPETITOR_FLAG, REFERENCE_USE_FLAG, THIRD_PARTY_FLAG — tax and party-level flags.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..N — descriptive flexfield columns from the customer account.

Common Use Cases and Queries

Typical scenarios include customer master extracts for data warehousing, legacy interface reconciliation, and quick lookups in custom concurrent programs. A representative query retrieves the core identification and status of active customers:

• SELECT customer_id, customer_name, customer_number, status FROM apps.ar_customers WHERE status = 'A';
• SELECT customer_id, customer_name, customer_class_code, primary_salesrep_id FROM apps.ar_customers WHERE customer_category_code = 'R';
• SELECT customer_number, tax_reference, taxpayer_id FROM apps.ar_customers WHERE tax_reference IS NOT NULL;

Analysts should note the "Release 11.5 only" designation: new development should prefer the current TCA views (for example, HZ_CUST_ACCOUNTS_V2 and related party views) rather than this legacy construct.