Results for “psb_entity_set”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PSB_ENTITY_SET is a definition table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. The PSB module is documented as obsolete in release 12.1.1 and 12.2.2, and the table is explicitly recorded as "Not implemented in this database" in the ETRM reference data. Its documented purpose is to hold parameter, constraint, and allocation rule set definitions — in other words, it is the master configuration object that groups the entities against which budgeting parameters, constraints, and allocation rules are evaluated.

Because no 12.1.1 database implementation is recorded, PSB_ENTITY_SET should be treated as a legacy or archived metadata object. It retains research value for organizations that have upgraded from earlier EBS releases, because PSB configuration data may persist in a historical schema even after the module has been superseded by Oracle Public Sector Budgeting functionality delivered through other products.

Applying the heuristic Data Vault classification supplied in the metadata, PSB_ENTITY_SET is hub-leaning. It carries its own surrogate primary key and a natural business key, and it is referenced by a dependent child table, which is consistent with hub behavior rather than a pure link or satellite structure. This classification is a modeling suggestion, not an Oracle-documented attribute, and reflects only the mined foreign key topology.

Key Information Stored

The documented physical schema contains twenty-six columns, owned by the PSB schema in the 12.1.1 reference. The most significant columns are:

• ENTITY_SET_ID — surrogate primary key, defined by PSB_ENTITY_SET_PK and reinforced by unique index PSB_ENTITY_SET_U1. It is the value propagated to child tables.
• ENTITY_TYPE — the class or category of entity the set represents; together with NAME it forms the business-key candidate in unique index PSB_ENTITY_SET_U2.
• NAME — the user-facing identifier of the entity set; combined with ENTITY_TYPE for uniqueness.
• DESCRIPTION — free-text explanation of the set's purpose.
• BUDGET_GROUP_ID — foreign key to PSB_BUDGET_GROUPS, anchoring the set to a budgeting group.
• SET_OF_BOOKS_ID — the ledger context for which the set applies, maintaining multi-organization accounting separation.
• DATA_EXTRACT_ID — foreign key to PSB_DATA_EXTRACTS, linking the set to the source extraction definition.
• CONSTRAINT_THRESHOLD — the quantitative limit used when evaluating constraint rules.
• ENABLE_FLAG — controls whether the set is active for processing.
• EXECUTABLE_FROM_POSITION — governs the point in the budgeting flow from which the rule set may execute.
• ATTRIBUTE1 through ATTRIBUTE10 and CONTEXT — the standard Oracle descriptive flexfield columns, extending the table without schema change.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — the mandatory audit columns present on all Oracle EBS transactional and setup tables.

Distinguishing surrogate from business keys is important: ENTITY_SET_ID is the immutable internal identifier, while (NAME, ENTITY_TYPE) is the documented user-recognizable unique combination, making it the preferred key for lookups in reporting.

Common Use Cases and Queries

Typical usage centers on locating and auditing rule-set definitions. A basic active-set query follows the business key and enable flag:

SELECT entity_set_id, name, entity_type, description, constraint_threshold
FROM psb_entity_set
WHERE enable_flag = 'Y';

A context-enriched join resolves the owning budget group and ledger:

SELECT es.name, es.entity_type, bg.name budget_group, es.set_of_books_id
FROM psb_entity_set es, psb_budget_groups bg
WHERE es.budget_group_id = bg.budget_group_id;

A descendant query enumerates the entities assigned to each set:

SELECT ea.entity_set_id, ea.*
FROM psb_entity_assignment ea
WHERE ea.entity_set_id = :entity_set_id;

Reporting scenarios include reconciling legacy PSB configuration prior to decommissioning, tracing which extract feeds each rule set, and auditing whether constraint thresholds align with current budget policy. Because the table is flagged as not implemented, migration scripts should first verify existence — querying ALL_TABLES for table_name = 'PSB_ENTITY_SET' — before attempting data extraction.

Related Objects

The documented relationships cluster around a small set of parent and child objects:

• PSB_ENTITY_ASSIGNMENT — the sole documented child table. It references PSB_ENTITY_SET via ENTITY_SET_ID and holds the individual entity assignments belonging to each set.
• PSB_BUDGET_GROUPS — parent of PSB_ENTITY_SET through BUDGET_GROUP_ID; defines the budgeting group scope.
• PSB_DATA_EXTRACTS — parent through DATA_EXTRACT_ID; supplies the source data extraction associated with the set.
• PSB_ENTITY_SET_PK / PSB_ENTITY_SET_U1 / PSB_ENTITY_SET_U2 — the primary key and unique indexes enforcing identity and the (NAME, ENTITY_TYPE) business key.

No PL/SQL API or view layer is documented for this object in the supplied metadata. Any programmatic access should therefore be treated as direct SQL against the base table, with the caveat that the object is recorded as obsolete and not implemented in the release 12.1.1 or 12.2.2 schema.