Results for “payables_cost”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The FA_ADD_INVOICE_WEB_V view is an Oracle EBS 12.1.1 / 12.2.2 reporting object owned by the APPS schema and registered under the Oracle Assets (OFA) product family. Its documented purpose is to expose "invoice information pertaining to the asset," providing a consolidated, denormalized read model that joins asset-master attributes with the payable invoice lines that created or adjusted capitalized asset cost. The view is described as VALID and is intended for web-facing or reporting consumption of invoice-to-asset relationships without requiring the caller to navigate the underlying FA_ASSET_INVOICES table directly.

The name FA_ADD_INVOICE_WEB_V reflects its lineage: it draws from FA_ADDITIONS (the table holding the asset definition) combined with invoice detail from FA_ASSET_INVOICES, and it is presented as a view suited to web inquiry and reporting. It does not itself store data; it synthesizes a relational projection over the base tables and supporting lookup objects.

Underlying Base Objects

The ETRM metadata for 12.2.2 records the following referenced objects:

• FA_ADDITIONS, FA_ASSET_INVOICES, FA_BOOKS, FA_BOOK_CONTROLS, FA_CATEGORIES_B (synonyms to the Oracle Assets tables).
• FA_ASSET_KEYWORDS_KFV and FA_CATEGORIES_B_KFV — key-flexfield and category-flexfield views supplying concatenated account segments.
• FND_CURRENCY — a package whose SAFE_GET_FORMAT_MASK function is invoked to format monetary columns using the invoice currency format mask.
• GL_SETS_OF_BOOKS — the General Ledger set-of-books view used for book context.
• PO_VENDORS — the payables supplier view, providing vendor name, vendor number and invoice currency.

Structurally, the primary driving tables are FA_ADDITIONS (asset identity and descriptive attributes) and FA_ASSET_INVOICES (invoice lines that generated the asset), joined to FA_CATEGORIES_B, PO_VENDORS, and the books-related objects. The FA_BOOKS and FA_BOOK_CONTROLS joins supply the book context for the asset, while the flexfield views resolve the asset key and category accounting combinations.

Key Columns

• AI.DESCRIPTION is projected as INVOICE_DESCRIPTION — the payables line description, which is the column most users search for when tracing an asset back to its originating invoice.
• ASSET_ID, ASSET_NUMBER, TAG_NUMBER, ASSET_DESCRIPTION, ASSET_TYPE — asset identification and descriptive attributes from FA_ADDITIONS.
• PO_NUMBER, INVOICE_NUMBER, INVOICE_DATE, INVOICE_LINE_NUMBER, AP_DISTRIBUTION_LINE_NUMBER, INVOICE_ID — payable-side identifiers linking the asset to Oracle Payables.
• VENDOR_NUMBER, VENDOR_NAME, INVOICE_CURRENCY_CODE — supplier information from PO_VENDORS.
• FIXED_ASSETS_COST, PAYABLES_COST, UNREVALUED_COST — monetary amounts, each formatted through FND_CURRENCY.SAFE_GET_FORMAT_MASK.
• DATE_EFFECTIVE, DATE_INEFFECTIVE, DELETED_FLAG — effective-dating and logical-delete controls.
• PAYABLES_BATCH_NAME, FEEDER_SYSTEM_NAME, CREATE_BATCH_ID, CREATE_BATCH_DATE — mass-additions / batch provenance.
• ASSET_KEY, CATEGORY — concatenated flexfield segments from the KFV views.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY_CODE — descriptive flexfield columns.

Common Use Cases and Queries

Typical usage is asset-to-invoice reconciliation and audit tracing. The following query lists assets reconciled to a particular invoice description:

SELECT asset_number,
       tag_number,
       invoice_number,
       invoice_description,
       vendor_name,
       fixed_assets_cost,
       invoice_date
FROM   apps.fa_add_invoice_web_v
WHERE  UPPER(invoice_description) LIKE UPPER('%&desc%')
AND    NVL(deleted_flag,'N') = 'N';

A second common pattern retrieves all invoice lines tied to a given asset:

SELECT asset_number, invoice_number, ap_distribution_line_number,
       payables_cost, invoice_currency_code
FROM   apps.fa_add_invoice_web_v
WHERE  asset_id = :p_asset_id
ORDER  BY invoice_date DESC;

Because the view already resolves vendor, category, and formatted cost information, it is well suited to ad-hoc asset-invoice reports and to integration interfaces that need to move invoice-to-asset data without reimplementing the multi-table join logic.