Results for “start_year_flag”

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

Overview

APPS.PSB_WS_YEAR_PROFILES_V is a validity-checked (Status: VALID) internal Oracle E-Business Suite view owned by the APPS schema. It is registered in FND Design Data as PSB.PSB_WS_YEAR_PROFILES_V and carries an Oracle Internal Use Only warning: Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Its View Type is documented as Internal. The view belongs to the Public Sector Budgeting (PSB) product family and serves the Budgeting Worksheet user-interface, presenting the per-year budgeting configuration that a specific user profile applies when building a budget worksheet. In this reporting/integration role it is not a general-purpose data source but a supporting structure consumed by the worksheet generation and extraction logic. The column most relevant to the user's search term, ESTIMATE_FLAG, indicates whether estimate balances are to be retrieved for the associated budget period within the worksheet year profile.

Underlying Base Objects

The ETRM dependency information documents that APPS.PSB_WS_YEAR_PROFILES_V references the following base objects:

• APPS.PSB_BUDGET_PERIODS
• APPS.PSB_BUDGET_YEAR_TYPES
• APPS.PSB_WS_USER_PROFILES

The view therefore joins worksheet user-profile rows (PSB_WS_USER_PROFILES) to the budget calendar (PSB_BUDGET_PERIODS) and the year-type definition (PSB_BUDGET_YEAR_TYPES), producing one row of year-specific worksheet configuration per user, profile type, and budget period. No base-table join predicates are exposed in the documented view source, only the projected column list and the fully qualified SELECT from APPS.PSB_WS_YEAR_PROFILES_V. On the dependency side, the view is referenced by APPS.PSB_EXCEL_PVT, confirming its role as a feed for the budgeting worksheet Excel integration path. The 12.2.2 metadata records no separately documented owner or base objects beyond this dependency list, so the three PSB tables above should be treated as the authoritative underlying sources.

Key Columns

• ROW_ID (ROWID) and WORKSHEET_ID, USER_ID — identify the worksheet instance and the user whose profile is being resolved.
• PROFILE_TYPE, YEAR_CATEGORY_TYPE, YEAR_TYPE_NAME — describe the kind of profile and the budget year category/name from the year-type definition.
• BUDGET_PERIOD_ID, BUDGET_PERIOD_NAME, SEQUENCE_NUMBER — the budget period and its ordering within the year.
• FTE_FLAG — indicates whether the worksheet operates in full-time-equivalent terms.
• ACTUAL_FLAG, BUDGET_FLAG, ESTIMATE_FLAG, ENCUMBRANCE_FLAG — balance-type inclusion flags. ESTIMATE_FLAG signals whether estimate balances must be retrieved; the documented comment for ENCUMBRANCE_FLAG (Flag indicates if encumbrance balance must be retrieved) establishes the same semantics for the sibling flags. All such flags are VARCHAR2.
• START_YEAR_FLAG — marks the starting year of the profile range.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Because the object is internal, supported usage is confined to Oracle Applications programs such as PSB_EXCEL_PVT, and any direct query is diagnostic or support-oriented, typically executed from the APPS schema or a read-only reporting account with equivalent synonyms. Typical scenarios include verifying which balance types (actual, budget, estimate, encumbrance) a worksheet will retrieve for a given user and period, and tracing worksheet configuration to the underlying budget calendar.

• Inspect the estimate setting for a user: SELECT worksheet_id, user_id, budget_period_name, estimate_flag, encumbrance_flag FROM apps.psb_ws_year_profiles_v WHERE user_id = :user_id;
• List all profile rows for a worksheet: SELECT * FROM apps.psb_ws_year_profiles_v WHERE worksheet_id = :worksheet_id ORDER BY sequence_number;
• Audit recently changed profiles: SELECT year_type_name, budget_period_name, estimate_flag, last_update_date, last_updated_by FROM apps.psb_ws_year_profiles_v WHERE last_update_date > SYSDATE - 30;

Customers implementing custom reports should replicate the underlying PSB tables of record rather than depend on this internal view, since Oracle does not guarantee its definition across releases.