Search Results cac_sr_schdl_objects_pk

Overview

CAC_SR_SCHDL_OBJECTS is a CRM Foundation (JTF schema) table that stores the association between schedule objects and the business entities they govern within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Calendar and Scheduling (CAC) infrastructure used by Service Request, resource, and activity scheduling features across the CRM application family. Each row links a specific business object — identified by OBJECT_TYPE and OBJECT_ID — to a parent recurring schedule defined in CAC_SR_SCHEDULES_B, defining the period during which that object participates in the schedule.

From a Data Vault modeling perspective, the table's structure is heuristic-classified as hub-leaning. The presence of a surrogate primary key (SCHEDULE_OBJECT_ID), a foreign key to CAC_SR_SCHEDULES_B, and two downward FK dependencies from CAC_SR_SCHDL_DETAILS and CAC_SR_SCHDL_EXCEPTIONS suggests the table behaves as a central hub that anchors related satellite and detail records rather than a pure transaction link. Modelers should treat CAC_SR_SCHDL_OBJECTS as a durable business entity reference, with the detail and exception tables acting as dependent satellites.

Key Information Stored

The table contains 13 documented columns. The most significant include:

• SCHEDULE_OBJECT_ID — Surrogate primary key (CAC_SR_SCHDL_OBJECTS_PK) and the sole unique-index candidate (CAC_SR_SCHDL_OBJECTS_U1); uniquely identifies each schedule-to-object association.
• SCHEDULE_ID — Foreign key to CAC_SR_SCHEDULES_B, identifying the parent recurring schedule.
• OBJECT_TYPE and OBJECT_ID — Polymorphic reference identifying the business entity being scheduled (for example, a resource or activity).
• PARTY_ID — Optional reference to a party (person or organization) associated with the scheduled object.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating that bounds when the association is active.
• START_TEMPLATE_DETAIL_ID — Links the schedule object to a starting template detail for initialization.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking record ownership and change history.

Common Use Cases and Queries

Typical usage focuses on determining which objects belong to a schedule, effective-dated schedule membership, and exception/detail lookups for a scheduled entity. Common patterns include:

• Retrieving schedules for a specific object type and ID.
• Resolving the active schedule membership at a given date.
• Joining schedule objects to their details and exceptions for calendar rendering.

A representative query:

SELECT o.SCHEDULE_OBJECT_ID, o.SCHEDULE_ID, o.OBJECT_TYPE, o.OBJECT_ID, o.START_DATE_ACTIVE, o.END_DATE_ACTIVE FROM JTF.CAC_SR_SCHDL_OBJECTS o WHERE o.OBJECT_TYPE = :p_type AND o.OBJECT_ID = :p_id AND SYSDATE BETWEEN o.START_DATE_ACTIVE AND NVL(o.END_DATE_ACTIVE, SYSDATE);

Reporting use cases include schedule membership audit reports and conflict analysis, often driven from detail and exception tables filtered by SCHEDULE_OBJECT_ID.

Related Objects

• CAC_SR_SCHEDULES_B — Parent schedule definition; join on SCHEDULE_ID.
• CAC_SR_SCHDL_DETAILS — Dependent detail records; references SCHEDULE_OBJECT_ID.
• CAC_SR_SCHDL_EXCEPTIONS — Dependent exception records; references SCHEDULE_OBJECT_ID.
• JTF scheduling APIs and concurrent programs — Consume this table to materialize schedule instances.
• CRM service request and resource components — Reference scheduled objects by OBJECT_TYPE and OBJECT_ID.