Search Results apply_constraints

Overview

APPS.PSB_WORKSHEETS_V is a supplementary view in the Oracle E-Business Suite Applications (APPS) schema, registered in FND Design Data under the product short name PSB (Public Sector Budgeting, part of the ETRM/Enterprise Planning and Budgeting family). The view is currently VALID in the documented release. Its primary purpose is to simplify Oracle Forms coding by presenting a flattened, denormalized projection of budget worksheet data. The header row, the worksheet identifier, the joining budget group and calendar, and the various worksheet-level attributes are combined so a single form block can be driven without multiple post-query lookups.

Oracle explicitly warns that this is a supplementary view and does not recommend querying or altering data through it. The underlying definition may change dramatically in subsequent minor or major releases, so custom code, reports, and integrations that depend on its column list or join semantics carry upgrade risk. For the user search term "apply_constraints", the view is relevant because it exposes CONSTRAINT_SET_ID, CONSTRAINT_SET_NAME, and GLOBAL_CONSTRAINT_SET_ID, which identify the constraint set applied to a worksheet.

Underlying Base Objects

The ETRM 12.2.2 metadata documents no referenced base objects for PSB_WORKSHEETS_V; the dependency list is empty in the published extract. Based on the naming convention and the product schema, the view is expected to be defined over the PSB worksheet base table, joined to budget group, budget calendar, stage set, data extract, parameter set, constraint set, and allocation rule set lookup tables. Because the documented base objects are absent, the safest assumption is that PSB_WORKSHEETS_V resolves to PSB worksheets and the reference tables that translate numeric foreign keys into readable names. Any integration should query the base tables directly rather than relying on the view's internal join structure.

Key Columns

• WORKSHEET_ID, ROW_ID – Primary identifier and row locator for each worksheet record.
• BUDGET_GROUP_ID / BUDGET_GROUP_NAME, BUDGET_CALENDAR_ID / BUDGET_CALENDAR_NAME – The budget group and calendar governing the worksheet.
• WORKSHEET_TYPE, NAME, DESCRIPTION, FREEZE_FLAG – Worksheet classification, display name, description, and freeze status.
• STAGE_SET_ID, CURRENT_STAGE_SEQ – Stage set definition and the worksheet's current stage in the workflow.
• GLOBAL_WORKSHEET_FLAG, GLOBAL_WORKSHEET_ID, GLOBAL_WORKSHEET_OPTION, LOCAL_COPY_FLAG, COPY_OF_WORKSHEET_ID – Global/copy semantics for shared or replicated worksheets.
• CONSTRAINT_SET_ID, CONSTRAINT_SET_NAME, GLOBAL_CONSTRAINT_SET_ID – The constraint set applied to the worksheet, central to the "apply_constraints" search.
• PARAMETER_SET_ID / PARAMETER_SET_NAME, ALLOCRULE_SET_ID / ALLOCRULE_SET_NAME, GL_BUDGET_SET_ID / GL_BUDGET_SET_NAME – Parameter, allocation rule, and GL budget set associations.
• DATA_EXTRACT_ID / DATA_EXTRACT_NAME, GLOBAL_DATA_EXTRACT_ID – Data extract used to populate the worksheet.
• APPLY_ELEMENT_PARAMETERS, CREATE_NON_POS_LINE_ITEMS, BUDGET_BY_POSITION, USE_REVISED_ELEMENT_RATES (obsoleted) – Element and line-item processing controls.
• DATE_SUBMITTED, SUBMITTED_BY, WS_CREATION_COMPLETE, NUM_PROPOSED_YEARS, NUM_YEARS_TO_ALLOCATE, ROUNDING_FACTOR, GL_CUTOFF_PERIOD – Submission audit, planning horizon, and rounding controls.

Common Use Cases and Queries

A typical use case is identifying which constraint set is applied to a worksheet, which is exactly what an "apply_constraints" search targets. Example:

• SELECT worksheet_id, name, constraint_set_id, constraint_set_name FROM apps.psb_worksheets_v WHERE constraint_set_id IS NOT NULL;
• SELECT worksheet_id, name, budget_group_name, budget_calendar_name FROM apps.psb_worksheets_v WHERE freeze_flag = 'Y';
• SELECT worksheet_id, name, parameter_set_name FROM apps.psb_worksheets_v WHERE worksheet_type = :p_type;

Because the view is supplementary and Oracle discourages direct querying, production reports should join the underlying PSB base tables instead. Where the view is used, treat its column list as unstable across patches and test after any upgrade to 12.1.1 or 12.2.2 patch levels.