Results for “psb_set_relations_u1”

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

Overview

PSB.PSB_SET_RELATIONS is a transactional mapping table within the Oracle E-Business Suite Grants, Budgeting, and Position Control product family (PSB schema). It stores the assignment of account sets or position sets to various consuming entities, including budget groups, allocation rules, default rules, parameters, constraints, budget workflow rules, and General Ledger budgets. Once an account set or position set is defined, it may be shared across multiple entities; each individual usage of a set by an entity is captured as a discrete row in this table. This design allows a single set definition to be reused without duplication, while PSB_SET_RELATIONS records precisely which entity consumes which set and under what effective-date range.

The table occupies a central position in the PSB set-sharing model, acting as the junction between set definitions (account/position sets) and the functional objects that apply them during budget creation, allocation, defaulting, and position control processing. The physical schema is stored in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and all nine documented indexes reside in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the heuristic classification of PSB_SET_RELATIONS is a link. This is consistent with its physical structure: it contains no descriptive attributes of its own beyond administrative audit columns and effective dates, and it exists primarily to resolve many-to-many associations between set definitions and the entities that reference them.

Key Information Stored

• SET_RELATION_ID — The surrogate primary key (NUMBER(15)) and the column behind the unique index PSB_SET_RELATIONS_U1. It is the sole documented business-key candidate and uniquely identifies each set-to-entity relation.
• ACCOUNT_POSITION_SET_ID — The account or position set being shared. This is the anchor foreign key linking the relation to PSB_ACCOUNT_POSITION_SETS, and it is indexed by PSB_SET_RELATIONS_N6.
• ALLOCATION_RULE_ID — References PSB_ENTITY and identifies the allocation rule that consumes the set. Indexed by PSB_SET_RELATIONS_N4.
• BUDGET_GROUP_ID — References PSB_BUDGET_GROUPS, identifying the budget group to which the set is assigned. Indexed by PSB_SET_RELATIONS_N3.
• BUDGET_WORKFLOW_RULE_ID — References PSB_BUDGET_WORKFLOW_RULES, supporting workflow-driven budget processing. Indexed by PSB_SET_RELATIONS_N5.
• CONSTRAINT_ID — References PSB_ENTITY, identifying the constraint that applies the set. Indexed by PSB_SET_RELATIONS_N2.
• DEFAULT_RULE_ID — References PSB_DEFAULTS (position default rules). Indexed by PSB_SET_RELATIONS_N7.
• PARAMETER_ID — References PSB_ENTITY, identifying the parameter context for the relation. Indexed by PSB_SET_RELATIONS_N1.
• POSITION_SET_GROUP_ID — References PSB_ELEMENT_POS_SET_GROUPS, grouping position sets for the relation. Indexed by PSB_SET_RELATIONS_N8.
• GL_BUDGET_ID — References PSB_GL_BUDGETS, tying the set to an Oracle General Ledger budget. Indexed by PSB_SET_RELATIONS_N9.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Define the date range during which the relation is active, enabling historical tracking of set assignments.
• APPLY_BALANCE_FLAG — A control flag indicating whether balance application logic applies to the relation.
• RULE_ID — A secondary rule reference used alongside the primary entity identifiers.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO-column traceability across all nineteen documented columns.

Common Use Cases and Queries

A frequent requirement is determining which sets are attached to a given budget group. The query joins PSB_SET_RELATIONS to PSB_BUDGET_GROUPS through BUDGET_GROUP_ID and to PSB_ACCOUNT_POSITION_SETS through ACCOUNT_POSITION_SET_ID, filtering on the effective-date range so that only currently active assignments are returned.

Another common pattern reverses the perspective to perform impact analysis: identifying every entity that references a particular set before it is modified or deleted. Because the table carries eight distinct non-unique indexes on the entity reference columns, such lookups perform efficiently across PARAMETER_ID, CONSTRAINT_ID, ALLOCATION_RULE_ID, DEFAULT_RULE_ID, POSITION_SET_GROUP_ID, GL_BUDGET_ID, BUDGET_GROUP_ID, and BUDGET_WORKFLOW_RULE_ID.

Reporting queries typically aggregate set usage by entity type to reveal how broadly a set has been deployed, or join to PSB_DEFAULTS and PSB_GL_BUDGETS to reconcile budget defaulting behavior. Point-in-time reporting is supported by bracketing SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

Related Objects

• PSB_ACCOUNT_POSITION_SETS — joined on ACCOUNT_POSITION_SET_ID; the master set definition being shared.
• PSB_BUDGET_GROUPS — joined on BUDGET_GROUP_ID; budget group consumers of sets.
• PSB_BUDGET_WORKFLOW_RULES — joined on BUDGET_WORKFLOW_RULE_ID; workflow rule consumers.
• PSB_DEFAULTS — joined on DEFAULT_RULE_ID; position default rule definitions.
• PSB_ENTITY — referenced by PARAMETER_ID, CONSTRAINT_ID, and ALLOCATION_RULE_ID; the shared entity registry.
• PSB_ELEMENT_POS_SET_GROUPS — joined on POSITION_SET_GROUP_ID; position set grouping structure.
• PSB_GL_BUDGETS — joined on GL_BUDGET_ID; the GL budget association.