Results for “unapplied_amount”

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

Overview

IBE_PAYMENT_HEADER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is published under the IBE (iStore) product and exists to present a consolidated, customer-facing picture of receipt (payment) headers originating in Oracle Receivables. Because iStore order capture must reflect funds already received against a customer account, this view flattens the Receivables cash receipt, payment schedule, and receivable application data into a single denormalized row per cash receipt, exposing a stable column list that iStore pages and integrations can query directly.

The distinguishing feature of the view, and the reason it is frequently located through the search term "unapplied_amount", is its computed UNAPPLIED_AMOUNT column. Rather than requiring the caller to join AR_RECEIVABLE_APPLICATIONS_ALL and reason about application status codes, the view aggregates that logic internally and returns the remaining unapplied balance of the receipt. The view is documented as VALID and follows the standard Oracle view convention of exposing display-oriented aliases (for example CUSTOMER_NAME and TYPE) in place of raw column names.

Underlying Base Objects

The view is defined over six documented base objects, joining Receivables and Trading Community (HZ) entities:

• AR_CASH_RECEIPTS_ALL — the primary driver, supplying CASH_RECEIPT_ID, RECEIPT_NUMBER, AMOUNT, RECEIPT_DATE, CURRENCY_CODE, TYPE, PAY_FROM_CUSTOMER, and CREATED_BY. It is joined to AR_RECEIVABLE_APPLICATIONS_ALL with the outer (+) operator.
• AR_PAYMENT_SCHEDULES_ALL — supplies the scheduled-installment context, including AMOUNT_APPLIED, DUE_DATE, and ORG_ID, joined to the receipt with the outer (+) operator.
• AR_RECEIVABLE_APPLICATIONS_ALL — the application detail used to compute UNAPPLIED_AMOUNT, aggregated with SUM(DECODE(RA.STATUS,'UNAPP',NVL(RA.AMOUNT_APPLIED,0),0)).
• AR_LOOKUPS — a view filtered to LOOKUP_TYPE = 'PAYMENT_CATEGORY_TYPE' to translate the receipt TYPE code into its MEANING.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — supply CUST_ACCOUNT_ID, PARTY_ID, and PARTY_NAME, linked through PAY_FROM_CUSTOMER and PARTY_ID. The account join to the receipt is outer (+).

The outer joins mean a receipt can still appear even when it has no matching customer account or payment schedule, which is important for reconciliation reporting where orphaned or partially configured receipts must not be silently dropped.

Key Columns

• CASH_RECEIPT_ID — the Receivables receipt identifier; the view's grouping key.
• RECEIPT_NUMBER — the user-visible receipt number.
• CUST_ACCOUNT_ID / PARTY_ID / CUSTOMER_NAME — the customer account, party, and display name of the remitter.
• AMOUNT — the receipt amount as recorded in AR_CASH_RECEIPTS_ALL.
• TYPE — the decoded payment category meaning derived from AR_LOOKUPS.
• APPLIED_AMOUNT — the payment-schedule applied amount (ABS of PS.AMOUNT_APPLIED).
• RECEIPT_DATE / DUE_DATE — receipt and schedule due dates.
• CURRENCY_CODE — the receipt currency.
• UNAPPLIED_AMOUNT — the sum of amount applied across applications whose status is 'UNAPP'; this is the on-account / unapplied remainder.
• CREATED_BY / ORG_ID — audit and operating unit context.

Common Use Cases and Queries

Typical usage is to display a customer's received payments alongside how much remains unapplied, and to feed downstream logic that consumes on-account credit. A representative query filtering by unapplied balance:

• SELECT cash_receipt_id, receipt_number, customer_name, amount, currency_code, unapplied_amount FROM apps.ibe_payment_header_v WHERE unapplied_amount > 0;
• SELECT receipt_number, receipt_date, type, applied_amount, unapplied_amount FROM apps.ibe_payment_header_v WHERE cust_account_id = :p_account_id ORDER BY receipt_date DESC;
• SELECT org_id, currency_code, SUM(unapplied_amount) FROM apps.ibe_payment_header_v GROUP BY org_id, currency_code;

Because UNAPPLIED_AMOUNT is aggregated by cash receipt, the view is well suited to iStore credit-balance checks and to reporting that reconciles applied versus unapplied receipt value within an operating unit.