Search Results ail_line_number




Overview
Explore in AI Chat

Overview

APPS.AP_PREPAYAPP_EXTRACT_DETAILS_V is a reporting and integration view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that consolidates prepayment application accounting detail into a single, flat projection. Its principal purpose is to expose the accounting lines generated when a prepayment is applied to an invoice, including distribution, line, and rounding attributes, so that downstream processes — particularly Subledger Accounting (SLA/XLA) extraction, custom reconciliation reports, and third-party data feeds — can consume the data without navigating the normalized prepayment and invoice distribution tables directly.

The view is registered in FND Design Data as FND.AP_PREPAYAPP_EXTRACT_DETAILS_V and SQLAP.AP_PREPAYAPP_EXTRACT_DETAILS_V, confirming it ships as a seeded APPS object owned by the Payables (SQLAP) product. Because it draws from both the Payables transactional model and XLA event/GT structures, it is positioned at the boundary between transaction entry and accounting event generation, making it useful when auditing how prepayment applications flow into the accounting event model.

Underlying Base Objects

The view is defined over a set of APPS synonyms that map to the core Payables and Subledger Accounting tables. Documented referenced base objects include:

Key Columns

The column list is organized around three logical groups. Event and linkage columns — EVENT_ID, LINE_NUMBER, DISTRIBUTION_LINK_TYPE, APAD_INVOICE_ADJ_EVENT_ID — identify the accounting event and its relationship to the transaction. Prepay and distribution columns — APAD_DISTRIBUTION_IDENTIFIER, APAD_AMOUNT, APPH_PREPAY_INVOICE_ID, PREPAY_PAY_CURRENCY_CODE, PREPAY_CLEAR_CURRENCY_CODE, DEFERRED_OPTION, DEFERRED_START_DATE, DEFERRED_END_DATE, DEFERRED_NUMBER_OF_PERIODS, DEFERRED_PERIOD_TYPE, and APAD_DIST_LOOKUP_CODE — describe the applied prepayment and its deferred accounting behavior.

The AIL_ prefix columns mirror the invoice line accounting context: AIL_LINE_NUMBER, AIL_LINE_TYPE_LOOKUP_CODE, AIL_ACCOUNTING_DATE, AIL_PERIOD_NAME, AIL_AMOUNT, the account segment columns (AIL_ACCOUNT_SEGMENT, AIL_BALANCING_SEGMENT, AIL_COST_CENTER_SEGMENT, AIL_OVERLAY_DIST_CODE_CONCAT, AIL_DEFAULT_DIST_CCID), the descriptive flexfield columns AIL_ATTRIBUTE1 through AIL_ATTRIBUTE15 and AIL_GLOBAL_ATTRIBUTE1 onward with their categories, and — directly relevant to the search term — AIL_ROUNDING_AMT.

AIL_ROUNDING_AMT holds the residual rounding difference computed when the prepayment application amount is allocated across distribution lines. Rounding differences arise when a base amount cannot be divided evenly, and this column captures the adjustment posted to force the distribution to reconcile. It is typically paired with AIL_AMOUNT and APAD_AMOUNT when validating that applications balance to the payment and invoice amounts.

Common Use Cases and Queries

Typical scenarios include reconciling prepayment applications to their accounting events, extracting rounding differences for audit, and feeding external reconciliation systems. A representative query listing applied amounts alongside rounding differences:

  • SELECT event_id, apad_amount, ail_amount, ail_rounding_amt, ail_line_number, prepay_pay_currency_code FROM apps.ap_prepayapp_extract_details_v WHERE event_id = :p_event_id;
  • SELECT apad_distribution_identifier, apad_amount, ail_rounding_amt FROM apps.ap_prepayapp_extract_details_v WHERE NVL(ail_rounding_amt,0) <> 0 ORDER BY event_id, ail_line_number;
  • SELECT apad_invoice_adj_event_id, SUM(apad_amount) applied, SUM(ail_amount) accounted, SUM(NVL(ail_rounding_amt,0)) rounding FROM apps.ap_prepayapp_extract_details_v GROUP BY apad_invoice_adj_event_id;

Because the view joins XLA event structures, queries should filter by EVENT_ID or accounting date to keep result sets bounded. Users should verify ledger and operating unit context through the system parameter-backed columns before relying on aggregations across data sets.