Results for “budget_year_name”

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

Overview

PSB_WS_COLUMNS_I is a table in the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its documented purpose is to record the budget years exported for a given worksheet. Each row associates an export run with a worksheet type and a positional column number, then describes the budget year, budget period, and balance types that occupy that column in the exported worksheet layout.

The table is flagged as Obsolete and is not implemented in the current database. It belongs to the PSB product area, which supported budget preparation and worksheet-based data entry for public sector customers. Because the object is obsolete, it is primarily relevant to historical data migrations, upgrade remediation, and the interpretation of legacy exports generated before PSB worksheet functionality was retired.

The metadata carries a heuristic Data Vault classification of "standalone," derived from the absence of foreign key relationships in the documented schema. In Data Vault modeling terms, this suggests the table is best treated as a standalone satellite or reference structure rather than a hub or link, since no parent business entity is enforced through foreign keys. This classification is a modeling suggestion only and does not reflect an Oracle-defined constraint.

Key Information Stored

The table contains 17 documented columns. The primary key, PSB_WS_COLUMNS_I_PK, is composed of three columns: EXPORT_ID, EXPORT_WORKSHEET_TYPE, and COLUMN_NUMBER. A unique index, PSB_WS_COLUMNS_I_U1, covers the same three columns, making this composite the business-key candidate that uniquely identifies a worksheet column within an export.

• EXPORT_ID — Identifier of the export run or export definition to which the worksheet column belongs.
• EXPORT_WORKSHEET_TYPE — The worksheet type being exported, distinguishing among the various PSB worksheet formats.
• COLUMN_NUMBER — Positional ordinal of the column within the exported worksheet.
• BUDGET_YEAR_ID and BUDGET_YEAR_NAME — Surrogate identifier and descriptive name of the budget year represented by the column.
• BUDGET_PERIOD_ID and BUDGET_PERIOD_NAME — Identifier and name of the budget period displayed in the column.
• COLUMN_TYPE — Classification of the column, such as a year, period, or total column.
• BALANCE_TYPE and DISPLAYED_BALANCE_TYPE — The stored balance type and the balance type as presented to the user.
• YEAR_CATEGORY_TYPE and DISPLAYED_YEAR_CATEGORY_TYPE — The stored and displayed year category values, permitting separate internal and presentation semantics.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATED_DATE — Standard Oracle EBS audit columns.

The pairing of stored and displayed attributes indicates that the export layout could carry user-facing labels distinct from the underlying budget configuration values.

Common Use Cases and Queries

Because PSB_WS_COLUMNS_I drives the column definition of exported budget worksheets, the most common uses involve reconstructing or validating the structure of a historical export. A typical query selects the descriptive attributes for a known export and worksheet type, ordered by column position:

• SELECT column_number, column_type, budget_year_name, budget_period_name, balance_type, displayed_balance_type FROM psb_ws_columns_i WHERE export_id = :export_id AND export_worksheet_type = :worksheet_type ORDER BY column_number;
• Reporting queries that enumerate every budget year and period included in a specific export, useful for audit and reconciliation against the source budget.
• Migration queries that map legacy exported columns back to budget year and period identifiers via BUDGET_YEAR_ID and BUDGET_PERIOD_ID.
• Metadata queries that inspect the distinct COLUMN_TYPE and YEAR_CATEGORY_TYPE values used across exports to document worksheet conventions.

Given the table's obsolete status, queries are generally one-time or diagnostic rather than part of active transactional processing. Filtering by EXPORT_ID and EXPORT_WORKSHEET_TYPE is essential, since the key is composite and column numbers repeat across exports.

Related Objects

The documented schema records no foreign key relationships, and the heuristic classification confirms the object is standalone. Consequently, related objects are inferred from the business meaning of the columns rather than from enforced constraints.

• PSB worksheet export headers — Parent export records joined on EXPORT_ID, providing the export context for each column definition.
• PSB worksheet export data tables — Detail tables that consume EXPORT_ID, EXPORT_WORKSHEET_TYPE, and COLUMN_NUMBER to align budget amounts with their column definitions.
• Budget year definition tables — Referenced logically through BUDGET_YEAR_ID and BUDGET_YEAR_NAME.
• Budget period definition tables — Referenced logically through BUDGET_PERIOD_ID and BUDGET_PERIOD_NAME.
• Balance type and year category lookup tables — Source of BALANCE_TYPE, DISPLAYED_BALANCE_TYPE, YEAR_CATEGORY_TYPE, and DISPLAYED_YEAR_CATEGORY_TYPE values.
• PSB worksheet definition tables — Define the EXPORT_WORKSHEET_TYPE values that seed the export process.
• FND audit and user tables — Resolve CREATED_BY and LAST_UPDATED_BY to application user accounts.

Because no foreign keys are enforced, join integrity must be validated at the application or reporting layer. Any upgrade or decommissioning exercise should treat PSB_WS_COLUMNS_I as read-only legacy metadata and confirm that dependent custom reports no longer reference it before removal.