Results for “fa_source_lines_v”

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

Overview

FA_SOURCE_LINES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and belonging to the Oracle Assets (OFA) product family. It presents the Payables-sourced lines that flow into Oracle Assets, exposing the linkage between a Payables invoice distribution and the corresponding asset line record. In releases 12.1.1 and 12.2.2 the view is documented as VALID and is used primarily for reporting, reconciliation, and integration queries that need to correlate purchasing, Payables, and Assets data in a single result set.

The view is central to the reconciliation of Payables mass additions with Oracle Assets. Fields such as PAYABLES_BATCH_NAME, PAYABLES_CODE_COMBINATION_ID, PAYABLES_COST, and PAYABLES_UNITS give a consolidated picture of the source Payables transaction behind each asset line. The presence of the PAYABLES_BATCH_NAME column explains why users searching for that term are directed to this view: it is one of the few seeded objects that surfaces the Payables batch name alongside the asset line, invoice, and vendor attributes.

Underlying Base Objects

The documented view definition joins three referenced base objects:

• FA_ASSET_INVOICES (SYNONYM) — aliased as AI; the driving table containing the asset invoice and source line information.
• FA_EXT_INV_RETIREMENTS (SYNONYM) — aliased as SL; outer-joined on SOURCE_LINE_ID to supply external invoice retirement data such as MASS_EXTERNAL_RETIRE_ID and COST_RETIRED.
• PO_VENDORS (VIEW) — aliased as PO; outer-joined on PO_VENDOR_ID to supply VENDOR_NUMBER and VENDOR_NAME.

The join predicate restricts results to rows where DATE_INEFFECTIVE IS NULL, meaning only currently effective asset invoice lines are returned by default. Because both the retirement and vendor joins are outer joins, asset lines without a matching retirement record or vendor record are still included.

Key Columns

• PAYABLES_BATCH_NAME — the Payables batch name associated with the source transaction; the column most frequently searched by users.
• SOURCE_LINE_ID / ASSET_INVOICE_ID / ASSET_ID — identifiers that key the asset line back to the asset invoice and the asset itself.
• FIXED_ASSETS_COST / PAYABLES_COST / PAYABLES_UNITS — cost and unit values as recorded in Assets versus as sourced from Payables.
• PO_VENDOR_ID, VENDOR_NUMBER, VENDOR_NAME — supplier identification from PO_VENDORS.
• PO_NUMBER, INVOICE_NUMBER, INVOICE_DATE, INVOICE_LINE_NUMBER — the originating purchasing and invoice references.
• PAYABLES_CODE_COMBINATION_ID — the Payables accounting flexfield combination used for the distribution.
• CREATE_BATCH_ID / CREATE_BATCH_DATE / POST_BATCH_ID — batch identifiers and dates used for mass additions processing.
• DATE_EFFECTIVE / DATE_INEFFECTIVE / DELETED_FLAG — effective-dating and logical deletion indicators.
• SPLIT_CODE / MERGED_CODE / SPLIT_MERGED_CODE — flags indicating whether the line participated in a split or merge operation.

Common Use Cases and Queries

Typical scenarios include reconciling Payables mass additions to Assets, auditing the Payables batch that produced a given asset line, and tracing vendor or purchase order details for capitalized costs.

To locate all asset lines tied to a specific Payables batch:

• SELECT source_line_id, asset_id, invoice_number, payables_batch_name, payables_cost
FROM apps.fa_source_lines_v
WHERE payables_batch_name = :batch_name;

To review vendor and purchasing detail for capitalized asset lines:

• SELECT a.asset_id, a.po_number, a.vendor_name, a.invoice_number, a.fixed_assets_cost
FROM apps.fa_source_lines_v a
WHERE a.vendor_number = :vendor_number;

Because the view already filters on DATE_INEFFECTIVE IS NULL, no additional effective-dating predicate is normally required. All access should reference the APPS schema and observe the standard read-only conventions applied to seeded OFA reporting views.