Results for “customer_class_code”

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

Overview

OKE_CUSTOMER_ACCOUNTS_V is an APPS-owned database view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the OKE – Project Contracts product module and exposes customer account information drawn primarily from Oracle Receivables (AR) and Oracle Trading Community Architecture (TCA) data structures. The view carries a VALID status in the ETRM metadata and serves as a reporting and integration layer that flattens customer account master data into a single, queryable object for Project Contracts and related downstream processes.

Because it is a view rather than a base table, OKE_CUSTOMER_ACCOUNTS_V does not store data itself. Instead, it presents a simplified, denormalized projection over customer accounts and party records. This makes it suitable for use in concurrent programs, reports, SQL*Plus extracts, and interface logic where a stable read-only representation of customer account attributes is required without navigating the more complex underlying TCA model.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• HZ_CUST_ACCOUNTS (aliased CA) – the core customer accounts table within TCA. It supplies the account-level attributes such as customer account ID, party reference, account number, customer type, status, coterminate day/month, and the various account lifecycle dates.
• HZ_PARTIES (aliased P) – the master party table within TCA. It supplies the party identifier and party name, and is joined to HZ_CUST_ACCOUNTS on the shared PARTY_ID column.

The join condition is an inner join on PARTY_ID (CA.PARTY_ID = P.PARTY_ID), meaning only customer accounts with a matching party record are returned. The view text also includes a literal '#' value and a DECODE expression on account status, indicating the view applies presentation-level transformations to map source status codes into a normalized form.

Key Columns

The view exposes the following columns, which the ETRM metadata documents:

• PARTY_ID – the unique identifier of the party associated with the customer account.
• NAME – the party name sourced from HZ_PARTIES, i.e., the customer's display name.
• DESCRIPTION – a descriptive attribute associated with the account record.
• CUSTOMER_TYPE – classification of the customer (for example, internal or external designations from HZ_CUST_ACCOUNTS).
• B_STATUS – a derived or base status value mapped in the view.
• STATUS – the customer account status code, with a DECODE transformation applied so that 'A' (active) is preserved and inactive values resolve to 'I'.
• COTERMINATE_DAY_MONTH – the day and month on which the account is scheduled to coterminate with related contracts or subscriptions. This column is the object of the search term "coterminate_day_month."
• ACCOUNT_ESTABLISHED_DATE – the date the customer account was established.
• END_DATE_ACTIVE – the date through which the account remains active.
• START_DATE_ACTIVE – the date from which the account becomes active.
• CUSTOMER_CLASS_CODE – the customer class code used for grouping and classification.
• PRIMARY_UOM_CODE – the primary unit of measure code associated with the account.

Common Use Cases and Queries

The most frequent use of OKE_CUSTOMER_ACCOUNTS_V is to retrieve cotermination scheduling information alongside customer identity and status. A typical query returns accounts approaching their coterminate day/month:

• Reporting active customer accounts filtered by STATUS = 'A'.
• Extracting account lifecycles using ACCOUNT_ESTABLISHED_DATE, START_DATE_ACTIVE, and END_DATE_ACTIVE.
• Joining the view to Project Contracts tables for cotermination planning using COTERMINATE_DAY_MONTH.

Illustrative SQL:

• SELECT party_id, name, status, coterminate_day_month FROM oke_customer_accounts_v WHERE status = 'A';
• SELECT cust_account_id, account_number, coterminate_day_month, account_termination_date FROM oke_customer_accounts_v WHERE coterminate_day_month IS NOT NULL;
• SELECT name, customer_class_code, account_established_date FROM oke_customer_accounts_v ORDER BY account_established_date;

These queries support account maintenance, renewal forecasting, and contract cotermination analysis within the Project Contracts module.