Search Results cac_sr_object_capacity




Overview

The CAC_SR_OBJECT_CAPACITY table is a CRM Foundation (JTF) data object within Oracle E-Business Suite that stores availability summary information for schedulable resources. As documented in the ETRM metadata, the table records capacity in three functional categories: Schedules, Exception, and Tasks. This makes it a central repository for the calculated or derived availability of objects such as service representatives, technicians, or field resources, expressed in terms of available hours across defined time windows. The table is owned by the JTF schema, is marked VALID, and appears in both 12.1.1 and 12.2.2 environments.

The heuristic Data Vault classification mined from the foreign-key structure identifies this table as standalone. As a modeling suggestion, this indicates that CAC_SR_OBJECT_CAPACITY behaves more like a self-contained reference of availability records rather than a pure junction (link) table between two hubs. Its only outbound foreign key points to the schedule detail, while multiple downstream tables reference it, suggesting it acts as a hub-like anchor for capacity data referenced by task assignments and plan options.

Key Information Stored

Of the eighteen documented columns, the following are the most significant:

Two unique indexes serve as business-key candidates: CAC_SR_OBJECT_CAPACITY_U1 on (OBJECT_CAPACITY_ID) and CAC_SR_OBJECT_CAPACITY_U2 on (OBJECT_ID, START_DATE_TIME, OBJECT_TYPE). The U2 index is particularly meaningful because it enforces a single capacity summary per object per start time per object type, preventing duplicate availability windows for the same resource.

Common Use Cases and Queries

Capacity records are consumed by scheduling engines and CRM service applications to determine whether a resource can be assigned to a task. A typical reporting query retrieves available hours for a given object within a time range:

  • SELECT object_id, start_date_time, end_date_time, available_hours FROM jtf.cac_sr_object_capacity WHERE object_id = :p_object_id AND start_date_time BETWEEN :p_from AND :p_to;
  • Joining to schedule details via schedule_detail_id to trace how availability was derived from the underlying schedule.
  • Aggregating available_hours by object_type to produce capacity dashboards for service teams.
  • Filtering by status, availability_type, or source_type to isolate exceptions versus regular schedules.

These queries are commonly embedded in resource-utilization reports, capacity-planning extracts, and integration routines feeding external workforce management tools.

Related Objects

  • CAC_SR_SCHDL_DETAILS — referenced through CAC_SR_OBJECT_CAPACITY.SCHEDULE_DETAIL_ID; the parent schedule detail that defines the availability context.
  • JTF_TASK_ASSIGNMENTS — references this table through OBJECT_CAPACITY_ID; links task assignments to the capacity record that authorized them.
  • CSF_R_PLAN_OPTION_TASKS — references this table through OBJECT_CAPACITY_ID; ties plan option tasks back to capacity summaries in field service planning.

Together these relationships position CAC_SR_OBJECT_CAPACITY as the anchor for resource availability across scheduling, task assignment, and field service planning workflows in the CRM Foundation module.