Search Results pa_amount_types_b




Overview
Explore in AI Chat

Overview

The PA_AMOUNT_TYPES_B table is a core reference table within the Oracle E-Business Suite Projects (PA) module, specifically in versions 12.1.1 and 12.2.2. It functions as the master repository for defining and storing the distinct types of financial amounts used throughout the project accounting and financial planning lifecycle. Its primary role is to support the summarization and categorization of project costs, revenue, budgets, and forecasts. By providing a standardized set of amount types, this table ensures consistency in how financial data is aggregated, reported, and analyzed across the Projects module, forming a critical component of the underlying data architecture for project performance management.

Key Information Stored

While the provided metadata does not list specific columns, the structure and relationships indicate the table's essential data elements. The primary identifier is the AMOUNT_TYPE_ID column, which serves as the unique key for each amount type record. Based on its functional description and foreign key relationships, the table likely stores descriptive columns such as a name (e.g., AMOUNT_TYPE), a user-facing code, and potentially a category or classification field. The existence of foreign key references from PA_PROJ_PERIODS_DENORM for both AMOUNT_TYPE_ID and AMOUNT_SUBTYPE_ID strongly suggests the table may also define hierarchical relationships or subtypes, allowing for detailed granularity in financial categorizations, such as distinguishing between original budget, current budget, and actual costs.

Common Use Cases and Queries

This table is predominantly accessed for reference and validation in reporting and data integration processes. A common use case is enriching project financial summary reports with meaningful amount type descriptions. For instance, when querying summarized project data from a denormalized table like PA_PROJ_PERIODS_DENORM, a report would join to PA_AMOUNT_TYPES_B to translate the numeric AMOUNT_TYPE_ID into a business-friendly name. Sample SQL to retrieve all defined amount types would be: SELECT AMOUNT_TYPE_ID, NAME FROM PA.PA_AMOUNT_TYPES_B ORDER BY NAME;. Another critical use case is within the Financial Planning (FP) processes, where the table provides valid values for amount categories used by tools like WebADI (via PA_FP_OF_WEBADI_XFACE) for data import, ensuring data integrity during budget and forecast uploads.

Related Objects

The PA_AMOUNT_TYPES_B table is central to the project financial data model, with documented relationships to key transactional and reporting objects. The primary key (PA_AMOUNT_TYPES_B_PK on AMOUNT_TYPE_ID) is referenced by the following foreign keys:

  • PA_FP_OF_WEBADI_XFACE: The CATEGORY_ID column in this interface table references PA_AMOUNT_TYPES_B, linking uploaded financial data to a valid amount category.
  • PA_PROJ_PERIODS_DENORM: This denormalized reporting table has two separate foreign key relationships:
    • The AMOUNT_TYPE_ID column references PA_AMOUNT_TYPES_B to categorize the primary financial amount.
    • The AMOUNT_SUBTYPE_ID column also references PA_AMOUNT_TYPES_B, allowing for a secondary, more specific classification within an amount type.
These relationships underscore the table's role in both transactional processing (WebADI uploads) and analytical reporting (period denormalization).