Search Results as_group_party_map_u2

Overview

OSM.AS_GROUP_PARTY_MAP is a table owned by the OSM schema within Oracle E-Business Suite, registered under FND Design Data as AS.AS_GROUP_PARTY_MAP and holding a VALID status. It functions as a mapping table that associates issue groups with issues, linking a group identifier to a party identifier. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free setting of 10.

In Oracle EBS, this object supports the Assignment Manager and issue-tracking functionality, where parties (persons or organizations) are grouped for the purposes of grouping, routing, and resolving issues. The record carries effective-dating controls, interest-tracking fields, and a full set of descriptive flexfield columns, indicating that it is intended for operational tracking as well as extensible configuration.

The Data Vault classification derived heuristically from the foreign-key structure is standalone. In modeling terms, the presence of a two-column business key (ISSUE_GROUP_ID, PARTY_ID), combined with effective dates and an OBJECT_VERSION_NUMBER, suggests that this table can be treated as a link-style relationship table with satellite-like attributes. A Data Vault implementation might model the ISSUE_GROUP_ID and PARTY_ID combination as a link, with START_DATE_ACTIVE, END_DATE_ACTIVE, and LAST_INTEREST_DATE as dependent descriptive attributes.

Key Information Stored

The table contains 29 documented columns. The primary key is defined as AS_GROUP_PARTY_MAP_PK, composed of ISSUE_GROUP_ID and PARTY_ID. Two unique business-key candidates exist: AS_GROUP_PARTY_MAP_U1 on (ISSUE_GROUP_ID, PARTY_ID) and AS_GROUP_PARTY_MAP_U2 on (PARTY_ID, ISSUE_GROUP_ID), the latter being the index the user referenced.

• ISSUE_GROUP_ID — Issue Group identifier; part of the surrogate primary key and of both unique indexes.
• PARTY_ID — Party identifier; the counterpart key column.
• START_DATE_ACTIVE — Effective start date for the group-to-party association.
• END_DATE_ACTIVE — Effective end date for the association.
• LAST_INTEREST_DATE — Timestamp of the most recent interest recorded against the mapping.
• NET_CHANGE — Numeric value representing accumulated net change for the association.
• SECURITY_GROUP_ID — Foreign key into FND_SECURITY_GROUPS, enforcing row-level security grouping.
• OBJECT_VERSION_NUMBER — Optimistic locking counter used by the framework.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard Who columns recording the most recent modification.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_LOGIN — Standard audit columns for creation and session context.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield segments for extensible, customer-defined data.

Common Use Cases and Queries

Typical reporting and integration scenarios use this table to resolve which parties belong to a given issue group, or conversely to discover the groups a party is associated with. Because both orderings are indexed, either direction can be queried efficiently.

Query patterns commonly include filtering on active associations by date range:

• Listing members of a group: SELECT PARTY_ID FROM OSM.AS_GROUP_PARTY_MAP WHERE ISSUE_GROUP_ID = :group_id AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Finding groups for a party: SELECT ISSUE_GROUP_ID FROM OSM.AS_GROUP_PARTY_MAP WHERE PARTY_ID = :party_id;
• Audit and change tracking: join to FND_USER on LAST_UPDATED_BY to attribute edits.
• Flexfield reporting: select ATTRIBUTE_CATEGORY and relevant ATTRIBUTE columns for extended attributes captured at the mapping level.

Related Objects

The documented foreign-key relationship links SECURITY_GROUP_ID to FND_SECURITY_GROUPS, tying each mapping row to a security group used for function and data security in Oracle EBS. Beyond that, the ISSUE_GROUP_ID and PARTY_ID columns logically reference the assignment and issue-grouping entities that this map joins together, and the Standard Who columns reference FND_USER through LAST_UPDATED_BY and CREATED_BY. Descriptive flexfield definitions are governed by the APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME registered for the AS product, extending the base columns at runtime.