Search Results iex_repossessions




Overview
Explore in AI Chat

Overview

IEX_REPOSSESSIONS is a transaction-detail table in the Oracle EBS Collections (IEX) module. It stores the operational and legal attributes associated with the repossession of a financed asset — typically a vehicle, equipment unit, or other collateralized item — after a customer delinquency has escalated to recovery action. The table functions as the system of record for repossession events, capturing the date of recovery, the asset involved, its assessed value, and the downstream remarketing or legal disposition path.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is characterized as standalone, meaning it does not act as a classical hub or link within a hub-and-link model but rather serves as a self-contained event record keyed by a single business identifier. In a Data Vault modeling exercise, this suggests IEX_REPOSSESSIONS could be modeled as a satellite or a standalone transaction entity rather than a linking structure. The physical schema spans 51 documented columns under the IEX schema, owned by Oracle and flagged VALID.

Key Information Stored

The table is anchored by a surrogate primary key, REPOSSESSION_ID, which is enforced by the unique index IEX_REPOSSESSIONS_U1 and forms the IRN_PK constraint. This column is the canonical business-key candidate for joins and lookups.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY/ATTRIBUTE1–15 flexfield set are present, providing extensibility and traceability.

Common Use Cases and Queries

Collections and recovery analysts query this table to track repossession volume, recovery value, and legal status by customer or period. A typical reporting query joins the customer account and delinquency sources:

  • Repossession listings by date range: SELECT r.REPOSSESSION_ID, r.REPOSSESSION_DATE, r.ASSET_NUMBER, r.ASSET_VALUE FROM IEX.IEX_REPOSSESSIONS r WHERE r.REPOSSESSION_DATE BETWEEN :from AND :to;
  • Customer-level history: join to HZ_CUST_ACCOUNTS on CUST_ACCOUNT_ID and to IEX_DELINQUENCIES_ALL on DELINQUENCY_ID to reconstruct the delinquency-to-repossession chain.
  • Legal pipeline reporting: filter on REPLEVIN_COURT_DATE and REPLEVIN_JUDGEMENT_DATE to monitor attorney-driven recovery cases.
  • Remarketing analysis: aggregate ASSET_VALUE grouped by DISPOSITION_CODE and REMARKET_FLAG to assess recovery rates.
  • Org-security-scoped dashboards using ORG_ID and SECURITY_GROUP_ID.

Related Objects

  • IEX_REPOS_OBJECTS — references this table via REPOSSESSION_ID; stores the line-level objects tied to a repossession.
  • IEX_DELINQUENCIES_ALL — parent delinquency record referenced through DELINQUENCY_ID.
  • HZ_CUST_ACCOUNTS — customer account master referenced through CUST_ACCOUNT_ID.
  • FND_SECURITY_GROUPS — security-group definition referenced through SECURITY_GROUP_ID.
  • IEX_CUSTOMER_ACCOUNTS and IEX_DISPOSITIONS (conceptual peers) — used alongside for account and disposition lookups.
  • OE_ORDER_HEADERS_ALL and MTL_SYSTEM_ITEMS — commonly joined when repossessed assets are resold or revalued.

Together these objects form the repossession and recovery backbone within Oracle Collections, enabling both operational management and downstream financial reconciliation.