Search Results line_number_reversed




Overview
Explore in AI Chat

Overview

APPS.PABV_COST_DISTRIBUTIONS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered in the ETRM as a VALID view with the FND Design Data reference PA.PABV_COST_DISTRIBUTIONS. Its stated purpose is to present information about cost distribution lines, exposing the accounting distribution of project expenditure alongside the source transaction that generated it.

The view is a denormalized read-only projection. It is not intended for transactional DML; rather, it serves reporting, extract, and integration requirements where the cost distribution of a project-related transaction must be joined to its originating invoice, payment, or expenditure item. Because the projections are pre-joined across Project Costing and Payables structures, the view is commonly consumed by BI Publisher reports, custom concurrent programs, and downstream data warehouse loads that need a single consistent access path to distribution-level cost data.

Underlying Base Objects

The documented dependency list shows the view is defined over two base objects, both accessed through synonyms in the APPS schema:

  • PA_COST_DISTRIBUTION_LINES_ALL (SYNONYM) — the primary source, supplying the distribution line number, amount, quantity, burdened cost, reversal information, transfer status, and account code combinations.
  • PA_EXPENDITURE_ITEMS_ALL (SYNONYM) — the expenditure item header, supplying the item identity and related expenditure attributes that link back to projects and tasks.

Both underlying tables are multi-organization (_ALL) tables, keyed in the view output by ORG_ID. The join retains distribution granularity, so a single expenditure item may appear on multiple rows where several distribution lines exist.

Key Columns

The column list is significant because it drives both query design and interpretation of results. Notable columns include:

  • EXPENDITURE_ITEM_ID — the distribution's parent expenditure item; the primary join key back to PA_EXPENDITURE_ITEMS_ALL.
  • LINE_NUMBER — the distribution line sequence within the expenditure item.
  • LINE_NUMBER_REVERSED — the line number of the distribution line that this row reverses, or the line number used when the row was created as a reversal. This is the column most relevant to the user's search term: it identifies reversal relationships between distribution lines, enabling analysis of which line offsets which original entry.
  • AMOUNT, QUANTITY, BURDENED_COST — the raw distributed amount, quantity, and total burdened cost of the line.
  • _LA:BILLABLE_FLAG, _LA:REVERSED_FLAG, _LA:LINE_TYPE, _LA:TRANSFER_STATUS — lookup-validated attribute columns that expose the billable indicator, reversal indicator, distribution line type, and transfer status in decoded (meaning) form rather than raw codes.
  • PA_DATE, GL_DATE, TRANSFERRED_DATE, TRANSFER_REJECTION_REASON — the project accounting date, general ledger date, the date the line was transferred, and the reason for any transfer rejection.
  • AP_INVOICE_ID, AP_INVOICE_DISTRIBUTION_ID, AP_INVOICE_LINE_NUMBER, AP_INVOICE_PAYMENT_ID, VENDOR_ID — Payables linkage, identifying the source invoice, invoice distribution, invoice line, payment, and supplier.
  • DR_CODE_COMBINATION_ID, CR_CODE_COMBINATION_ID — the debit and credit accounting flexfield combinations for the distribution.
  • Currency and rate columns — DENOM_, ACCT_, and PROJECT_ currency codes, raw and burdened costs, rate types, rate dates, and exchange rates, permitting reporting in any of the three currency perspectives.
  • SI_ASSETS_ADDITION_FLAG — indicates whether the distribution is treated as an asset addition for Subledger Accounting / asset purposes.

Common Use Cases and Queries

Typical uses include reconciliation of transferred versus rejected cost distributions, analysis of reversal activity, and reporting of burdened cost by accounting period and organization.

To list reversed distribution lines and identify the reversed counterpart:

  • SELECT expenditure_item_id, line_number, line_number_reversed, amount, burdened_cost FROM apps.pabv_cost_distributions WHERE line_number_reversed IS NOT NULL;

To review transfer status and rejection reasons for a period:

  • SELECT expenditure_item_id, line_number, gl_date, transferred_date, transfer_rejection_reason FROM apps.pabv_cost_distributions WHERE gl_date BETWEEN :start_date AND :end_date;

To trace a distribution back to its Payables invoice:

  • SELECT cd.expenditure_item_id, cd.line_number, cd.ap_invoice_id, cd.ap_invoice_line_number, cd.vendor_id, cd.burdened_cost FROM apps.pabv_cost_distributions cd WHERE cd.ap_invoice_id = :invoice_id;

To summarize burdened cost by organization and currency:

  • SELECT org_id, acct_currency_code, SUM(acct_burdened_cost) FROM apps.pabv_cost_distributions GROUP BY org_id, acct_currency_code;

Because the view exposes lookup-decoded (_LA) columns, results are directly presentable without additional joins to lookup tables, which simplifies report development. Queries should always filter on ORG_ID where multi-organization security is required.