Search Results as_issue_group_details_v




Overview
Explore in AI Chat

Overview

The AS_ISSUE_GROUP_DETAILS_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the AS - Sales Foundation product family, which provides the shared party, classification, and grouping infrastructure used across Oracle Sales, Oracle Telesales, and related modules. The view presents a denormalized, query-ready representation of issue groups — the groupings used to categorize and organize issues, service requests, and related sales activities — by joining base, translation, type, and identifier tables into a single flattened result set.

Its primary role is to decouple downstream consumers from the normalized base table structure. Rather than requiring applications, reports, or interfaces to repeatedly join four separate tables and enforce language and type-lookup logic, the view encapsulates that logic once. This makes it particularly suited to operational reports, concurrent programs, and integration extracts that need issue group metadata in a single pass. Because it exposes descriptive multilingual fields and identifier values directly, it is well positioned for use in Oracle Reports, BI Publisher data models, and outbound interfaces.

Underlying Base Objects

Per the ETRM metadata, AS_ISSUE_GROUP_DETAILS_V is defined over four base objects, each referenced through APPS synonyms:

The relationships are: ISSUE_GROUPS_B joins to ISSUE_GROUPS_TL on ISSUE_GROUP_ID; joins to ISSUE_GROUPS_IDFR on ISSUE_GROUP_ID (outer); and joins to ISSUE_GROUP_TYPES on ISSUE_GROUP_TYPE_CODE. No other AS tables participate, making the view relatively lightweight but dependent on the language environment.

Key Columns

The view exposes eighteen columns. The identification and descriptive columns are central:

  • ISSUE_GROUP_ID — primary key value of the issue group, from AS_ISSUE_GROUPS_B.
  • ISSUE_GROUP_NAME — the translated name from AS_ISSUE_GROUPS_TL.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window controlling whether the group is currently active.
  • ORIG_SYSTEM_REFERENCE — the source system name in a multi-source or heterogeneous data environment. Note the view text aliases this as ORIG_SYSTEM_REFERNCE (a documented spelling artifact); the column name in the view is ORIG_SYSTEM_REFERENCE.
  • ORIG_SYSTEM_REFERENCE_ID — the source system's identifier for the same entity, which is the attribute users search on when reconciling issue groups back to an external or upstream application (for example, a legacy system's issue group key pulled into EBS). This is the column referenced in the search query "orig_system_reference_id".

Additional columns include ISSUE_GROUP_TYPE_CODE, ISSUE_GROUP_TYPE_MEANING, and ISSUE_GROUP_TYPE_DESCRIPTION (from the type lookup), the type behavior flags CLIENT_CONTACT_ENABLED_FLAG and CLIENT_ORG_ENABLED_FLAG, the identifier attributes ISSUE_GROUP_IDFR_ID, SCHEME, VALUE, and SEARCH_CODE, and the standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include validating issue group setup, retrieving the external reference for integration reconciliation, and populating LOV or reporting datasets. A common pattern is to filter by the original system reference:

  • SELECT issue_group_id, issue_group_name, orig_system_reference, orig_system_reference_id FROM apps.as_issue_group_details_v WHERE orig_system_reference_id = :p_ref_id;
  • Listing currently active groups: SELECT issue_group_id, issue_group_name FROM apps.as_issue_group_details_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
  • Reporting by type: SELECT issue_group_type_meaning, COUNT(*) FROM apps.as_issue_group_details_v GROUP BY issue_group_type_meaning;

Because the view enforces USERENV('LANG') filtering on two translation tables, callers must set the language environment (via FND_GLOBAL or session settings) to obtain meaningful names. When querying from outside APPS, the standard APPS synonym should be used with appropriate grants.