Search Results psb_revision_rule_sets_v

Overview

PSB_REVISION_RULE_SETS_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID. It belongs to the PSB (Public Sector Budgeting) product family, which supports budget formulation, revision, and submission workflows for public sector and government organizations. The view presents budget revision rule sets — configurations that determine which budget entities are eligible for revision and the constraints applied during the revision process. Its defining characteristic is a hard-coded filter that restricts the underlying data to rows whose ENTITY_TYPE equals 'BRR', isolating Budget Revision Rule definitions from other entity types sharing the same physical table.

From a reporting and integration perspective, the view functions as a purpose-built interface over a generic entity-set table. Rather than requiring consuming applications and reports to know the ENTITY_TYPE discriminator, the view exposes only revision rule sets. Typical consumers include budget revision entry forms, validation logic, concurrent programs that apply revision rules, and custom reports or extracts that need to enumerate the rule sets available for a given budget group and ledger.

Underlying Base Objects

The view is defined over the single base table PSB_ENTITY_SET. The view definition selects ROWID along with a defined column list and applies the predicate ENTITY_TYPE = 'BRR'. This confirms that PSB_ENTITY_SET stores multiple logical entity categories, with the ENTITY_TYPE column acting as a discriminator, and that revision rule sets occupy one such category.

The ETRM metadata documents no additional referenced base objects; the view is a straightforward projection and filter rather than a join-based construct. Consequently, all columns returned by the view originate from PSB_ENTITY_SET, and no aggregation, union, or outer join behavior applies. There is no DDL or INSTEAD OF trigger documented for this object, so the view is read-only and must be treated as such in custom code.

Key Columns

The column list in the view definition and the documented column headings differ slightly in naming, and both are relevant to consumers. Notable attributes include:

• ROW_ID / ROWID — The physical row identifier of the underlying PSB_ENTITY_SET row; useful for direct row access, though unstable across table reorganization.
• RULE_SET_ID / ENTITY_SET_ID — The primary identifier of the revision rule set. The view definition aliases ENTITY_SET_ID, while the documented column list presents RULE_SET_ID; the two refer to the same logical key.
• NAME and DESCRIPTION — The user-facing name and descriptive text of the rule set, as defined during setup.
• CONSTRAINT_THRESHOLD — The threshold value governing the constraint applied by the rule set, typically used in revision amount or percentage validation.
• BUDGET_GROUP_ID — Identifies the budget group to which the rule set belongs, tying the rule set to a specific budgeting configuration.
• SET_OF_BOOKS_ID — The ledger context for the rule set, enabling multi-ledger installations to keep rule sets separate.
• ENABLE_FLAG — Indicates whether the rule set is active and therefore applicable during revision processing.
• ATTRIBUTE1 through ATTRIBUTE15 (descriptive flexfield context) — The standard DFF columns (ATTRIBUTE1–ATTRIBUTE10 and CONTEXT) supporting installation-specific extensions.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard who-column auditing.

Common Use Cases and Queries

The most frequent use is listing enabled rule sets for a budget group and ledger before applying revision processing. A representative query is:

SELECT rule_set_id, name, description, constraint_threshold, enable_flag FROM apps.psb_revision_rule_sets_v WHERE enable_flag = 'Y' AND budget_group_id = :p_budget_group_id AND set_of_books_id = :p_set_of_books_id;

Another common pattern is a validation lookup to confirm that a supplied rule set identifier exists and is active, or to retrieve constraint thresholds for downstream calculations. Reporting extracts often join the view to budget group and ledger reference views to produce a readable listing of rule sets by organization and period. Because the view is read-only and unfiltered by ledger security, custom queries should always constrain by SET_OF_BOOKS_ID and BUDGET_GROUP_ID where those dimensions are meaningful, and should avoid relying on ROW_ID for persistent references, preferring RULE_SET_ID instead.