Search Results iex_score_comp_params_u1

Overview

IEX_SCORE_COMP_PARAMS is a seed-data configuration table owned by the IEX schema within Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It belongs to the Oracle Advanced Collections (IEX) product family and stores the scoring parameters that govern how individual score components are evaluated when Collections assigns scores to customers, transactions, or collection strategies. Each row represents a defined parameter for a given score component, supplying the code, value, and activation status that the scoring engine consumes during evaluation.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as a repository of setup and reference data rather than transactional volume. It carries the standard Oracle Applications Who columns, the multi-org style SECURITY_GROUP_ID used for CRM Online Services subscriber isolation, and the ZD_EDITION_NAME column that supports edition-based redefinition in 12.2.x online patching. Based on the documented foreign key structure, the table is standalone with respect to Data Vault modeling heuristics: it references parent entities but is not itself decomposed into hub, link, or satellite constructs. A sound modeling suggestion is to treat SCORE_COMP_PARAM_ID as a durable business key hub of scoring parameters, with the descriptive and Who columns forming a satellite.

Key Information Stored

The surrogate primary key is SCORE_COMP_PARAM_ID, enforced by the constraint IEX_SCORE_COMP_PARAMS_PK. The business-key candidate is expressed through the unique index IEX_SCORE_COMP_PARAMS_U1, which covers SCORE_COMP_PARAM_ID together with ZD_EDITION_NAME. The most significant columns are:

• SCORE_COMP_PARAM_ID — surrogate identifier for the parameter row.
• SCORE_COMPONENT_ID — foreign key to IEX_SCORE_COMPONENTS; identifies the owning score component.
• CODE — the parameter code the scoring engine resolves at runtime.
• VALUE — the configured value or threshold applied to that code.
• DESCRIPTION — free-text explanation of the parameter's purpose.
• ACTIVE_FLAG — indicates whether the parameter is currently in force.
• SECURITY_GROUP_ID — subscriber identifier, foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — editioning column supporting 12.2 online patching.
• OBJECT_VERSION_NUMBER — optimistic locking for the HTML front end.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Concurrent program columns — PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes auditing the scoring configuration applied to a component, reporting which parameters are inactive, and diagnosing unexpected collection scores. A representative query joins the parameter table to its component parent:

• SELECT p.SCORE_COMP_PARAM_ID, p.CODE, p.VALUE, p.ACTIVE_FLAG FROM IEX.IEX_SCORE_COMP_PARAMS p WHERE p.SCORE_COMPONENT_ID = :component_id AND p.ACTIVE_FLAG = 'Y';
• SELECT c.NAME, p.CODE, p.VALUE FROM IEX.IEX_SCORE_COMPONENTS c, IEX.IEX_SCORE_COMP_PARAMS p WHERE c.SCORE_COMPONENT_ID = p.SCORE_COMPONENT_ID ORDER BY c.NAME, p.CODE;

Reporting extracts commonly filter on ACTIVE_FLAG for setup validation, and support teams query by CODE to trace the effective configuration behind a score. Because the table is seed data, all access should be read-only; modifications must occur through Oracle Applications programs, per the documented warning that this object is for Oracle Internal Use Only.

Related Objects

The principal relationships documented are:

• IEX_SCORE_COMPONENTS — referenced by SCORE_COMPONENT_ID; the parent component for each parameter.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for subscriber isolation.
• FND_USER — implied by CREATED_BY and LAST_UPDATED_BY.
• FND_CONCURRENT_PROGRAM — implied by PROGRAM_ID.
• FND_CONCURRENT_REQUESTS — implied by REQUEST_ID.
• FND_APPLICATION — implied by PROGRAM_APPLICATION_ID.
• FND_LOGINS — implied by LAST_UPDATE_LOGIN.