Results for “writeoff_invoice_id”

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

Overview

The IEX_WRITEOFF_INVOICES table is a Collections module (IEX) data object in Oracle E-Business Suite, owned by the IEX schema. It records invoice-level write-off decisions applied during collections and delinquency management processing. Each row represents the association between a write-off disposition and a specific lease invoice or lease invoice line, together with the delinquency context and security-group scoping required by Multi-Org Access Control (MOAC). The table is populated when collections agents or automated write-off programs flag delinquent receivables for write-off, and it serves as the audit anchor linking the operational decision to the underlying lease invoice.

The metadata classifies this object heuristically as standalone within a Data Vault modeling perspective: it carries its own surrogate key and descriptive attributes rather than acting purely as a hub, link, or satellite. In practice this designation suggests that a Data Vault implementation could treat WRITEOFF_INVOICE_ID as a hub key, with disposition and reason attributes modeled as a satellite, and the references to delinquency and invoice identifiers modeled as links. This is a modeling suggestion, not an EBS-enforced constraint.

The documented physical schema for ETRM 12.2.2 lists 20 columns. The object is marked VALID, indicating no invalidated compilation state in the data dictionary. The same structure is generally applicable to 12.1.1 and 12.2.2, since Collections object definitions remained stable across these releases.

Key Information Stored

• WRITEOFF_INVOICE_ID — surrogate primary key, enforced by unique index IEX_WRITEOFF_INVOICES_U1. This is the business-key candidate for integration and de-duplication.
• LEASE_INVOICE_ID — reference to the lease invoice being written off; the principal transaction identifier.
• LEASE_INV_LINE_ID — the specific invoice line when the write-off is applied at line level rather than header level.
• OBJECT_CODE / OBJECT_ID — a generic reference pair identifying the source object type and instance associated with the write-off.
• DISPOSITION_CODE — the classification of the write-off action taken against the invoice.
• DISP_REASON_CODE — the reason code explaining why the disposition was assigned.
• ACTIVE_YN — flag indicating whether the write-off record is currently active or has been superseded.
• DELINQUENCY_ID — foreign key to IEX_DELINQUENCIES_ALL, tying the write-off to the delinquency record that triggered it.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing MOAC security-group visibility.
• Audit and concurrency columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER provide standard WHO audit and optimistic-locking support.
• Concurrent program columns — PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID attribute rows to the concurrent request that created or last updated them.

Common Use Cases and Queries

Typical reporting scenarios include listing all write-offs for a given delinquency, auditing disposition and reason code distributions, and reconciling write-off activity by security group. A representative query joining the delinquency parent is:

• SELECT w.WRITEOFF_INVOICE_ID, w.LEASE_INVOICE_ID, w.DISPOSITION_CODE, w.DISP_REASON_CODE, w.ACTIVE_YN FROM IEX.IEX_WRITEOFF_INVOICES w, IEX.IEX_DELINQUENCIES_ALL d WHERE w.DELINQUENCY_ID = d.DELINQUENCY_ID AND w.ACTIVE_YN = 'Y';
• Filtering by SECURITY_GROUP_ID to respect MOAC data access in custom reports.
• Joining to FND_SECURITY_GROUPS for security-group naming in ad-hoc extracts.
• Reconciling concurrent program output using REQUEST_ID against FND_CONCURRENT_REQUESTS.

Because the row set is relatively narrow (20 columns) and driven by collections events, these patterns are efficient when indexed on DELINQUENCY_ID and SECURITY_GROUP_ID.

Related Objects

• IEX_DELINQUENCIES_ALL — parent delinquency record; joined on DELINQUENCY_ID.
• FND_SECURITY_GROUPS — MOAC security group; joined on SECURITY_GROUP_ID.
• IEX_WRITEOFF_INVOICES_U1 — unique index enforcing the WRITEOFF_INVOICE_ID primary key.
• Lease invoice tables (e.g., OKL/IA invoice headers and lines) — referenced logically via LEASE_INVOICE_ID and LEASE_INV_LINE_ID.
• FND_CONCURRENT_REQUESTS — traceability via REQUEST_ID and program columns.