Search Results ap_extract_invoice_dtls_bc_v




Overview
Explore in AI Chat

Overview

The AP_EXTRACT_INVOICE_DTLS_BC_V view is a Payables extract object in the APPS schema, defined for Oracle E-Business Suite 12.1.1 and 12.2.2. Its name indicates it supplies invoice distribution detail lines for a Subledger Accounting (SLA) or Business Connect (BC) accounting extract. It joins invoice distribution rows to their parent invoice lines and maps them to the accounting event identifier (BC_EVENT_ID) used by the SLA extract engine. The view is not an operational data-entry object; it is a reporting and integration artifact consumed by ETRM (Enterprise Transaction Reporting Model), subledger accounting programs, and downstream data warehouses. It exposes both distribution-level and line-level attributes in a single flattened row, allowing accounting events, distributions, and descriptive flexfields to be extracted without additional joins.

Underlying Base Objects

The view is defined over several APPS synonyms and supporting packages. Invoice and distribution data originate from AP_INVOICE_DISTRIBUTIONS_ALL and AP_INVOICE_LINES_ALL, with invoice header context from AP_INVOICES_ALL. System configuration and defaults are drawn from AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL. Withholding tax group attributes come from AP_AWT_GROUPS and self-assessed tax distributions from AP_SELF_ASSESSED_TAX_DIST_ALL. Encumbrance typing is provided by GL_ENCUMBRANCE_TYPES, and purchasing context by PO_DISTRIBUTIONS_ALL and PO_HEADERS_ALL. Receiving context is supplied by RCV_TRANSACTIONS. Accounting event linkage leverages IGC_CC_SLA_BFLOW_PRIOR_V together with the PSA_BC_XLA_PUB and AP_UTILITIES_PKG packages. This composition confirms the view is an intersection of invoice, distribution, purchasing, receiving, and SLA extraction layers rather than a simple table projection.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling invoice distributions to SLA events, validating deferred accounting schedules, and feeding tax or asset extract routines. A representative query filtered by accounting period follows:

  • Extract all distributions for a given GL period: SELECT BC_EVENT_ID, INVOICE_DISTRIBUTION_ID, ACCOUNTING_DATE, AMOUNT FROM APPS.AP_EXTRACT_INVOICE_DTLS_BC_V WHERE PERIOD_NAME = :p_period;
  • Identify deferred accounting lines: SELECT INVOICE_DISTRIBUTION_ID, DEF_ACCTG_START_DATE, DEF_ACCTG_END_DATE FROM APPS.AP_EXTRACT_INVOICE_DTLS_BC_V WHERE DEFERRED_ACCTG_FLAG = 'Y';
  • Reconcile distribution to accounting event: SELECT BC_EVENT_ID, COUNT(*) FROM APPS.AP_EXTRACT_INVOICE_DTLS_BC_V GROUP BY BC_EVENT_ID;
  • Tax extract by merchant: SELECT MERCHANT_DOCUMENT_NUMBER, MERCHANT_TAXPAYER_ID, STAT_AMOUNT FROM APPS.AP_EXTRACT_INVOICE_DTLS_BC_V WHERE MERCHANT_TAX_REG_NUMBER IS NOT NULL;

Because the view references package-backed SLA logic, queries should be executed with the APPS schema context and appropriate Payables access privileges. Performance is best when filters are applied on PERIOD_NAME, ACCOUNTING_DATE, or INVOICE_DISTRIBUTION_ID, since these align with the underlying distribution table indexes.