Results for “hz_organization_profiles_v”

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

Overview

The HZ_ORGANIZATION_PROFILES_V view in the APPS schema exposes organizational profile information maintained within the Oracle E-Business Suite Trading Community Architecture (TCA). It presents a consolidated, read-oriented projection of the organization profile records stored in the underlying HZ_ORGANIZATION_PROFILES table, joined to party-level attributes held in HZ_PARTIES. The view belongs to the Receivables (AR) product family, where organizational profiles are used to drive customer and prospect classification, credit evaluation, and Dun & Bradstreet-related risk scoring.

Because the view surfaces the full set of descriptive, financial, and demographic attributes of an organization, it is commonly consumed by reporting layers, third-party data integration points (such as credit-bureau enrichment), and extension code that requires organization profile data without directly querying the TCA base tables. The ETRM metadata confirms the object is VALID and owned by APPS in release 12.2.2, with an identical lineage applicable to 12.1.1.

Underlying Base Objects

The documented base objects referenced by the view are:

• HZ_ORGANIZATION_PROFILES (accessed via a SYNONYM) — the primary source, supplying organization profile identifiers, organization names, attribute flexfields, and all analytical and scoring columns.
• HZ_PARTIES (accessed via a SYNONYM) — the party master, providing the linkage through PARTY_ID that anchors each profile to its owning party record.

In the standard EBS data model, HZ_ORGANIZATION_PROFILES holds a foreign-key relationship to HZ_PARTIES via PARTY_ID. The view exposes columns from both sources, allowing consumers to read organization profile data alongside the party identity without an explicit join in application code. The view text selects aliased columns from the profile source, retaining the descriptive flexfield segments, global descriptive flexfield segments, and the analytical and credit-scoring fields.

Key Columns

Among the most significant columns exposed are the following:

• ORGANIZATION_PROFILE_ID and PARTY_ID — the primary identifiers linking the profile to its party.
• ORGANIZATION_NAME, ORGANIZATION_NAME_PHONETIC, TAX_NAME, TAX_REFERENCE — organization identity and tax-registration details.
• DUNS_NUMBER, ENQUIRY_DUNS, CEO_NAME, CEO_TITLE, PRINCIPAL_NAME, PRINCIPAL_TITLE — business identification and leadership data, typically enriched from Dun & Bradstreet.
• DB_RATING — the Dun & Bradstreet rating, which is the attribute most relevant to the search term db_rating and a primary risk indicator.
• CREDIT_SCORE, CREDIT_SCORE_COMMENTARY, FAILURE_SCORE, GLOBAL_FAILURE_SCORE, FAILURE_SCORE_NATL_PERCENTILE — predictive credit and failure-risk scoring fields.
• PAYDEX_SCORE, PAYDEX_THREE_MONTHS_AGO, PAYDEX_NORM — payment-behavior scoring metrics.
• Demographic and classification columns such as SIC_CODE, LINE_OF_BUSINESS, EMPLOYEES_TOTAL, MINORITY_OWNED_IND, WOMAN_OWNED_IND, SMALL_BUS_IND, and various trade indicators.
• Descriptive flexfield columns (ATTRIBUTE1–ATTRIBUTE20) and global flexfield columns (GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20) for customer-defined extensions.

Common Use Cases and Queries

Typical usage centers on retrieving risk and credit information for a party. A common pattern filters on the DB_RATING column to segment customers by creditworthiness, or joins the view to HZ_CUST_ACCOUNTS to associate profiles with customer accounts in Receivables.

SELECT party_id,
       organization_name,
       duns_number,
       db_rating,
       credit_score,
       failure_score
  FROM apps.hz_organization_profiles_v
 WHERE db_rating IS NOT NULL;

Another frequent scenario enriches a customer list with payment-behavior metrics for collections or credit-review dashboards. Because the view is a simple projection, queries against it are read-only and suitable for ad hoc reporting, concurrent program extracts, and integration staging.

Consultants should note that the view does not itself enforce security; row-level access to the underlying TCA data is governed by the base tables and any organization-level access controls in place.