Search Results iex_litigations




Overview
Explore in AI Chat

Overview

IEX_LITIGATIONS is a transaction-detail table within the Oracle EBS Advanced Collections (IEX) module. It stores litigation-related records raised against delinquent customer accounts, capturing the legal actions, court events, judgements, and hold requests associated with a collections dispute. Rows in this table are owned by the IEX schema and are keyed by the surrogate primary key ILT_PK, which is physically implemented as the LITIGATION_ID column through the unique index IEX_LITIGATIONS_U1. In Oracle EBS 12.1.1 and 12.2.2 the table is registered as VALID and forms part of the collections delinquency workflow that collectors and credit analysts use to escalate non-paying customers into formal legal proceedings.

The ETRM metadata classifies IEX_LITIGATIONS as a standalone object under the heuristic Data Vault model. Because it references multiple parent entities (delinquencies, customer accounts, and security groups) without being joined through an intermediate link table, the most natural Data Vault interpretation is that it behaves as a satellite attached to the delinquency hub, with additional dimensional references to customer and security-group hubs. It is not a pure hub or link in its own right.

Key Information Stored

The table contains 47 documented columns covering identification, legal status, workflow flags, and standard WHO/audit attributes. The columns of greatest functional importance are:

Common Use Cases and Queries

Collections analysts query IEX_LITIGATIONS to monitor litigation pipelines, ageing of court cases, and hold decisions. A typical join returns the customer and delinquency context for each litigation:

  • Open litigations by customer: join IEX_LITIGATIONS L to HZ_CUST_ACCOUNTS HCA on L.CUST_ACCOUNT_ID = HCA.CUST_ACCOUNT_ID, filtered by ORG_ID and disposition code.
  • Litigations raised against delinquencies: join to IEX_DELINQUENCIES_ALL on DELINQUENCY_ID to obtain the collection status that triggered the legal action.
  • Court calendar report: filter on COURT_DATE between system dates to produce upcoming hearings, grouped by DISPOSITION_CODE.
  • Hold approval audit: select rows where CREDIT_HOLD_REQUEST_FLAG = 'Y' and CREDIT_HOLD_APPROVED_FLAG = 'N' to identify pending approvals.
  • Multi-org reporting: always constrain on ORG_ID and SECURITY_GROUP_ID to respect operating-unit and security-group visibility.

Related Objects

The most significant objects related to IEX_LITIGATIONS through documented keys are:

  • IEX_DELINQUENCIES_ALL — parent delinquency table joined on DELINQUENCY_ID.
  • HZ_CUST_ACCOUNTS — customer master joined on CUST_ACCOUNT_ID.
  • FND_SECURITY_GROUPS — security model joined on SECURITY_GROUP_ID.
  • HZ_CUST_ACCT_SITES_ALL / HZ_CUST_SITE_USES_ALL — resolved via CUSTOMER_SITE_USE_ID for site-level context.
  • IEX_LITIGATIONS_U1 — unique index enforcing the business key on LITIGATION_ID.
  • OKC_CONTRACTS_ALL — contract reference resolved via CONTRACT_ID / CONTRACT_NUMBER.

In practice, these objects are consumed together through the Collections workbench and related concurrent programs rather than directly via public APIs, so report developers should treat IEX_LITIGATIONS as an internal IEX detail table and respect its security-group and org constraints in every query.