Search Results hq_branch_ind




Overview
Explore in AI Chat

Overview

APPS.JTF_PARTIES_ALL_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema. It exposes a denormalized projection of party records used by the CRM/Trade Management (JTF) foundation layer and by TCA (Trading Community Architecture) dependent modules. The view presents business party identity — party number, party name, party type, and validation status — alongside the standard WHO columns (creation/update audit fields), a set of descriptive flexfield (DFF) columns (ATTRIBUTE_CATEGORY through ATTRIBUTE24), and global descriptive flexfield columns (GLOBAL_ATTRIBUTE_CATEGORY through GLOBAL_ATTRIBUTE20). It also surfaces ORIG_SYSTEM_REFERENCE, which ties a party back to its originating application record.

The view is frequently referenced in data extraction, party de-duplication diagnostics, and integration interfaces where a flattened party profile is more convenient than joining TCA tables directly. Because the view collapses multiple attribute sets into a single row shape, it is commonly used as the source for extracts that feed downstream systems or for ad hoc verification of party records during implementations and upgrades.

Underlying Base Objects

The documented base object for this view is HZ_PARTIES, accessed via a synonym in the APPS schema. HZ_PARTIES is the master table in the TCA model, storing one row per party (person, organization, or group) with the party_name, party_number, party_type, and validated_flag attributes. The view does not introduce additional joins in the documented metadata; it projects columns from this single base table and applies a column-alias pattern for the DFF and GDF attribute blocks. This means the row count and party_id granularity of the view mirror HZ_PARTIES. Any filter or security predicate applied at the base table level propagates to consumers of the view.

Key Columns

Common Use Cases and Queries

The view is typically queried to obtain a flat party snapshot for reporting, migration validation, or interface staging. The query below lists parties with their number, name, and type. The user search term "hq_branch_ind" is not a column exposed by this view; branch indicators are generally stored as DFF segments on HZ_PARTIES or in HZ_ORGANIZATION_PROFILES, not as a named attribute here.

  • Extract party master data: SELECT party_id, party_number, party_name, party_type FROM apps.jtf_parties_all_v;
  • Reconcile integration-sourced records: SELECT party_id, orig_system_reference FROM apps.jtf_parties_all_v WHERE orig_system_reference IS NOT NULL;
  • Audit recently changed parties: SELECT party_id, party_name, last_updated_by, last_update_date FROM apps.jtf_parties_all_v WHERE last_update_date >= SYSDATE - 7;

Because the view projects HZ_PARTIES directly, consumers requiring branch indication, classification codes, or addresses should join to HZ_ORGANIZATION_PROFILES, HZ_CODE_ASSIGNMENTS, or HZ_LOCATIONS using party_id.