Search Results export_id

Overview

The PSB_WORKSHEETS_I table is a core interface table within the Oracle E-Business Suite Public Sector Budgeting (PSB) module. Its primary function is to serve as a staging area for data during the import and export processes between the EBS application and external spreadsheets. This table facilitates the bulk loading of budget worksheet data from user-prepared spreadsheets into the transactional tables of the PSB module, as well as the extraction of data for offline analysis and manipulation. Its role is critical for enabling the flexible, spreadsheet-driven budgeting workflows that are common in public sector and other complex budgeting environments, acting as the system of record for data in transit during these integration processes.

Key Information Stored

As an interface table, PSB_WORKSHEETS_I holds the raw data extracted from or prepared for spreadsheet integration. The documented metadata explicitly identifies EXPORT_ID as the table's primary key column. This indicates that each unique export (or import batch) operation is assigned a distinct identifier, which is used to track and manage the entire set of rows associated with that specific data movement job. While the full column list is not detailed in the provided excerpt, typical columns in such an interface table would include the key budget dimensions (such as LEDGER_ID, BUDGET_ENTITY, ACCOUNT, PERIOD), the monetary AMOUNT, and status flags (like PROCESS_STATUS) to manage the interface lifecycle. All data resides within the PSB schema.

Common Use Cases and Queries

The primary use case is the execution and monitoring of spreadsheet-based budget data loads. A user initiates a process to export budget data to a template, which populates this table, or to import data from a completed spreadsheet, which first lands here. Common queries involve checking the status of a specific import or export batch or reviewing the data before it is processed into the main application tables. For example, to investigate a specific export batch identified by its ID, one might use:

• SELECT * FROM PSB.PSB_WORKSHEETS_I WHERE EXPORT_ID = <your_export_id> ORDER BY <sequence_column>;

Administrators may also run queries to identify pending interface rows that have not yet been processed or to clean up old interface data after successful migration to the production tables.

Related Objects

The key documented relationship for this table is its primary key constraint, named PSB_WORKSHEETS_I_PK, which is defined on the EXPORT_ID column. This primary key ensures the uniqueness of each record within the interface staging area for a given operation. Based on standard PSB architecture, this table is populated by and feeds into various PL/SQL package APIs (likely within the PSB_WS_* or PSB_BUDGET_* naming conventions) that manage the validation, transformation, and transfer of data to and from the core PSB transactional tables, such as PSB_BUDGET_LINES. While foreign key relationships to other tables are not specified in the provided metadata, the EXPORT_ID would be the critical column for joining to any related control or log tables that track the overall import/export job status and parameters.