Search Results prepay_dist_number




Overview
Explore in AI Chat

Overview

APPS.AP_DIST_PREPAY_APPLICATION_V is a documented Oracle E-Business Suite internal view owned by the APPS schema. It is classified as VALID and carries the designation "Oracle Internal Use Only," meaning Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Its FND Design Data reference is SQLAP.AP_DIST_PREPAY_APPLICATION_V, and its view type is Internal. The view is not referenced by any other database object, confirming its role as a leaf-level read construct used by Payables prepayment logic and reporting rather than as a foundation for further dependency chains.

Functionally, the view presents the application and distribution detail of prepayments (prepaid invoices) against their related distributions, exposing both the remaining prepaid amount and the remaining tax amount at the distribution level. For users searching the tax_amount_remaining column, this view is the primary internal source that surfaces that value alongside the corresponding prepayment amount remaining, distribution account, and source document identifiers. It therefore supports reconciliation of prepayment balances, tax recovery analysis, and integration extracts. The 12.1.1 and 12.2.2 releases share this object definition; no structural divergence is documented in the ETRM metadata.

Underlying Base Objects

The metadata documents that APPS.AP_DIST_PREPAY_APPLICATION_V references two dependent objects:

Because the remaining balances are computed, they reflect the current state of prepayment application at the time of query and are not persisted values.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling unapplied prepayment and tax balances by ledger and period, analyzing prepayments tied to purchase orders, and building integration extracts that must report remaining tax. A representative query is:

  • SELECT invoice_id, prepay_line_number, prepay_dist_number, prepay_amount_remaining, tax_amount_remaining, dist_code_combination_id, period_name, set_of_books_id, org_id FROM apps.ap_dist_prepay_application_v WHERE tax_amount_remaining <> 0 AND org_id = :p_org_id;

Because the object is marked Oracle Internal Use Only, production reporting should prefer supported Payables views or APIs, treating this view as a diagnostic and analysis aid rather than a supported integration interface.