Search Results party_object_version_number




Overview
Explore in AI Chat

Overview

HZ_WSRVC_PARTY_GROUPS_V is an internal reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Receivables (AR) product family. It exposes party records from the Trading Community Architecture (TCA) model that are specifically classified as groups, presenting a denormalised projection over HZ_PARTIES restricted to PARTY_TYPE = 'GROUP'. The view is documented as an internal view for Groups, meaning it is not intended as a public integration interface but rather as a supporting construct for web services, group-related processing, and diagnostic reporting within the EBS stack.

The view is significant in the context of concurrency control because it renames the base column OBJECT_VERSION_NUMBER to PARTY_OBJECT_VERSION_NUMBER. This rename isolates the group-level optimistic locking token as a distinctly named attribute, which is the exact identifier users search for when investigating record versioning behaviour. The view carries a VALID status in the ETRM metadata and is present in both 12.1.1 and 12.2.2 environments, where it is used primarily for read-only retrieval of group parties along with their originating system context.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed through synonyms in the APPS schema:

  • HZ_PARTIES (SYNONYM) — aliased as PTY, the primary TCA table holding party records. The view filters this table on PARTY_TYPE = 'GROUP', so only group-type parties are surfaced.
  • HZ_ORIG_SYS_REFERENCES (SYNONYM) — aliased as MOSR, the origin-system reference table that maps owning entities to the external systems from which they were imported or with which they are synchronised.

The join between the two tables is an outer join, indicated by the (+) operator on the HZ_ORIG_SYS_REFERENCES side. The join predicates are MOSR.OWNER_TABLE_NAME (+) = 'HZ_PARTIES' and MOSR.OWNER_TABLE_ID (+) = PTY.PARTY_ID. The outer-join semantics ensure that group parties with no corresponding origin-system reference row are still returned, with ORIG_SYSTEM populated as NULL.

Key Columns

The view exposes the full descriptive surface of HZ_PARTIES for group records, plus the origin-system attribute. The most notable columns include:

  • PARTY_OBJECT_VERSION_NUMBER — the aliased OBJECT_VERSION_NUMBER from HZ_PARTIES. This is the optimistic concurrency token used to detect conflicting updates to the party record.
  • PARTY_ID — the unique TCA identifier for the party, and the join key to HZ_ORIG_SYS_REFERENCES.OWNER_TABLE_ID.
  • GROUP_NAME — an alias of PARTY_NAME, providing the display name of the group.
  • PARTY_NUMBER — the user-visible party number assigned by TCA.
  • GROUP_TYPE, CATEGORY_CODE, ORIG_SYSTEM_REFERENCE, CREATED_BY_MODULE — classification and provenance attributes describing the group and the module that created it.
  • ORIG_SYSTEM — sourced from HZ_ORIG_SYS_REFERENCES, identifying the external system of record.
  • STATUS, VALIDATED_FLAG — lifecycle and validation state of the group party.
  • ATTRIBUTE1 through ATTRIBUTE20, ATTRIBUTE_CATEGORY — the flexible DFF columns inherited from HZ_PARTIES.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried for group membership reporting, origin-system reconciliation, and concurrency diagnostics. A representative query that retrieves group parties with their version token and originating system is:

SELECT party_id, group_name, party_number, party_object_version_number, orig_system, status FROM apps.hz_wsrvc_party_groups_v WHERE party_id = :p_party_id;

For auditing updates and detecting stale records, the version token is compared against a value read at the start of a transaction, and a nonzero difference indicates the record was modified concurrently. For reconciliation against external systems, filtering on ORIG_SYSTEM isolates groups imported from a specific source:

SELECT party_id, group_name, orig_system_reference FROM apps.hz_wsrvc_party_groups_v WHERE orig_system = :p_orig_system;

Because the view is internal and not part of the documented public API surface, custom code should prefer supported TCA APIs where possible; direct queries are best reserved for reporting and diagnostics.