Search Results apad_amount




Overview
Explore in AI Chat

Overview

APPS.AP_PREPAYAPP_EXTRACT_DTLS_BC_V is a valid Oracle E-Business Suite view owned by the APPS schema, registered in FND Design Data as FND.AP_PREPAYAPP_EXTRACT_DTLS_BC_V and shipped under the SQLAP product. Its name indicates its purpose: it exposes prepayment application (PREPAYAPP) extract detail rows for the Subledger Accounting (SLA) accounting extract. The "_BC_V" suffix denotes a business-consolidated view, meaning the view is designed to flatten the prepayment application distribution and invoice line detail into a single denormalized row set suitable for consumption by the accounting program and downstream reporting or integration.

The view is the source of the APAD_AMOUNT element that users frequently search for. APAD_AMOUNT represents the accounted amount of the prepayment application distribution, expressed in the ledger currency. It is a key balancing figure in the extract record and is distinct from the invoice line amount (AIL_AMOUNT) also exposed here.

The view's columns describe a single accounting event line: the event identity (EVENT_ID, LINE_NUMBER), the distribution linkage and identifier, deferral attributes, prepayment invoice reference, currency information, and a comprehensive carriage of invoice line (AIL) attributes including accounting flexfield segments, accounting date, period name, and descriptive flexfield columns.

Underlying Base Objects

The view is defined over the following documented base objects:

The view therefore joins prepayment application distributions to their invoice line, payment history, and Subledger Accounting event context, producing one extract detail row per application line.

Key Columns

Common Use Cases and Queries

Typical uses include reconciliation of prepayment application accounted amounts to the general ledger, analysis of deferred prepayment applications, and extracts feeding external reporting or data warehouses.

To retrieve the accounted amount for a specific application event:

  • SELECT event_id, line_number, apad_distribution_identifier, apad_amount, prepay_pay_currency_code FROM apps.ap_prepayapp_extract_dtls_bc_v WHERE event_id = :p_event_id;

To summarize accounted amounts by prepayment invoice:

  • SELECT apph_prepay_invoice_id, SUM(apad_amount) accounted_total FROM apps.ap_prepayapp_extract_dtls_bc_v GROUP BY apph_prepay_invoice_id ORDER BY apph_prepay_invoice_id;

To inspect deferral details:

  • SELECT event_id, line_number, deferred_option, deferred_start_date, deferred_end_date, deferred_number_of_periods, apad_amount FROM apps.ap_prepayapp_extract_dtls_bc_v WHERE deferred_option IS NOT NULL;

Because the view is read-only and built on SLA extract logic, it should be queried rather than modified, and bind predicates on EVENT_ID or the prepayment invoice identifier are recommended to limit the volume of joined rows returned.