Search Results ls_attribute_category_code




Overview
Explore in AI Chat

Overview

FA_FUTURE_MASS_ADDITIONS_V is an Oracle EBS Assets (OFA) view owned by the APPS schema, classified as VALID and defined over the FA module's asset and lease structures. It presents the set of asset additions that are pending or staged for future mass addition processing, combining asset-level detail from FA_ADDITIONS with lease, book, category, and parent-asset context. In Oracle EBS 12.1.1 and 12.2.2, the view is used for reporting, reconciliation, and integration scenarios where asset information must be reviewed before it is capitalized or posted through the Prepare Mass Additions process.

Its practical value lies in the fact that it exposes descriptive lease attributes—notably LEASE_DESC (sourced from FA_LEASES.DESCRIPTION) and the LS_ATTRIBUTE1 through LS_ATTRIBUTE15 columns—alongside standard asset attributes. Users searching for "lease_desc" are typically attempting to report lease descriptions for leased assets awaiting addition, and this view is the appropriate access point for that requirement because it joins the staged asset row directly to its lease record.

Underlying Base Objects

The documented view text references several base objects, several of which are exposed through APPS synonyms: FA_ADDITIONS and FA_ADDITIONS_B (synonyms), FA_BOOKS, FA_BOOK_CONTROLS, FA_CATEGORIES, FA_DISTRIBUTION_HISTORY, FA_LEASES, FA_RETIREMENTS, and PO_VENDORS (a view). It also draws on FA_ADDITIONS_NON_SEC_VL, FA_MASS_ADDITIONS_V (both views), and the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages for security and naming context.

The primary row source is the asset addition record (aliased AD), joined to parent-asset information (PAD), the lessor vendor (PV), and the lease row (LEASE) to supply LEASE_NUMBER, LEASE_DESC, LESSOR_ID, and the lease descriptive flexfield attributes. Category behavior (CATEGORY_TYPE, CAPITALIZE_FLAG) comes from FA_CATEGORIES, while BK.DATE_PLACED_IN_SERVICE originates from the book context. The HR_SECURITY package drives row-level access, ensuring users see only the assets permitted by their security profile.

Key Columns

Common Use Cases and Queries

Typical uses include reporting pending additions with their lease details, validating lease descriptive flexfield values before capitalization, and feeding downstream integration extracts. Because the view is secured via HR_SECURITY, results respect the caller's asset security profile.

Sample query retrieving lease descriptions for staged additions:

  • SELECT asset_number, description, lease_number, lease_desc, lessor FROM fa_future_mass_additions_v WHERE owned_leased = 'LEASED';
  • SELECT asset_number, lease_desc, ls_attribute1, ls_attribute_category_code FROM fa_future_mass_additions_v WHERE lease_id IS NOT NULL ORDER BY asset_number;
  • SELECT asset_number, parent_asset, category_type, capitalize_flag, date_placed_in_service FROM fa_future_mass_additions_v WHERE capitalize_flag = 'Y';

Consumers should note that this is a reporting view, not an interface table; inserts and updates must target the underlying base tables rather than the view itself.