Search Results aid_task_id

Overview

AP_PREPAYAPP_EXTRACT_DTLS_BC_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite. The suffix "BC" denotes a Business Events/Subledger Accounting (SLA) extract view, and it is designed to surface prepayment application distribution detail for accounting event extraction in Oracle Subledger Accounting (XLA). In EBS 12.1.1 and 12.2.2 the view functions as an interface between Payables prepayment application data and the Subledger Accounting engine, exposing distribution-level rows that carry both accounting attributes and source identifiers required to construct and transfer journal entries. Its role is primarily diagnostic and integration-oriented: it allows technical consultants and support analysts to inspect exactly what Payables feeds into SLA when prepayments are applied to invoices, including deferred accounting flags, reversal information, and the associated invoice adjustment event. The view is not intended for end-user reporting, but rather supports troubleshooting of accounting events, subledger extracts, and prepayment application distributions.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, this view is defined over a broad set of base objects, all referenced as APPS synonyms. The core driver tables include AP_PREPAY_APP_DISTS (prepayment application distributions), AP_PAYMENT_HISTORY_ALL and AP_PAYMENT_HIST_DISTS (payment history and clearing distributions), and AP_PREPAY_HISTORY_ALL (prepayment history). Invoice-related attributes come from AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_INVOICE_LINES_ALL. Additional configuration and reference objects include FINANCIALS_SYSTEM_PARAMS_ALL, GL_ENCUMBRANCE_TYPES, PO_DISTRIBUTIONS_ALL, and the XLA_EVENTS_GT global temporary table. Notably, the view also invokes the PSA_BC_XLA_PUB package, indicating that business-event extraction logic for Subledger Accounting is embedded directly in the access path. The view therefore joins prepayment distributions to their accounting lines and to the SLA event context in a single flattened projection.

Key Columns

The view exposes several critical identifiers and attributes:

• EVENT_ID — derived from APPH.BC_EVENT_ID, the Subledger Accounting event identifier.
• LINE_NUMBER — sourced from APAD.PREPAY_APP_DIST_ID, serving as the distribution line identifier.
• DISTRIBUTION_LINK_TYPE — a literal 'AP_PREPAY' identifying the distribution source type.
• DEFERRED_OPTION, DEFERRED_START_DATE, DEFERRED_END_DATE, DEFERRED_NUMBER_OF_PERIODS, DEFERRED_PERIOD_TYPE — deferred accounting attributes taken from AP_INVOICE_LINES_ALL.
• APAD_DISTRIBUTION_IDENTIFIER — the prepayment application distribution ID from AP_PREPAY_APP_DISTS.
• DIST_ACCOUNT_REVERSAL_OPTION — DECODE result ('Y'/'N') indicating whether the distribution was reversed, based on REVERSED_PREPAY_APP_DIST_ID.
• APAD_INVOICE_ADJ_EVENT_ID, APPH_PREPAY_INVOICE_ID — event and prepay invoice linkages from payment history.
• APAD_AMOUNT — the prepayment application distribution amount.
• PREPAY_PAY_CURRENCY_CODE, PREPAY_CLEAR_CURRENCY_CODE — payment and clearing currency codes.
• AIL_* columns — a wide set of accounting line attributes from AP_INVOICE_LINES_ALL, including LINE_NUMBER, LINE_TYPE_LOOKUP_CODE, ACCOUNT_SEGMENT, BALANCING_SEGMENT, COST_CENTER_SEGMENT, OVERLAY_DIST_CODE_CONCAT, DEFAULT_DIST_CCID, ACCOUNTING_DATE, PERIOD_NAME, AMOUNT, ROUNDING_AMT, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15, and GLOBAL_ATTRIBUTE_CATEGORY.

Common Use Cases and Queries

The primary use case is investigating how prepayment applications were passed to Subledger Accounting. A typical query filters by prepay invoice or event:

• SELECT event_id, line_number, apad_amount, prepay_pay_currency_code, deferred_option, dist_account_reversal_option FROM ap_prepayapp_extract_dtls_bc_v;
• SELECT * FROM ap_prepayapp_extract_dtls_bc_v WHERE apph_prepay_invoice_id = :invoice_id;
• SELECT event_id, apad_distribution_identifier, ail_accounting_date, ail_period_name, ail_amount FROM ap_prepayapp_extract_dtls_bc_v WHERE event_id = :event_id;

These queries are commonly used to reconcile prepayment application amounts against SLA journal lines, to confirm deferred accounting treatment, and to verify that reversal indicators and invoice adjustment events are correctly populated. Because the view references the PSA_BC_XLA_PUB package and XLA_EVENTS_GT, queries should generally be scoped by event or invoice to limit the extraction cost.