Search Results deferred_end_date




Overview
Explore in AI Chat

Overview

APPS.AP_INVOICE_EXTRACT_DETAILS_V is a reporting and integration view in the Oracle E-Business Suite Payables (SQLAP) product family. Its FND design data identifier, SQLAP.AP_INVOICE_EXTRACT_DETAILS_V, places it firmly within the invoice extraction layer used by Payables accounting and third-party data extraction programs. The view exposes invoice header, line, distribution, and deferred accounting attributes in a single denormalized result set, which makes it suitable for feeding subledger accounting (SLA) processing, external reporting, and downstream data warehouses.

The object is registered in the APPS schema as a VALID view in both Oracle EBS 12.1.1 and 12.2.2. Because it is owned by APPS, it is accessible to any responsibility whose data grants permit execution against APPS objects, and it is typically consumed by concurrent programs, Oracle Reports, and custom PL/SQL that need to reconstruct invoice accounting detail without joining the base transactions directly.

Underlying Base Objects

The documented dependency list for the 12.2.2 metadata shows that the view is defined over the following base objects and synonyms:

The view therefore bridges transactional Payables tables with purchasing, receiving, and Subledger Accounting constructs, producing an extract that is already aligned to the accounting event model.

Key Columns

The columns fall into recognizable groups. The identifier columns EVENT_ID, LINE_NUMBER, INV_DISTRIBUTION_IDENTIFIER, and AID_DISTRIBUTION_LINE_NUMBER establish the accounting event and its line/distribution lineage. The deferred accounting columns are central to the user's search term:

  • DEFERRED_OPTION — indicates whether the distribution is subject to deferred expense recognition.
  • DEFERRED_START_DATE — the date from which deferred recognition begins; this is the column targeted by the "deferred_start_date" search.
  • DEFERRED_END_DATE — the date on which deferred recognition concludes.
  • DEFERRED_PERIOD_TYPE — the period granularity (for example, monthly) used for deferral.
  • DEFERRED_NUMBER_OF_PERIODS — the count of periods over which the amount is recognized.

The AID_* columns (AID_AMOUNT, AID_ACCOUNTING_DATE, AID_DIST_CCID, AID_PERIOD_NAME, AID_EXPENDITURE_TYPE, AID_ATTRIBUTE1 through AID_ATTRIBUTE15, and related reference fields) carry the accounting distribution detail, while AIL_* columns carry line-level descriptive and segment data. DIST_ACCOUNT_REVERSAL_OPTION governs reversal behavior.

Common Use Cases and Queries

Typical scenarios include reconciling deferred expense schedules, extracting invoice accounting for a data warehouse, and auditing distributions flagged for deferral. A representative query retrieving deferred distributions is:

  • SELECT EVENT_ID, LINE_NUMBER, DEFERRED_OPTION, DEFERRED_START_DATE, DEFERRED_END_DATE, DEFERRED_PERIOD_TYPE, DEFERRED_NUMBER_OF_PERIODS, AID_AMOUNT, AID_PERIOD_NAME FROM APPS.AP_INVOICE_EXTRACT_DETAILS_V WHERE DEFERRED_START_DATE IS NOT NULL;
  • To scope by accounting period: ... WHERE AID_PERIOD_NAME = :period_name AND DEFERRED_OPTION = 'Y';
  • To reconcile against a specific distribution: ... WHERE INV_DISTRIBUTION_IDENTIFIER = :dist_id;

Because the view draws on multiple operational tables, queries should be constrained by period, event, or distribution identifier to control execution cost. As with all APPS views, access is governed by data security and the responsibility's grants.