Results for “quarter_or_month_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_SUMM_BALANCES is a Projects (PA) module table in Oracle EBS 12.1.1 and 12.2.2 that stores summarized balance information for reporting objects. Rather than persisting every individual project transaction, this table holds pre-aggregated monetary and non-monetary balances keyed by reporting object, period, version, and amount type. It serves as a performance-oriented staging layer that Project Management reporting, Project Status Inquiry, and period-based analytics rely on to avoid costly real-time aggregation against transactional tables.

Each row associates a reporting object (through OBJECT_ID referenced to PA_OBJECTS) with a specific accounting or project period and an amount type. Because balances are versioned and partitioned by period set, the same object can carry multiple rows representing different reporting versions, period types, and calendar contexts. The table is central to multi-currency project reporting, since it stores balances expressed simultaneously in several currency perspectives.

From a dimensional modeling standpoint, the heuristic Data Vault classification mined from the foreign-key structure is link. This suggests treating PA_SUMM_BALANCES as a relationship artifact connecting reporting objects, versions, period sets, and amount types, with the balance measures acting as effectivity attributes of that association.

Key Information Stored

The table comprises 23 documented columns. The most significant are:

• OBJECT_ID — the reporting object identifier; foreign key to PA_OBJECTS.
• OBJECT_TYPE_CODE — distinguishes the type of reporting object referenced.
• VERSION_ID — the project or reporting version; foreign key to VEA_VERSIONS.
• PERIOD_SET_NAME — the accounting calendar; foreign key to GL_PERIOD_SETS.
• PERIOD_NAME and PERIOD_TYPE — the specific period and its classification (e.g., month, quarter).
• PERIOD_YEAR, PERIOD_NUM, and QUARTER_OR_MONTH_NUMBER — numeric period-relative attributes supporting sorting and year-over-year comparisons.
• GLOBAL_EXP_PERIOD_END_DATE — the global expenditure period end date.
• AMOUNT_TYPE_ID — the measure classification; foreign key to PA_AMOUNT_TYPES_B.
• PERIOD_BALANCE and UNIT_OF_MEASURE — the base balance and its unit.
• The currency-perspective columns: GLOBAL_PERIOD_BALANCE, DENOM_PERIOD_BALANCE, PVDR_PERIOD_BALANCE, RCVR_PERIOD_BALANCE, and PROJ_PERIOD_BALANCE, each paired with its corresponding currency code column (GLOBAL_CURRENCY_CODE, DENOM_CURRENCY_CODE, PVDR_CURRENCY_CODE, RCVR_CURRENCY_CODE, PROJ_CURRENCY_CODE).

The documented unique index PA_SUMM_BALANCES_U1 spans PERIOD_TYPE, OBJECT_TYPE_CODE, OBJECT_ID, VERSION_ID, PERIOD_SET_NAME, PERIOD_NAME, GLOBAL_EXP_PERIOD_END_DATE, and AMOUNT_TYPE_ID. This composite constitutes the business-key candidate; no single surrogate primary key column is separately documented, so the unique index serves as the natural grain definition.

Common Use Cases and Queries

The primary use cases are period-based project reporting, currency-converted balance extraction, and version comparison. A typical query retrieves balances for a given object across periods:

• Project Status Inquiry and Project Management Reporting: join PA_SUMM_BALANCES to PA_OBJECTS and PA_AMOUNT_TYPES_B to render balance summaries by amount type.
• Multi-currency reporting: select the appropriate *_PERIOD_BALANCE column matching the reporting currency perspective.
• Period trend analysis: filter by PERIOD_SET_NAME, PERIOD_YEAR, and PERIOD_NUM to produce time-series trends.
• Version comparison: constrain by VERSION_ID to contrast forecast, budget, or baseline versions.

A representative pattern is SELECT object_id, period_name, amount_type_id, proj_period_balance FROM pa_summ_balances WHERE period_set_name = :p AND version_id = :v. Reporting extracts frequently restrict on the leading columns of PA_SUMM_BALANCES_U1 to exploit the unique index.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• PA_OBJECTS — joined on PA_SUMM_BALANCES.OBJECT_ID = PA_OBJECTS.OBJECT_ID.
• GL_PERIOD_SETS — joined on PERIOD_SET_NAME to resolve calendar definitions.
• VEA_VERSIONS — joined on VERSION_ID for version context.
• PA_AMOUNT_TYPES_B — joined on AMOUNT_TYPE_ID for measure classification.