Results for “global_default_flag”

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

Overview

PSBFV_DEFAULT_RULES is a read-only database view in the Oracle E-Business Suite Public Sector Budgeting (PSB) module. Public Sector Budgeting is an obsolete product in both EBS 12.1.1 and 12.2.2, but the underlying schema objects may still persist in databases that were upgraded from earlier releases where the module was active. The view presents a consolidated, denormalized result set that joins default budget rule definitions with their associated data extract definitions, allowing report authors, conversion scripts, and integration developers to resolve a rule to the extract it references without writing the join manually. When users or developers search for the column DATA_EXTRACT_NAME, they are typically attempting to trace which data extract drives a given default rule, and this view supplies exactly that mapping. Because the view is declared WITH READ ONLY, it is strictly a query surface; no DML is permitted through it.

Underlying Base Objects

The view is defined over two documented base tables joined on the DATA_EXTRACT_ID column. The first is PSB_DEFAULTS, aliased PD in the view definition, which stores the default rule header records including name, priority, global default flag, and audit columns. The second is PSB_DATA_EXTRACTS, aliased PDE, which holds the extract definitions referenced by those rules. The join is an equi-join on PD.DATA_EXTRACT_ID = PDE.DATA_EXTRACT_ID, meaning any default rule whose DATA_EXTRACT_ID does not resolve to a matching row in PSB_DATA_EXTRACTS will be excluded from the result set. ETRM metadata notes that the view is not implemented in some databases, reflecting the obsolete status of the PSB module; therefore, the PSB_DEFAULTS and PSB_DATA_EXTRACTS tables may not exist in a given instance, and the view should be treated as conditionally available when writing cross-environment scripts.

Key Columns

• NAME — the descriptive name of the default rule, taken from PSB_DEFAULTS.
• GLOBAL_DEFAULT_FLAG — indicates whether the rule applies globally across the budgeting organization or is restricted in scope.
• PRIORITY — the precedence value used to resolve conflicts when multiple default rules match the same budgeting condition; lower or higher values determine which rule wins depending on the original application logic.
• DATA_EXTRACT_NAME — the human-readable name of the data extract sourced from PSB_DATA_EXTRACTS; this is the column most frequently searched by report developers.
• DEFAULT_RULE_ID — the primary key of the default rule record in PSB_DEFAULTS.
• DATA_EXTRACT_ID — the foreign key linking the rule to its extract definition; it is the join column between the two base tables.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS audit columns inherited from PSB_DEFAULTS, used for change tracking and data lineage reporting.

Common Use Cases and Queries

Typical uses include auditing which extracts are referenced by which rules, generating configuration reports during upgrades or data migrations, and supporting historical analysis of budgeting setups. A straightforward query filtering by extract name would be:

SELECT name, priority, global_default_flag, data_extract_name, default_rule_id
FROM   psbfv_default_rules
WHERE  data_extract_name = :p_extract_name
ORDER  BY priority;

To enumerate all rules and their extracts, including audit context:

SELECT r.default_rule_id, r.name, r.global_default_flag, r.priority,
       r.data_extract_id, r.data_extract_name, r.last_update_date, r.last_updated_by
FROM   psbfv_default_rules r
ORDER  BY r.data_extract_id, r.priority;

Because the module is obsolete and the view may return no rows or may not exist, defensive queries should verify object existence via ALL_VIEWS before execution. Joining this view back to PSB_DATA_EXTRACTS is unnecessary in most cases since DATA_EXTRACT_NAME is already exposed, but developers may still join to PSB_DEFAULTS by DEFAULT_RULE_ID when additional rule attributes outside the view's column list are required.