Search Results min_due_date




Overview
Explore in AI Chat

Overview

APPS.XTR_AP_OPEN_APLD_TRX_V is an Oracle E-Business Suite internal reporting view owned by the APPS schema. It exposes open and applied Payables transactions—invoices and their payment schedules—in a denormalized form enriched with operating unit, vendor, ledger, and party attributes. The view is registered in FND Design Data as XTR.XTR_AP_OPEN_APLD_TRX_V and carries a status of VALID. Because Oracle classifies it as "Oracle Internal Use Only," the view is not a supported public interface; it is intended for consumption by standard Oracle Applications programs, notably the Treasury (XTR) module and its dependent view XTR_AP_OPEN_TRX_V.

Functionally, the view provides a consolidated picture of transaction amounts, discount windows, and due dates. The search term "min_due_date" reflects a common requirement: identifying the earliest payment due date across a set of open or applied invoices, which is central to cash forecasting, payment scheduling, and Treasury cash positioning.

Underlying Base Objects

The view is defined over a combination of base tables, views, and packages:

The view is itself referenced by APPS.XTR_AP_OPEN_TRX_V, forming a layered dependency chain within the XTR object family.

Key Columns

Common Use Cases and Queries

Typical usage focuses on cash forecasting, payment batching, and identifying the earliest obligation date. A representative query selecting the minimum due date by operating unit and supplier:

SELECT ORG_ID, VENDOR_NAME, TRX_NUMBER,
       MIN_DUE_DATE, AMOUNT, CURRENCY_CODE
FROM   APPS.XTR_AP_OPEN_APLD_TRX_V
WHERE  APPLIED_TRX IS NULL
ORDER BY MIN_DUE_DATE;

A second pattern isolates invoices meeting discount windows:

SELECT INVOICE_ID, TRX_NUMBER, MIN_DISCOUNTED_DATE,
       MIN_DISCOUNTED_AMOUNT, MIN_DUE_DATE
FROM   APPS.XTR_AP_OPEN_APLD_TRX_V
WHERE  MIN_DISCOUNTED_DATE < MIN_DUE_DATE
AND    ORG_ID = :p_org_id;

Because the view embeds XTR_USER_ACCESS security predicates, results are implicitly filtered by the caller's Treasury access privileges. Direct SQL access is discouraged by Oracle; supported retrievals should be performed through standard Treasury or Payables programs that consume this view and its dependents.