Search Results default_rule_id




Overview
Explore in AI Chat

Overview

The PSB.PSB_DEFAULTS table is a core repository for position default rule definitions within Oracle E-Business Suite's Project Suite, specifically for the Project Suite Base module. Its primary role is to automate and standardize the population of position data during the extraction process from external Human Resource Management Systems (HRMS). When a new position is created, the system applies these stored default rules to supply essential default position assignments and attributes that may be missing from the source data. This ensures data consistency and reduces manual entry. The rules are not universally applied but are intelligently assigned based on position sets, meaning a position inherits a default rule only if its attributes match the specific criteria of a rule's associated position set.

Key Information Stored

The table's structure is designed to define, prioritize, and manage the application of these rules. The most critical columns include:

  • DEFAULT_RULE_ID (NUMBER): The primary key and unique identifier for each default rule.
  • NAME (VARCHAR2): The descriptive name of the default rule for identification.
  • GLOBAL_DEFAULT_FLAG (VARCHAR2): A flag indicating whether the rule applies globally or is restricted.
  • DATA_EXTRACT_ID (NUMBER): Links the rule to a specific data extract definition, scoping which elements it applies to.
  • BUSINESS_GROUP_ID (NUMBER): Associates the rule with a specific business group for security and data partitioning.
  • PRIORITY (NUMBER): Determines the processing order for non-global rules when multiple rules could apply.
  • OVERWRITE (VARCHAR2): A crucial flag that defines whether the rule has the power to overwrite existing data or only fill in blanks.

The table also contains standard Oracle EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

A primary use case is troubleshooting or reporting on the configuration of position defaulting. Administrators often need to understand which rules are in effect for a given business group or extract. A common query pattern involves joining with related setup tables to see a complete rule definition. For example, to list all default rules for a specific business group, ordered by priority:

SELECT DEFAULT_RULE_ID, NAME, GLOBAL_DEFAULT_FLAG, PRIORITY, OVERWRITE FROM PSB.PSB_DEFAULTS WHERE BUSINESS_GROUP_ID = :p_bg_id ORDER BY PRIORITY;

Another critical scenario is validating rule uniqueness and relationships before a data extract process. Since the DEFAULT_RULE_ID is referenced by several child tables, queries often join to PSB_DEFAULT_ASSIGNMENTS or PSB_SET_RELATIONS to understand what a specific rule is assigned to. When users search for a specific default_rule_id, they are typically investigating errors in position creation, auditing rule usage, or diagnosing why a particular default assignment was (or was not) applied during HRMS integration.

Related Objects

The PSB_DEFAULTS table sits at the center of the default rule configuration. Its primary key is enforced by the index PSB_DEFAULTS_U1. It has defined foreign key relationships where its DEFAULT_RULE_ID column is referenced as a parent, including:

  • PSB_DEFAULT_ACCOUNT_DISTRS: Links default rules to specific accounting distributions.
  • PSB_DEFAULT_ASSIGNMENTS: Stores the actual default assignment details (e.g., job, organization) defined by the rule.
  • PSB_SET_RELATIONS: Connects the default rule to position sets, determining which positions inherit the rule based on attribute matching.

These relationships are essential for a complete understanding of a rule's configuration. The UNIQUE index on DATA_EXTRACT_ID (PSB_DEFAULTS_U2) also indicates a tight coupling with the data extract definition entity.