Search Results iex_score_comp_det




Overview
Explore in AI Chat

Overview

IEX_SCORE_COMP_DET is a table in the IEX (Collections) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description states that it "stores range and value details for components," which places it as the detail-level companion to the scoring components that drive Advanced Collections strategy and scoring engines. In the Collections architecture, scoring components define the weighted inputs (for example, invoice age, customer risk, payment history) that the scoring engine uses to compute a numeric collection score for a customer or transaction. IEX_SCORE_COMP_DET provides the ranges and corresponding values that translate a raw component measurement into a score contribution, and it also holds the resulting value used by the engine.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as standalone. That classification is presented here as a modeling suggestion only; because the table carries its own primary key and business-key uniqueness without an obvious dependent-child or link pattern, it can reasonably be treated as a standalone dimension or reference satellite rather than a transactional hub or link in a Data Vault reimplementation. Organizations designing a warehouse layer around ETRM data should validate that interpretation against actual data cardinality and change frequency before committing to it.

Key Information Stored

The table is documented with 15 columns; the most significant are summarized below.

  • SCORE_COMP_DET_ID — the surrogate primary key. The PK constraint is documented as IEX_SCORE_COMP_DET_FK, which is enforced on this column. This is the unique identifier for each range/value detail row.
  • SCORE_COMPONENT_ID — foreign key to IEX_SCORE_COMPONENTS. This is the critical business relationship column, tying each range/value pair back to its parent scoring component.
  • VALUE — the score value assigned when a measurement falls within the associated range, i.e., the contribution applied by the scoring engine.
  • RANGE_LOW and RANGE_HIGH — the lower and upper bounds that define the interval to which VALUE applies. Together these implement the banding logic of the scoring component.
  • NEW_VALUE — a secondary value field, typically used where a component supports an alternate or post-adjustment value distinct from the primary VALUE.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing the multi-tenant security partitioning used throughout EBS.
  • ZD_EDITION_NAME — the edition/version discriminator associated with the unique index IEX_SCORE_COMP_DET_U1 (SCORE_COMP_DET_ID, ZD_EDITION_NAME), indicating the table participates in EBS edition-based redefinition.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
  • Audit and who-columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and PROGRAM_ID, the standard EBS audit and concurrent-program attribution set.

The documented unique index IEX_SCORE_COMP_DET_U1 on (SCORE_COMP_DET_ID, ZD_EDITION_NAME) is the closest thing to a business-key candidate, though SCORE_COMPONENT_ID combined with the range bounds is the more meaningful logical key in practice.

Common Use Cases and Queries

Typical use cases center on interpreting or auditing how a collection score was derived, and on maintaining the range banding configuration for a scoring component. A frequent pattern is to retrieve all ranges for a component in order:

  • Listing ranges for a component: SELECT range_low, range_high, value, new_value FROM iex_score_comp_det WHERE score_component_id = :component_id ORDER BY range_low;
  • Reporting component configuration by joining to IEX_SCORE_COMPONENTS to include the component name and weight alongside each band.
  • Validating configuration integrity — detecting gaps or overlaps between consecutive RANGE_LOW/RANGE_HIGH bands within a component.
  • Auditing changes over time using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance or troubleshooting unexplained score shifts.

Because the table is secured, queries run under a responsibility must respect SECURITY_GROUP_ID; reporting extracts typically join to FND_SECURITY_GROUPS or rely on the security predicate applied by the application's views.

Related Objects

  • IEX_SCORE_COMPONENTS — parent table; join on IEX_SCORE_COMP_DET.SCORE_COMPONENT_ID = IEX_SCORE_COMPONENTS.SCORE_COMPONENT_ID. This is the primary relationship for this object.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID to enforce group-based data security.
  • IEX_SCORE_COMPONENTS related scoring configuration tables (for example, scoring component associations and score-to-strategy mappings) that consume the component values defined here.
  • IEX_STRATEGIES / IEX_STRATEGY_* — strategy definitions that ultimately consume computed component scores.
  • FND_CONCURRENT_PROGRAMS — attributable via PROGRAM_ID for the concurrent program that last updated a row.

These relationships should be confirmed against the deployed 12.1.1 or 12.2.2 instance, since documented FK metadata for this table is limited to the two references above.