Results for “amount_applied”

1 result




Overview
Explore in AI Chat

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

Overview

The IEX.IEX_PRD_APPL_XREF table is a Collections module (IEX) data object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores promise application information, capturing how amounts that were committed against a promise to pay have subsequently been applied to specific receivables. In the Collections workflow an agent records a customer commitment (a promise) with one or more promise details; when cash, credit memos, or adjustments later arrive and are applied against the delinquent transactions, the application is tracked here. The table therefore acts as the reconciliation bridge between the promise-to-pay commitment and the actual receivable application, supporting promise fulfillment and broken-promise analysis.

The schema is documented with 17 columns and is owned by IEX. The ETRM metadata classifies the object heuristically through its foreign-key structure as standalone. As a modeling suggestion, this indicates the table is not an obvious hub or link in a Data Vault sense; it behaves more like a detail or association record whose relationships are carried through its parent promise detail rather than through multiple hub references. Practically, this means modelers should treat it as a dependent record of the promise, joined primarily through PROMISE_DETAIL_ID.

Key Information Stored

The primary surrogate key is PRD_APPL_XREF_ID, uniquely enforced by the index IEX_PRD_APPL_XREF_U1; the metadata identifies this index as the business-key candidate. The principal business relationships are held in PROMISE_DETAIL_ID, which links the record to its parent promise detail, and RECEIVABLE_APPLICATION_ID, which ties the applied amount to the underlying receivables application. The financial effect is captured by AMOUNT_APPLIED and APPLY_DATE, while ADJUSTMENT_ID optionally associates an adjustment transaction with the same application event.

Reversal handling is provided by REVERSED_FLAG and REVERSED_DATE, enabling the system to back out applications without deleting history. Standard EBS who-columns are present: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and PROGRAM_ID, with REQUEST_ID identifying the concurrent request that created or modified the row. OBJECT_VERSION_NUMBER supports optimistic locking for the Collections UI, and SECURITY_GROUP_ID enforces multi-tenant/operating-unit style data security, referencing FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical usage centers on promise fulfillment reporting: determining how much of a promise has actually been applied, whether applications were later reversed, and which adjustment or application transactions satisfied the commitment.

  • Open applied promises for a customer: join IEX_PRD_APPL_XREF to IEX_PROMISE_DETAILS on PROMISE_DETAIL_ID and filter REVERSED_FLAG = 'N'.
  • Reversal audit: SELECT amt.* FROM iex.iex_prd_appl_xref amt WHERE amt.reversed_flag = 'Y' AND amt.reversed_date >= :from_date.
  • Collection effectiveness: sum AMOUNT_APPLIED by APPLY_DATE to trend how quickly promised amounts convert to real collections.
  • Reconciliation to Receivables: join RECEIVABLE_APPLICATION_ID to AR_RECEIVABLE_APPLICATIONS_ALL to trace the cash or credit that fulfilled the promise.
  • Adjustment tracing: where ADJUSTMENT_ID is populated, link to the adjustment source to explain write-offs applied against a promise.

Related Objects

  • IEX_PROMISE_DETAILS — parent via IEX_PRD_APPL_XREF.PROMISE_DETAIL_ID; holds the promise terms being applied.
  • IEX_PROMISES — header of the promise; reached indirectly through IEX_PROMISE_DETAILS for promise-level reporting.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for data security.
  • AR_RECEIVABLE_APPLICATIONS_ALL — target of RECEIVABLE_APPLICATION_ID, the actual cash/credit application.
  • AR_ADJUSTMENTS_ALL — where ADJUSTMENT_ID is populated, the adjustment that satisfied part of the promise.
  • IEX_DELINQUENCIES / IEX_STRATEGIES — related Collections objects providing the case context in which promises and their applications arise.