Search Results pa_cost_distribution_lines_all

Overview

The PA_COST_DISTRIBUTION_LINES_ALL table is a core transactional table within Oracle E-Business Suite Projects (PA) module, specifically for releases 12.1.1 and 12.2.2. It serves as the central repository for detailed cost accounting distributions generated from project-related expenditures. When an expenditure item is processed—whether from labor, supplier invoices, or other sources—the system creates one or more records in this table to represent the financial impact across projects, tasks, and accounts. Its primary role is to capture the fully burdened cost distribution, including raw cost, burden cost, and revenue, and to serve as the critical link between project expenditures and the General Ledger (GL). The table supports multi-organization architecture, as indicated by the '_ALL' suffix and the ORG_ID column.

Key Information Stored

The table stores comprehensive distribution details for each cost line. Its primary key is a composite of LINE_NUM and EXPENDITURE_ITEM_ID, ensuring uniqueness for multiple distributions from a single expenditure. Key columns include EXPENDITURE_ITEM_ID, linking to the source transaction in PA_EXPENDITURE_ITEMS_ALL, and PROJECT_ID and TASK_ID for project accounting. Financial accounting is facilitated by DR_CODE_COMBINATION_ID and CR_CODE_COMBINATION_ID, which reference GL_CODE_COMBINATIONS for debit and credit entries. Currency conversion data is held in ACCT_CURRENCY_CODE, PROJECT_CURRENCY_CODE, ACCT_RATE_TYPE, and PROJECT_RATE_TYPE. The table also tracks reversal relationships via LINE_NUM_REVERSED and integrates with other modules through SYSTEM_REFERENCE columns, which can link to records in AP_INVOICE_DISTRIBUTIONS_ALL or PO_VENDORS.

Common Use Cases and Queries

A primary use case is tracing the complete accounting distribution of project costs for financial reporting and audit trails. Analysts frequently query this table to reconcile project costs with General Ledger entries or to analyze cost accumulation by project and task. Another critical scenario involves investigating integration issues, such as matching invoice distributions from Payables to their corresponding project cost distributions. Common SQL patterns include joining to related project and financial tables.

• Cost Summary by Project: SELECT pcd.project_id, ppa.segment1 project_number, SUM(pcd.raw_cost) total_raw_cost FROM pa_cost_distribution_lines_all pcd JOIN pa_projects_all ppa ON pcd.project_id = ppa.project_id GROUP BY pcd.project_id, ppa.segment1;
• Distributions for a Specific Expenditure Item: SELECT * FROM pa_cost_distribution_lines_all WHERE expenditure_item_id = &exp_item_id ORDER BY line_num;
• GL Reconciliation: Queries often join this table to GL_JE_LINES via the code combination IDs and reference columns to ensure all project costs have been properly transferred to the ledger.

Related Objects

PA_COST_DISTRIBUTION_LINES_ALL has extensive relationships with other EBS objects, as documented by its foreign keys. It is fundamentally a child of PA_EXPENDITURE_ITEMS_ALL via EXPENDITURE_ITEM_ID. For project context, it links to PA_PROJECTS_ALL (PROJECT_ID) and PA_TASKS (TASK_ID). Its accounting integrity depends on GL_CODE_COMBINATIONS for both DR_CODE_COMBINATION_ID and CR_CODE_COMBINATION_ID. Integration with other financial modules is evidenced by foreign keys to AP_INVOICE_DISTRIBUTIONS_ALL (SYSTEM_REFERENCE2, SYSTEM_REFERENCE3) and PO_VENDORS (SYSTEM_REFERENCE2). It also references PA_EXPENDITURE_BATCHES_ALL (BATCH_NAME, ORG_ID), GL_DAILY_CONVERSION_TYPES for rate types, FND_CURRENCIES, GL_ENCUMBRANCE_TYPES, and PA_WORK_TYPES_B. A self-referential foreign key exists for tracking reversals (LINE_NUM_REVERSED, EXPENDITURE_ITEM_ID).