Search Results iex_strategy_temp_groups_u1

Overview

IEX.IEX_STRATEGY_TEMPLATE_GROUPS is a seed-data configuration table within the Oracle E-Business Suite Collections (Advanced Collections / IEX) module. It stores the grouping definitions and group-level attributes that govern how collection strategy templates are organized and executed. Each row associates a strategy template with a strategy group, capturing ranking, enablement, filtering, and scoring parameters that drive automated collections processing. The table resides in the APPS_TS_SEED tablespace, reflecting its role as setup and reference data rather than high-volume transactional data.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. This suggests the table is best treated as a standalone reference or configuration entity, rather than a strict hub, link, or satellite. It has minimal foreign-key dependencies and largely carries its own business attributes, making it a candidate for a reference table in an analytic model.

Oracle flags this object as Internal Use Only; direct DML should be avoided, and access should flow through standard Oracle Applications programs and concurrent processes.

Key Information Stored

The table is defined with 29 documented columns. The most significant include:

• STRATEGY_GROUP_ID — Numeric identifier for the strategy group; a core business attribute of each row.
• STRATEGY_GROUP_NAME — Descriptive name of the group, up to 200 characters.
• GROUP_ID — The column that forms the unique index IEX_STRATEGY_TEMP_GROUPS_U1 (with ZD_EDITION_NAME), making it the principal business-key candidate.
• GROUP_NAME — Human-readable group label.
• STRATEGY_TEMP_ID and STRATEGY_ORDER_ID — Link the group to its parent strategy template and ordering context.
• STRATEGY_RANK — Determines execution or display precedence within the strategy.
• ENABLED_FLAG — Controls whether the group is active in processing.
• CATEGORY_TYPE and CHANGE_STRATEGY_YN — Classify the group and indicate strategy-change behavior.
• CHECK_LIST_YN and CHECK_LIST_TEMP_ID — Indicate checklist usage and reference the associated checklist template.
• VALID_FROM_DT and VALID_TO_DT — Effective-dating of the group configuration.
• OBJECT_FILTER_ID — Foreign key to IEX_OBJECT_FILTERS, defining the population the group applies to.
• SCORING_ENGINE_ID, STRATEGY_LEVEL, and SCORE_TOLERANCE — Scoring and strategy-tier parameters.
• OBJECT_VERSION_NUMBER and the standard WHO/Concurrent columns — Audit and optimistic-locking fields.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.x.

The surrogate primary key is documented as ISP_PK on GROUP_ID, while the unique index IEX_STRATEGY_TEMP_GROUPS_U1 on (GROUP_ID, ZD_EDITION_NAME) serves as the business-key candidate.

Common Use Cases and Queries

Typical reporting scenarios include listing active groups for a given strategy template, auditing effective-dated configuration, and reconciling object filters to scoring rules. A representative query:

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

Because the table is editioned, queries in 12.2.x must account for ZD_EDITION_NAME when joining or filtering across versions. Analysts commonly join to IEX_OBJECT_FILTERS to determine filter scope and to template tables to trace full strategy composition.

Related Objects

• IEX_OBJECT_FILTERS — Referenced via OBJECT_FILTER_ID; defines the population a group targets.
• IEX_STRATEGY_TEMPLATES — Parent template identified through STRATEGY_TEMP_ID.
• IEX_STRATEGY_TEMPLATE_DETAILS — Detail lines associated with template groups.
• IEX_STRATEGY_ASSIGNMENTS — Binds strategies to customers or scoring engines.
• IEX_SCORING_ENGINE — Referenced through SCORING_ENGINE_ID for scoring behavior.
• FND_USER and FND_CONCURRENT_REQUESTS — Join targets for WHO and concurrent audit columns.