Search Results iex_writeoffs




Overview
Explore in AI Chat

Overview

IEX_WRITEOFFS is a core transactional table in the Oracle EBS Advanced Collections (IEX) module. It stores the master record for each write-off action processed against a delinquent customer obligation, capturing the request, approval workflow state, financial amount, and final disposition. The table resides in the IEX schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Per the ETRM physical schema documentation for 12.2.2, the table contains 63 columns and is owned by IEX with a single-column surrogate primary key, IEX_WRITEOFFS_PK, defined on WRITEOFF_ID. The Data Vault classification mined heuristically from the foreign-key structure is designated as "standalone," indicating that the table is not a pure hub, link, or satellite under a strict Data Vault reading. In practice, it behaves as a hybrid hub-satellite because WRITEOFF_ID acts as a durable business identifier while attributes such as WRITEOFF_AMOUNT, WRITEOFF_DATE, and the approval flags describe state that evolves over the record's lifetime.

Key Information Stored

The surrogate primary key, WRITEOFF_ID, uniquely identifies each write-off record and is also exposed as a unique business-key candidate through the unique index IEX_WRITEOFFS_U1. The most operationally significant columns include:

Common Use Cases and Queries

Typical reporting includes write-off aging, approval turnaround analysis, and bad-debt exposure by customer or operating unit. A common query pattern joins the write-off to its case and delinquency:

  • SELECT w.WRITEOFF_ID, w.WRITEOFF_AMOUNT, w.WRITEOFF_DATE, c.CASE_NUMBER FROM IEX_WRITEOFFS w, IEX_CASES_ALL_B c WHERE w.CAS_ID = c.CASE_ID;
  • Aggregating write-offs by reason and period using WRITEOFF_REASON, WRITEOFF_DATE, and WRITEOFF_AMOUNT.
  • Filtering pending approvals via SUGGESTION_APPROVED_FLAG and APPROVER_ID.
  • Reconciling write-off amounts to customer accounts through CUST_ACCOUNT_ID join to HZ_CUST_ACCOUNTS.

Related Objects

The table participates in a small but well-defined relationship set:

  • IEX_DELINQUENCIES_ALL — joined via DELINQUENCY_ID.
  • IEX_CASES_ALL_B — joined via CAS_ID.
  • HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.
  • IEX_WRITEOFF_OBJECTS — child table referencing WRITEOFF_ID, storing the individual objects subject to the write-off.