Search Results psb_default_assignments




Overview
Explore in AI Chat

Overview

The PSB_DEFAULT_ASSIGNMENTS table is a data object within the Oracle E-Business Suite (EBS) Public Sector Budgeting (PSB) module. As indicated by its description, "Position default assignments," this table functioned as a junction or assignment table, linking specific budgeting rules (defaults) to individual pay elements for positions. Its primary role was to define and store the default budgetary assignments that should be applied to positions, a core configuration step in the automated budget calculation and allocation processes of the PSB module. It is critical to note that the PSB module is marked as obsolete in the provided metadata, and the documentation explicitly states this specific table is "Not implemented in this database," indicating it may not be present in all EBS 12.1.1 or 12.2.2 instances, particularly those where PSB was not implemented or has been decommissioned.

Key Information Stored

The table's structure centers on creating unique assignment records that associate a default rule with a pay element. The primary key, DEFAULT_ASSIGNMENT_ID, ensures each assignment record is unique. The two critical foreign key columns define the relationship: DEFAULT_RULE_ID links to a specific budgeting rule defined in the PSB_DEFAULTS table, and PAY_ELEMENT_ID links to a specific compensation component defined in the PSB_PAY_ELEMENTS table. Together, these columns form the core data model, enabling the system to determine which default budgetary treatment (e.g., a specific GL account, funding source, or calculation basis) should be applied to a particular type of pay for a position.

Common Use Cases and Queries

In an active PSB implementation, this table would be central to configuration and validation reports. Administrators would query it to audit which pay elements were governed by which default rules. A common reporting use case would be to list all assignments for a given default rule to understand its scope of application. A sample SQL pattern for such a report would involve joining to the related tables for descriptive information:

  • SELECT da.DEFAULT_ASSIGNMENT_ID, d.RULE_NAME, pe.ELEMENT_NAME FROM PSB_DEFAULT_ASSIGNMENTS da, PSB_DEFAULTS d, PSB_PAY_ELEMENTS pe WHERE da.DEFAULT_RULE_ID = d.DEFAULT_RULE_ID AND da.PAY_ELEMENT_ID = pe.PAY_ELEMENT_ID ORDER BY d.RULE_NAME;

Another critical use case would be during the budget preparation cycle, where the system would reference these assignments to automatically populate budget worksheets or generate journal line rules for position-based expenses.

Related Objects

The PSB_DEFAULT_ASSIGNMENTS table has documented foreign key relationships with two core PSB tables, forming a key part of the module's data model.

  • PSB_DEFAULTS: This table is referenced via the column PSB_DEFAULT_ASSIGNMENTS.DEFAULT_RULE_ID. It stores the master definition of the default budgeting rules themselves.
  • PSB_PAY_ELEMENTS: This table is referenced via the column PSB_DEFAULT_ASSIGNMENTS.PAY_ELEMENT_ID. It contains the list of compensable elements (e.g., salary, allowances, bonuses) that can be assigned a default rule.

The table's primary key, PSB_DEFAULT_ASSIGNMENTS_PK, is defined on the DEFAULT_ASSIGNMENT_ID column, ensuring referential integrity for any potential child tables or internal processing logic that might reference a specific assignment record.