Search Results score_comp_param_id

Overview

The IEX_SCORE_COMP_PARAMS table is a foundational configuration object within the Oracle EBS Collections (IEX) module. It stores the individual parameters that drive the behavior of score components, which in turn feed the collection scoring engine used to prioritize customers, invoices, and delinquent accounts for collector follow-up. Each row defines a discrete attribute—an expected value, threshold, or weighting input—associated with a parent score component. Because scoring logic in Advanced Collections is highly configurable, this table allows implementers to tune how a given component evaluates its underlying data without modifying application code.

The table is owned by the IEX schema, is marked VALID, and contains eighteen documented columns in the 12.2.2 physical schema. The heap table is classified heuristically as a satellite under a Data Vault modeling suggestion: it is standalone with no descendant foreign keys, and it carries descriptive attributes (CODE, VALUE, DESCRIPTION, ACTIVE_FLAG) that describe the state of its parent score component over time rather than acting as a hub or link between independent business entities. The parent SCORE_COMPONENT_ID reference positions this table as a dependent detail satellite hanging off the score component entity.

Key Information Stored

The surrogate primary key is SCORE_COMP_PARAM_ID, enforced by the IEX_SCORE_COMP_PARAMS_PK constraint. A secondary unique index, IEX_SCORE_COMP_PARAMS_U1, spans SCORE_COMP_PARAM_ID and ZD_EDITION_NAME, indicating an editioned business-key candidate that supports the EBS online patching (ZD_EDITION_NAME) infrastructure introduced in 12.2.

• SCORE_COMPONENT_ID — Foreign key to IEX_SCORE_COMPONENTS; identifies the parent component to which the parameter belongs.
• CODE — The parameter identifier or lookup key that the scoring engine interprets.
• VALUE — The configured value, threshold, or operand assigned to that parameter.
• DESCRIPTION — Free-text explanation of the parameter's purpose.
• ACTIVE_FLAG — Enables or disables the parameter without deletion.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking control for concurrent updates.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY — Standard EBS audit columns.
• PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program and request traceability.
• ZD_EDITION_NAME — Editioning column underpinning the unique index.

Common Use Cases and Queries

Consultants typically query this table to audit scoring configuration, verify parameter values after a setup change, or troubleshoot unexpected scoring behavior. A representative query lists all active parameters for a component:

• SELECT p.CODE, p.VALUE, p.DESCRIPTION FROM IEX.IEX_SCORE_COMP_PARAMS p WHERE p.SCORE_COMPONENT_ID = :component_id AND p.ACTIVE_FLAG = 'Y' AND p.ZD_EDITION_NAME = 'ORA$BASE';
• Joining to IEX_SCORE_COMPONENTS to view parameters across an entire score definition.
• Identifying components missing required parameters by comparing configured CODE values against expected parameter sets.
• Extracting configuration for change-control or migration documentation.

Related Objects

• IEX_SCORE_COMPONENTS — Parent table via SCORE_COMPONENT_ID; defines each scoring component.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security partitioning.
• IEX_SCORE_COMP_PARAMS_PK — Primary key constraint on SCORE_COMP_PARAM_ID.
• IEX_SCORE_COMP_PARAMS_U1 — Unique index on SCORE_COMP_PARAM_ID and ZD_EDITION_NAME.
• IEX_SCORE_DEFINITIONS / IEX_SCORING_ENGINE — Consume parameter values at runtime during collection scoring.