Results for “score_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IEX_SCORE_HISTORIES is a table in the IEX (Collections) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores historical data about collection scores, providing an auditable trail of how scoring values for a given scoring object evolved over time. Collection scoring in Advanced Collections assigns numeric values to customers, delinquencies, or strategies to drive prioritization, strategy assignment, and collector workload balancing. Because scores are recalculated by concurrent programs, the current value alone is insufficient for trend analysis, score volatility reporting, or reconstructing what a collector saw on a prior date. IEX_SCORE_HISTORIES fills that gap by persisting point-in-time snapshots of each score alongside the context in which it was produced.

From a Data Vault modeling perspective, the mined relationship structure suggests this object behaves as a satellite-leaning entity. Its grain is driven by the parent delinquency (via DEL_DELINQUENCY_ID) and the score object, while the descriptive measures and audit attributes accumulate against that parent key. Modelers designing a warehouse layer should treat it as a historical descriptor table rather than as an independent hub.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• SCORE_HISTORY_ID — surrogate primary key, enforced by IEX_SCORE_HISTORIES_PK and backed by unique index IEX_SCORE_HISTORIES_U1. This is the only documented business-key candidate.
• SCORE_ID — reference to the score definition that produced the value.
• SCORE_VALUE — the numeric score captured at that point in time; the principal analytical measure.
• SCORE_OBJECT_ID / SCORE_OBJECT_CODE — the entity being scored (for example a customer, delinquency, or strategy) and its type discriminator.
• PARTY_ID — the trading party or customer associated with the score.
• ICO_ID — the collections-related identifier (such as a collection case or interaction) tied to the score.
• DEL_DELINQUENCY_ID — foreign key to IEX_DELINQUENCIES_ALL, anchoring the history to a specific delinquency.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security grouping.
• ORG_ID — operating unit context.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — identify the concurrent request and program that generated the record, enabling traceability back to the scoring run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns consistent with the EBS WHO columns pattern.

Common Use Cases and Queries

Typical reporting scenarios include score trend analysis, comparison of current versus prior scores, and verification of the scoring run that produced a given value. A score trend query joins the table to its parent delinquency:

• SELECT h.SCORE_HISTORY_ID, h.PARTY_ID, h.SCORE_VALUE, h.CREATION_DATE, h.REQUEST_ID FROM iex_score_histories h WHERE h.DEL_DELINQUENCY_ID = :del_id ORDER BY h.CREATION_DATE;
• Score movement detection between the two most recent snapshots uses an analytic LAG(SCORE_VALUE) window partitioned by SCORE_OBJECT_ID.
• Tracing a score back to its generating run joins PROGRAM_ID/REQUEST_ID to FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS.
• Multi-org reporting filters on ORG_ID and SECURITY_GROUP_ID to respect operating unit and security group access.

Related Objects

The most significant related objects, based on documented foreign keys and the Collections data model, are:

• IEX_DELINQUENCIES_ALL — joined on IEX_SCORE_HISTORIES.DEL_DELINQUENCY_ID = IEX_DELINQUENCIES_ALL.DELINQUENCY_ID; the primary parent for score history.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs row-level security visibility.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — joined via REQUEST_ID and PROGRAM_ID for run traceability.
• IEX_SCORES / score definition tables — joined via SCORE_ID to resolve score names and thresholds.
• IEX_STRATEGIES and IEX_STRATEGY_ASSIGNMENTS — related via PARTY_ID and ICO_ID where score values drive strategy selection.
• HZ_PARTIES — joined on PARTY_ID to obtain customer identification for score reporting.