Results for “psb_defaults”

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

Overview

PSB_DEFAULTS is a transactional configuration table owned by the PSB schema that stores position default rules for Oracle EBS Public Sector Budgeting (PSB). Each row defines a reusable rule that governs how budget positions, assignments, and account distributions are defaulted when budget data is generated or maintained. In the ETRM 12.1.1 physical schema, the table contains 13 documented columns and is validated as a base table in the PSB product.

The table functions as the header or rule container for the defaulting framework. Rules defined here are referenced by child tables that supply the detailed account distribution, assignment, and set relationships associated with each rule. Because PSB_DEFAULTS is referenced by multiple downstream tables and itself holds a foreign key to PSB_DATA_EXTRACTS, the mined relationship structure suggests a hub-leaning classification in a Data Vault model — that is, it behaves primarily as a business-key-bearing hub with dependent satellites and links, rather than as a pure transaction satellite.

Key Information Stored

The surrogate primary key of the table is DEFAULT_RULE_ID, enforced by the PSB_DEFAULTS_PK constraint. Two unique indexes establish business-key candidates: PSB_DEFAULTS_U1 on DEFAULT_RULE_ID, and PSB_DEFAULTS_U2 on the composite of DATA_EXTRACT_ID and NAME, which enforces uniqueness of a rule name within a given data extract.

• DEFAULT_RULE_ID — surrogate primary key; the identifier used by all child tables and foreign keys.
• NAME — the user-visible name of the default rule, unique per data extract.
• DATA_EXTRACT_ID — foreign key to PSB_DATA_EXTRACTS; ties the rule to a specific budget data extract.
• BUSINESS_GROUP_ID — multi-tenant partition identifying the business group that owns the rule.
• GLOBAL_DEFAULT_FLAG — indicates whether the rule applies globally or only within its extract scope.
• PRIORITY — ordering value that determines which default rule is applied when multiple rules match.
• ENTITY_ID — the organizational entity to which the default rule applies.
• OVERWRITE — controls whether the rule overwrites existing values or only fills blanks.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard EBS audit columns.

Common Use Cases and Queries

Typical queries retrieve the default rules applicable to a given extract or business group, often filtered by priority and the global flag. A common pattern is to join PSB_DEFAULTS to PSB_DATA_EXTRACTS to resolve extract context, or to the child tables PSB_DEFAULT_ACCOUNT_DISTRS, PSB_DEFAULT_ASSIGNMENTS, and PSB_SET_RELATIONS to reconcile a rule with its detail lines.

• Listing active rules for an extract: SELECT DEFAULT_RULE_ID, NAME, PRIORITY, OVERWRITE FROM PSB_DEFAULTS WHERE DATA_EXTRACT_ID = :extract_id ORDER BY PRIORITY;
• Identifying global rules: SELECT DEFAULT_RULE_ID, NAME FROM PSB_DEFAULTS WHERE GLOBAL_DEFAULT_FLAG = 'Y' AND BUSINESS_GROUP_ID = :bg_id;
• Resolving rule detail by joining to child distribution rows on DEFAULT_RULE_ID.
• Auditing changes by scanning LAST_UPDATE_DATE for rules modified within a period.

Reporting usage centers on documenting which defaults are in force for a budget cycle and validating that priority ordering does not produce conflicting assignments.

Related Objects

• PSB_DEFAULT_ACCOUNT_DISTRS — references PSB_DEFAULTS via DEFAULT_RULE_ID; holds account distribution details per rule.
• PSB_DEFAULT_ASSIGNMENTS — references PSB_DEFAULTS via DEFAULT_RULE_ID; holds assignment-level default details.
• PSB_SET_RELATIONS — references PSB_DEFAULTS via DEFAULT_RULE_ID; defines set relationships tied to a default rule.
• PSB_DATA_EXTRACTS — parent table referenced by PSB_DEFAULTS.DATA_EXTRACT_ID.

Together these objects form the PSB defaulting subsystem, with PSB_DEFAULTS acting as the rule header consumed by its three dependent detail tables.