Search Results as_group_party_map_pk

Overview

AS_GROUP_PARTY_MAP is a Sales Foundation (AS) table owned by the OSM schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. As stated in the ETRM documentation, it is the "mapping table between issue groups and issues," providing the association between an issue group and the parties (customers, prospects, or other trading partners) that belong to it. In the OSM (Order and Settlement Management / Trade Management) data model, issue groups act as a grouping mechanism for collections of issues or disputes raised against trading partners; this table establishes which parties are associated with each group, and optionally the active date range and net-change tracking for that association.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone. This is a modeling suggestion: the table does not fit cleanly into a pure hub, link, or satellite pattern because it carries both the association key and descriptive attributes, and its only documented foreign key points outward to a security group rather than to a parent business entity. Treating it as a standalone reference or mapping entity is the pragmatic classification.

Key Information Stored

The table contains 29 documented columns. The primary key is AS_GROUP_PARTY_MAP_PK, defined over the composite of ISSUE_GROUP_ID and PARTY_ID. Two unique indexes reinforce these business-key candidates: AS_GROUP_PARTY_MAP_U1 (ISSUE_GROUP_ID, PARTY_ID) and AS_GROUP_PARTY_MAP_U2 (PARTY_ID, ISSUE_GROUP_ID). Because both are composite, there is no single-column surrogate; the business key is the natural pairing of group and party.

The most significant attributes:

• ISSUE_GROUP_ID — identifies the issue group to which the party is mapped.
• PARTY_ID — the trading partner or party associated with the group.
• START_DATE_ACTIVE / END_DATE_ACTIVE — define the effective date window of the mapping.
• LAST_INTEREST_DATE — records the most recent date interest was accrued, used in interest and aging calculations.
• NET_CHANGE — captures the net movement or change amount for the party within the group.
• SECURITY_GROUP_ID — the only documented foreign key, referencing FND_SECURITY_GROUPS, enforcing multi-org security.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns.

Common Use Cases and Queries

Typical usage includes listing all parties in an issue group, diagnosing which group a party belongs to, filtering by effective dates, and extracting data for interest or net-change reporting by security group.

SELECT issue_group_id, party_id, start_date_active, end_date_active, net_change
FROM   as_group_party_map
WHERE  issue_group_id = :p_group_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE+1);

Reverse lookup by party for security-scoped reporting:

SELECT g.party_id, g.issue_group_id, g.security_group_id
FROM   as_group_party_map g
WHERE  g.party_id = :p_party_id
AND    g.security_group_id = :p_security_group_id;

Related Objects

• FND_SECURITY_GROUPS — joined on AS_GROUP_PARTY_MAP.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; the sole documented FK.
• AS_ISSUE_GROUPS (or equivalent issue-group master) — implied join on ISSUE_GROUP_ID.
• HZ_PARTIES — joined on PARTY_ID for party name and profile data.
• AS_ISSUES / AS_ISSUE_PARTIES — sibling AS tables referencing the same issue-group and party domains.
• FND_OBJECTS / FND_USER — for audit columns (CREATED_BY, LAST_UPDATED_BY).
• APIs: OSM issue-group and party-mapping public APIs, and standard ADF (Application Development Framework) DFF definitions for the attribute columns.