Results for “tax_header_level_flag”

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

Overview

The AR_CUSTOMERS_ACTIVE_V view is a legacy Oracle Receivables (AR) database object owned by the APPS schema. According to the ETRM metadata, this view is documented specifically for Oracle E-Business Suite Release 11.5, and it exposes customer information in a flat, denormalized format suitable for reporting, integration, and backward compatibility with earlier releases of the application.

In the Oracle EBS 12.1.1 and 12.2.2 data models, customer master data resides in the Oracle Trading Community Architecture (TCA) tables, primarily HZ_CUST_ACCOUNTS and HZ_PARTIES. The AR_CUSTOMERS_ACTIVE_V view merges columns from both of these underlying entities — the customer account record and its corresponding party record — into a single row per customer. This design allows legacy code, reports, and interfaces that were built against the earlier AR_CUSTOMERS model to continue functioning without modification.

Because it represents a customer-oriented, presentation-layer abstraction, the view is most frequently encountered in custom reports and migration scripts that predate the full adoption of TCA-based APIs.

Underlying Base Objects

The ETRM metadata for Release 12.2.2 identifies two referenced base objects, each resolved through APPS synonyms:

• HZ_CUST_ACCOUNTS (SYNONYM) — supplies account-level attributes such as CUST_ACCOUNT_ID, ACCOUNT_NUMBER, STATUS, CUSTOMER_CLASS_CODE, CUSTOMER_TYPE, and various order-management attributes.
• HZ_PARTIES (SYNONYM) — supplies party-level attributes such as PARTY_NAME, CUSTOMER_KEY, CATEGORY_CODE, TAX_REFERENCE, and organization-specific fields.

The view joins these two entities on the relationship between the customer account and its owning party. In the underlying view text, the DECODE on PARTY.PARTY_TYPE demonstrates that several columns are populated only when the party is an ORGANIZATION; for person-type parties these columns return NULL. This structure reflects the TCA model, in which a customer account is linked to exactly one party record.

Key Columns

The view exposes a broad set of columns. Notable ones include:

• CUSTOMER_ID — alias for CUST_ACCOUNT_ID, the primary identifier of the customer account.
• CUSTOMER_NAME — the party name, truncated to 50 bytes via SUBSTRB.
• CUSTOMER_NUMBER — the account number from HZ_CUST_ACCOUNTS.
• CUSTOMER_KEY — the TCA customer key from HZ_PARTIES.
• STATUS — the account status (for example, active or inactive).
• CUSTOMER_PROSPECT_CODE — a literal 'CUSTOMER', distinguishing these rows from prospect records.
• CUSTOMER_CLASS_CODE, CUSTOMER_TYPE, CUSTOMER_CATEGORY_CODE — classification attributes.
• TAX_REFERENCE, TAXPAYER_ID, TAX_CODE — tax-related identifiers.
• Organization-only fields such as SIC_CODE, NUM_OF_EMPLOYEES, POTENTIAL_REVENUE_CURR_FY, and YEAR_ESTABLISHED, which are populated only for organization parties.

Common Use Cases and Queries

This view is typically used for reporting on active customers, validating customer data during data conversions, and supporting legacy integrations. Despite its 11.5 designation, it remains queryable in 12.1.1 and 12.2.2 schemas where the underlying TCA tables exist.

A representative query to list active customers with their account numbers is:

• SELECT customer_id, customer_name, customer_number, status FROM ar_customers_active_v WHERE status = 'A';

A second example, retrieving customer classification for a given account, illustrates filtering on exposed columns:

• SELECT customer_name, customer_class_code, customer_type FROM ar_customers_active_v WHERE customer_number = :acct_num;

Because the view is defined over TCA base tables, results reflect the current state of customer records maintained through standard Receivables and TCA functionality. Organizations operating on 12.1.1 or 12.2.2 should note that Oracle directs new development toward TCA APIs and the HZ_CUST_ACCOUNTS_V family, treating AR_CUSTOMERS_ACTIVE_V as a compatibility object rather than a strategic interface.