Results for “parent_budget_group_id”

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

Overview

PSB_WS_DISTRIBUTE_RULE_LINES_V is an APPS-owned view in the Oracle E-Business Suite Public Sector Budgeting (PSB) module. It exposes distribution rule line data joined to budget group information for redistribution and worksheet processing. The view is designed primarily to support the PSB worksheet and budget distribution functionality, where budget lines are allocated or downloaded according to defined distribution rules across a hierarchy of budget groups.

The view is most relevant when working with budget group hierarchies, distribution rules, and the flags that control whether amounts are distributed or downloaded to child budget groups. Users and developers frequently search for PARENT_BUDGET_GROUP_ID because it is a key column for navigating the budget group hierarchy — it identifies the immediate parent of a budget group and, together with ROOT_BUDGET_GROUP_ID, allows reconstruction of the full organizational or budgeting tree.

Underlying Base Objects

The view is defined over two primary sources:

• PSB_BUDGET_GROUPS_V — a view that supplies budget group attributes such as BUDGET_GROUP_ID, NAME, PARENT_BUDGET_GROUP_ID, PARENT_NAME, ROOT_BUDGET_GROUP_ID, and effective date ranges.
• PSB_WS_DISTRIBUTION_RULE_LINES — the base table that stores the actual distribution rule line records, including distribution flags, year/category type, DFF attributes, and audit columns.

The join is an outer join from budget groups to distribution rule lines: BG.BUDGET_GROUP_ID = DR.BUDGET_GROUP_ID(+). The view restricts data to budget groups where BUDGET_GROUP_TYPE = 'R', meaning only "rule"-type budget groups are returned. An additional outer join condition ties the rule lines to a current distribution rule ID obtained through PSB_WS_DISTRIBUTION_RULES_PVT.GET_RULE_ID, a PL/SQL API function that returns the applicable rule for the runtime session.

Key Columns

• ROW_ID — the ROWID of the distribution rule line, useful for identifying and updating rows.
• BUDGET_GROUP_ID — the unique identifier of the budget group.
• NAME — the descriptive name of the budget group.
• PARENT_BUDGET_GROUP_ID — the identifier of the parent budget group, enabling hierarchical navigation. This is the column most commonly queried.
• PARENT_NAME — the name of the parent budget group for reporting purposes.
• ROOT_BUDGET_GROUP_ID — the identifier of the top-level (root) budget group in the hierarchy.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the budget group is active.
• DISTRIBUTION_RULE_LINE_ID / DISTRIBUTION_RULE_ID — identifiers linking the line to its owning distribution rule.
• DISTRIBUTE_FLAG / DISTRIBUTE_ALL_LEVEL_FLAG — control whether amounts are distributed to the group, or to all levels beneath it.
• DOWNLOAD_FLAG / DOWNLOAD_ALL_LEVEL_FLAG — control whether amounts are downloaded for the group or all levels beneath it.
• YEAR_CATEGORY_TYPE — indicates the budget year/category context for the rule line.
• ATTRIBUTE1–15 and CONTEXT — descriptive flexfield columns for additional client-specific data.

Common Use Cases and Queries

Typical usage involves querying the view to inspect distribution rule lines for a given budget group hierarchy, filtering by parent or root group, or tracing which rules apply to a specific group level.

SELECT budget_group_id, name, parent_budget_group_id,
       parent_name, root_budget_group_id,
       distribute_flag, distribute_all_level_flag,
       download_flag, download_all_level_flag, year_category_type
FROM   apps.psb_ws_distribute_rule_lines_v
WHERE  parent_budget_group_id = :parent_budget_group_id;

Another common query retrieves all rule lines for a root budget group:

SELECT budget_group_id, name, parent_budget_group_id
FROM   apps.psb_ws_distribute_rule_lines_v
WHERE  root_budget_group_id = :root_budget_group_id
AND    year_category_type = :year_category_type;

Because the view depends on the session context returned by PSB_WS_DISTRIBUTION_RULES_PVT.GET_RULE_ID, results reflect the rule applicable to the current runtime environment, and querying outside that context may return fewer rows than expected.