Search Results psb_entity_set




Overview
Explore in AI Chat

Overview

The PSB_ENTITY_SET table is a core data object within the Oracle E-Business Suite (EBS) Public Sector Budgeting (PSB) module. As indicated by its description, this table serves as the central repository for definitions of rule sets, specifically parameters, constraints, and allocation rules. These rule sets are fundamental building blocks used to define and enforce complex budgeting policies, calculations, and workflows tailored for public sector financial management. The table's primary role is to store the master definition of each rule set, which can then be assigned to various budgeting entities or transactions via related assignment tables. It is critical to note that the PSB module is marked as "Obsolete" in the provided metadata, indicating it is a legacy component that may not be present in newer EBS implementations or cloud offerings.

Key Information Stored

While the full column list is not detailed in the provided excerpt, the structure centers on the unique identification and definition of a rule set. The primary key, ENTITY_SET_ID, is the unique numeric identifier for each rule set record. Based on the table's purpose, other columns would typically store descriptive and control attributes for the rule set. This likely includes fields such as a name (e.g., ENTITY_SET_NAME), a description, an effective date range (START_DATE, END_DATE), the type of rule set (e.g., parameter, constraint, allocation), status, and creation/modification audit information (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). The specific logic or formulas for the rules are typically stored in related child tables or configuration files, not within this header table.

Common Use Cases and Queries

A primary use case involves administrative setup and reporting on the available budgeting rule sets. System administrators would query this table to review all defined rule sets, while budget analysts might reference it to understand the rules applied to their budgets. Common SQL patterns include listing active rule sets or finding a specific set by name for assignment or troubleshooting. For example, a query to find all active constraint rule sets might resemble: SELECT entity_set_id, entity_set_name FROM psb_entity_set WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate) AND rule_set_type = 'CONSTRAINT';. Reporting often joins this table to assignment tables to show which rules are applied to specific funds, departments, or projects.

Related Objects

The PSB_ENTITY_SET table has a documented parent-child relationship with the PSB_ENTITY_ASSIGNMENT table, as defined by the foreign key. This is the primary relationship for applying rule sets to specific budgeting entities.

  • PSB_ENTITY_ASSIGNMENT: This child table references PSB_ENTITY_SET via the foreign key column ENTITY_SET_ID. It is used to assign a defined rule set from PSB_ENTITY_SET to a specific budgeting entity, such as a ledger, budget organization, or project.

Given its role as a definition table, PSB_ENTITY_SET would also logically relate to other PSB tables storing detailed rule components, such as parameter values or constraint formulas, though these relationships are not specified in the provided metadata.