Results for “pa_bc_balances”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_BC_BALANCES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores actual, budget, and encumbrance balances at the granular level of project, task, period, budget version, and resource. Budget balances are populated during the budget baselining process, while actuals and encumbrances are reflected as accounting entries are generated and summarized. The table therefore acts as a consolidated balance repository supporting project performance reporting, budget-versus-actual analysis, and commitment tracking across the project lifecycle.

The documented physical schema contains 23 columns owned by the PA schema, with a unique index PA_BC_BALANCES_U1 spanning BUDGET_VERSION_ID, PROJECT_ID, BALANCE_TYPE, START_DATE, END_DATE, TASK_ID, TOP_TASK_ID, PARENT_MEMBER_ID, RESOURCE_LIST_MEMBER_ID, and SET_OF_BOOKS_ID. Because this composite key resolves relationships among projects, tasks, budget versions, resources, and accounting contexts rather than describing an immutable entity, the ETRM heuristic Data Vault classification is best read as a link. Treating the table as a link suggests it connects hubs representing project, task, budget version, resource list member, and set of books, with the balance amounts and period measures carried as link-level attributes.

Key Information Stored

Each row represents a balance snapshot for a specific combination of project, task, period, budget version, and resource. The most significant columns are:

• PROJECT_ID – Foreign key to PA_PROJECTS_ALL identifying the project whose balance is stored.
• TASK_ID – Foreign key to PA_TASKS identifying the task within the project.
• TOP_TASK_ID – Foreign key to PA_TOP_TASKS_IT identifying the top-level task for hierarchical rollup.
• BUDGET_VERSION_ID – Foreign key to PA_BUDGET_VERSIONS indicating the budget version associated with the balance.
• PBN_BUDGET_VERSION_ID – Additional budget version reference, also linked to PA_BUDGET_VERSIONS, used for baseline comparison.
• RESOURCE_LIST_MEMBER_ID – Foreign key to PA_RESOURCE_LIST_MEMBERS identifying the resource (for example, labor or expenditure category).
• SET_OF_BOOKS_ID – Accounting set of books under which the balances are recorded.
• BALANCE_TYPE – Classifies the row as actual, budget, or encumbrance balance.
• PERIOD_NAME – Accounting period to which the balance belongs.
• START_DATE / END_DATE – Effective date range for the balance record.
• ACTUAL_PERIOD_TO_DATE – Period-to-date actual amount.
• BUDGET_PERIOD_TO_DATE – Period-to-date budget amount.
• ENCUMB_PERIOD_TO_DATE – Period-to-date encumbrance amount.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE – Concurrent program context that created or last updated the row.

The unique index PA_BC_BALANCES_U1 provides the business-key candidate; the table has no separately documented surrogate primary key column exposed as a single attribute, so the composite unique key effectively serves that role.

Common Use Cases and Queries

Typical usage includes budget-versus-actual reports, period-close variance analysis, and encumbrance tracking. A representative query retrieves balances for a given project and budget version:

• SELECT project_id, task_id, period_name, balance_type, actual_period_to_date, budget_period_to_date, encumb_period_to_date FROM pa_bc_balances WHERE project_id = :project_id AND budget_version_id = :budget_version_id ORDER BY period_name;
• Aggregating by top task for hierarchical rollups: joining on TOP_TASK_ID to summarize actuals across child tasks.
• Comparing budget and actual PTD amounts grouped by BALANCE_TYPE and PERIOD_NAME for variance reporting.
• Extracting encumbrance balances by set of books for commitment reporting.

Related Objects

The table integrates with core Projects entities through documented foreign keys:

• PA_PROJECTS_ALL – joined via PROJECT_ID and PPL_PROJECT_ID.
• PA_TASKS – joined via TASK_ID and PTK_TASK_ID.
• PA_BUDGET_VERSIONS – joined via BUDGET_VERSION_ID and PBN_BUDGET_VERSION_ID.
• PA_RESOURCE_LIST_MEMBERS – joined via RESOURCE_LIST_MEMBER_ID.
• PA_TOP_TASKS_IT – joined via TOP_TASK_ID.
• SET_OF_BOOKS reference – joined via SET_OF_BOOKS_ID.

These relationships make PA_BC_BALANCES central to project cost and budget reporting, and it is commonly accessed alongside PA_BUDGET_VERSIONS and PA_PROJECTS_ALL in project performance extracts and Oracle Business Intelligence reporting layers.