Results for “analysis_fy”

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

Overview

AR_CUSTOMERS_ALL_V is a legacy compatibility view in the APPS schema of Oracle E-Business Suite, owned by the Receivables (AR) product. It was originally introduced in Release 11.5 to expose customer master data through the older AR customer column naming conventions while sourcing that data from the Oracle Trading Community Architecture (TCA) model. In 12.1.1 and 12.2.2 the view remains valid and is retained primarily for backward compatibility with custom reports, interfaces, and third-party integrations written against the 11.5 data model. It presents one row per customer account, joining the TCA customer account record to its underlying party record, and is typically used for read-only reporting rather than transactional processing. Because Oracle's strategic direction is the HZ_CUST_ACCOUNTS and HZ_PARTIES TCA tables, this view should be treated as a reporting convenience layer, not a source of truth for new development.

Underlying Base Objects

Per the documented ETRM metadata, AR_CUSTOMERS_ALL_V is defined over two base objects: HZ_CUST_ACCOUNTS (accessed via a synonym) and HZ_PARTIES (accessed via a synonym). The view aliases HZ_CUST_ACCOUNTS as CUST and HZ_PARTIES as PARTY. HZ_CUST_ACCOUNTS supplies the account-level attributes—account number, status, customer class, customer type, orig system reference, credit and order-management defaults—while HZ_PARTIES supplies party-level attributes such as party name, customer key, tax reference, and the profile classification flags. The join links each customer account to its owning party, so account and party attributes are presented together in the flat, denormalized shape that 11.5-era code expects.

Key Columns

• CUSTOMER_ID — mapped from CUST.CUST_ACCOUNT_ID; the customer account identifier.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_KEY — from PARTY.PARTY_NAME, CUST.ACCOUNT_NUMBER, and PARTY.CUSTOMER_KEY respectively.
• STATUS, ORIG_SYSTEM_REFERENCE, CUSTOMER_CLASS_CODE, CUSTOMER_TYPE — account status and classification sourced from HZ_CUST_ACCOUNTS.
• CUSTOMER_PROSPECT_CODE — literal 'CUSTOMER', distinguishing this view from prospect views.
• CUSTOMER_CATEGORY_CODE — from PARTY.CATEGORY_CODE.
• TAX_REFERENCE, TAXPAYER_ID (JGZZ_FISCAL_CODE), TAX_CODE — tax-related identifiers.
• PRIMARY_SALESREP_ID, PRICE_LIST_ID, FREIGHT_TERM, ORDER_TYPE_ID, SALES_CHANNEL_CODE, WAREHOUSE_ID, FOB_POINT, SHIP_VIA — order-management and shipping defaults from the customer account.
• REFERENCE_USE_FLAG — from PARTY.REFERENCE_USE_FLAG, indicating whether the party may be used as a reference.
• COMPETITOR_FLAG, THIRD_PARTY_FLAG — party-level classification flags.
• Organization-only columns — SIC_CODE, MISSION_STATEMENT, NUM_OF_EMPLOYEES, POTENTIAL_REVENUE_CURR_FY, POTENTIAL_REVENUE_NEXT_FY, FISCAL_YEAREND_MONTH, YEAR_ESTABLISHED, ANALYSIS_FY, GSA_INDICATOR are returned via DECODE on PARTY.PARTY_TYPE, yielding values only for organizations.

Common Use Cases and Queries

Typical uses include legacy customer listings, reference-data validation, and joins to AR transactions where the old CUSTOMER_ID is expected. The REFERENCE_USE_FLAG is frequently queried to identify parties approved for use as customer references.

• List active customers: SELECT customer_id, customer_name, customer_number, status FROM ar_customers_all_v WHERE status = 'A';
• Find reference-eligible customers: SELECT customer_id, customer_name, reference_use_flag FROM ar_customers_all_v WHERE reference_use_flag = 'Y';
• Retrieve organization demographics: SELECT customer_name, sic_code, num_of_employees, year_established FROM ar_customers_all_v WHERE customer_class_code = 'ORG';

For new development on 12.1.1 or 12.2.2, query HZ_CUST_ACCOUNTS and HZ_PARTIES directly to ensure full TCA support.