Results for “psb_worksheets_u1”

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

Overview

PSB.PSB_WORKSHEETS is the core worksheet definition table in the Oracle Public Sector Budgeting (PSB) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the fundamental attributes of every budget worksheet created in the application, including both global worksheets generated through the worksheet creation process and local worksheets derived from a global worksheet for individual budget groups within the budget group hierarchy. A global worksheet requires a budget group, budget calendar, extraction options from Oracle Public Sector General Ledger, and the parameter sets, constraint sets, and allocation rule sets used during creation; a local worksheet requires only the budget group for which it was created. Each worksheet row carries status information such as the current processing stage, freeze status, and submission status.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying PSB_WORKSHEETS as a hub: it holds the durable business key (WORKSHEET_ID), and surrounding transactional tables reference it as a dependent link or satellite. Its physical storage resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10.

Key Information Stored

The surrogate primary key is WORKSHEET_ID (NUMBER(20)), uniquely enforced by index PSB_WORKSHEETS_U1 (uniqueness on WORKSHEET_ID, tablespace APPS_TS_TX_IDX). A second business-key candidate is NAME (VARCHAR2(80)), enforced by the unique index PSB_WORKSHEETS_U2. Mandatory/identity columns and the most significant attributes include:

• WORKSHEET_ID — surrogate unique identifier for the worksheet (PK).
• NAME — business worksheet name; a unique business-key candidate.
• DESCRIPTION — free-text description (up to 2000 characters).
• BUDGET_GROUP_ID — the budget group for which the worksheet is created (FK to PSB_BUDGET_GROUPS); indexed by PSB_WORKSHEETS_N1.
• BUDGET_CALENDAR_ID — the budget calendar used (FK to PSB_BUDGET_CALENDARS).
• WORKSHEET_TYPE — O for distributed worksheet or F for non-distributed worksheet.
• GLOBAL_WORKSHEET_ID / GLOBAL_WORKSHEET_FLAG — linkage and indicator distinguishing global from locally generated worksheets.
• STAGE_SET_ID and CURRENT_STAGE_SEQ — the stage set and current sequence within the worksheet workflow (FK to PSB_BUDGET_STAGE_SETS).
• GL_BUDGET_SET_ID, DATA_EXTRACT_ID, PARAMETER_SET_ID, CONSTRAINT_SET_ID, ALLOCRULE_SET_ID, FLEX_MAPPING_SET_ID — the configuration sets driving extraction, constraints, allocation, and flex mapping.
• FREEZE_FLAG and WS_CREATION_COMPLETE — status flags controlling editability and confirming worksheet creation completion.
• DATE_SUBMITTED and SUBMITTED_BY — submission audit information.
• FEDERAL_WS_FLAG — indicates federal-specific worksheet behavior.

Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and descriptive flexfield columns (ATTRIBUTE1–ATTRIBUTE10, CONTEXT) are also present.

Common Use Cases and Queries

Because PSB_WORKSHEETS is the hub for budget worksheet processing, it is the natural driving table for worksheet-status dashboards, worksheet-creation audits, and frozen/submitted worksheet reports. Typical query patterns join outward to the budget group, stage set, and calendar dimensions:

• List active global worksheets by budget group: SELECT w.worksheet_id, w.name, w.worksheet_type, w.freeze_flag FROM psb_worksheets w WHERE w.budget_group_id = :group_id AND w.global_worksheet_flag = 'Y';
• Identify worksheets not yet complete: SELECT worksheet_id, name FROM psb_worksheets WHERE ws_creation_complete = 'N';
• Trace local worksheets back to their global parent: join GLOBAL_WORKSHEET_ID to the parent WORKSHEET_ID.
• Submission reporting: filter on DATE_SUBMITTED and SUBMITTED_BY to audit worksheet cycle activity.

Because NAME is uniquely indexed, NAME lookups are efficient; because BUDGET_GROUP_ID is non-uniquely indexed (PSB_WORKSHEETS_N1), filtering by budget group is also well supported.

Related Objects

PSB_WORKSHEETS participates in a dense referential web. It references parent configuration tables and is itself referenced by many worksheet-processing children (all joined on WORKSHEET_ID unless noted):

• PSB_BUDGET_GROUPS — via BUDGET_GROUP_ID; defines the group each worksheet serves.
• PSB_BUDGET_CALENDARS — via BUDGET_CALENDAR_ID.
• PSB_BUDGET_STAGE_SETS — via STAGE_SET_ID; drives the worksheet workflow stages.
• PSB_GL_BUDGET_SETS — via GL_BUDGET_SET_ID; GL extraction source.
• PSB_DATA_EXTRACTS, PSB_FLEX_MAPPING_SETS, and GMP_PROCESS_PARAMETER_SET_B — via DATA_EXTRACT_ID, FLEX_MAPPING_SET_ID, and PARAMETER_SET_ID respectively.
• PSB_WS_LINES_POSITIONS, PSB_POSITION_ASSIGNMENTS, PSB_PAY_ELEMENT_RATES — child detail rows for worksheet lines, positions, and rates.
• PSB_WS_DISTRIBUTIONS and PSB_WS_DISTRIBUTION_DETAILS — distribution records referencing WORKSHEET_ID and GLOBAL_WORKSHEET_ID.
• PSB_WORKFLOW_PROCESSES, PSB_SERVICE_PACKAGES, and PSB_WS_SUBMIT_SERVICE_PACKAGES — workflow and submission processing that reference the worksheet.

Together these objects form the operational footprint of the Public Sector Budgeting worksheet lifecycle, with PSB_WORKSHEETS acting as the central hub record.