Results for “dunning_method”

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

Overview

IEX_DUNNINGS is the primary transactional table within the Oracle E-Business Suite Collections (IEX) module that stores data on all dunning transactions generated and sent by the system. Dunning is the process by which an organization formally communicates with delinquent customers to recover overdue receivables, escalating in tone and urgency across successive contact attempts. Each row in IEX_DUNNINGS represents a single dunning event, capturing the recipient, delivery channel, associated delinquency, template used, monetary amounts, and delivery outcome. The table is owned by the IEX schema and is valid in both EBS 12.1.1 and 12.2.2, with 59 documented columns in the 12.2.2 reference schema.

From a heuristic Data Vault modeling perspective, the FK structure mined from ETRM metadata classifies this object as standalone, suggesting it is best modeled as a hub (or a hub with an embedded satellite) anchored on the DUNNING_ID business key. Practitioners building a vault or warehouse layer should treat DUNNING_ID as the durable business key and the descriptive attributes (status, method, amounts, dates) as satellite payload.

Key Information Stored

The surrogate primary key is DUNNING_ID, backed by the sequence IEX_DN_HISTORIES_S and the unique index IEX_DUNNINGS_U1, which also serves as the business-key candidate. The most operationally significant columns include:

• DELINQUENCY_ID — FK to IEX_DELINQUENCIES_ALL; identifies the delinquency case this dunning action addresses.
• STATUS and DELIVERY_STATUS — lifecycle and delivery outcome of the dunning communication.
• DUNNING_METHOD, DUNNING_MODE, and CONFIRMATION_MODE — how the dunning was dispatched (letter, email, fax) and whether confirmation was required.
• DUNNING_LEVEL and DUNNING_PLAN_ID — escalation tier and governing dunning plan.
• TEMPLATE_ID, XML_TEMPLATE_ID, ADDT_XML_TEMPLATE_ID, and LETTER_NAME — template and correspondence configuration.
• AMOUNT_DUE_REMAINING, FINANCIAL_CHARGE, INTEREST_AMT, and CURRENCY_CODE — monetary context of the dunning.
• CONTACT_PARTY_ID and CONTACT_DESTINATION — who was contacted and via which address or endpoint.
• CORRESPONDENCE_DATE and AS_OF_DATE — the date of correspondence and the effective as-of date for amounts.
• SECURITY_GROUP_ID, ORG_ID, AG_DN_XREF_ID, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) — multi-tenancy, organization, aging cross-reference, and audit context.
• PARENT_DUNNING_ID — supports hierarchical dunning chains.

Common Use Cases and Queries

Collections analysts and receivables reporting typically query IEX_DUNNINGS to audit dunning history, measure recovery effectiveness, and reconcile correspondence against delinquent balances.

• Dunning history by customer: join to IEX_DELINQUENCIES_ALL on DELINQUENCY_ID to attribute dunning events to specific customers and invoices.
• Delivery success reporting: filter on DELIVERY_STATUS to identify failed correspondence requiring reissue.
• Escalation analysis: group by DUNNING_LEVEL or DUNNING_PLAN_ID to assess letter-stage progression.
• Financial impact: sum FINANCIAL_CHARGE and INTEREST_AMT by ORG_ID and CURRENCY_CODE over CORRESPONDENCE_DATE ranges.

A representative query:

SELECT d.DUNNING_ID, d.DELINQUENCY_ID, d.STATUS, d.DELIVERY_STATUS, d.DUNNING_METHOD, d.CORRESPONDENCE_DATE, d.AMOUNT_DUE_REMAINING FROM iex.iex_dunnings d WHERE d.ORG_ID = :org_id AND d.CORRESPONDENCE_DATE >= :from_date ORDER BY d.CORRESPONDENCE_DATE DESC;

Related Objects

• IEX_DUNNING_TRANSACTIONS — references IEX_DUNNINGS.DUNNING_ID; stores individual transaction-level detail for each dunning event.
• IEX_DELINQUENCIES_ALL — parent delinquency case referenced via DELINQUENCY_ID.
• IEX_AG_DN_XREF — aging-to-dunning cross-reference keyed by AG_DN_XREF_ID.
• FND_SECURITY_GROUPS — multi-tenant security context via SECURITY_GROUP_ID.
• IEX_DN_HISTORIES_S — sequence supplying DUNNING_ID values.