Search Results customer_status_code




Overview
Explore in AI Chat

Overview

APPS.AMS_PARTY_CUSTOMERS_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents a consolidated, reporting-oriented projection of party and customer information sourced primarily from the Oracle Trading Community Architecture (TCA) and associated ordering and marketing attributes. The view is registered in FND Design Data as AMS.AMS_PARTY_CUSTOMERS_V and carries a VALID status in the data dictionary.

Because the view is flagged "Oracle Internal Use Only," Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Accordingly, it functions chiefly as an internal reporting and integration surface used by Oracle Marketing, order-capture, and customer-analytics components rather than as a published or supported API. Its presence in the APPS schema means it can be joined to other EBS data dictionary views in read-only reporting contexts, but developers adopting it for custom code assume the associated risk of an unsupported interface.

Underlying Base Objects

The documented dependency metadata identifies HZ_PARTIES (referenced as a SYNONYM) as the base object this view is defined over. HZ_PARTIES is the central registry of persons and organizations in TCA, supplying the party identity, party type, party number, and name columns that underpin the view.

The view augments that core party record with customer-oriented attributes, computed order metrics, and a set of descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY). It also exposes colloquial, phonetic, and validated-name columns that support fuzzy matching and deduplication scenarios typical of customer data management. The view therefore behaves as a denormalized read layer atop HZ_PARTIES and companion customer and order sources, optimized for retrieval rather than transactional update.

Key Columns

  • ROW_ID (ROWID): The physical row identifier for join and cursor optimization.
  • CUSTOMER_ID (NUMBER) and PARTY_ID (NUMBER): Surrogate identifiers linking the record to the customer account and the underlying TCA party.
  • PARTY_TYPE (VARCHAR2): Distinguishes person versus organization records.
  • CUSTOMER_NAME and CUSTOMER_NUMBER: Display name and human-readable account number.
  • CUSTOMER_STATUS_CODE (VARCHAR2): The status of the customer record. This is the column most commonly targeted when users search for "customer_status_code," since it drives active/inactive filtering in reporting. No length is documented for this column.
  • CUSTOMER_CATEGORY_CODE and SIC_CODE: Classification attributes for segmentation and industry analysis.
  • TOTAL_NUM_OF_ORDERS, TOTAL_ORDERED_AMOUNT, and LAST_ORDERED_DATE: Aggregated purchasing metrics supporting customer-value and recency analysis.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15: Descriptive flexfield storage for extensible customer attributes.
  • VALIDATED_FLAG: Indicates whether the underlying party record has been validated.

Common Use Cases and Queries

The view is typically queried to produce customer master extracts, segmentation reports, and status-driven operational lists. Because CUSTOMER_STATUS_CODE drives active/inactive logic, a frequent pattern selects customers by status.

Example:

SELECT CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME, CUSTOMER_STATUS_CODE
FROM APPS.AMS_PARTY_CUSTOMERS_V
WHERE CUSTOMER_STATUS_CODE = 'A';

Analysts also rank customers by purchase behavior:

SELECT CUSTOMER_NUMBER, CUSTOMER_NAME, TOTAL_NUM_OF_ORDERS, TOTAL_ORDERED_AMOUNT
FROM APPS.AMS_PARTY_CUSTOMERS_V
WHERE TOTAL_ORDERED_AMOUNT > 0
ORDER BY TOTAL_ORDERED_AMOUNT DESC;

Joins to HZ_PARTIES via PARTY_ID remain available for retrieving additional TCA attributes. Given the internal-use designation, consumers should confine usage to reporting and analytics rather than embedding the view in supported custom application logic.