Search Results pa_alloc_runs_all




Overview
Explore in AI Chat

Overview

The PA_ALLOC_RUNS_ALL table is a core transactional table within the Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for information pertaining to allocation runs. An allocation run is the execution of a defined allocation rule, which systematically distributes costs or revenue from a set of source projects or tasks to a set of target projects or tasks based on a specified basis, such as headcount or square footage. This table is the central point for tracking each execution instance, storing the run's parameters, status, and linkage to the controlling rule and related financial plan types. As an "ALL" table, it is designed to support multi-organization structures by including the ORG_ID column.

Key Information Stored

The table's primary key is the RUN_ID, which uniquely identifies each allocation execution. Critical foreign key columns establish relationships to other master data and control tables. The RULE_ID links the run to its governing definition in PA_ALLOC_RULES_ALL. The PPL_PROJECT_TYPE and PPL_ORG_ID columns reference PA_PROJECT_TYPES_ALL, defining the project type context for the run. The BASIS_FIN_PLAN_TYPE_ID, referencing PA_FIN_PLAN_TYPES_B, identifies the financial plan type used as the allocation basis. Other significant columns typically include status flags (e.g., run status, approval status), control totals (e.g., total basis amount, total allocated amount), run dates, and identifiers for the requesting user. The CINT_RATE_NAME column links to PA_IND_COST_CODES for indirect cost rate information when applicable.

Common Use Cases and Queries

This table is central to auditing, troubleshooting, and reporting on allocation activities. Common operational queries involve listing runs for a specific rule, checking the status of recent executions, or identifying runs that generated exceptions. For instance, to audit all completed runs for a specific allocation rule in the current month, a query might join PA_ALLOC_RULES_ALL on RULE_ID and filter on the rule name and run date. Support personnel frequently query this table alongside PA_ALLOC_EXCEPTIONS to diagnose failed runs. Reporting use cases include generating summaries of allocation volumes over time, analyzing the financial impact of allocation rules, and reconciling allocated amounts back to their source transactions. A typical pattern involves selecting from PA_ALLOC_RUNS_ALL and joining to related detail tables like PA_ALLOC_RUN_BASIS_DET and PA_ALLOC_TXN_DETAILS for granular reporting.

Related Objects

  • Primary Source/Dependencies: PA_ALLOC_RULES_ALL (defines the rule executed), PA_PROJECT_TYPES_ALL (project type context), PA_FIN_PLAN_TYPES_B (basis plan type).
  • Detail/Transaction Tables: PA_ALLOC_RUN_BASIS_DET, PA_ALLOC_RUN_SOURCE_DET, PA_ALLOC_TXN_DETAILS (store the granular results of the run).
  • Exception/Control Tables: PA_ALLOC_EXCEPTIONS, PA_ALLOC_MISSING_COSTS (capture errors and missing data from the run).
  • Integration Point: GL_AUTO_ALLOC_BATCH_HISTORY (links General Ledger auto-allocation batches to the Projects allocation run).