Search Results jtf_cust_accounts_all_v




Overview
Explore in AI Chat

Overview

JTF_CUST_ACCOUNTS_ALL_V is an APPS-owned database view in the Oracle E-Business Suite CRM Foundation (JTF) product, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to expose the account information of a party. The view does not introduce new business logic, transformation, or filtering: it is described as identical to the underlying table HZ_CUST_ACCOUNTS and was created so that it serves as a single point of interface to the AR schema object. In practice, this makes JTF_CUST_ACCOUNTS_ALL_V a compatibility and decoupling layer. CRM Foundation code, and third-party components built against the JTF data model, can reference customer account data through a stable name rather than binding directly to the Receivables (AR) base table. For reporting and integration, the view behaves as a one-to-one projection of HZ_CUST_ACCOUNTS, so it inherits that table's grain: one row per customer account record.

Because the underlying table is the transactional owner of customer account data, the view is read-mostly in reporting scenarios. Responsibility for the data remains with Receivables; the view is the access path, not the source of truth. The presence of the WHO columns and the standard program/request columns confirms that the view surfaces the full concurrency and audit context of each row.

Underlying Base Objects

The documented metadata lists a single referenced base object: HZ_CUST_ACCOUNTS, accessed through a SYNONYM. The view text is a flat SELECT of column names mapped to identically named columns of that table, with no joins, unions, or filters. This is consistent with the description that the view is identical to the table.

HZ_CUST_ACCOUNTS is the Trading Community Architecture (TCA) table that stores customer accounts, each linked to a party via PARTY_ID. TCA permits one party to own multiple accounts, so the join key between this view and HZ_PARTIES is PARTY_ID, and the primary key of the view is CUST_ACCOUNT_ID. Because the view is a synonym-based pass-through, its query plan reduces to a simple table access on HZ_CUST_ACCOUNTS (full scan or unique/index scan on CUST_ACCOUNT_ID), and any index available on the base table is equally usable through the view.

Key Columns

Common Use Cases and Queries

Typical uses include TCA-based account extracts, CRM-to-AR reconciliation, and integrations that must remain insulated from direct dependencies on the AR base table.

  • Account lookup by number: SELECT cust_account_id, party_id, account_number FROM jtf_cust_accounts_all_v WHERE account_number = :acct_number;
  • Accounts for a party: SELECT cust_account_id, account_number FROM jtf_cust_accounts_all_v WHERE party_id = :party_id;
  • Reconcile the view against its base table: SELECT COUNT(*) FROM jtf_cust_accounts_all_v MINUS SELECT COUNT(*) FROM hz_cust_accounts;

Regarding the searched term acct_life_cycle_status: this attribute is not among the columns documented for JTF_CUST_ACCOUNTS_ALL_V above. Account lifecycle status is normally held on TCA party/account profile tables rather than on HZ_CUST_ACCOUNTS itself, so callers searching for it should query the appropriate status or profile view for the party, joined by CUST_ACCOUNT_ID or PARTY_ID. Users must not assume this column is exposed here; verify against the live view definition in the target instance.