Results for “discharge_date”

20 results




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

Overview

IEX_BANKRUPTCIES is a transactional table within the Oracle E-Business Suite Collections (IEX) module. It stores and tracks bankruptcy case information associated with customer accounts, delinquencies, and collection cases. Each row in this table represents an individual bankruptcy proceeding filed by or against a customer, capturing the legal, financial, and administrative dimensions of that proceeding. The table resides in the IEX schema and is classified as VALID in Oracle EBS releases 12.1.1 and 12.2.2.

The entity's principal role is to provide collections agents and credit analysts with a consolidated view of bankruptcy activity so that collection efforts, invoicing, and credit holds can be adjusted in accordance with legal constraints such as the automatic stay. The documented physical schema contains 75 columns, including a set of descriptive flexfield (DFF) attribute columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) plus the standard Oracle WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

From a Data Vault modeling perspective, the heuristic classification supplied in the metadata identifies this table as standalone. It should therefore be treated as a candidate satellite (or, depending on how the CAS_ID and DELINQUENCY_ID relationships are modeled, a link with an attached satellite) rather than a pure hub, since its grain is the individual bankruptcy event.

Key Information Stored

The surrogate primary key is BANKRUPTCY_ID, enforced by the unique index IEX_BANKRUPTCIES_U1 and the constraint IEX_BANKRUPTCIES_PK. The most significant business and descriptive columns include:

Common Use Cases and Queries

Collections teams query this table to determine which customer accounts are under bankruptcy protection and to suppress dunning, statements, and invoicing accordingly. Credit departments use it to apply credit holds and to assess exposure by chapter type. Reporting typically identifies active filings, upcoming court dates, and discharge timelines.

A representative query joining the parent case and customer account follows:

  • SELECT b.bankruptcy_id, b.case_number, b.chapter_code, b.bankruptcy_file_date, a.account_number, c.case_number FROM iex_bankruptcies b, hz_cust_accounts a, iex_cases_all_b c WHERE b.cust_account_id = a.cust_account_id AND b.cas_id = c.cas_id AND b.active_flag = 'Y';
  • SELECT chapter_code, COUNT(*) FROM iex_bankruptcies WHERE cease_collections_yn = 'Y' GROUP BY chapter_code;
  • SELECT bankruptcy_id FROM iex_bankruptcies WHERE discharge_date BETWEEN :from_date AND :to_date;

Related Objects

The following objects are directly related through the documented foreign key structure and are the most relevant for joins and dependency analysis:

  • IEX_CASES_ALL_B — Parent collection case (join on CAS_ID).
  • IEX_DELINQUENCIES_ALL — Associated delinquency record (join on DELINQUENCY_ID).
  • HZ_CUST_ACCOUNTS — Debtor customer account (join on CUST_ACCOUNT_ID).
  • FND_SECURITY_GROUPS — Row-level security grouping (join on SECURITY_GROUP_ID).
  • IEX_BANKRUPTCIES_PK / IEX_BANKRUPTCIES_U1 — Primary key constraint and unique index on BANKRUPTCY_ID.

Because the metadata classifies this table as standalone, no additional child tables are documented as referencing it directly, though case and collections APIs that read the parent case typically surface bankruptcy status for downstream processing.