Search Results cac_sr_schedules_b




Overview
Explore in AI Chat

Overview

CAC_SR_SCHEDULES_B is the base (non-translated) definition table for service request schedules within the JTF – CRM Foundation product of Oracle E-Business Suite. It stores the header-level definition of a schedule, which governs recurring or date-driven activity applied to one or more service request (SR) objects. Schedules act as reusable timing containers: they define a category, an active lifetime window, and a link to a schedule template that provides the underlying recurrence pattern. Because the table is the _B variant of a translated entity pair, language-specific descriptive text is held separately in CAC_SR_SCHEDULES_TL, while CAC_SR_SCHEDULES_B retains the language-independent control attributes.

The table sits in the JTF schema and is classified, per heuristic Data Vault mining of its foreign-key structure, as hub-leaning. As a modeling suggestion, SCHEDULE_ID can be treated as a durable business key around which satellite tables (language text, schedule details, exceptions, and published instances) orbit. This classification reflects the fact that the table references relatively few parents while being referenced by several dependent detail tables.

Key Information Stored

The primary key of the table is the surrogate identifier SCHEDULE_ID, enforced by the constraint CAC_SR_SCHEDULES_B_PK and mirrored by the unique index CAC_SR_SCHEDULES_B_U1. It is the single documented business-key candidate and is the value propagated to all dependent detail and translation tables.

Common Use Cases and Queries

Typical usage centers on identifying which schedules are active for a given template or category, and on reconciling schedule headers with their detail, exception, and publish records.

  • Active schedule listing — filter on the active window while excluding soft-deleted rows: 
    SELECT schedule_id, template_id, schedule_category,
       start_date_active, end_date_active
FROM   jtf.cac_sr_schedules_b
WHERE  deleted_date IS NULL
AND    TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Template-driven reporting — join to CAC_SR_TEMPLATES_B to attribute schedules to their originating templates, or to CAC_SR_SCHEDULES_TL for translated display names.
  • Audit and change tracking — compare TEMPLATE_OVN against the current template's object version to find schedules that may need regeneration.

Related Objects

The following relationships are documented and anchor the table within the scheduling subsystem.

  • CAC_SR_TEMPLATES_B — parent template; joined via CAC_SR_SCHEDULES_B.TEMPLATE_ID.
  • CAC_SR_SCHEDULES_TL — translated name/description; joined via SCHEDULE_ID.
  • CAC_SR_SCHDL_DETAILS — the recurrence detail lines for each schedule; joined via SCHEDULE_ID.
  • CAC_SR_SCHDL_EXCEPTIONS — date exceptions that override the base pattern; joined via SCHEDULE_ID.
  • CAC_SR_SCHDL_OBJECTS — the SR objects governed by the schedule; joined via SCHEDULE_ID.
  • CAC_SR_PUBLISH_SCHEDULES — published or materialized schedule instances; joined via SCHEDULE_ID.

Collectively these tables form the schedule aggregate: the header in CAC_SR_SCHEDULES_B, timing details in CAC_SR_SCHDL_DETAILS, deviations in CAC_SR_SCHDL_EXCEPTIONS, scope in CAC_SR_SCHDL_OBJECTS, presentation in CAC_SR_SCHEDULES_TL, and runtime instances in CAC_SR_PUBLISH_SCHEDULES.