Results for “account_status”

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

Overview

OKX_CUSTOMER_PROFILES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the OKX – Contracts Integration product, the module responsible for exposing customer, contract, and party data to the Oracle Contracts integration layer and related downstream flows. The view presents a simplified, denormalized projection of customer profile records maintained in the Oracle Receivables/Trading Community Architecture (TCA) data model.

In EBS reporting and integration contexts, OKX_CUSTOMER_PROFILES_V serves as a stable interface between the TCA foundation tables and OKX consumers. Rather than querying HZ_CUSTOMER_PROFILES directly, integration code and reports can reference this view to obtain customer profile identifiers, account associations, profile classifications, site-use context, and the account status value in a single result set. The view is documented as VALID in the ETRM repository, indicating its definition compiles successfully and is supported at the current patch level.

Underlying Base Objects

The view is defined over a single referenced base object: HZ_CUSTOMER_PROFILES, accessed through a SYNONYM in the APPS schema. HZ_CUSTOMER_PROFILES is the TCA table that stores profile records applying to customer accounts, profile classes, and site uses. Each row in the base table represents one profile assignment and carries a primary key column, CUST_ACCOUNT_PROFILE_ID, together with foreign keys to the customer account, profile class, and site use.

Because the view selects directly from HZ_CUSTOMER_PROFILES without joins, it inherits the base table's cardinality: one row per customer profile record. The view owner is APPS and the object type is VIEW, so it carries no storage of its own and cannot be updated through DML. Any change to the base table is immediately reflected when the view is queried.

Key Columns

• STATUS – The profile record's own status flag inherited from HZ_CUSTOMER_PROFILES, indicating whether the profile row itself is active.
• ACCOUNT_STATUS – The status of the associated customer account. This column is the most likely target of a search for "account_status," as it exposes account-level status directly through the contract integration view.
• CUST_ACCOUNT_PROFILE_ID – Primary key identifying the customer profile record.
• CUST_ACCOUNT_ID – Foreign key to the customer account, linking the profile to its owning account.
• PROFILE_CLASS_ID – Identifier of the profile class applied to the record.
• SITE_USE_ID – Identifier of the site use associated with the profile, where applicable.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective dating columns. The view text hard-codes START_DATE_ACTIVE to 1950-01-01 and END_DATE_ACTIVE to NULL, meaning these are static placeholders rather than true date-range values from the base table.

Note that the view text projects a literal '#'ID2 in the second position, a placeholder commonly used by EBS view-generation utilities for flexfield or key concatenation purposes. The documented column list nevertheless exposes NAME, DESCRIPTION, STATUS, the date columns, and the identifier columns.

Common Use Cases and Queries

The primary use case is retrieving customer account profile context for OKX contract integration processing, particularly when the account status must be evaluated before contracts are created or validated. A typical query filters by account or profile identifier:

• SELECT cust_account_profile_id, cust_account_id, profile_class_id, site_use_id, status, account_status FROM okx_customer_profiles_v WHERE account_status = 'A';
• SELECT cust_account_id, account_status FROM okx_customer_profiles_v WHERE profile_class_id = :profile_class_id;
• SELECT v.cust_account_id, v.account_status, v.site_use_id FROM okx_customer_profiles_v v WHERE v.cust_account_id = :account_id;

Because the view resolves to a single base table, such queries are inexpensive and can be joined to HZ_CUST_ACCOUNTS or OKX contract tables on CUST_ACCOUNT_ID. When interpreting results, note that the date columns are static placeholders and must not be relied upon for effective-dating logic.