Results for “as_group_issue_map_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AS_GROUP_ISSUE_MAP table is a Sales Foundation (AS) data object owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its documented description states, it is a "mapping table between issue groups and issues." In practice, it associates individual issues with issue groups, while also carrying a set of position- or tracking-oriented attributes such as target price, buy/sell indicator, holding, currency code, and net change. This dual role makes it both a relationship table and a lightweight transactional detail store.

From a Data Vault modeling perspective, the heuristic classification is standalone, meaning the table is not easily categorized as a pure hub, link, or satellite. Its composite primary key (ISSUE_GROUP_ID, ISSUE_ID) would suggest a link-like relationship between two business entities, but the presence of descriptive attributes (target price, holding, net change) gives it satellite-like characteristics. Analysts should treat it as a hybrid mapping-detail table rather than a clean Data Vault construct.

Key Information Stored

The table contains 32 documented columns. The most significant are the two primary key columns and the business keys defined by unique indexes. ISSUE_GROUP_ID and ISSUE_ID together form the primary key AS_GROUP_ISSUE_MAP_PK. Two unique indexes exist — AS_GROUP_ISSUE_MAP_U1 (ISSUE_GROUP_ID, ISSUE_ID) and AS_GROUP_ISSUE_MAP_U2 (ISSUE_ID, ISSUE_GROUP_ID) — confirming these two columns are the effective business keys and that an issue belongs to a given group at most once.

• ISSUE_GROUP_ID — surrogate/foreign identifier of the parent issue group.
• ISSUE_ID — identifier of the individual issue mapped into the group.
• ISSUE_GROUP_TYPE_CODE — classifies the issue group type.
• LAST_INTEREST_DATE — date of last interest activity.
• TARGET_PRICE — target price associated with the issue.
• BUY_SELL_INDICATOR — buy/sell flag for the position.
• HOLDING — quantity or holding amount.
• CURRENCY_CODE — currency of monetary values.
• NET_CHANGE — net change value for the issue.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, governing data access.
• OBJECT_VERSION_NUMBER — optimistic locking version for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — DFF (descriptive flexfield) segments.

Common Use Cases and Queries

Typical use cases include reporting group membership, resolving issue-level positions to their group context, and auditing access by security group. A common query pattern retrieves all issues for a group:

SELECT ISSUE_ID, TARGET_PRICE, BUY_SELL_INDICATOR, HOLDING, CURRENCY_CODE
FROM OSM.AS_GROUP_ISSUE_MAP
WHERE ISSUE_GROUP_ID = :group_id;

Reverse lookup, finding which groups reference a given issue, uses the U2 index path:

SELECT ISSUE_GROUP_ID, NET_CHANGE, LAST_INTEREST_DATE
FROM OSM.AS_GROUP_ISSUE_MAP
WHERE ISSUE_ID = :issue_id;

Security-scoped reporting joins the security group:

SELECT m.ISSUE_GROUP_ID, m.ISSUE_ID
FROM OSM.AS_GROUP_ISSUE_MAP m, FND_SECURITY_GROUPS s
WHERE m.SECURITY_GROUP_ID = s.SECURITY_GROUP_ID;

Concurrent-update checks should compare OBJECT_VERSION_NUMBER, and DFF reporting can pivot on ATTRIBUTE_CATEGORY with ATTRIBUTE1–ATTRIBUTE15.

Related Objects

• FND_SECURITY_GROUPS — referenced via AS_GROUP_ISSUE_MAP.SECURITY_GROUP_ID; the only documented foreign key.
• AS_ISSUE_GROUPS (conceptual parent) — supplies ISSUE_GROUP_ID values.
• AS_ISSUES/issue master (conceptual) — supplies ISSUE_ID values.
• AS_GROUP_ISSUE_MAP_PK — primary key constraint on (ISSUE_GROUP_ID, ISSUE_ID).
• AS_GROUP_ISSUE_MAP_U1 and _U2 — unique indexes enforcing the business keys.
• FND_CURRENCIES — implied by CURRENCY_CODE lookups.
• Sales Foundation issue-group APIs and concurrent programs that maintain the mapping.

Because only one explicit FK is documented, the parent issue-group and issue tables above are inferred from the mapping semantics and should be validated against the customer's actual dictionary.