Search Results payables_batch_name




Overview
Explore in AI Chat

Overview

FA_MC_ASSET_INVOICES is a table in the FA (Fixed Assets) schema belonging to the OFA – Assets product in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores accounts payable and purchasing information for each asset, expressed in the reporting currency rather than the functional currency. The "MC" prefix reflects the multi-currency (reporting currency) copy of asset invoice data maintained by the Assets module for reporting and revaluation purposes. In the documented 12.2.2 physical schema, the table contains 63 columns, owned by FA with status VALID.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as a link object. It associates an asset with the AP/PO documents that contributed to its cost, and the heavy pattern of foreign keys to operational and reference tables supports treating it as an intersection between asset, invoice, purchasing, and project entities. The documented unique index FA_MC_ASSET_INVOICES_U1 (SET_OF_BOOKS_ID, SOURCE_LINE_ID) provides the business key candidate for that link.

Key Information Stored

The table captures the relationship between a fixed asset and its source invoice distributions, with both functional and reporting-currency attributes. The most significant columns include:

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE1–ATTRIBUTE15 with ATTRIBUTE_CATEGORY_CODE are also present for extensibility.

Common Use Cases and Queries

The primary purpose of FA_MC_ASSET_INVOICES is to support reporting-currency asset cost reporting, invoice-to-asset reconciliation, and multi-currency revaluation within Oracle Assets. Typical scenarios include reconciling payables cost to the asset cost booked in FA_ADDITIONS_B, tracing an asset back to the AP invoice and PO that generated it, and reporting fixed-asset cost by vendor or supplier in reporting currency.

A representative query joins the table to FA_ADDITIONS_B to obtain the asset number and to AP_INVOICES_ALL for invoice detail:

  • SELECT ai.ASSET_INVOICE_ID, ai.ASSET_ID, ai.INVOICE_NUMBER, ai.PAYABLES_COST, ai.PAYABLES_UNITS, ai.EXCHANGE_RATE FROM FA_MC_ASSET_INVOICES ai WHERE ai.SET_OF_BOOKS_ID = :sob AND ai.DELETED_FLAG = 'N';
  • SELECT a.ASSET_NUMBER, ai.PO_NUMBER, ai.INVOICE_NUMBER, ai.PAYABLES_COST FROM FA_MC_ASSET_INVOICES ai, FA_ADDITIONS_B a WHERE ai.ASSET_ID = a.ASSET_ID AND ai.SET_OF_BOOKS_ID = :sob;

Because the unique key is (SET_OF_BOOKS_ID, SOURCE_LINE_ID), lookups by source line are efficient, which is useful when reconciling a specific payables distribution or project asset line into the assets subledger. Filtering on DATE_EFFECTIVE and DATE_INEFFECTIVE supports as-of-date reporting, while CREATE_BATCH_ID and POST_BATCH_ID allow tracing back to the FND concurrent request that produced the row.

Related Objects

FA_MC_ASSET_INVOICES is extensively referenced and referencing through foreign keys. The most significant related objects are:

This dense FK footprint confirms the table's role as a central link between the Assets, Payables, Purchasing, Projects, and General Ledger subledgers, and explains why it is frequently queried in reconciliation and multi-currency asset reporting extracts.