Search Results psb_workflow_processes




Overview
Explore in AI Chat

Overview

The PSB_WORKFLOW_PROCESSES table is a core data object within the Oracle E-Business Suite (EBS) Public Sector Budgeting (PSB) module. It functions as a repository for workflow item key information specifically tied to budgeting worksheets. In Oracle EBS, the Workflow Engine manages and automates business processes. This table serves as the critical link between a PSB worksheet and its associated workflow instance, enabling the tracking, routing, and approval of budgeting tasks. Its role is to persist the unique identifier (item key) that the Oracle Workflow engine uses to manage the lifecycle of a worksheet's approval process, ensuring that budgeting activities adhere to defined organizational procedures and audit trails.

Key Information Stored

The table's primary purpose is to store the relationship between a worksheet and its workflow process. The most critical column is the ITEM_KEY, which serves as the table's primary key. This column holds the unique identifier generated by the Oracle Workflow engine for a specific instance of a worksheet's approval process. A second crucial column is WORKSHEET_ID, which is a foreign key linking directly to a specific record in the PSB_WORKSHEETS table. This one-to-one or one-to-many relationship (depending on configuration) ensures every workflow item key is associated with a concrete budgeting worksheet. Together, these columns form the essential data structure for workflow state management within the PSB module.

Common Use Cases and Queries

This table is primarily accessed for troubleshooting, reporting, and system integration. A common scenario involves diagnosing a stalled worksheet approval. Administrators can query this table to verify if a workflow item key exists for a given worksheet and then use that ITEM_KEY to investigate the workflow's status in the standard Oracle Workflow tables (e.g., WF_ITEM_ACTIVITY_STATUSES). Another typical use case is generating a report of all worksheets currently in the approval pipeline. A sample query to join worksheet details with its workflow key would be:

  • SELECT ws.WORKSHEET_NAME, wfp.ITEM_KEY FROM PSB_WORKFLOW_PROCESSES wfp, PSB_WORKSHEETS ws WHERE wfp.WORKSHEET_ID = ws.WORKSHEET_ID;

This table is also essential for custom integrations that need to trigger actions based on a worksheet's workflow state, using the ITEM_KEY to interact with the Workflow Engine's APIs.

Related Objects

The PSB_WORKFLOW_PROCESSES table has a direct and documented foreign key relationship with the PSB_WORKSHEETS table. The join is performed on the column PSB_WORKFLOW_PROCESSES.WORKSHEET_ID, which references the primary key in PSB_WORKSHEETS. This is the primary relationship, anchoring the workflow data to the core budgeting entity. Furthermore, while not listed in the provided metadata, this table's ITEM_KEY column is intrinsically linked to the foundational Oracle Workflow tables in the APPS schema, such as WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_ITEM_ATTRIBUTE_VALUES. Any process or report examining the status of a PSB worksheet's workflow will typically join from PSB_WORKFLOW_PROCESSES to PSB_WORKSHEETS and then to these standard workflow tables using the ITEM_KEY.