Search Results psb_cost_distributions_i

Overview

The PSB_COST_DISTRIBUTIONS_I table is a core interface table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary role is to serve as a staging area for position salary distribution data before it is validated and processed into the main application tables. As an interface table, it is a critical component of data import and integration processes, enabling the batch loading of detailed salary cost allocations associated with budget positions from external systems or legacy data sources. This facilitates the accurate budgeting of personnel expenses across different funding sources, departments, or projects.

Key Information Stored

While the provided metadata does not list specific columns, the table's description as an "Interface table for Position salary distributions" indicates it holds data necessary to allocate salary costs. Based on standard interface table design and the module's purpose, it would typically store records linking a position, a funding source (like a GL account combination), and a distribution percentage or amount. A key structural element documented is the DATA_EXTRACT_ID column. This foreign key column links each distribution record to a parent record in the PSB_DATA_EXTRACTS table, which manages and tracks the overall batch or extract of data being imported. Other inferred columns would likely include identifiers for the position, the budget entity, effective dates, distribution percentages, and status flags to track processing success or errors.

Common Use Cases and Queries

The primary use case is the batch upload of position salary distributions during budget preparation or data conversion. A typical process involves populating this table via a custom SQL*Loader script or database link, followed by the execution of a standard PSB import program to validate and transfer the data. Common queries involve monitoring the interface for errors or checking load status. For example, to find all distributions from a specific data extract that failed processing, one might query based on the DATA_EXTRACT_ID and a hypothetical STATUS column. Reporting directly from this interface table is generally for diagnostic purposes; operational reporting would query the base transactional tables after successful import.

Related Objects

The documented foreign key relationship is fundamental to understanding this table's integration. The table has a direct dependency on the PSB_DATA_EXTRACTS table.

• PSB_DATA_EXTRACTS: This table is referenced via the foreign key constraint where PSB_COST_DISTRIBUTIONS_I.DATA_EXTRACT_ID = PSB_DATA_EXTRACTS.[Primary Key Column, likely DATA_EXTRACT_ID]. This relationship ensures every salary distribution record is associated with a controlled data extraction or import batch, providing auditability and process management.

While not documented in the provided snippet, this interface table would ultimately feed base PSB transactional tables (potentially like PSB_COST_DISTRIBUTIONS). Furthermore, it is likely accessed by standard PL/SQL APIs or concurrent programs within the PSB module responsible for the validation and import of interface data.