Search Results psb_entity_assignment_u1

Overview

The PSB.PSB_ENTITY_ASSIGNMENT table is a core data structure within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, specifically for the Public Sector Budgeting (PSB) module. Its primary function is to manage the assignment of entities—which can represent parameters, constraints, or allocation rules—to logical groupings known as entity sets. This design facilitates the reuse of business rules across different budgeting scenarios while allowing for context-specific configurations, such as varying processing priorities or severity levels. The table is essential for defining and controlling the behavior of budgeting calculations and validations, acting as a junction between individual rule definitions and the sets in which they are applied.

Key Information Stored

The table's columns store the critical relationships and attributes for each assignment. The ENTITY_SET_ID and ENTITY_ID form the core foreign key relationship, identifying the specific set and the entity assigned to it. The PRIORITY column dictates the processing order for entities within a Parameter Set, while the SEVERITY_LEVEL defines the enforcement strictness for entities within a Constraint Set. Temporal validity is managed via EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, enabling rule assignments to be activated or retired over time. Standard Oracle EBS "Who" columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) complete the record for auditing purposes.

Common Use Cases and Queries

A primary use case is analyzing the composition and hierarchy of parameter or constraint sets for budgetary configuration or troubleshooting. Developers and functional analysts frequently query this table to understand which rules are active for a given set and their respective priorities. A common query pattern involves joining to the underlying entity master tables (not listed in the provided metadata) to get descriptive names. For example, to retrieve all active assignments for a specific entity set, one might use:

• SELECT ea.* FROM psb.psb_entity_assignment ea WHERE ea.entity_set_id = :p_set_id AND SYSDATE BETWEEN NVL(ea.effective_start_date, SYSDATE) AND NVL(ea.effective_end_date, SYSDATE) ORDER BY ea.priority;

Reporting often focuses on validating configuration, such as identifying sets where an entity is assigned multiple times with overlapping effective dates, which could indicate a configuration error.

Related Objects

Based on the provided metadata, the table's structure indicates clear relationships with other PSB objects, though explicit foreign key dependencies are not listed. The unique index PSB_ENTITY_ASSIGNMENT_U1 on (ENTITY_ID, ENTITY_SET_ID) suggests these columns are foreign keys referencing primary keys in master entity and entity set tables, likely named PSB_ENTITY and PSB_ENTITY_SET or similar. The non-unique index PSB_ENTITY_ASSIGNMENT_N1 on (ENTITY_SET_ID, EFFECTIVE_START_DATE) supports performance for queries filtering by set. This table is a central link in the PSB rule management architecture and is expected to be referenced by the engine that processes budgeting calculations and constraint validations.