Search Results iex_score_components_pk

Overview

IEX_SCORE_COMPONENTS is a Collections (IEX) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual building blocks — or components — that together define a collection score. In Advanced Collections, scores are calculated values used to rank and prioritize delinquent customers, transactions, and strategies. Each row in IEX_SCORE_COMPONENTS represents one weighted element contributing to a parent score, such as a delinquency factor, a customer risk attribute, or another scoring input. The table therefore acts as the definitional backbone for the scoring engine, connecting a score definition (SCORE_ID) to a reusable component type (SCORE_COMP_TYPE_ID) with a numeric weight applied at evaluation time.

From a Data Vault modeling perspective, the metadata’s structural heuristics classify IEX_SCORE_COMPONENTS as satellite-leaning. Its 16-column layout, single-column surrogate primary key, and heavy descriptive/audit attribute set are consistent with a satellite hanging off a business key hub, with SECURITY_GROUP_ID providing the warehouse-mandated row-level access dimension.

Key Information Stored

The table’s surrogate primary key is SCORE_COMPONENT_ID, defined by IEX_SCORE_COMPONENTS_PK. A unique index, IEX_SCORE_COMPONENTS_U1, covers SCORE_COMPONENT_ID together with ZD_EDITION_NAME, reflecting the editioning scheme used in 12.2.x online patching. The most semantically important columns include:

• SCORE_COMPONENT_ID — surrogate primary key uniquely identifying each component row.
• SCORE_ID — foreign reference to the parent score definition to which this component belongs.
• SCORE_COMP_TYPE_ID — foreign key identifying the type or category of scoring component being applied.
• SCORE_COMP_WEIGHT — numeric weighting applied to this component when the score is computed.
• ENABLED_FLAG — indicates whether the component is active and included in score calculation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/operating-unit row security.
• ZD_EDITION_NAME — editioning column supporting 12.2 online patching.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Notably, the metadata does not expose explicit business-key columns beyond the primary key and editioned unique index; the parent/child relationship through SCORE_ID and SCORE_COMP_TYPE_ID carries the semantic identity.

Common Use Cases and Queries

Typical uses involve score definition maintenance, weight audits, and reproduction of scoring logic for reporting. Because component weights directly influence customer prioritization in Collections, reconciliations often compare configured weights against effective scoring outcomes.

A common query lists all active components for a given score:

• SELECT score_component_id, score_comp_type_id, score_comp_weight, enabled_flag FROM iex_score_components WHERE score_id = :score_id AND enabled_flag = 'Y';
• Join to component types and parameters: SELECT c.score_component_id, t.* FROM iex_score_components c, iex_score_comp_types t WHERE c.score_comp_type_id = t.score_comp_type_id;
• Drill-down: SELECT * FROM iex_score_comp_det WHERE score_component_id = :id;
• Parameter retrieval: SELECT * FROM iex_score_comp_params WHERE score_component_id = :id;

Reporting use cases include effective-dating analyses of weight changes, auditing disabled components, and validating that configured scores match scoring-transaction outputs.

Related Objects

The table occupies a central position within the scoring data model, referenced and referencing several key objects:

• IEX_SCORE_COMP_DET — child detail table joined via SCORE_COMPONENT_ID; holds granular component data.
• IEX_SCORE_COMP_PARAMS — child parameter table joined via SCORE_COMPONENT_ID; holds component parameter values.
• IEX_SCORE_COMPONENTS.SCORE_COMP_TYPE_ID — parent reference to the component type definition (component type master).
• IEX_SCORE_COMPONENTS.SECURITY_GROUP_ID → FND_SECURITY_GROUPS — enforces row-level security across the Collections scoring model.
• Parent score definition table referenced by SCORE_ID, representing the score header to which the component belongs.

Together these objects form the definitional side of Collections scoring, which the scoring engine reads at runtime to compute customer and transaction scores.