Results for “gl_budget_start_date”

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

Overview

PSB_GL_BUDGETS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the PSB (Public Sector Budgeting) product. It is a valid database object in both Oracle EBS 12.1.1 and 12.2.2 and is classified as a view rather than a table, meaning it exposes no independent storage and functions purely as a query interface over underlying budget definition data. Its role is to present general ledger budget definition records in a reporting-friendly form for Public Sector Budgeting, blending PSB-specific budget version attributes with descriptive general ledger budget information.

The view is particularly relevant to reporting and integration requirements that need to resolve PSB budget periods, dates, and posting behavior against the corresponding GL budget name. Because it joins PSB control data to the GL budgets repository, it allows reporting tools, concurrent programs, and interfaces to retrieve budget definition information without navigating multiple objects independently. The END_PERIOD column, which is the term the user searched for, is exposed directly from the PSB_GL_BUDGETS table and defines the closing accounting period of a budget definition.

Underlying Base Objects

The view text is documented and is defined over two objects:

• PSB_GL_BUDGETS (alias PB) — the PSB-side budget definition table that supplies the primary key, budget set and version identifiers, start and end periods, start and end dates, dual posting type, and the standard WHO audit columns.
• GL_BUDGETS_V (alias GB) — the general ledger budgets view that supplies the descriptive budget name and the GL-level budget start and end dates.

The two objects are joined with the equijoin condition PB.GL_BUDGET_VERSION_ID = GB.BUDGET_VERSION_ID, so each row in the view corresponds to a PSB budget record matched to its GL budget version. The ETRM metadata lists no other referenced base objects, and no further join or filter predicates are documented beyond this condition.

Key Columns

The view exposes the following columns. Several are duplicated in meaning, so alias carefully in queries.

• ROW_ID — the ROWID of the underlying PSB_GL_BUDGETS row, useful for direct row identification.
• GL_BUDGET_ID — identifier of the general ledger budget.
• GL_BUDGET_SET_ID — identifier of the budget set to which the budget belongs.
• GL_BUDGET_VERSION_ID — identifier of the budget version; this is the column used to join to GL_BUDGETS_V.
• START_PERIOD / END_PERIOD — the first and last accounting periods covered by the budget definition. END_PERIOD is the searched column and marks the budget's closing period.
• START_DATE / END_DATE — the PSB-side budget start and end dates.
• DUAL_POSTING_TYPE — indicates the dual posting behavior associated with the budget record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns captured on the PSB record.
• GL_BUDGET_NAME — the descriptive name of the budget from GL_BUDGETS_V.
• GL_BUDGET_START_DATE / GL_BUDGET_END_DATE — the GL-side start and end dates for the budget version.

Common Use Cases and Queries

Typical usage includes budget period validation, reporting on budget coverage ranges, and lookups that need the human-readable budget name alongside PSB period information. A basic query retrieving the budget name and its period range is:

• SELECT gl_budget_name, start_period, end_period, start_date, end_date FROM psb_gl_budgets_v ORDER BY gl_budget_name;
• Filter budgets by closing period: SELECT gl_budget_name, start_period, end_period FROM psb_gl_budgets_v WHERE end_period = :p_end_period;
• Join to budget set or version identifiers for integration extracts: SELECT gl_budget_set_id, gl_budget_version_id, gl_budget_name, end_period FROM psb_gl_budgets_v;

Because the view performs the PSB-to-GL join, it is convenient for concurrent programs and reports that would otherwise require separate queries against PSB_GL_BUDGETS and GL_BUDGETS_V. Queries should qualify columns where the duplicated date and name definitions could cause ambiguity.