Search Results watch_balance_indicator




Overview
Explore in AI Chat

Overview

APPS.JTF_CUST_ACCOUNTS_ALL_V is a reporting and integration view in Oracle E-Business Suite that exposes customer account records from the Trading Community Architecture (TCA) model. It is owned by the APPS schema and is referenced extensively by Oracle Customer Relationship Management (CRM) and Order Management modules, particularly by the JTF (Java Technology Foundation) framework that underpins TCA-based components. The view presents a denormalized projection of the underlying customer account entity, combining core account attributes with descriptive flexfield columns, global descriptive flexfield columns, and audit tracking fields.

The _ALL_V naming convention signals that the view is intended to present the complete set of customer accounts available to the current organization, subject to any multi-org or security predicates embedded in the view definition. Because the view is owned by APPS and exposed as a public synonym, it is typically referenced by forms, concurrent programs, and custom extensions without requiring fully qualified schema names.

In the context of the search term account_replication_key, this column generally appears among the flexible attribute set on customer account entities and is used during data replication and master-data synchronization flows. Applications performing account replication across instances or subsystems rely on such a key to uniquely identify a source account record during insert, update, or merge operations.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is defined over the base object HZ_CUST_ACCOUNTS, accessed through a synonym. HZ_CUST_ACCOUNTS is the central TCA table storing customer account records, keyed by CUST_ACCOUNT_ID and linked to a PARTY_ID in the HZ_PARTIES table.

The view does not appear to join additional tables in the documented excerpt; it is a single-table projection that carries forward the columns of HZ_CUST_ACCOUNTS, including audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), the warehouse update timestamp (WH_UPDATE_DATE), descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE20), global descriptive flexfield columns (GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20), and key business columns such as ORIG_SYSTEM_REFERENCE, STATUS, CUSTOMER_TYPE, CUSTOMER_CLASS_CODE, PRIMARY_SALESREP_ID, and SALES_CHANNEL. Because the view mirrors its base table nearly column-for-column, it behaves as a stable interface through which JTF components can query customer account data.

Key Columns

  • CUST_ACCOUNT_ID — Primary identifier of the customer account record in HZ_CUST_ACCOUNTS.
  • PARTY_ID — Foreign key to HZ_PARTIES, linking the account to its owning party.
  • ACCOUNT_NUMBER — The user-visible account number assigned to the customer account.
  • ORIG_SYSTEM_REFERENCE — Identifier of the record in the originating (source) system; closely associated with replication and import processes and with account_replication_key semantics.
  • STATUS — Lifecycle status of the account (for example, active or inactive).
  • CUSTOMER_TYPE and CUSTOMER_CLASS_CODE — Classification attributes used in reporting and eligibility rules.
  • PRIMARY_SALESREP_ID and SALES_CHANNEL — Sales assignment and channel attribution columns.
  • ATTRIBUTE1–ATTRIBUTE20 — Descriptive flexfield segments that can store site-specific data, potentially including a replication key value.
  • GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — Global descriptive flexfield segments used for country-specific or legislatively required data.
  • WH_UPDATE_DATE, LAST_UPDATE_DATE, CREATION_DATE — Timestamps supporting incremental extraction and change detection for replication.

Common Use Cases and Queries

The view is commonly used for reporting on customer accounts, validating replication status against ORIG_SYSTEM_REFERENCE, and extracting account records for downstream systems. A representative query lists active accounts with their identifiers and audit timestamps:

  • SELECT cust_account_id, party_id, account_number, orig_system_reference, status, last_update_date FROM apps.jtf_cust_accounts_all_v WHERE status = 'A';
  • SELECT cust_account_id, account_number, attribute1 FROM apps.jtf_cust_accounts_all_v WHERE attribute_category = 'REPLICATION' AND attribute1 IS NOT NULL;
  • SELECT cust_account_id, account_number, last_update_date FROM apps.jtf_cust_accounts_all_v WHERE last_update_date >= :p_since_date ORDER BY last_update_date;

Where a replication key is stored in a flexfield segment or derived from ORIG_SYSTEM_REFERENCE, queries against this view support reconciliation between the source instance and the target, identifying accounts that have not yet been propagated. The audit and update columns make the view suitable as the driver of incremental extracts, while the CUST_ACCOUNT_ID and PARTY_ID columns allow joins to HZ_PARTIES and related TCA entities for richer reporting.