Results for “to_gl_period_name”

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

Overview

PSBFV_BUDGET_REVISIONS is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Public Sector Budgeting (PSB) product within the Oracle ETRM (Enterprise Technical Reference Model). The view presents budget revision records — the formal, versioned changes applied to a budget group's baseline — enriched with descriptive attributes drawn from budget groups, GL budget sets, and entity (parameter and constraint) sets. Its name prefix "PSBFV" follows the PSB convention for "Public Sector Budgeting Form/View" objects, indicating it was designed primarily to back an Oracle Forms-based inquiry and maintenance screen rather than to serve as a pure reporting interface. Because it is defined WITH READ ONLY, it cannot be used to insert or update revision data; DML must target the underlying base table.

Underlying Base Objects

The view is defined over five base objects, joined primarily on the PSB_BUDGET_REVISIONS table (aliased BR), which supplies the revision-level attributes:

• PSB_BUDGET_REVISIONS (BR) — the driving table holding revision identity, balance type, GL period range, submission and approval data, and the global revision flags.
• PSB_BUDGET_GROUPS (BG) — joined on BUDGET_GROUP_ID to resolve the group short name, and filtered so only groups of type 'R' that are currently effective are returned. A hierarchical CONNECT BY clause restricts results to budget groups reachable from the responsibilities assigned to the current user (via FND_GLOBAL.RESP_ID and PSB_BUDGET_GROUP_RESP), enforcing PSB responsibility-based security at the view level.
• PSB_GL_BUDGET_SETS (GLS) — outer-joined on GL_BUDGET_SET_ID to supply the GL budget set name.
• PSB_ENTITY_SET (PESP, PESC) — outer-joined twice to resolve the parameter set and constraint set names referenced by the revision.

The view also embeds Flexfield/descriptive-flex and lookup references: _LA tokens for BUDGET_REVISION_TYPE (lookup PSB_REVISION_SOURCE_TYPE) and TRANSACTION_TYPE (lookup PSB_REVISION_TRANSACTION_TYPES), and a _DF:PSB:PSB_BUDGET_REVISIONS:BR reference identifying the associated descriptive flexfield context.

Key Columns

Column names align closely with the base table, with renamed aliases where joins are involved:

• BUDGET_REVISION_ID — primary identifier of the revision.
• BUDGET_GROUP_ID / BUDGET_GROUP_SHORT_NAME — the budget group the revision belongs to.
• BALANCE_TYPE — indicates whether the revision affects an appropriated, expenditure, or other fund balance category.
• GL_BUDGET_SET_ID / GL_BUDGET_SET_NAME — the GL budget set the revision posts against.
• FROM_GL_PERIOD_NAME / TO_GL_PERIOD_NAME — the period range the revision spans.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — validity window of the revision.
• PERMANENT_REVISION, REVISE_BY_POSITION — flags controlling how the revision is applied (permanently, or position by position).
• REQUESTOR, SUBMISSION_DATE, SUBMISSION_STATUS, APPROVAL_ORIG_SYSTEM, APPROVAL_OVERRIDE_BY, FREEZE_FLAG — workflow and approval-tracking columns.
• BASE_LINE_REVISION, GLOBAL_BUDGET_REVISION, GLOBAL_BUDGET_REVISION_ID — the flags most relevant to the "global_budget_revision" search. GLOBAL_BUDGET_REVISION identifies a revision that spans or applies across all positions/groups, and GLOBAL_BUDGET_REVISION_ID references the associated global revision record, allowing position-level revisions to be traced back to their global parent.
• PARAMETER_SET_ID / PARAMETER_SET_NAME, CONSTRAINT_SET_ID / CONSTRAINT_SET_NAME — the entity sets governing how the revision was calculated.
• _LA:BUDGET_REVISION_TYPE, _LA:TRANSACTION_TYPE — lookup-derived descriptive columns for revision source and transaction type.

Common Use Cases and Queries

Typical uses include auditing revisions by status, isolating global budget revisions, and tracing position-level revisions to their global parent. A representative query:

• List all global revisions for accessible budget groups: SELECT budget_revision_id, budget_group_short_name, justification, submission_date, submission_status FROM psbfv_budget_revisions WHERE global_budget_revision = 'Y' ORDER BY submission_date DESC;
• Trace position-level revisions to a global parent: SELECT budget_revision_id, global_budget_revision_id, budget_group_short_name FROM psbfv_budget_revisions WHERE global_budget_revision_id = :p_global_rev_id;
• Approval and freeze audit: SELECT budget_revision_id, requestor, submission_status, freeze_flag, approval_override_by FROM psbfv_budget_revisions WHERE budget_group_id = :p_group_id;

Because responsibility-based filtering is enforced inside the view, results returned to any given user are automatically scoped to their assigned budget group hierarchy, which makes the view convenient for self-service inquiry but means a query intended for a full organization-wide audit must be run against the base table PSB_BUDGET_REVISIONS directly.