Search Results reference_use_flag

Overview

UMX_ORGANIZATION_PVT_V is a private database view owned by the APPS schema within the FND — Application Object Library product family. The "PVT" designation indicates that the view is intended for internal consumption by the Oracle User Management (UMX) framework rather than for direct customer use. It exposes a curated subset of organization-level attributes drawn from the Trading Community Architecture (TCA) party model, presenting them in a flattened, report-friendly structure.

The view is defined with a single filter: only rows where PARTY_TYPE equals 'ORGANIZATION' are returned, effectively excluding person parties maintained in the same underlying table. Because it is a view and not a table, it stores no data of its own and inherits the security, indexing, and partitioning characteristics of its base object. Within Oracle EBS 12.1.1 and 12.2.2, the view participates in UMX role and permission resolution logic, and it is frequently encountered when administrators inspect organization-related registrations, party assignments, or language-specific organization attributes.

Underlying Base Objects

The view is defined over HZ_PARTIES, referenced through the APPS.HZ_PARTIES synonym. All columns projected by UMX_ORGANIZATION_PVT_V originate from this single base table; the view adds no joins, aggregations, or calculated expressions. The relationship is therefore one-to-one at the row level for organization parties: every row in the view corresponds to exactly one organization record in HZ_PARTIES, and every organization party in HZ_PARTIES is eligible to appear in the view.

Two important consequences follow. First, any update to an organization party through the TCA APIs is immediately visible through the view. Second, because the definition filters on PARTY_TYPE, person parties such as employees and contacts are excluded. Administrators should treat the view as a read-only presentation layer and perform DML against HZ_PARTIES or the supported TCA public APIs instead.

Key Columns

• PARTY_ID — Primary identifier for the organization party; the join key to virtually all other TCA objects.
• PARTY_NAME, KNOWN_AS, KNOWN_AS2–KNOWN_AS5 — Organization naming attributes, including alternative and historical names.
• PARTY_NUMBER — System-assigned unique party number; useful for external references.
• LANGUAGE_NAME — The language associated with the organization record, relevant to multilingual and localization reporting.
• TAX_NAME, TAX_REFERENCE, JGZZ_FISCAL_CODE — Tax registration and fiscal identifiers used in statutory reporting.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — Denormalized address components.
• EMAIL_ADDRESS — Primary electronic contact for the organization.
• CATEGORY_CODE, SIC_CODE_TYPE — Classification attributes for reporting and segmentation.
• DUNS_NUMBER, GSA_INDICATOR_FLAG, COMPETITOR_FLAG, THIRD_PARTY_FLAG, REFERENCE_USE_FLAG — Trade and qualification flags.
• EMPLOYEES_TOTAL, ANALYSIS_FY, FISCAL_YEAREND_MONTH, YEAR_ESTABLISHED, CURR_FY_POTENTIAL_REVENUE, NEXT_FY_POTENTIAL_REVENUE — Firmographic and revenue-planning attributes.
• STATUS, OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY — Lifecycle and concurrency-control metadata.

Common Use Cases and Queries

Typical scenarios include identifying organizations by language for localization audits, reconciling party numbers against external systems, and producing address and firmographic extracts for downstream reporting. The following query returns active organizations and their language attributes:

• SELECT party_id, party_name, party_number, language_name, country, status FROM apps.umx_organization_pvt_v WHERE status = 'A' ORDER BY party_name;
• SELECT category_code, COUNT(*) FROM apps.umx_organization_pvt_v GROUP BY category_code;
• SELECT p.party_name, p.duns_number, p.employees_total FROM apps.umx_organization_pvt_v p WHERE p.year_established >= 2000;

Because the object is a private UMX view, Oracle does not guarantee its definition across patch levels. Custom code should prefer public TCA views such as HZ_ORGANIZATIONS_V2 where equivalent attributes are available, reserving UMX_ORGANIZATION_PVT_V for diagnostic or investigative queries.