Results for “estimate_flag”

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

Overview

PSB_WS_YEAR_PROFILES_V is a reporting and integration view belonging to the Public Sector Budgeting (PSB) product family in Oracle E-Business Suite, documented across Release 12.1.1 and 12.2.2. It exposes the year-level worksheet profile definitions that drive how a budgeting worksheet behaves for a given user and worksheet. Each row represents a single year profile entry, filtered to the profile type 'Y', and joins that profile to its budget period and budget year type so that descriptive names are available alongside the raw identifiers.

The view is documented in ETRM with the notation "Not implemented in this database," indicating that it is a legacy or obsolete object within the PSB module and may not exist in every environment. Where present, it serves as a read-only presentation layer used by budget worksheet configuration screens, profile maintenance reports, and integration extracts that need to understand which data categories a worksheet is configured to include. In your case the search term "encumbrance_flag" resolves directly to the ENCUMBRANCE_FLAG column this view exposes, which is the indicator of whether encumbrance balances are enabled for the profile.

Underlying Base Objects

The view is defined over three PSB tables. The primary table is PSB_WS_USER_PROFILES (aliased WUP), which stores the profile records themselves keyed by worksheet and user. It is joined to PSB_BUDGET_PERIODS (BP) on BUDGET_PERIOD_ID and to PSB_BUDGET_YEAR_TYPES (YTP) on BUDGET_YEAR_TYPE_ID through the budget period.

• PSB_WS_USER_PROFILES (WUP) — the driving table holding the flag columns (FTE, ACTUAL, BUDGET, ESTIMATE, ENCUMBRANCE, START_YEAR) plus audit columns, constrained by PROFILE_TYPE = 'Y'.
• PSB_BUDGET_PERIODS (BP) — the budget period master, joined with an outer join (BP.BUDGET_PERIOD_ID(+)), supplying the period name.
• PSB_BUDGET_YEAR_TYPES (YTP) — the year type / year category definition, also outer-joined, supplying the year category type and year type name.

The outer joins mean that profile rows are retained even when the corresponding period or year type is not defined, with NULLs returned for the descriptive columns. ETRM documents no additional referenced base objects beyond these three.

Key Columns

The view exposes a ROWID plus the substantive profile attributes. Note that the documented column list uses ROW_ID and YEAR_TYPE_NAME, while the view text aliases them ROWID and NAME respectively; the underlying SELECT references WUP.ROWID and YTP.NAME.

• WORKSHEET_ID, USER_ID, PROFILE_TYPE — identify the worksheet, the user owning the profile, and confirm the profile type ('Y' for year profiles).
• BUDGET_PERIOD_ID, BUDGET_PERIOD_NAME — the budget period to which the profile applies.
• YEAR_CATEGORY_TYPE, YEAR_TYPE_NAME, SEQUENCE_NUMBER — the year type classification and its display ordering.
• FTE_FLAG, ACTUAL_FLAG, BUDGET_FLAG, ESTIMATE_FLAG, ENCUMBRANCE_FLAG, START_YEAR_FLAG — the core behavioral flags. ENCUMBRANCE_FLAG indicates whether encumbrance amounts are included in the worksheet profile.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns inherited from the base table.

Common Use Cases and Queries

Typical usage includes verifying which profiles have encumbrances enabled, reconciling profile configuration across worksheets, and feeding worksheet setup data into extracts or downstream budget models. The following query lists all year profiles with encumbrance enabled for a worksheet:

SELECT worksheet_id, user_id, budget_period_name, year_type_name,
  encumbrance_flag, start_year_flag
FROM psb_ws_year_profiles_v
WHERE encumbrance_flag = 'Y'
ORDER BY worksheet_id, sequence_number;

A second common pattern joins the view back to PSB_WS_USER_PROFILES to compare the profile flags against the raw source records, and a third summarizes flag values per year type. Because the object is documented as obsolete and not implemented in all databases, queries should be preceded by a validation of object existence, for example a query against ALL_VIEWS for VIEW_NAME = 'PSB_WS_YEAR_PROFILES_V', before deployment into any report or integration package.