Results for “predicted_recovery_amount”

31 results




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

Overview

IEX.IEX_DELINQUENCIES_ALL is a transactional table within the Oracle EBS Advanced Collections module (product code IEX). It holds transaction data about customer delinquencies — the central record that identifies a delinquent customer obligation and drives the Collections work queue, dunning, scoring, and recovery lifecycle. Each row represents one delinquency case tied to a customer account, transaction, and payment schedule.

The table is owned by the IEX schema and is marked VALID. Physically it comprises 42 columns. In Oracle EBS 12.1.1 and 12.2.2, IEX objects reside in the same schema and are largely unaffected by the 12.2 online patching editioning changes applied to many other product schemas, so references to IEX.IEX_DELINQUENCIES_ALL remain stable across both releases.

From a Data Vault modeling perspective, the mined relationship structure classifies this table as hub-leaning. The surrogate primary key DELINQUENCY_ID is referenced by a large number of dependent collections tables, which is characteristic of a hub entity carrying the business case. This classification is a heuristic suggestion, not an Oracle-documented designation.

Key Information Stored

The single-column surrogate primary key is DELINQUENCY_ID, enforced by the unique constraint IEX_DELINQUENCIES_PK. Three additional unique indexes expose business-key candidates: IEX_DELINQUENCIES_ALL_U1 on DELINQUENCY_ID (redundant with the PK), IEX_DELINQUENCIES_ALL_U2 on PAYMENT_SCHEDULE_ID, and IEX_DELINQUENCIES_ALL_U3 on CASE_ID. The latter two are the practical natural keys for identifying a delinquency by its underlying payment obligation or its case.

Common Use Cases and Queries

The table is queried by collections analysts and reporting tools to enumerate open delinquencies, drive the work queue, and feed aging and recovery analytics.

  • Listing delinquent accounts for an operating unit: SELECT delinquency_id, cust_account_id, status, uWQ_status FROM iex_delinquencies_all WHERE org_id = :org_id;
  • Joining to dunning history to see which cases have been dunned: SELECT d.delinquency_id, d.cust_account_id, dn.dunning_id FROM iex_delinquencies_all d JOIN iex_dunnings dn ON dn.delinquency_id = d.delinquency_id;
  • Recovery forecasting: aggregate PREDICTED_RECOVERY_AMOUNT and PREDICTED_CHANCE by STRATEGY_ID.
  • Work-queue backlog reporting filtered on UWQ_STATUS and UWQ_ACTIVE_DATE.
  • Case lookup by business key: ... WHERE case_id = :case_id; or ... WHERE payment_schedule_id = :ps_id;.

Related Objects

The table is a hub referenced extensively by dependent collections sub-entities via DELINQUENCY_ID. The most significant related objects include: