Search Results issue_group_name




Overview
Explore in AI Chat

Overview

APPS.AS_ISSUE_GROUP_PARTIES_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes the association between issue groups and the trading parties (counterparties) mapped to them. Issue groups are fundamental constructs in Oracle's treasury and risk management functionality, used to aggregate financial instruments, cash flows, or exposure positions that share a common characteristic—such as a counterparty, portfolio, or hedging strategy. This view is the primary interface through which the issue group name (ISSUE_GROUP_NAME) is surfaced alongside the participating parties, making it the natural access point when the object of interest is issue_group_name.

The view is owned by APPS and is intended to be queried by reporting tools, concurrent programs, and integration layers, providing a denormalized, language-filtered projection of the underlying transactional data.

Underlying Base Objects

The view is defined over four base objects, all referenced as APPS synonyms:

This four-way join is central to the view's design: the header-to-translation join ensures language filtering without exposing untranslated names, while the map and party joins deliver the counterparty detail.

Key Columns

  • ISSUE_GROUP_ID — Unique identifier of the issue group; the join key across all base objects.
  • ISSUE_GROUP_NAME — The translated issue group name, sourced from AS_ISSUE_GROUPS_TL and restricted to the session language.
  • ISSUE_GROUP_TYPE_CODE — Classifies the issue group (for example, by business purpose or portfolio type).
  • PARTY_ID / PARTY_NAME / PARTY_TYPE — The unique party identifier, name, and classification drawn from HZ_PARTIES.
  • LAST_INTEREST_DATE — The most recent interest date recorded on the group-party mapping.
  • NET_CHANGE — The net movement or change associated with the mapping.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns propagated from AS_GROUP_PARTY_MAP.

Common Use Cases and Queries

A frequent requirement is to list every party mapped to a known issue group by name. Because the translated name resides only in the TL table, this view is the most direct path:

SELECT issue_group_name, party_name, party_type, net_change FROM apps.as_issue_group_parties_v WHERE issue_group_name = 'GROUP_NAME';

Integration and reconciliation programs use the view to verify that every issue group has at least one mapped party, or to compare the party population across environments. In treasury and risk reporting, NET_CHANGE and LAST_INTEREST_DATE support exposure and interest analysis by counterparty. Because the view enforces USERENV('LANG'), results are automatically localized to the querying session's language, eliminating the need for callers to manage translation themselves. Note that joins to the translations and party registry are inner joins, so issue groups without a mapped party, or parties missing from TCA, are not returned.