Search Results iex_score_components_u1

Overview

The IEX.IEX_SCORE_COMPONENTS table is a seed and configuration table within the Oracle EBS Advanced Collections (IEX) application. It stores the definition of the individual components that, when combined, form a scoring model used by the Collections score engine. Each row describes one weighted ingredient contributing to an overall score, allowing collections administrators to tune how customer or transaction risk is evaluated across the scoring framework.

The table resides in the APPS_TS_SEED tablespace, which is consistent with its role as a reference and setup data object rather than a high-volume transactional entity. Its primary key is IEX_SCORE_COMPONENTS_PK on SCORE_COMPONENT_ID. The heuristic Data Vault classification derived from the foreign key structure is satellite-leaning; when modeled in Data Vault terms, this object is best treated as a satellite describing score components, with SCORE_COMPONENT_ID acting as the business key and the standard WHO and concurrent program columns serving as descriptive attributes. The presence of ZD_EDITION_NAME in the unique index IEX_SCORE_COMPONENTS_U1 indicates this table is edition-enabled, supporting Oracle's edition-based redefinition (EBR) architecture used in EBS 12.2.x.

Key Information Stored

The most significant columns include:

• SCORE_COMPONENT_ID — Surrogate primary key and the sole column in IEX_SCORE_COMPONENTS_PK; uniquely identifies each component.
• ZD_EDITION_NAME — Edition discriminator; combined with SCORE_COMPONENT_ID in the unique index IEX_SCORE_COMPONENTS_U1, it forms the documented business-key candidate for edition-aware environments.
• SCORE_ID — Foreign key identifying the parent score engine this component belongs to; indexed by IEX_SCORE_COMPONENTS_N1 for efficient lookup by score.
• SCORE_COMP_TYPE_ID — Foreign key to the score component type, classifying the nature of the component.
• SCORE_COMP_WEIGHT — Numeric weight determining how heavily this component influences the resulting score.
• ENABLED_FLAG — Indicator of whether the component is currently active and usable by the scoring engine.
• SECURITY_GROUP_ID — Subscriber identifier, with a foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, recording the request that last modified the row.

Common Use Cases and Queries

Typical usage centers on reviewing and maintaining the configuration of scoring models, and diagnosing why particular customers receive certain collection scores. A frequent query lists all active components for a given score and their relative weights:

• SELECT SCORE_COMPONENT_ID, SCORE_ID, SCORE_COMP_TYPE_ID, SCORE_COMP_WEIGHT, ENABLED_FLAG FROM IEX.IEX_SCORE_COMPONENTS WHERE SCORE_ID = :score_id AND ENABLED_FLAG = 'Y';
• Joining to IEX_SCORE_COMP_DET and IEX_SCORE_COMP_PARAMS to reconstruct the full detail and parameter set of each component.
• Audit and change-tracking reports using LAST_UPDATE_DATE, LAST_UPDATED_BY, and the concurrent program columns to determine who last changed a score configuration.
• Weight distribution analysis to verify that the sum of SCORE_COMP_WEIGHT values across components of a score is consistent with expectations.

Related Objects

The following objects have documented relationships with IEX_SCORE_COMPONENTS:

• IEX_SCORE_COMP_DET — References this table via SCORE_COMPONENT_ID; holds detail rows for each component.
• IEX_SCORE_COMP_PARAMS — References this table via SCORE_COMPONENT_ID; stores parameter values driving component behavior.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, establishing the subscriber/security context.
• Score component type object — Referenced by SCORE_COMP_TYPE_ID, providing the classification of each component.