Search Results xtr_ap_open_apld_trx_v




Overview
Explore in AI Chat

Overview

XTR_AP_OPEN_APLD_TRX_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents open, applied accounts payable transactions — that is, invoices that have been applied against payments and still carry a remaining balance — in a form tailored to Treasury cash management and counterparty exposure reporting. The view is built from standard Payables transactional data (AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL) joined to vendor, vendor site, party, ledger, and operating unit reference objects, and it enriches those rows with lookup-driven display values, reporting currency, and discount-aware payment dates and amounts. Its principal design goal is to expose open AP liabilities alongside the party identifiers used elsewhere in the Treasury data model, so that Treasury reports, cash forecasts, and party exposure queries can present payables activity consistently with receivables and Treasury instruments.

Underlying Base Objects

The view selects from the following documented objects:

  • AP_INVOICES_ALL (synonym) — the invoice header, supplying invoice ID, number, date, type lookup code, vendor and vendor site IDs, payment currency, source, and org ID.
  • AP_PAYMENT_SCHEDULES_ALL (synonym) — the scheduled payment lines, supplying payment number, amount remaining, due date, and the three discount dates with their available discount amounts.
  • AP_LOOKUP_CODES (view) — supplies the displayed field values (ALK.DISPLAYED_FIELD, ALC.DISPLAYED_FIELD) for invoice source and invoice type.
  • PO_VENDORS and PO_VENDOR_SITES_ALL (views) — supply vendor name, vendor site code, and the ALWAYS_TAKE_DISC_FLAG used in the discount logic.
  • XTR_PARTIES_V (view) — provides the Treasury party code and set of books currency for the vendor.
  • HR_OPERATING_UNITS (view) — resolves ORG_ID to the operating unit name.
  • GL_LEDGER_LE_V (view) — ledger/legal entity information used in the Treasury context.
  • FND_MESSAGE (package) — used to fetch translatable message text for the invoice source categories XTR_AP_SOURCE_MANUAL and XTR_AP_SOURCE_OTHER.
  • FND_GLOBAL (package) and XTR_USER_ACCESS (package) — provided for security and session context.

Key Columns

  • INVOICE_ID, INVOICE_NUM, INVOICE_DATE, INVOICE_TYPE_LOOKUP_CODE — the invoice identity and classification.
  • SOURCE / decoded SOURCE — the invoice source, translated through AP_LOOKUP_CODES or, when no displayed field exists, mapped to XTR_AP_SOURCE_MANUAL for manual entry and XTR_AP_SOURCE_OTHER otherwise.
  • PAYMENT_NUM and AMOUNT_REMAINING — the scheduled payment reference and outstanding balance.
  • Discount-aware amount and due date columns — computed from ALWAYS_TAKE_DISC_FLAG and the three discount dates, yielding the effective payment amount and effective due date Treasury should plan against.
  • VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE, PARTY_CODE — the counterparty identifiers, with PARTY_CODE linking to the Treasury party model.
  • PAYMENT_CURRENCY_CODE and SET_OF_BOOKS_CURRENCY — the transaction and ledger currencies.
  • ORG_ID and the operating unit NAME — the organizational context for the row.

Common Use Cases and Queries

Treasury analysts use this view for cash forecasting, party exposure reporting, and reconciliation between Treasury party records and open payables. A typical query selects invoices for a party within an operating unit:

  • SELECT invoice_num, vendor_name, party_code, payment_num, AMOUNT_REMAINING, PAYMENT_CURRENCY_CODE, INVOICE_DATE FROM XTR_AP_OPEN_APLD_TRX_V WHERE PARTY_CODE = :p_party AND ORG_ID = :p_org
  • SELECT SOURCE, COUNT(*), SUM(AMOUNT_REMAINING) FROM XTR_AP_OPEN_APLD_TRX_V GROUP BY SOURCE — summarizes open liabilities by invoice source.
  • SELECT invoice_num, due-date-column, AMOUNT_REMAINING FROM XTR_AP_OPEN_APLD_TRX_V WHERE INVOICE_DATE BETWEEN :p_from AND :p_to — supports maturity and due-date analysis.

Because the view applies discount logic and message-based source translation at query time, consumers should treat it as a reporting object rather than a transactional target, and should filter by ORG_ID or party to keep result sets aligned with Treasury security and performance expectations.