Search Results fa_asset_distribution_v




Overview

FA_ASSET_DISTRIBUTION_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OFA (Oracle Assets) product family. Its documented purpose is "Asset Identification and Distribution," reflecting that it joins static asset identification attributes (number, tag, description, manufacturer, serial, model) with the accounting and physical distribution of those assets across expense accounts, employees, and locations. The view operates within a single corporate book context, filtering on FA_BOOK_CONTROLS.BOOK_CLASS = 'CORPORATE', so it returns only assets belonging to the corporate book class and excludes fully retired or ineffective book and distribution rows.

The view is intended for operational reporting and downstream integration rather than for transaction processing. It flattens asset master data, depreciation book cost, category accounting, distribution history, employee assignment, physical location, and the expense charge account into a single denormalized result set. A distinctive characteristic is the extensive use of /* CUSTOMIZE */ annotations in the view text against the SEGMENTx columns of the category, location, and expense code combination flexfields. These markers signal that the segment-to-meaning mapping (for example, SEGMENT6 mapped to "SUB_ACCOUNT") is a delivered default that customers are expected to adjust to match their own chart of accounts and location flexfield structures.

Underlying Base Objects

The documented base objects are: FA_ADDITIONS, FA_BOOKS, FA_BOOK_CONTROLS, FA_CATEGORIES_B, FA_CATEGORY_BOOKS, FA_DISTRIBUTION_HISTORY, FA_EMPLOYEES (a view), FA_LOCATIONS, and GL_CODE_COMBINATIONS, all referenced as synonyms except FA_EMPLOYEES, which is a view. Supporting packages include HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, used for employee name resolution and security enforcement on employee-related columns.

  • FA_ADDITIONS supplies asset identification: asset number, tag number, description, manufacturer, serial number, model number, category, and current units.
  • FA_BOOK_CONTROLS and FA_BOOKS drive the book context, cost, and date placed in service; the join filters BOOK_CLASS = 'CORPORATE', excludes fully retired periods (PERIOD_COUNTER_FULLY_RETIRED IS NULL), and excludes ineffective book rows (DATE_INEFFECTIVE IS NULL).
  • FA_CATEGORIES_B and FA_CATEGORY_BOOKS provide category segment values and the asset cost account (ASSET_COST_ACCT).
  • FA_DISTRIBUTION_HISTORY supplies the assignment of units, assigned-to employee, location, and the code combination used to derive the expense account; ineffective distribution rows are excluded.
  • GL_CODE_COMBINATIONS describes the expense charge account, whose segments are exposed as COMPANY through SUB_ACCOUNT.
  • FA_EMPLOYEES and FA_LOCATIONS resolve the employee and physical location details.

Cost is apportioned across distribution lines using ROUND(BK.COST * DH.UNITS_ASSIGNED / AD.CURRENT_UNITS, 2), so multi-line distributions receive a pro-rata share of book cost.

Key Columns

The view exposes columns grouped into four logical areas:

The sub_account column in the user's search corresponds to EXPENSE_CC.SEGMENT6 "SUB_ACCOUNT". Because it is protected by a /* CUSTOMIZE */ marker, the sixth segment of the customer's chart of accounts may not semantically be a "sub-account" — it is simply the sixth segment position. Confirm the actual segment meaning against the customer's Accounting Flexfield definition before relying on this label. The column represents the sixth segment of the expense charge account assigned on the distribution line.

Common Use Cases and Queries

Typical uses include asset distribution and cost-allocation reporting, employee-asset assignment listings, location-based asset rollups, and general ledger account analysis where assets are charged to expense accounts containing a sub-account segment. It is also used to feed external asset registers and reconciliation processes.

Example: list all asset distributions for a given book with their expense sub-account.

  • SELECT asset_number, tag_number, description, book_type_code, cost, employee_name, company, cost_center, sub_account FROM apps.fa_asset_distribution_v WHERE book_type_code = 'CORP' ORDER BY asset_number;

Example: total distributed cost by sub-account.

  • SELECT sub_account, SUM(cost) total_cost FROM apps.fa_asset_distribution_v GROUP BY sub_account ORDER BY sub_account;

Example: assets assigned to a specific employee.

  • SELECT asset_number, tag_number, cost, city, site, locator FROM apps.fa_asset_distribution_v WHERE employee_number = :emp_num;

Because the view enforces BOOK_CLASS = 'CORPORATE' and excludes retired and ineffective rows, reports built on it reflect current, active corporate-book distributions only. Queries against non-corporate books cannot be satisfied without modifying or replacing the view, and the segment labels must be validated against the customer's own flexfield configuration before the sub_account column is treated as a true sub-account.