Search Results psb_data_extracts




Overview
Explore in AI Chat

Overview

The table PSB_DATA_EXTRACTS is a core definitional table within the Oracle E-Business Suite (EBS) module Public Sector Budgeting (PSB), which is documented as obsolete. It serves as the master repository for data extract definitions. In the PSB architecture, a data extract is a fundamental partitioning mechanism, acting as a logical container that segments all position-related budgeting data. This partitioning is critical for managing and processing budget information in large, complex public sector organizations, allowing data to be isolated and manipulated by specific extracts for operations like budgeting, forecasting, and reporting. Its role is to establish the context and boundaries for a distinct set of budget data.

Key Information Stored

While the provided ETRM excerpt does not list specific columns beyond key identifiers, the structure and relationships indicate the table stores essential metadata for each extract definition. The primary key, DATA_EXTRACT_ID, uniquely identifies each extract record. Critical foreign keys, such as SET_OF_BOOKS_ID (linking to GL_SETS_OF_BOOKS) and BUDGET_GROUP_ID (linking to PSB_BUDGET_GROUPS), define the accounting and organizational context for the data extract. It is logical to infer the table also contains descriptive columns like NAME, DESCRIPTION, STATUS, and effective date ranges (START_DATE, END_DATE) to manage the extract's lifecycle and usage within the budgeting system.

Common Use Cases and Queries

The primary use case is the administration and execution of budget data processes segmented by extract. Common operational queries would involve listing active extracts for a specific set of books or validating the existence of an extract before running a budget process. For reporting and integration, a typical pattern is to join this table to various position data tables to filter results for a specific extract context. A foundational query to retrieve extract definitions with their ledger context would be:

SELECT de.DATA_EXTRACT_ID, de.NAME, sob.NAME SET_OF_BOOKS
FROM PSB_DATA_EXTRACTS de,
    GL_SETS_OF_BOOKS sob
WHERE de.SET_OF_BOOKS_ID = sob.SET_OF_BOOKS_ID
AND de.STATUS = 'ACTIVE';

Another critical use case is data integrity validation, ensuring that child records (e.g., positions, employees) have a valid parent DATA_EXTRACT_ID.

Related Objects

PSB_DATA_EXTRACTS has a central relationship with numerous transactional and setup tables in the PSB module, as documented by its foreign key constraints. The DATA_EXTRACT_ID column is referenced as a foreign key in the following tables, demonstrating its role as a partitioning key for all position-related data:

Furthermore, it holds foreign key relationships to parent setup tables: