Search Results psb_budget_workflow_rules

Overview

The PSB_BUDGET_WORKFLOW_RULES table is a core data object within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as the master repository for defining and storing the rules that govern the automated workflow processes for budget submissions, reviews, and approvals. This table is fundamental to configuring the sequence of stages a budget must pass through, specifying which organizational groups are responsible for review or approval at each stage, and defining conditions for routing or overriding the standard workflow path. Its role is to provide the structural logic that automates and enforces budgetary control and compliance within the PSB application.

Key Information Stored

The table's primary key is BUDGET_WORKFLOW_RULE_ID, a unique identifier for each rule definition. Critical foreign key columns establish relationships with other master PSB tables, defining the rule's parameters. The BUDGET_GROUP_ID links to the PSB_BUDGET_GROUPS table, identifying the budget group to which the rule applies. The STAGE_ID and OVERRIDE_STAGE_ID columns reference PSB_BUDGET_STAGES, defining the current workflow stage and a potential override destination, respectively. The REVIEW_BUDGET_GROUP_ID (also referencing PSB_BUDGET_GROUPS) specifies the group responsible for review at that stage. The DATA_EXTRACT_ID links to PSB_DATA_EXTRACTS, likely associating a specific data template or view with the workflow rule for reporting or review purposes.

Common Use Cases and Queries

A primary use case is auditing and analyzing the configured budget approval hierarchy. Administrators may run queries to list all workflow rules for a specific budget group or to trace the complete stage progression. For instance, a query to retrieve the workflow sequence for a budget group would join PSB_BUDGET_WORKFLOW_RULES with PSB_BUDGET_STAGES. Another common scenario involves troubleshooting workflow routing; a support query might examine rules where an OVERRIDE_STAGE_ID is populated to understand exception paths. Reporting on review responsibilities often requires joining this table with PSB_BUDGET_GROUPS (via REVIEW_BUDGET_GROUP_ID) to list all groups tasked with budget reviews at various stages.

• Sample SQL: SELECT rule.budget_workflow_rule_id, bg.name budget_group, stage.name stage, review_bg.name review_group FROM psb_budget_workflow_rules rule, psb_budget_groups bg, psb_budget_stages stage, psb_budget_groups review_bg WHERE rule.budget_group_id = bg.budget_group_id AND rule.stage_id = stage.stage_id AND rule.review_budget_group_id = review_bg.budget_group_id ORDER BY bg.name, stage.sequence_num;

Related Objects

PSB_BUDGET_WORKFLOW_RULES is centrally connected to several key PSB tables. It is a parent table to PSB_SET_RELATIONS and PSB_WF_REVIEW_GROUPS, which store additional, rule-dependent configuration details. As indicated by its foreign keys, it is a child table that draws its valid values from critical master tables: PSB_BUDGET_GROUPS (twice, for both the primary and review groups), PSB_BUDGET_STAGES (twice, for current and override stages), and PSB_DATA_EXTRACTS. This network of relationships positions PSB_BUDGET_WORKFLOW_RULES as a pivotal junction table that orchestrates the interaction between budget entities, organizational groups, and process stages within the Public Sector Budgeting workflow engine.