Search Results isp_pk

Overview

IEX_STRATEGY_TEMPLATE_GROUPS is a Collections (IEX) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the grouping layer within a collections strategy template: each row associates a strategy template with an ordered group of collection activities, ranks, checklists, scoring attributes, and object filters. Collections administrators use this configuration to control how delinquent customers are segmented and which actions the scoring and strategy engines apply to each segment.

From a Data Vault modeling perspective, the metadata classifies this table heuristically as standalone. It can therefore be treated as a hub-like reference entity anchored on its primary key, without a documented parent link to another hub in the mined FK structure. The table is edition-enabled, as indicated by the ZD_EDITION_NAME column and the unique index IEX_STRATEGY_TEMP_GROUPS_U1, which supports the multi-edition configuration model introduced in EBS 12.2.

Key Information Stored

The surrogate primary key is GROUP_ID, enforced through the ISP_PK constraint. The unique index IEX_STRATEGY_TEMP_GROUPS_U1 on (GROUP_ID, ZD_EDITION_NAME) acts as the business-key candidate and reflects the editioning strategy. The most operationally significant columns include:

• STRATEGY_GROUP_ID / STRATEGY_GROUP_NAME — identifies and labels the group within the strategy template.
• STRATEGY_TEMP_ID — the parent strategy template to which the group belongs.
• GROUP_NAME / GROUP_ID — descriptive and surrogate identifiers used by the runtime strategy engine.
• STRATEGY_ORDER_ID / STRATEGY_RANK — controls the sequence and priority in which groups execute.
• ENABLED_FLAG — determines whether the group is active during strategy evaluation.
• CATEGORY_TYPE / STRATEGY_LEVEL / SCORE_TOLERANCE — drive scoring-based segmentation and tolerance thresholds.
• CHANGE_STRATEGY_YN / CHECK_LIST_YN / CHECK_LIST_TEMP_ID — determine whether the group invokes a change of strategy or a checklist template.
• VALID_FROM_DT / VALID_TO_DT — effective-dating window for the group definition.
• OBJECT_FILTER_ID — foreign key to IEX_OBJECT_FILTERS, defining which customers or transactions qualify.
• SCORING_ENGINE_ID — links the group to the scoring engine configuration.
• ZD_EDITION_NAME — supports the 12.2 editioning model.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present for audit and process tracking.

Common Use Cases and Queries

Typical reporting and configuration queries retrieve the ordered groups within a given strategy template, or join to the object filter to understand which customers a group targets.

• List active groups for a template ordered by execution rank:

SELECT g.strategy_group_id, g.strategy_group_name, g.strategy_rank, g.enabled_flag
FROM iex.iex_strategy_template_groups g
WHERE g.strategy_temp_id = :template_id AND g.enabled_flag = 'Y'
ORDER BY g.strategy_rank;

• Identify groups linked to object filters or checklists for audit purposes.
• Validate effective dating windows to detect overlapping or expired group definitions.
• Feed downstream scoring and segmentation reports by joining on SCORING_ENGINE_ID.

Related Objects

The documented foreign key relationship defines the principal dependency:

• IEX_OBJECT_FILTERS — referenced via OBJECT_FILTER_ID; supplies the customer or transaction filter applied to the group.

Additional related objects suggested by the column set and module context include the parent strategy template table keyed by STRATEGY_TEMP_ID, the checklist template referenced by CHECK_LIST_TEMP_ID, and the scoring engine configuration referenced by SCORING_ENGINE_ID. The editioning column ZD_EDITION_NAME implies dependency on the editioning infrastructure introduced in EBS 12.2.2. Together these objects form the configuration backbone of the Collections strategy engine.