Search Results pa_spread_curves_b

Overview

The PA_SPREAD_CURVES_B table is a core data object within the Oracle E-Business Suite Projects (PA) module. It serves as the primary repository for storing the definition of spread curves, which are essential for financial planning and cost accounting in project management. A spread curve defines the pattern for distributing a total amount—such as a budget, forecast, or revenue—across multiple accounting periods. This enables systematic planning and reporting of project financials over time, ensuring costs and revenues are recognized according to a predefined schedule. The table is a base table, meaning it stores the fundamental, non-translatable attributes of a spread curve, which are then referenced by numerous other components within the Projects application.

Key Information Stored

While the provided metadata does not list specific columns, the primary key and foreign key relationships indicate the critical data elements. The central column is SPREAD_CURVE_ID, a unique system-generated identifier for each curve definition. Other columns typically found in this structure include fields for the curve name, a description, the curve type (e.g., even spread, front-loaded, back-loaded, user-defined), the number of periods it spans, and creation/modification audit information (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). The table holds the master definition, while the actual percentage or value for each period within the curve is commonly stored in a related child table, such as PA_SPREAD_CURVE_DETAILS.

Common Use Cases and Queries

This table is central to configuring and applying financial schedules across projects. A primary use case is assigning a spread curve to a project budget line or a resource assignment to dictate how planned costs are allocated monthly or quarterly. Administrators query this table to maintain a library of available curves. Common SQL patterns include retrieving all curves for a setup review or joining to assignment tables for analysis. For example, to list all curves and their assignments, one might use: SELECT b.spread_curve_id, b.name, COUNT(ra.resource_assignment_id) FROM pa_spread_curves_b b LEFT JOIN pa_resource_assignments ra ON b.spread_curve_id = ra.spread_curve_id GROUP BY b.spread_curve_id, b.name;. Reporting use cases involve analyzing planned expenditure patterns by linking project financial data back to the curve definitions stored here.

Related Objects

The PA_SPREAD_CURVES_B table has documented foreign key relationships with several key transactional and setup tables in the Projects module, as per the provided metadata:

• PA_PLAN_RES_DEFAULTS: References PA_SPREAD_CURVES_B via the SPREAD_CURVE_ID column. This table stores default planning options for project resources.
• PA_RESOURCE_ASSIGNMENTS: References PA_SPREAD_CURVES_B via the SPREAD_CURVE_ID column. This is a major transactional table where the curve is applied to specific project team member assignments for financial planning.
• PA_SPREAD_CURVES_TL: References PA_SPREAD_CURVES_B via the SPREAD_CURVE_ID column. This is the corresponding translation table that stores language-specific names and descriptions for the spread curves.

These relationships confirm that PA_SPREAD_CURVES_B acts as a master source, with its SPREAD_CURVE_ID being propagated to dependent objects to enforce data integrity and consistent financial scheduling.