Results for “cac_sr_schdl_exceptions”

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

Overview

CAC_SR_SCHDL_EXCEPTIONS is a CRM Foundation (JTF) table within Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the relationship between service resource schedules and the exceptions that govern their availability. It is part of the scheduling infrastructure used by CRM applications — most notably Field Service, TeleService, and interaction-center scheduling — to determine when a resource is unavailable, available outside normal hours, or subject to special handling for a given calendar period.

The table functions as an associative entity rather than an independent business entity. Each row binds a specific schedule to a specific exception definition and, where applicable, to a specific schedule object. Based on the documented foreign-key topology — three distinct outbound references and a single column surrogate key — the object is best characterized under a Data Vault modelling heuristic as a link table. It records the intersection of schedules, schedule objects, and exception definitions rather than describing attributes of any one of them, and therefore behaves as a relationship-resolution structure between otherwise independent hubs.

Key Information Stored

The table contains nine documented columns. The most significant are:

• SCHEDULE_EXCEPTION_ID — the surrogate primary key, enforced by the constraint CAC_SR_SCHDL_EXCPTNS_B_PK and uniquely indexed by CAC_SR_SCHDL_EXCEPTIONS_U1. This is the technical identifier and the column referenced by downstream objects.
• SCHEDULE_ID — foreign key to CAC_SR_SCHEDULES_B; identifies the parent schedule to which the exception applies.
• EXCEPTION_ID — foreign key to CAC_SR_EXCEPTIONS_B; identifies the exception definition being applied.
• SCHEDULE_OBJECT_ID — foreign key to CAC_SR_SCHDL_OBJECTS; scopes the exception to a particular schedulable object within the schedule.
• CREATED_BY, CREATION_DATE — standard audit columns capturing row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and the session that made it.

Of these, only SCHEDULE_EXCEPTION_ID carries a documented unique index and is therefore the sole business-key candidate; the three foreign-key columns collectively define the grain of the relationship but are not individually unique. There are no descriptive or effective-dating columns documented, so temporal variation in exception assignment is expressed by inserting and deleting rows rather than by versioning them.

Common Use Cases and Queries

Typical usage centres on resolving resource availability. A reporting query might join the exception link to its exception definition to list all non-working periods for a schedule:

• Enumerate exceptions for a given schedule: join CAC_SR_SCHDL_EXCEPTIONS to CAC_SR_EXCEPTIONS_B on EXCEPTION_ID filtered by SCHEDULE_ID.
• Determine which schedulable objects within a schedule are affected: join to CAC_SR_SCHDL_OBJECTS on SCHEDULE_OBJECT_ID.
• Audit exception assignment history by joining to PA_SCHEDULE_EXCEPT_HISTORY or PA_SCHED_EXCPT_HSTRY_AR on SCHEDULE_EXCEPTION_ID.
• Reconcile project-side scheduling: PA_SCHEDULE_EXCEPTIONS holds the same key, enabling cross-module comparison between CRM Foundation and Projects scheduling data.

Because the audit columns follow EBS conventions, standard "who changed what and when" queries are supported directly against this table without joining to a shadow history table for the row's current state.

Related Objects

The following objects have documented dependency relationships with CAC_SR_SCHDL_EXCEPTIONS:

• CAC_SR_SCHEDULES_B — referenced via SCHEDULE_ID; the parent schedule definition.
• CAC_SR_EXCEPTIONS_B — referenced via EXCEPTION_ID; the exception definition.
• CAC_SR_SCHDL_OBJECTS — referenced via SCHEDULE_OBJECT_ID; the schedulable object scope.
• PA_SCHEDULE_EXCEPTIONS — references this table via SCHEDULE_EXCEPTION_ID.
• PA_SCHEDULE_EXCEPT_HISTORY — references this table via SCHEDULE_EXCEPTION_ID, providing change history.
• PA_SCH_EXCPT_HSTRY_AR — archive counterpart referencing SCHEDULE_EXCEPTION_ID.

Together these objects form the exception-handling layer of the CRM scheduling model, with the Projects tables consuming the same keys for cross-module visibility.