Search Results lutl_pt

Overview

APPS.FA_ADDITIONS_V is a seeded Oracle E-Business Suite view in the Fixed Assets (FA) module that exposes asset addition and descriptive information in a single, denormalized result set. It is defined as a join over the core asset tables (FA_ADDITIONS_B, FA_ADDITIONS_TL, FA_CATEGORIES_B, FA_LEASES, FA_LOOKUPS_B, FA_LOOKUPS_TL) plus the PO_VENDORS view, allowing report writers, integrations, and diagnostic queries to retrieve asset attributes without manually reconstructing the underlying joins. The view is available in both EBS 12.1.1 and 12.2.2 and follows the standard APPS synonym convention.

The name FA_ADDITIONS_V reflects its primary source table, FA_ADDITIONS_B, which stores the base asset addition record (asset number, asset ID, key CCID, units, type, tag, and descriptive flexfield context). The view enriches each row with translated descriptions, category information, parent asset details, lease information, and lookup meanings.

Underlying Base Objects

The ETRM metadata documents the following referenced objects for this view:

• FA_ADDITIONS_B (synonym) — the base asset table holding asset_id, asset_number, asset_key_ccid, current_units, asset_type, tag_number, category, property codes, and the full DFF attribute set (ATTRIBUTE1–ATTRIBUTE30, ATTRIBUTE_CATEGORY_CODE, CONTEXT).
• FA_ADDITIONS_TL (synonym) — the translated description table, joined to provide ADT.DESCRIPTION (asset description) and PADT.DESCRIPTION (parent asset description).
• FA_CATEGORIES_B (synonym) — supplies CA.CATEGORY_TYPE and CA.CAPITALIZE_FLAG for the asset's category.
• FA_LEASES (synonym) — supplies lease_id, LEASE_NUMBER, LEASE_DESC, LESSOR_ID, lease-level DFF attributes (LS_ATTRIBUTE1–LS_ATTRIBUTE15, LS_ATTRIBUTE_CATEGORY_CODE).
• FA_LOOKUPS_B / FA_LOOKUPS_TL (synonyms) — join to lookup codes to resolve meanings, notably lutl_pt.meaning for PROPERTY_TYPE_MEANING and lutl_pc.meaning for PROPERTY_1245_1250_MEANING.
• PO_VENDORS (view) — resolves the lessor vendor name (PV.VENDOR_NAME) referenced by the lease.

The view also performs self-joins against the asset tables to derive PARENT_ASSET and PARENT_DESCRIPTION, and LEFT (or equivalent outer) joins against FA_LEASES so that non-leased assets still return a row.

Key Columns

• ROW_ID / ASSET_ID / ASSET_NUMBER — unique row identifier and asset identifiers.
• ASSET_KEY_CCID, CURRENT_UNITS, ASSET_TYPE, TAG_NUMBER — core asset attributes.
• PROPERTY_TYPE_CODE / PROPERTY_TYPE_MEANING — the property type code and its resolved lookup meaning (lutl_pt).
• PROPERTY_1245_1250_CODE / PROPERTY_1245_1250_MEANING — the Section 1245/1250 property classification code and its meaning (lutl_pc), which is the specific column pair surfaced by the search term "lutl_pc". The alias lutl_pc is the lookup alias used when joining FA_LOOKUPS for the 1245/1250 meaning.
• PARENT_ASSET / PARENT_DESCRIPTION — parent asset number and translated description.
• LESSOR, LEASE_NUMBER, LEASE_DESC, LESSOR_ID — lease/vendor information resolved from FA_LEASES and PO_VENDORS.
• CATEGORY_TYPE, CAPITALIZE_FLAG — category behavior flags.
• ATTRIBUTE1–ATTRIBUTE30, ATTRIBUTE_CATEGORY_CODE, CONTEXT — the asset descriptive flexfield columns.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include Fixed Assets reporting, tax property classification reporting, and land/asset investigations that require the 1245/1250 designation alongside the asset description and category.

Return assets with their resolved property classifications:

• SELECT asset_number, description, property_type_meaning, property_1245_1250_meaning FROM apps.fa_additions_v WHERE property_1245_1250_code IS NOT NULL;
• SELECT asset_number, description, parent_asset, lessor, lease_number FROM apps.fa_additions_v WHERE lease_id IS NOT NULL AND lessor IS NOT NULL;
• SELECT asset_number, category_type, capitalize_flag, tag_number FROM apps.fa_additions_v WHERE capitalize_flag = 'Y';

Because the view includes translated description columns and lookup meanings, it is well suited to operational reports and interfaces that need human-readable output without additional joins. Note that DFF columns (ATTRIBUTE1–ATTRIBUTE30) require the applicable ATTRIBUTE_CATEGORY_CODE/CONTEXT filter to return meaningful values. Always qualify the view with the APPS schema and restrict output with a WHERE clause, since unfiltered queries against FA_ADDITIONS_V can return every asset addition recorded in the instance.