Search Results psb_position_pay_distributions

Overview

The PSB_POSITION_PAY_DISTRIBUTIONS table is a core data object within the Oracle E-Business Suite Public Sector Budgeting (PSB) module. It serves as the primary repository for defining and storing position cost distribution rules. In the context of government and public sector budgeting, positions are often funded from multiple sources, such as different grants, projects, or general ledger accounts. This table enables the systematic allocation of a single position's salary and associated costs across these various funding lines according to predefined percentages or amounts. Its role is critical for ensuring accurate budgetary planning, cost accounting, and compliance with funding restrictions in Oracle EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture the essential components of a distribution rule. The primary key, DISTRIBUTION_ID, uniquely identifies each distribution rule record. A critical foreign key is POSITION_ID, which links the distribution rule to a specific position defined in the PSB_POSITIONS table. Another significant foreign key is DATA_EXTRACT_ID, linking to the PSB_DATA_EXTRACTS table, which manages the batch or context of the imported or created data. While specific column details beyond the keys are not fully enumerated in the provided metadata, typical data stored would include the funding source identifier (such as a project ID, task ID, or account code), the distribution percentage or fixed amount, and effective date ranges to manage rule changes over time.

Common Use Cases and Queries

The primary use case is the creation and maintenance of multi-funded position budgets. Analysts define distribution rules to split a position's full-time equivalent (FTE) cost. Common reporting and validation queries include summarizing total budgeted salary by funding source or verifying that distribution percentages for a position sum to 100%. A typical SQL pattern to retrieve all distribution rules for a specific position would be:

• SELECT * FROM PSB.PSB_POSITION_PAY_DISTRIBUTIONS WHERE POSITION_ID = <position_id> ORDER BY DISTRIBUTION_ID;

Another common query joins with the PSB_POSITIONS table to report on position names alongside their funding splits:

• SELECT pos.POSITION_NAME, dist.* FROM PSB.PSB_POSITIONS pos, PSB.PSB_POSITION_PAY_DISTRIBUTIONS dist WHERE pos.POSITION_ID = dist.POSITION_ID;

Related Objects

PSB_POSITION_PAY_DISTRIBUTIONS has integral relationships with other key PSB tables. As documented, its two primary foreign key dependencies are:

• PSB_POSITIONS: The master table for position definitions. The relationship via POSITION_ID ensures every distribution rule is associated with a valid position.
• PSB_DATA_EXTRACTS: The table managing data extraction and staging processes. The relationship via DATA_EXTRACT_ID ties distribution rules to specific budget batches or data loads, providing auditability and process control.

Furthermore, this table is foundational for the PSB budgeting engine and is likely referenced by various internal APIs, budget calculation programs, and summary reporting views within the module to aggregate distributed costs.