Search Results as_issue_groups_b_pk

Overview

The AS_ISSUE_GROUPS_B table is a base (transactional) entity table owned by the OSM schema within the AS – Sales Foundation product family of Oracle E-Business Suite. It holds the definition of Issue Groups, the configuration construct used to categorize and control how material issues (for example, shipping or returns-related releases) are grouped and processed by downstream Oracle Order Management and Inventory logic. In Release 12.1.1 and 12.2.2 the table remains a VALID, active dictionary object with 29 documented columns and a single unique index, AS_ISSUE_GROUPS_B_U1, defined on ISSUE_GROUP_ID. The heuristic Data Vault classification mined from the foreign-key structure is standalone. As a modeling suggestion, this implies the table behaves primarily as a hub-style reference entity—it defines an issue group identity and its attributes without participating in the classic hub-to-link relationship chain that characterizes dependent or junction tables.

Key Information Stored

The table stores the master definition of each issue group. The most significant columns are:

• ISSUE_GROUP_ID – Surrogate primary key (AS_ISSUE_GROUPS_B_PK) and also the business-key candidate identified by the unique index AS_ISSUE_GROUPS_B_U1. This is the value propagated to dependent tables.
• ISSUE_GROUP_TYPE_CODE – Classifies the issue group by type, driving which processing or grouping behavior applies.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective-dating fields controlling the active window of the definition.
• ORIG_SYSTEM_REFERENCE / ORIG_SYSTEM_REFERENCE_ID – Tracks the source system and its identifier for records originating outside EBS.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.
• OBJECT_VERSION_NUMBER – Optimistic-locking column used by the OAF/BC4J framework on update.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – The standard EBS descriptive flexfield (DFF) segment columns for customer-defined extensions.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on validating and reporting issue-group configuration. To list active issue groups:

SELECT issue_group_id, issue_group_type_code, start_date_active, end_date_active
FROM osm.as_issue_groups_b
WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

To join issue groups to their dependent funds records:

SELECT g.issue_group_id, f.funds_id
FROM osm.as_issue_groups_b g, osm.as_funds_b f
WHERE g.issue_group_id = f.issue_group_id;

Common scenarios include auditing security-group assignments, extracting DFF attribute values for reporting, and reconciling cross-system integrations via ORIG_SYSTEM_REFERENCE_ID. The _B suffix indicates this is the base table; translated or view-layer access should be confirmed against the corresponding TL/view objects.

Related Objects

• FND_SECURITY_GROUPS – Referenced by AS_ISSUE_GROUPS_B.SECURITY_GROUP_ID.
• AS_FUNDS_B – References this table via ISSUE_GROUP_ID.
• AS_ISSUE_GROUP_IDFR – Identifier/interface table referencing ISSUE_GROUP_ID.
• AS_ISSUE_GROUPS_TL – Translation table (where present) supplying language-specific names/descriptions.
• AS_ISSUE_GROUPS_V – Common validation view exposing the base definition.

Together these objects form the issue-group configuration domain within Sales Foundation.