Search Results psb_set_relations_pk

Overview

The PSB_SET_RELATIONS table is a core data object within the Oracle E-Business Suite Public Sector Budgeting (PSB) module, versions 12.1.1 and 12.2.2. As indicated by its description, its primary role is to manage the assignment of predefined account sets or position sets to various controlling entities within the budgeting system. This table functions as a central junction, linking sets of accounts or positions to rules, groups, and definitions that govern budget preparation, workflow, and control. It is critical for enforcing budgetary policies by associating specific financial or position structures with budgeting processes. Notably, the PSB module is marked as obsolete in the provided documentation, indicating it is a legacy component that may not be present in newer implementations or cloud offerings.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which reveal the nature of the relationships it stores. The primary key, SET_RELATION_ID, uniquely identifies each assignment record. The foreign key columns are the most critical data points, as they store the IDs that link to other major PSB entities. Key foreign key columns include ACCOUNT_POSITION_SET_ID, which references the specific set of accounts or positions being assigned. Other essential columns like BUDGET_GROUP_ID, BUDGET_WORKFLOW_RULE_ID, DEFAULT_RULE_ID, and CONSTRAINT_ID define the target entities to which the set is linked, such as budget groups, workflow rules, defaulting rules, and budgetary constraints, respectively. The presence of GL_BUDGET_ID also indicates a direct relationship with General Ledger budget definitions.

Common Use Cases and Queries

A primary use case is auditing and reporting on how budgetary control rules are configured. For instance, an administrator may need to identify all account sets assigned to a specific budget group or workflow rule to validate setup. A typical query would join PSB_SET_RELATIONS with PSB_ACCOUNT_POSITION_SETS and PSB_BUDGET_GROUPS. Another common scenario is troubleshooting budget preparation issues by verifying the sets of accounts available to a user or process based on linked defaults or constraints. Given the module's obsolete status, queries are often for historical analysis, data migration, or supporting legacy processes. A sample query pattern is:

• SELECT sgr.set_relation_id, aps.name AS set_name, bg.name AS budget_group_name
• FROM psb_set_relations sgr,
• psb_account_position_sets aps,
• psb_budget_groups bg
• WHERE sgr.account_position_set_id = aps.account_position_set_id
• AND sgr.budget_group_id = bg.budget_group_id;

Related Objects

PSB_SET_RELATIONS is a hub table with dependencies to numerous other PSB entities, as detailed by its foreign keys. Key related tables include PSB_ACCOUNT_POSITION_SETS, which defines the actual collections of accounts or positions being assigned. PSB_BUDGET_GROUPS, PSB_BUDGET_WORKFLOW_RULES, and PSB_DEFAULTS are major control tables that use these set assignments to govern budget behavior. The multiple foreign keys to PSB_ENTITY (for PARAMETER_ID, CONSTRAINT_ID, and ALLOCATION_RULE_ID) highlight its role in linking sets to various system parameters and rules. PSB_GL_BUDGETS represents the connection to the finalized budget in the General Ledger. The existence of a dedicated primary key constraint (PSB_SET_RELATIONS_PK) and the multiple foreign key constraints ensure referential integrity across this complex configuration data.