Search Results psb_attribute_values_i

Overview

The PSB_ATTRIBUTE_VALUES_I table is an interface table within the Oracle E-Business Suite module Public Sector Budgeting (PSB), which is noted as obsolete in the provided documentation. Its primary role is to serve as a staging area for data loading and integration processes. Specifically, it acts as the intermediary data store for attribute values before they are validated and transferred into the main transactional table, PSB_ATTRIBUTE_VALUES. This design pattern is common in EBS for managing data imports from external systems or legacy sources, ensuring data integrity before committing records to production tables. The documentation explicitly states it was "Not implemented in this database," indicating it may have been a planned object for specific upgrade or migration paths that was not deployed in the referenced EBS instances (12.1.1 / 12.2.2).

Key Information Stored

As an interface table, PSB_ATTRIBUTE_VALUES_I would typically hold the same core data attributes as its target table, along with control columns for the interface process. Based on its foreign key relationships and standard interface table design, key columns include:

• ATTRIBUTE_VALUE_ID: The primary key identifier for each record in the interface.
• DATA_EXTRACT_ID: A foreign key linking to the PSB_DATA_EXTRACTS table, identifying the source data extract or batch that populated the interface record.
• ATTRIBUTE_ID: A foreign key linking to the PSB_ATTRIBUTES table, defining which specific budgeting attribute the value is assigned to.
• Additional columns would likely store the actual attribute value, context information (like effective dates), and interface process flags (e.g., PROCESS_STATUS, ERROR_MESSAGE) to track the success or failure of the data migration.

Common Use Cases and Queries

The primary use case for this table is the batch loading of budgeting attribute values. A typical process would involve an external program or EBS concurrent program inserting records into this interface table. A subsequent validation and import program would then select records, apply business rules, and transfer valid data to the PSB_ATTRIBUTE_VALUES table. Common SQL patterns would involve querying records pending processing or identifying errors. For example, a query to review unprocessed records for a specific data extract might resemble:
SELECT attribute_id, attribute_value FROM psb_attribute_values_i WHERE data_extract_id = &extract_id AND process_status = 'PENDING';
Reporting use cases would be limited to monitoring the interface process itself, such as generating summaries of records by status or tracking load performance over time.

Related Objects

PSB_ATTRIBUTE_VALUES_I has documented relationships with two key tables in the Public Sector Budgeting module, as per the provided metadata:

• PSB_DATA_EXTRACTS: Linked via the foreign key PSB_ATTRIBUTE_VALUES_I.DATA_EXTRACT_ID. This relationship ties interface records to a specific source data extraction batch or job.
• PSB_ATTRIBUTES: Linked via the foreign key PSB_ATTRIBUTE_VALUES_I.ATTRIBUTE_ID. This relationship ensures the value being loaded corresponds to a valid, predefined attribute in the system.

The ultimate target for successfully processed data is the PSB_ATTRIBUTE_VALUES table, as indicated in the table's description, though a direct foreign key from that table to the interface is not documented here.