Search Results ps_inv




Overview
Explore in AI Chat

Overview

APPS.IBE_PAYMENT_DETAIL_V is a reporting view in Oracle E-Business Suite that consolidates receipt application activity against transaction payment schedules. It is part of the iStore/IBE (Internet Business Essentials) object family and is commonly referenced during payment-detail inquiries where a receipt must be traced to the invoices or credit memos it was applied against, along with the resulting remaining balance on each transaction. The view joins receivable applications to their payment schedules, customer accounts, cash receipts, and several AR lookup types, producing a denormalized result set suitable for direct presentation or downstream integration.

The view is significant for the search term "ps_inv," which corresponds to the alias assigned to AR_PAYMENT_SCHEDULES_ALL in the view definition. Analysts searching that alias are typically tracing how installment and transaction schedule information is exposed through the IBE payment-detail layer. The view resolves transaction numbers, transaction classes, statuses, discount amounts, and remaining amounts using DECODE logic keyed on APPLIED_PAYMENT_SCHEDULE_ID, allowing a single result set to represent both actual invoice applications and certain receipt-level adjustments.

Underlying Base Objects

The view is defined over six documented objects: AR_PAYMENT_SCHEDULES_ALL (synonym, aliased ps_inv), AR_RECEIVABLE_APPLICATIONS_ALL (synonym, aliased app), AR_CASH_RECEIPTS_ALL (synonym, aliased cr), HZ_CUST_ACCOUNTS (synonym, aliased acct), AR_LOOKUPS (view, referenced three times as l_class, l_acc, and AL_STATUS), plus an undocumented iStore object relating to the IBE payment layer. Join predicates are fully specified in the view text:

  • AR_RECEIVABLE_APPLICATIONS_ALL drives the view; rows are restricted by display = 'Y', meaning only visible (non-reversed, effective) applications are returned.
  • AR_PAYMENT_SCHEDULES_ALL is joined on applied_payment_schedule_id = payment_schedule_id, linking each application to the transaction schedule it settles.
  • AR_CASH_RECEIPTS_ALL is joined on cash_receipt_id = app.cash_receipt_id to furnish the receipt number.
  • HZ_CUST_ACCOUNTS is joined on customer_id = cust_account_id to supply customer context.
  • AR_LOOKUPS provides three decoded meanings: INV/CM class descriptions, the PAYMENT_TYPE code 'ACC', and INVOICE_TRX_STATUS status meanings.

Key Columns

  • cash_receipt_id / receipt_number — identifier and human-readable number of the applied receipt.
  • trx_number — via DECODE on APPLIED_PAYMENT_SCHEDULE_ID = -1, the payment-type meaning is returned instead of a transaction number, distinguishing unapplied or on-account lines from true invoice applications.
  • trx_class_name — the INV/CM lookup meaning, nulled for the -1 case.
  • amount_applied — the amount of the receipt applied to the schedule.
  • discount — sum of earned and unearned discount taken, nulled for the -1 case.
  • amount_due_original — original amount due on the transaction schedule.
  • amount_due_remaining — negated amount_applied for the -1 case, otherwise the schedule's amount_due_remaining.
  • customer_trx_id, status, status_meaning — transaction identifier and decoded INVOICE_TRX_STATUS meaning.
  • currency_code, org_id, apply_date — invoice currency, operating unit, and application date.

Common Use Cases and Queries

The view supports receipt-to-invoice reconciliation, collections inquiry, and iStore order payment display. A typical query lists applied receipts for a transaction:

SELECT trx_number, receipt_number, amount_applied, discount, amount_due_remaining, status_meaning FROM apps.ibe_payment_detail_v WHERE customer_trx_id = :p_trx_id;

A second pattern retrieves all applications for a receipt:

SELECT trx_number, trx_class_name, apply_date, amount_applied FROM apps.ibe_payment_detail_v WHERE cash_receipt_id = :p_receipt_id ORDER BY apply_date;

Because the view filters on display = 'Y', results exclude reversed applications, making it appropriate for balances and customer-facing reporting without additional reversal logic.