Search Results as_issue_group_types




Overview
Explore in AI Chat

Overview

The AS_ISSUE_GROUP_TYPES table is a Sales Foundation (AS) reference and setup object owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it holds Issue Group Types — the configurable categories used by Service/Depot and field service processes to classify and group issues raised against a customer, contact, or installed base asset. Because Issue Group Types drive downstream rules such as which contact or organization roles are permitted to raise an issue, the table functions as a controlled lookup rather than a transactional table.

Under the heuristic Data Vault classification mined from its foreign-key structure, AS_ISSUE_GROUP_TYPES is identified as a standalone object. In modeling terms, this suggests treating it as a reference or hub-style entity: it carries its own business key and attributes without participating as a link or satellite in a broader integration schema, apart from the security-group reference noted below.

The table is multilingual: translation rows are keyed by ISSUE_GROUP_TYPE_CODE combined with LANGUAGE, allowing the meaning and description text to be maintained per installed language.

Key Information Stored

The documented physical schema contains 31 columns. The most operationally significant are:

  • ISSUE_GROUP_TYPE_CODE — the user-defined lookup code that uniquely identifies each issue group type. This column forms the leading component of the primary key and of the unique business-key index.
  • LANGUAGE — the language of the translation row; paired with ISSUE_GROUP_TYPE_CODE, it completes the primary key AS_ISSUE_GROUP_TYPES_PK and the unique index AS_ISSUE_GROUP_TYPES.
  • MEANING — the translatable display name of the issue group type.
  • DESCRIPTION — a longer, translatable explanation of the type's purpose.
  • ENABLED_FLAG — controls whether the type is selectable in the application.
  • CLIENT_CONTACT_ENABLED_FLAG — indicates whether a client contact may be associated with this issue group type.
  • CLIENT_ORG_ENABLED_FLAG — indicates whether a client organization may be associated with this issue group type.
  • SOURCE_LANG — the language in which the row was originally created, used by the translation framework.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS that enforces multi-org/security-group access.
  • OBJECT_VERSION_NUMBER — the optimistic-locking column used by the Oracle Applications Framework.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive-flexfield container for customer-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The surrogate primary key is AS_ISSUE_GROUP_TYPES_PK, while the unique business-key candidate is the combination of ISSUE_GROUP_TYPE_CODE and LANGUAGE.

Common Use Cases and Queries

Typical usage centers on populating and validating list-of-values for issue entry screens, and on joining issue transaction tables to the type definitions for reporting. A standard enabled-type lookup with the base-language meaning would be:

SELECT ISSUE_GROUP_TYPE_CODE, MEANING, DESCRIPTION
FROM   AS_ISSUE_GROUP_TYPES
WHERE  ENABLED_FLAG = 'Y'
AND    LANGUAGE = USERENV('LANG')
ORDER BY MEANING;

To confirm which issue group types permit client contacts versus organizations:

SELECT ISSUE_GROUP_TYPE_CODE,
       CLIENT_CONTACT_ENABLED_FLAG,
       CLIENT_ORG_ENABLED_FLAG
FROM   AS_ISSUE_GROUP_TYPES
WHERE  LANGUAGE = USERENV('LANG');

Reporting frequently joins issues to this table on the code to collapse raw codes into readable labels, and checks the SECURITY_GROUP_ID to honor multi-org access.

Related Objects

  • FND_SECURITY_GROUPS — referenced via AS_ISSUE_GROUP_TYPES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; governs which responsibility can access each type.
  • AS_ISSUE_GROUP_TYPE_TL — the translation table that stores MEANING and DESCRIPTION per LANGUAGE.
  • AS_ISSUE_TYPES — issue type definitions that are commonly associated with an issue group type.
  • AS_ISSUES / CS_ISSUES — the transaction tables that reference ISSUE_GROUP_TYPE_CODE when issuing is recorded.
  • AS_LOOKUPS / FND_LOOKUP_VALUES — historical lookup pattern; the AS table supersedes generic lookup storage for this domain.
  • FND_FLEX_VALUES / FND_FLEX_VALUES_TL — backing structures for the ATTRIBUTE descriptive-flexfield columns.