Search Results as_issue_group_idfr_u1




Overview

OSM.AS_ISSUE_GROUP_IDFR is a transactional data table in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the OSM schema and registered under the application design data path AS.AS_ISSUE_GROUP_IDFR. Its documented purpose is to store records for issue group identifiers, acting as the identifier-value child of the issue group model used by Oracle CRM Service and related telephony, contact center, and interaction-tracking functions. Each row associates a specific identifying scheme and value with a parent issue group, providing the flexible key-value layer that allows a single issue group to carry multiple external or internal identifiers such as routing codes, channel references, or third-party system keys.

The object is VALID in the ETRM 12.2.2 data dictionary and is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, while its supporting indexes reside in APPS_TS_TX_IDX. With 28 documented columns, it carries the full standard WHO audit set, a full descriptive flexfield block (ATTRIBUTE1 through ATTRIBUTE15 plus ATTRIBUTE_CATEGORY), and an OBJECT_VERSION_NUMBER for optimistic locking. Based on the mined foreign key structure, the heuristic Data Vault classification for this table is standalone; as a modeling suggestion, this indicates the table behaves as an independent reference structure rather than a hub, link, or satellite in a strict Data Vault sense, though its columns can still be profiled to determine hub and satellite roles if a Data Vault representation is required.

Key Information Stored

The most significant columns documented for AS_ISSUE_GROUP_IDFR are:

  • ISSUE_GROUP_IDFR_ID (NUMBER) — surrogate primary key of the table, enforced by constraint AS_ISSUE_GROUP_IDFR_PK. This is the column referenced by unique index AS_ISSUE_GROUP_IDFR_U1.
  • ISSUE_GROUP_ID (NUMBER) — foreign key to AS_ISSUE_GROUPS_B, establishing the parent issue group to which the identifier belongs.
  • SCHEME (VARCHAR2(15)) — the naming scheme or namespace under which VALUE is interpreted.
  • VALUE (VARCHAR2(80)) — the actual identifier value held for the issue group under the given scheme.
  • SEARCH_CODE (VARCHAR2(15)) — a short code used for lookup and search operations against identifiers.
  • SECURITY_GROUP_ID (NUMBER) — subscriber identifier used for CRM Online Services and, per the foreign key definition, mapped to FND_SECURITY_GROUPS.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN (DATE / NUMBER) — the standard WHO audit columns recording who created and last changed the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 (VARCHAR2) — descriptive flexfield structure definition and segment columns for customer-specific extension.
  • OBJECT_VERSION_NUMBER (NUMBER) — object version used for concurrent update control.

The unique index AS_ISSUE_GROUP_IDFR_U1 is defined on ISSUE_GROUP_IDFR_ID alone, so it functions primarily as the surrogate key enforcement rather than a composite natural business key. Where business-key uniqueness is required across SCHEME and VALUE, that constraint is not documented as a unique index on this table and must be validated separately.

Common Use Cases and Queries

Typical usage centers on resolving an issue group from an external identifier or enumerating all identifiers attached to a group. A common pattern lists identifiers for a scheme:

  • SELECT ISSUE_GROUP_IDFR_ID, ISSUE_GROUP_ID, SCHEME, VALUE FROM OSM.AS_ISSUE_GROUP_IDFR WHERE SCHEME = :scheme AND SECURITY_GROUP_ID = :sg_id;
  • SELECT i.SCHEME, i.VALUE FROM OSM.AS_ISSUE_GROUP_IDFR i, OSM.AS_ISSUE_GROUPS_B g WHERE i.ISSUE_GROUP_ID = g.ISSUE_GROUP_ID AND g.ISSUE_GROUP_ID = :group_id;
  • SELECT COUNT(*) FROM OSM.AS_ISSUE_GROUP_IDFR WHERE SEARCH_CODE = :search_code; — used to guard against duplicate identifier creation.

Reporting scenarios include auditing identifier coverage per issue group, reconciling externally supplied identifiers against EBS master data, and extracting identifier mappings into downstream Data Vault or warehouse models. Because the table carries ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY, customer-specific descriptive flexfield reporting follows the usual EBS FND_DFF pattern.

Related Objects

  • OSM.AS_ISSUE_GROUPS_B — parent table; joined via ISSUE_GROUP_IDFR.ISSUE_GROUP_ID = AS_ISSUE_GROUPS_B.ISSUE_GROUP_ID.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, controlling subscriber-level data visibility for CRM Online Services.
  • AS_ISSUE_GROUP_IDFR_PK — primary key constraint on ISSUE_GROUP_IDFR_ID.
  • AS_ISSUE_GROUP_IDFR_U1 — the unique index the user searched for; defined on ISSUE_GROUP_IDFR_ID in APPS_TS_TX_IDX and supporting the primary key access path.
  • FND_DESCR_FLEX_COLUMN_USAGES / FND_DF_FLEXFIELDS — descriptive flexfield metadata underpinning the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns for application AS.
  • FND_WHO columns usage — standard EBS audit consumers that read LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

No child tables or additional foreign keys beyond the two documented references are identified in the metadata, reinforcing the standalone classification for this reference-like identifier table.