Search Results pa_schedule_except_history




Overview
Explore in AI Chat

Overview

The PA_SCHEDULE_EXCEPT_HISTORY table is a Projects (PA) module object within the Oracle E-Business Suite 12.1.1 / 12.2.2 data model. It stores the historical record of schedule exception requirements and assignments applied against project schedules. Whenever exceptions such as non-working days, duration shifts, or calendar percentage changes are applied to a workplan or resource assignment, the resulting requirement and assignment details are captured here as an audit and reconstruction trail. The table holds 30 documented columns in the PA schema and is classified as VALID at the 12.2.2 ETRM level.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone, meaning the mined foreign key structure does not reveal a dense parent-child web. As a modeling suggestion rather than a physical constraint, this table most closely resembles a satellite attached to a schedule exception hub, since it records descriptive, time-versioned attributes (hours by weekday, duration shifts, status) that describe an exception identified by SCHEDULE_EXCEPTION_ID. It is not a hub in its own right given the single documented outbound relationship.

Key Information Stored

The surrogate primary key is SCHEDULE_EXCEPTION_ID, which is also the sole unique index candidate (PA_SCHEDULE_EXCEPTIONS_HIST_U1) and the column that links back to the exception definition. The most operationally significant columns include:

Common Use Cases and Queries

Typical use cases include auditing historical schedule changes, reconciling assignment capacity after exceptions, and reconstructing workplan hours for a given period. A common pattern joins the history to its exception definition:

  • History of a specific exception: SELECT * FROM PA_SCHEDULE_EXCEPT_HISTORY WHERE SCHEDULE_EXCEPTION_ID = :id;
  • Project-level exception reporting: filter by PROJECT_ID and START_DATE/END_DATE to list exceptions active within a window.
  • Calendar impact analysis: aggregate RESOURCE_CALENDAR_PERCENT and weekday hour columns to measure the capacity effect of exceptions.
  • Audit trails: order by LAST_UPDATE_DATE and CHANGE_ID to trace who applied which exception and when.
  • Non-working-day reporting: filter on NON_WORKING_DAY_FLAG = 'Y' for downtime analysis.

Related Objects

The documented foreign key relationship ties this history table to CAC_SR_SCHDL_EXCEPTIONS via SCHEDULE_EXCEPTION_ID, which is the authoritative exception definition. Related objects of significance include:

  • CAC_SR_SCHDL_EXCEPTIONS – parent exception definition (join on SCHEDULE_EXCEPTION_ID).
  • PA_PROJECTS_ALL – project master referenced by PROJECT_ID.
  • Assignment objects referenced by ASSIGNMENT_ID (e.g., PA_ASSIGNMENTS).
  • Calendar objects referenced by CALENDAR_ID and CHANGE_CALENDAR_ID.
  • Project scheduling and workplan APIs that generate exception history during schedule application.