Results for “score_comp_type_id”

50+ results




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

Overview

The IEX_METRIC_SUMMARIES_ALL table is a core data object within the Oracle EBS IEX – Collections module (Advanced Collections). It stores batch-level summary information for collection metrics — the calculated scores, values, and ratings that drive collector prioritization, strategy assignment, and delinquency analytics. Rather than persisting each metric for every individual transaction or customer interaction, this table captures aggregated metric outcomes keyed by a scoring component type, an organization, and a referenced object. It therefore serves as the authoritative store of computed metric results that Collection strategies and dashboards consume at runtime.

Under the heuristic Data Vault classification mined from the foreign-key structure, this table is modeled as standalone. That is, it contains no downstream referencing tables and does not participate in a many-to-many link. As a modeling suggestion, it behaves as a satellite-like fact holder: the SCORE_COMP_TYPE_ID foreign key anchors the metric definition, while the value, rating, and audit columns describe the measured outcome at a point in time. Because it is org-striped (ORG_ID) and carries the standard EBS _ALL suffix semantics, it is designed to support Multi-Org (MOAC) access across operating units.

Key Information Stored

The documented physical schema exposes eleven columns. The most important are:

  • OBJECT_ID – Identifies the specific business object (e.g., a customer, deliverable, or transaction) to which the metric summary pertains; the primary business-key candidate that ties the summary back to its subject.
  • OBJECT_TYPE – A discriminator that qualifies the meaning of OBJECT_ID, indicating which entity type is being measured. Together with OBJECT_ID it forms the logical identity of a summary row.
  • SCORE_COMP_TYPE_ID – Foreign key to IEX_SCORE_COMP_TYPES_B; identifies the scoring component / metric definition being summarized. This is the principal business-key candidate on the definition side.
  • METRIC_VALUE – The computed numeric value produced by the scoring engine for the given object and metric.
  • METRIC_RATING – The derived rating or grade associated with the metric value, used to bucket customers or items into strategy tiers.
  • ORG_ID – Operating unit identifier enabling Multi-Org security partitioning of the summary rows.
  • LAST_UPDATE_DATE, CREATION_DATE – Standard audit timestamps for the record lifecycle.
  • CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Who-created/who-changed columns, essential for audit trails and concurrent-program attribution.

The table does not expose a single surrogate primary key column (such as a sequence-generated ID) in the documented metadata; identity is expressed through the composite of OBJECT_ID, OBJECT_TYPE, SCORE_COMP_TYPE_ID, and ORG_ID.

Common Use Cases and Queries

Collection analysts and report developers query this table to retrieve the latest metric outcomes for a scoring component. A typical pattern joins the definition table to resolve metric names:

  • Metric retrieval by component: SELECT m.object_id, m.metric_value, m.metric_rating FROM iex_metric_summaries_all m WHERE m.score_comp_type_id = :p AND m.org_id = :org;
  • Dashboards and Strategy Workbench: Advanced Collections screens display metric scores per customer; the same data is surfaced via this table for interactive querying.
  • Batch reconciliation: Compare counts and max(LAST_UPDATE_DATE) per SCORE_COMP_TYPE_ID to verify the scoring concurrent program completed for the period.
  • Audit reporting: Filter on CREATED_BY and CREATION_DATE to trace which job generated a batch of summaries.
  • MOAC-aware extracts: Always constrain ORG_ID or apply MO_GLOBAL initialization to respect operating-unit security.

Related Objects

  • IEX_SCORE_COMP_TYPES_B – The parent definition table referenced by SCORE_COMP_TYPE_ID; join to obtain metric names, descriptions, and scoring logic.
  • IEX_SCORE_COMPONENTS and related score component tables – Define the rule sets that produce the values stored here.
  • IEX_STRATEGIES / IEX_STRATEGY_ASSIGNMENTS – Consume metric ratings to assign collection strategies to customers.
  • IEX_CUSTOMERS / HZ_CUST_ACCOUNTS – Logical subjects targeted by OBJECT_ID when OBJECT_TYPE denotes a customer.
  • IEX_DELINQUENCIES / IEX_DUNNING_* – Downstream collections reports that overlay metric scores with delinquency data.
  • FND_USER – Join on CREATED_BY/LAST_UPDATED_BY for audit attribution.