Search Results as_issue_group_parties_v




Overview
Explore in AI Chat

Overview

The AS_ISSUE_GROUP_PARTIES_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, belonging to the AS – Sales Foundation product. Its documented purpose is to display all parties associated with issue groups. The view consolidates descriptive issue group data with the party records mapped to each group, producing a denormalized result set suited to inquiry screens, concurrent reports, and interface extractions.

Because the view joins translatable issue group names with party master data, it respects the session language through USERENV('LANG'), returning issue group names translated for the current runtime language. This makes the view appropriate for multilingual environments where downstream consumers require localized descriptions rather than base identifiers. The view is read-only and carries no DML logic; all maintenance occurs against the underlying base tables. In EBS 12.1.1 and 12.2.2 the object is registered as VALID and is exposed as APPS.AS_ISSUE_GROUP_PARTIES_V.

Underlying Base Objects

The view is defined over four synonyms resolving to Sales Foundation and Trading Community Architecture base objects:

The joins are inner joins across all four objects, so a row is returned only when an issue group has a valid translation, a party mapping exists, and the referenced party is present in HZ_PARTIES. Issue groups without mapped parties, or mappings referencing a missing party record, are excluded from the result set.

Key Columns

  • ISSUE_GROUP_ID — primary identifier of the issue group; the principal join key across all base objects.
  • ISSUE_GROUP_NAME — translated name from AS_ISSUE_GROUPS_TL, language-dependent.
  • ISSUE_GROUP_TYPE_CODE — classification of the issue group, useful for filtering by group category.
  • PARTY_ID, PARTY_NAME, PARTY_TYPE — the party identifier and descriptive attributes from TCA, defining which party is associated with the group.
  • LAST_INTEREST_DATE, NET_CHANGE — interest tracking attributes from the mapping table, used in interest and position analytics.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns sourced from the mapping table.

Common Use Cases and Queries

Typical scenarios include listing parties per issue group for relationship review, filtering groups by type, and extracting interest change data for reconciliation. A standard query is:

  • SELECT ISSUE_GROUP_ID, ISSUE_GROUP_NAME, PARTY_ID, PARTY_NAME FROM AS_ISSUE_GROUP_PARTIES_V WHERE ISSUE_GROUP_TYPE_CODE = :p_type;
  • SELECT PARTY_ID, PARTY_NAME, LAST_INTEREST_DATE, NET_CHANGE FROM AS_ISSUE_GROUP_PARTIES_V WHERE ISSUE_GROUP_ID = :p_group_id ORDER BY PARTY_NAME;

Because the view contains no bind variables or security predicates beyond language resolution, consumers should apply their own filtering and, where required, organization-level access controls. For high-volume extracts, joining directly to the base tables may offer greater control over execution plans.