Search Results cong_dist_code




Overview
Explore in AI Chat

Overview

HZ_ORG_PROFILES_CPUI_V is a valid APPS-owned view in Oracle E-Business Suite 12.1.1 and 12.2.2, documented under the Receivables (AR) product family within the Trading Community Model (TCM) foundation. It presents a consolidated, denormalized projection of organization profile data: party-level attributes sourced from HZ_PARTIES are joined to organization-specific attributes from HZ_ORGANIZATION_PROFILES, keyed by PARTY_ID. The view therefore exposes both the core party record (party number, party name, party type, validation state) and the extended organization profile (DUNS numbers, CEO/principal details, legal status, SIC codes, employee statistics, fiscal year data, and Effective Date–based date tracking). Because the source objects carry bilingual/date-effective attributes and concurrency columns (such as EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, LAST_UPDATE_DATE, CREATED_BY), the view is most suitable for read-only reporting, extract feeds, and integration staging rather than as a maintenance surface.

Underlying Base Objects

The documented base objects underlying the view are:

  • HZ_ORGANIZATION_PROFILES (SYNONYM) — aliased as ORG; supplies the organization profile identifier and the vast majority of business columns.
  • HZ_PARTIES (SYNONYM) — aliased as PTY; supplies party_number, party_name, salutation, party_type, orig_system_reference, validated_flag, country, and customer_key.

The join key is PARTY_ID, which is present on both base objects and acts as the correlation pivot. As with most TCM-hosted views, HZ_ORGANIZATION_PROFILES and HZ_PARTIES are globally-defined Data Sources exposed through synonyms and often partitioned through MOAC/date-effective logic at the table layer. The CPUI convention indicates a multi-purpose interface view—conceptually similar to "Complete Public User Interface"—intended to provide a stable, flat projection over otherwise normalized data.

Key Columns

The user's search term bank_or_branch_number does not correspond to any column in this view's documented text; the closest structural match is ENQUIRY_DUNS/DUNS_NUMBER_C (Dun & Bradstreet identifiers) and the branch flags. Bank and branch numbers are normally held on organization payment/supplier-bank sites (for example HZ_PARTY_SITE_USES-related bank profile views), not on this profile view.

Common Use Cases and Queries

Typical reporting scenarios include customer/party master extracts, DUNS-based deduplication analysis, and feed generation for external CRM or data-warehouse loads.

SELECT p.party_number,
       p.organization_name,
       p.duns_number_c,
       p.sic_code,
       p.employees_total
FROM   apps.hz_org_profiles_cpui_v p
WHERE  p.party_number = :party_number;

Identify organizations by DUNS presence:

SELECT party_id, party_number, organization_name, duns_number_c
FROM   apps.hz_org_profiles_cpui_v
WHERE  duns_number_c IS NOT NULL;

Retrieve organizations by fiscal-year attributes:

SELECT organization_name, jgzz_fiscal_code, fiscal_yearend_month, year_established
FROM   apps.hz_org_profiles_cpui_v
WHERE  year_established >= 2000
AND    effective_end_date > SYSDATE;