Search Results pa_subbudgets




Overview
Explore in AI Chat

Overview

The PA_SUBBUDGETS table is a core data object within the Oracle E-Business Suite (EBS) Projects module (PA). It serves as a master table for storing sub-budget definitions within the project budgeting architecture. The table's primary role is to establish and maintain the hierarchical relationship between a parent project budget and its constituent sub-budgets, which are typically defined at the task level. This structure is essential for detailed budget planning, tracking, and control, allowing organizations to allocate and monitor financial resources against specific work breakdown structure (WBS) elements. The metadata indicates this table is specific to the "10SC" context, which refers to a legacy project costing and billing functionality.

Key Information Stored

The table's structure centers on uniquely identifying a sub-budget and linking it to its associated project and parent budget. The primary key columns are PROJECT_ID, BUDGET_TYPE_CODE, and TASK_ID. The PROJECT_ID and BUDGET_TYPE_CODE together link the sub-budget to its parent budget record in the PA_BUDGETS table. The TASK_ID column links the sub-budget to a specific task within the project's work breakdown structure, as defined in the PA_TASKS table. This design enforces that a sub-budget is a child of a specific project budget and is assigned to a specific task. The table likely contains additional columns for status, versioning, and control totals, though the provided metadata focuses on its core relational integrity.

Common Use Cases and Queries

This table is central to operations involving task-level financial management. Common use cases include generating detailed budget versus actual reports at the task level, performing funds checks against sub-budget lines, and aggregating task budgets to roll up to the total project budget. A typical query would join PA_SUBBUDGETS with PA_PROJECTS_ALL, PA_TASKS, and PA_BUDGETS to retrieve a comprehensive budget hierarchy. For example, to list all sub-budgets for a specific project, one might use:

  • SELECT ps.PROJECT_ID, ps.TASK_ID, pt.TASK_NAME, ps.BUDGET_TYPE_CODE, pb.BUDGET_NAME FROM PA_SUBBUDGETS ps, PA_TASKS pt, PA_BUDGETS pb WHERE ps.PROJECT_ID = :p_project_id AND ps.TASK_ID = pt.TASK_ID AND ps.PROJECT_ID = pb.PROJECT_ID AND ps.BUDGET_TYPE_CODE = pb.BUDGET_TYPE_CODE;

Reporting often involves summarizing budget amounts from the related PA_BUDGET_ITEMS table, filtered by the sub-budget keys.

Related Objects

PA_SUBBUDGETS is a nexus within the Projects schema, with critical relationships to several key tables. As per the foreign key constraints, it is a child of PA_PROJECTS_ALL, PA_TASKS, and PA_BUDGETS. Its most significant relationship is with PA_BUDGET_ITEMS, where it acts as a parent table. The PA_BUDGET_ITEMS table stores the detailed revenue, cost, and quantity lines for a budget, and its records for a task are linked back to the sub-budget definition via the composite key (PROJECT_ID, BUDGET_TYPE_CODE, TASK_ID). This means PA_SUBBUDGETS defines the header, while PA_BUDGET_ITEMS holds the detailed lines. Consequently, any process creating or updating task-level budget lines will reference or depend on this table.