Results for “uwq_complete_date”

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

Overview

IEX.IEX_PROMISE_DETAILS is a Collections module table in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) that stores line-level detail for each promise to pay recorded against a delinquent customer. A promise to pay captures a collector's or customer's commitment to remit a specific amount by a specific date; IEX_PROMISE_DETAILS holds the granular attributes of that commitment, including the promised amount, the payment method, the source delinquency, the collector resource, and the associated customer account. It is a transactional child table, not a setup or reference table.

The ETRM relationship metadata classifies this table heuristically as standalone within a Data Vault model. This suggests it is best modeled as a satellite or hub-like entity rather than a dependent link: although it carries foreign keys, no parent table treats it as a mandatory intersection, and it owns its own unique business key.

Key Information Stored

The table contains 52 documented columns. The most operationally significant are:

• PROMISE_DETAIL_ID — the surrogate primary key (unique index IEX_PROMISE_DETAILS_U1); this is the column referenced by all dependent cross-reference tables.
• PROMISE_DATE and PROMISE_AMOUNT — the date the customer committed to pay and the amount committed.
• PROMISE_PAYMENT_METHOD — the intended remittance channel (for example check, wire, or credit card).
• STATUS — lifecycle state of the promise (for example open, kept, or broken).
• BROKEN_ON_DATE — populated when the promise is not honored, enabling broken-promise reporting.
• DELINQUENCY_ID — foreign key to IEX_DELINQUENCIES_ALL, linking the promise to the underlying delinquency record.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the customer account.
• CNSLD_INVOICE_ID and CONTRACT_ID — the consolidated invoice and contract against which the promise applies.
• RESOURCE_ID and PROMISE_MADE_BY — the collections agent who secured the promise.
• AMOUNT_DUE_REMAINING — the outstanding balance at the time the promise was recorded.
• CURRENCY_CODE, ACCOUNT, PROMISE_ITEM_NUMBER — monetary and identity attributes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID) and the ATTRIBUTE1–ATTRIBUTE15 flexfield set, plus workflow columns UWQ_STATUS, UWQ_ACTIVE_DATE, and UWQ_COMPLETE_DATE.

Common Use Cases and Queries

Collections analysts and AR reporting use this table to measure promise-keeping performance. A typical query joins promises to delinquencies and customer accounts:

SELECT p.promise_detail_id, p.promise_date, p.promise_amount,
       p.status, p.broken_on_date, c.account_number
FROM   iex.iex_promise_details p,
       hz_cust_accounts c
WHERE  p.cust_account_id = c.cust_account_id
AND    p.status = 'BROKEN';

Other common patterns include aging open promises by PROMISE_DATE, aggregating promised versus AMOUNT_DUE_REMAINING amounts by collector RESOURCE_ID, and reconciling promises against receipts through the IEX_PRD_RECEIPT_XREF table. Reporting on BROKEN_ON_DATE supports dunning strategy tuning.

Related Objects

• IEX_DELINQUENCIES_ALL — joined via DELINQUENCY_ID; the parent delinquency record.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; the customer account.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; security isolation.
• IEX_PRD_OKL_XREF — references PROMISE_DETAIL_ID; promise-to-order key linkage.
• IEX_PRD_APPL_XREF — references PROMISE_DETAIL_ID; promise application to receipts.
• IEX_PRD_RECEIPT_XREF — references PROMISE_DETAIL_ID; promise-to-receipt reconciliation.