Results for “psb_defaults_u2”

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

Overview

PSB.PSB_DEFAULTS is a transactional configuration table in the Oracle E-Business Suite PSB (Public Sector Budgeting / Position Control) schema. It stores the position default rules that supply missing information when position data is extracted from Human Resource Management Systems (HRMS). Whenever a new position is created, these default rules are consulted to populate default position assignments automatically, ensuring that incomplete source data does not result in positions lacking required attributes.

Default rules are assigned to position sets rather than to individual positions. Any position whose attributes match the criteria defined for a given position set inherits the corresponding default rule, allowing administrators to apply consistent defaults across large groups of positions without manual maintenance. The table also participates in FTE allocation rule creation, as indicated by the ENTITY_ID column, which references the allocation rule created for FTE allocation purposes.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. This suggests that DEFAULT_RULE_ID functions as a durable business key, with the surrounding descriptive and status columns behaving like satellite attributes. This classification is a modeling suggestion only and should be validated against the wider PSB schema before being adopted in any data warehouse design.

Key Information Stored

The table contains thirteen documented columns. The most significant are summarized below, distinguishing the surrogate primary key from the business-key candidates identified by the unique indexes.

• DEFAULT_RULE_ID (NUMBER) — The unique identifier for a position default rule and the table's primary key (PSB_DEFAULTS_PK). It is also the single-column unique index PSB_DEFAULTS_U1.
• NAME (VARCHAR2(30)) — The descriptive name of the default rule. Together with DATA_EXTRACT_ID it forms the composite unique index PSB_DEFAULTS_U2, making the pair a business-key candidate.
• DATA_EXTRACT_ID (NUMBER(15)) — The data extract to which the rule belongs. It limits the rule definition to elements belonging to that extract and is the second component of PSB_DEFAULTS_U2.
• GLOBAL_DEFAULT_FLAG (VARCHAR2) — Indicates whether the rule is a global default, applying broadly rather than being scoped to a specific extract.
• PRIORITY (NUMBER) — The processing priority for non-global default rules, used to resolve conflicts when multiple rules apply to the same position.
• BUSINESS_GROUP_ID (NUMBER(15)) — The business group (HR operating unit) unique identifier, supporting multi-organization partitioning.
• ENTITY_ID (NUMBER(15)) — The unique identifier for the allocation rule created for FTE allocation.
• OVERWRITE (VARCHAR2) — Distinguishes default rules that overwrite existing position values from those that do not, controlling whether the rule can replace populated attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who columns providing audit and concurrency information.

Common Use Cases and Queries

Typical scenarios include auditing which default rules are configured, identifying global versus extract-scoped rules, resolving precedence between competing rules through PRIORITY, and tracing how FTE allocation rules are linked through ENTITY_ID.

The canonical query pattern is a simple projection of the rule identity and configuration columns:

• SELECT DEFAULT_RULE_ID, NAME, GLOBAL_DEFAULT_FLAG, DATA_EXTRACT_ID, BUSINESS_GROUP_ID, PRIORITY FROM PSB.PSB_DEFAULTS;
• Filtering for global rules: WHERE GLOBAL_DEFAULT_FLAG = 'Y' — useful when auditing organization-wide defaults.
• Filtering by extract: WHERE DATA_EXTRACT_ID = :extract_id ORDER BY PRIORITY — determines rule precedence for a specific extract.
• Filtering by business group: WHERE BUSINESS_GROUP_ID = :bg_id — confines results to a single HR operating unit.
• Checking overwrite behavior: WHERE OVERWRITE = 'Y' — identifies rules empowered to replace existing position attributes.

Reporting use cases include a rule inventory report, an extract dependency report, and a precedence report that surfaces conflicting rules assigned to the same position set criteria.

Related Objects

PSB_DEFAULTS sits within a hub-like position in the PSB schema. It references PSB_DATA_EXTRACTS through DATA_EXTRACT_ID, and several dependent tables reference its primary key:

• PSB_DATA_EXTRACTS — Referenced by PSB_DEFAULTS.DATA_EXTRACT_ID; defines the extract to which rules belong.
• PSB_DEFAULT_ACCOUNT_DISTRS — References PSB_DEFAULTS.DEFAULT_RULE_ID; holds default account distributions associated with a rule.
• PSB_DEFAULT_ASSIGNMENTS — References PSB_DEFAULTS.DEFAULT_RULE_ID; holds the default position assignments applied by a rule.
• PSB_SET_RELATIONS — References PSB_DEFAULTS.DEFAULT_RULE_ID; links default rules to the position sets whose criteria trigger them.

These relationships make PSB_DEFAULTS the anchor for tracing how position defaults flow from extract definition through set assignment to final account distribution and position assignment.