Results for “customer_type”

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

Overview

OKX_CUSTOMER_ACCOUNTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product. Its purpose is to present a consolidated, denormalized picture of customer accounts by joining customer account records to their corresponding party records. In Oracle EBS 12.1.1 and 12.2.2, the view conforms to the standard OKX integration objects, which are commonly consumed by external applications, contract management modules, and downstream reporting layers that require account-level customer information without needing to navigate the underlying Trading Community Architecture (TCA) tables directly.

The view is documented with a status of VALID and carries a stable column contract, making it suitable for reusable queries and integration extracts. Parameterized placeholder columns (such as ID2, which returns the constant '#', and PRIMARY_UOM_CODE, which is returned as NULL) indicate that the object was designed as a generic integration interface where some attributes are standardized rather than sourced from TCA.

Underlying Base Objects

The view is defined over two documented base objects accessed through APPS synonyms:

• HZ_CUST_ACCOUNTS (SYNONYM) — the TCA customer accounts entity, aliased as CA. This is the primary driving table and supplies the account identifier, account name and number, customer type and class, status, coterminate day/month, the account established date, and the sales channel code.
• HZ_PARTIES (SYNONYM) — the TCA parties entity, aliased as P. This supplies the party identifier and party name, the party type (used to derive the GSA indicator), and the party e-mail address.

The two objects are joined on the common key: CA.PARTY_ID = P.PARTY_ID. Because the underlying objects are TCA entities, the view inherits the standard TCA integrity and naming conventions used throughout Oracle EBS 12.x.

Key Columns

• PARTY_ID — the TCA party identifier, enabling cross-reference back to HZ_PARTIES and related party-level objects.
• NAME — the account display name; derived with DECODE so that when ACCOUNT_NAME is null the party name is returned instead.
• DESCRIPTION — maps to CA.ACCOUNT_NUMBER, exposing the customer account number.
• CUSTOMER_TYPE, B_STATUS, STATUS — the customer type classification and the account status, with the status exposed under two aliases for integration compatibility.
• COTERMINATE_DAY_MONTH — the day and month used for contract cotermination processing.
• ACCOUNT_ESTABLISHED_DATE — the date the customer account was established, sourced from CA.ACCOUNT_ESTABLISHED_DATE. This is the column most directly relevant to searches for "account_established_date".
• CUSTOMER_CLASS_CODE, SALES_CHANNEL_CODE — the customer class and sales channel classifications.
• PRIMARY_UOM_CODE — returned as NULL by design in this interface.
• GSA_INDICATOR — derived via DECODE on party type; for ORGANIZATION parties the party GSA flag is returned, otherwise 'N'.
• EMAIL_ADDRESS — the party e-mail address.

Common Use Cases and Queries

Typical uses include account aging and establishment reporting, contract integration extracts, and customer master data reconciliation. A representative query retrieving accounts established within a period is shown below.

SELECT party_id, name, description, account_established_date, status
FROM apps.okx_customer_accounts_v
WHERE account_established_date >= :p_from_date
ORDER BY account_established_date;

For integration extracts, selecting the interface columns (ID1, ID2, and the classification codes) supports mapping into external contract systems. Filtering on GSA_INDICATOR isolates organization accounts with the GSA flag set, while joining back to HZ_CUST_ACCOUNTS on CUST_ACCOUNT_ID (alias ID1) allows enrichment with TCA attributes not exposed by the view.