Search Results iex_del_statuses




Overview

IEX_DEL_STATUSES is a configuration and reference table within the Oracle E-Business Suite Collections (IEX) module. Its documented purpose is to hold delinquency score and status configuration — the threshold definitions and scoring bands that the Collections application uses to classify a delinquent customer account into a particular delinquency status. Rather than storing transaction-level collection activity, the table stores the rules that drive classification logic, making it a foundational setup object that must be populated correctly before delinquency processing can produce meaningful results.

The object is owned by the IEX schema and is marked VALID in the ETRM 12.2.2 documentation, with a documented footprint of 17 columns. A heuristic Data Vault classification mined from the foreign key structure suggests this table behaves as a satellite-leaning object. In modeling terms, it is best understood as descriptive configuration data that hangs off a delinquency status identifier rather than as an independent hub or as a link resolving many-to-many relationships. The presence of editioning support through ZD_EDITION_NAME further confirms its role as a maintained reference entity rather than a high-volume transactional table.

Key Information Stored

The table is anchored by the surrogate primary key IDE_PK, which is defined on the DEL_STATUS_ID column. DEL_STATUS_ID also serves as the foreign key pointing to IEX_DELINQUENCIES_ALL, tying each configuration row to the delinquency framework it supports. The unique index IEX_DEL_STATUSES_U1 is defined on the combination of DEL_STATUS_ID and ZD_EDITION_NAME, making that pair the business-key candidate for the object and reflecting the editioning model introduced in recent EBS releases.

The most significant columns fall into three groups:

Common Use Cases and Queries

Typical usage centers on reviewing or tuning the delinquency score bands. A reporting query enumerates the configured bands ordered by score range so that overlapping or gapped thresholds can be identified before delinquency scoring runs:

  • SELECT del_status_id, score_value_low, score_value_high, del_status FROM iex.iex_del_statuses WHERE org_id = :org_id ORDER BY score_value_low;
  • Joining to IEX_DELINQUENCIES_ALL on DEL_STATUS_ID to see which delinquent accounts resolve to each configured status.
  • Auditing the last refresh of configuration by filtering on PROGRAM_UPDATE_DATE or REQUEST_ID to reconcile with concurrent program output.
  • Validating the unique business key by grouping on DEL_STATUS_ID and ZD_EDITION_NAME to detect duplicate edition rows.

Related Objects

The most significant related object is IEX_DELINQUENCIES_ALL, which this table references through DEL_STATUS_ID — the join that connects configuration rows to actual delinquent account records. The unique index IEX_DEL_STATUSES_U1 is the principal supporting database object, enforcing the DEL_STATUS_ID and ZD_EDITION_NAME business key. Reporting views and concurrent programs in the Collections module that perform delinquency scoring and status assignment consume this configuration directly, using DEL_STATUS, SCORE_VALUE_LOW and SCORE_VALUE_HIGH to drive classification. Multi-org queries additionally depend on ORG_ID alignment with the operating unit context.