Search Results as_issue_groups_b_n1

Overview

OSM.AS_ISSUE_GROUPS_B is a seed data table in the Oracle E-Business Suite 12.1.1 / 12.2.2 service (TeleService / Field Service) schema. It stores the master definitions of issue groups — the categorization construct used to group, classify, and route service issues, notes, and related transactional records throughout the customer support and field service modules. As a "_B" (base) table, it holds the language-independent definition rows, while any translated or descriptive content is maintained separately. The table resides in the APPS_TS_SEED tablespace with a PCTFREE of 10, consistent with the Oracle Applications convention for seeded reference data.

From a Data Vault modeling perspective, the mined relationship metadata suggests classifying AS_ISSUE_GROUPS_B as a hub candidate. It carries a single-column surrogate primary key (ISSUE_GROUP_ID) with no mandatory foreign key dependencies of its own except a reference to FND_SECURITY_GROUPS, and it is referenced by downstream transactional tables, which is characteristic of a hub-and-satellite pattern.

Key Information Stored

The table contains 29 documented columns. The most operationally significant are:

• ISSUE_GROUP_ID — the numeric surrogate primary key (AS_ISSUE_GROUPS_B_PK) and the column exposed by the unique index AS_ISSUE_GROUPS_B_U1. It is the business-key candidate used for cross-table joins.
• ISSUE_GROUP_TYPE_CODE — a VARCHAR2(15) code classifying the group type; also indexed non-uniquely via AS_ISSUE_GROUPS_B_N1.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the issue group is active, enabling time-bounded lookups.
• ORIG_SYSTEM_REFERENCE / ORIG_SYSTEM_REFERENCE_ID — traceability to the source system or table from which the row originated, supporting multi-source consolidation.
• SECURITY_GROUP_ID — the security partitioning reference to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM layer for concurrent update control.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide audit history.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield segments allowing customer-specific extension without schema change.

Common Use Cases and Queries

Typical uses include reporting on issue categorization, validating seeded issue groups during implementations, and building validation lists for service request entry. A common pattern resolves the active issue groups of a given type:

SELECT issue_group_id, issue_group_type_code, start_date_active, end_date_active
FROM osm.as_issue_groups_b
WHERE issue_group_type_code = :p_type
AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE + 1);

Another frequent query joins the base table to its related transactional tables to report issue volumes per group, using ISSUE_GROUP_ID as the join key against AS_FUNDS_B and AS_ISSUE_GROUP_IDFR. Security-filtered extracts commonly join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to enforce row-level visibility.

Related Objects

The metadata identifies the following significant relationships:

• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, enforcing data partition security.
• AS_FUNDS_B — references AS_ISSUE_GROUPS_B via ISSUE_GROUP_ID, linking funding records to their issue group.
• AS_ISSUE_GROUP_IDFR — the multi-lingual (identifier) counterpart, also referencing ISSUE_GROUP_ID, holding translated or language-specific content.
• AS_ISSUE_GROUPS_TL — the translated table conventionally paired with any _B table in EBS, storing language-specific names and descriptions keyed by ISSUE_GROUP_ID.
• AS_ISSUE_GROUPS_B_PK / AS_ISSUE_GROUPS_B_U1 / AS_ISSUE_GROUPS_B_N1 — the primary key constraint and its supporting unique and non-unique indexes.