Search Results pa_project_asset_lines_all

Overview

The PA_PROJECT_ASSET_LINES_ALL table is a core data structure within Oracle E-Business Suite (EBS) Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for summarized Capital Work in Progress (CIP) costs associated with project assets. Its fundamental role is to act as the central transactional link between the Projects module and the Fixed Assets (FA) module. When project costs are capitalized, summarized entries are created in this table, which are then used as the source for generating asset additions or adjustments in Fixed Assets. The table's multi-org structure, indicated by the "_ALL" suffix, allows it to store data for all operating units within a single installation.

Key Information Stored

The table's primary key is PROJECT_ASSET_LINE_ID, which uniquely identifies each summarized CIP cost line. The most critical columns define the relationships and financial context of the asset line. These include PROJECT_ID and TASK_ID, linking the cost to a specific project task, and PROJECT_ASSET_ID, which references the master asset definition in PA_PROJECT_ASSETS_ALL. The ASSET_CATEGORY_ID links to the FA_CATEGORIES_B table, defining the future fixed asset's category. Financial amounts, such as the capitalized cost, are stored in summarized form. Other key columns manage transactional integrity and process flow, such as CAPITAL_EVENT_ID (linking to the capital event that triggered the line creation) and REV_PROJ_ASSET_LINE_ID (supporting reversals of previous entries).

Common Use Cases and Queries

The primary use case is tracking and reporting on project costs destined for capitalization. Common queries involve joining to project and asset master tables to analyze CIP balances or to troubleshoot the flow of costs into Fixed Assets. For instance, to identify all capitalized costs for a specific project that have not yet been transferred to Fixed Assets, one might query lines where the associated mass addition or asset invoice ID is null. Another critical scenario is reconciliation between project expenditures and asset additions. A sample query pattern is:

• SELECT p.segment1 project_number, t.task_number, a.asset_number, pal.cost
• FROM pa_project_asset_lines_all pal
• JOIN pa_projects_all p ON pal.project_id = p.project_id
• JOIN pa_tasks t ON pal.task_id = t.task_id
• LEFT JOIN pa_project_assets_all pa ON pal.project_asset_id = pa.project_asset_id
• LEFT JOIN fa_additions_b a ON pa.asset_id = a.asset_id
• WHERE p.segment1 = 'P12345';

Related Objects

As indicated by its extensive foreign key relationships, PA_PROJECT_ASSET_LINES_ALL is a central hub. Key dependencies include:

• Parent Tables: PA_PROJECTS_ALL, PA_TASKS, PA_PROJECT_ASSETS_ALL, FA_CATEGORIES_B, PA_CAPITAL_EVENTS.
• Child Tables: PA_PROJECT_ASSET_LINE_DETAILS (holds detailed cost distributions), FA_MASS_ADDITIONS (receives generated records for asset import), FA_ASSET_INVOICES, and their multi-currency counterparts (FA_MC_ASSET_INVOICES, PA_MC_PRJ_AST_LINES_ALL).
• Process Flow: The table is directly referenced by the capital asset line generation and transfer processes. The foreign key to FA_TRANSACTION_HEADERS.RET_ADJUSTMENT_TXN_ID links it to specific asset retirement adjustments in Fixed Assets.