Search Results cac_sr_schdl_objects_u1

Overview

JTF.CAC_SR_SCHDL_OBJECTS is a transactional scheduling table within the Oracle E-Business Suite Customer Relationship Management (CRM) schema, owned by the JTF (Java Foundation / Telephony) product family. It stores the association between a schedule — defined in the parent CAC_SR_SCHEDULES_B table — and the individual business objects (resources, parties, or template-driven entities) that the schedule is applied to. Each row represents one scheduled object, bounded by an active date range, and effectively defines which object participates in a given schedule and when. The object is classified as VALID in the ETRM 12.2.2 repository and is flagged by Oracle as Internal Use Only, meaning it must be accessed only through supported Oracle Applications programs rather than through direct SQL in production.

The table is physically stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its supporting indexes reside in APPS_TS_TX_IDX. The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. In Data Vault modeling terms this suggests treating SCHEDULE_OBJECT_ID as the hub business key, with SCHEDULE_ID and the object attributes forming the surrounding link and satellite structures. This classification is offered as a modeling suggestion for teams building a warehouse or analytical layer over the EBS scheduling data; it is not an Oracle-imposed construct.

Key Information Stored

The primary key of the table is SCHEDULE_OBJECT_ID, a system-generated surrogate key. The single unique index documented on the table, CAC_SR_SCHDL_OBJECTS_U1, is also defined on SCHEDULE_OBJECT_ID, confirming it as the business-key candidate for unique identification of each scheduled object row. Full query text is available through the documented select statement.

• SCHEDULE_OBJECT_ID — surrogate primary key; the unique identifier for each schedule-to-object association.
• SCHEDULE_ID — foreign key to JTF.CAC_SR_SCHEDULES_B, indicating the parent schedule that this object row belongs to.
• OBJECT_TYPE — a VARCHAR2(30) discriminator identifying the class of object referenced (for example, a resource or party type).
• OBJECT_ID — the identifier of the referenced object within the scope defined by OBJECT_TYPE.
• PARTY_ID — the party associated with the scheduled object, enabling customer and organisation-centric lookups.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date boundaries during which the object participates in the schedule.
• START_TEMPLATE_DETAIL_ID — reference to the template detail that generated or governs the schedule start.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications WHO columns recording audit history.

Four non-unique indexes support alternate access paths: _N1 on SCHEDULE_ID, _N2 on OBJECT_ID and OBJECT_TYPE, _N3 on PARTY_ID, and _N4 on START_TEMPLATE_DETAIL_ID. These indexes indicate the primary query dimensions expected by the application.

Common Use Cases and Queries

Typical usage centers on retrieving all objects attached to a schedule, finding schedules for a given object, or reporting on active assignments within a date window. Because the object is flagged Internal Use Only, queries should generally be issued from reporting extracts, custom concurrent programs, or a replicated reporting schema rather than against production directly.

• Schedule drill-down: SELECT SCHEDULE_OBJECT_ID, OBJECT_TYPE, OBJECT_ID, START_DATE_ACTIVE, END_DATE_ACTIVE FROM JTF.CAC_SR_SCHDL_OBJECTS WHERE SCHEDULE_ID = :schedule_id;
• Object-centric lookup using the _N2 index: SELECT * FROM JTF.CAC_SR_SCHDL_OBJECTS WHERE OBJECT_ID = :object_id AND OBJECT_TYPE = :object_type;
• Party reporting using the _N3 index: filter by PARTY_ID to list all schedules a customer or organisation is engaged in.
• Active-window analysis: filter on START_DATE_ACTIVE <= SYSDATE AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= SYSDATE) for current assignments.
• Template traceability: join on START_TEMPLATE_DETAIL_ID via the _N4 index to identify schedules spawned from a specific template.

Related Objects

The table sits between a parent schedule definition and child detail/exception records, and the following relationships are the most significant for joins and dependency analysis.

• JTF.CAC_SR_SCHEDULES_B — parent table; join on CAC_SR_SCHDL_OBJECTS.SCHEDULE_ID = CAC_SR_SCHEDULES_B.SCHEDULE_ID.
• JTF.CAC_SR_SCHDL_DETAILS — child table referencing this object via SCHEDULE_OBJECT_ID; holds per-slot detail rows.
• JTF.CAC_SR_SCHDL_EXCEPTIONS — child table referencing this object via SCHEDULE_OBJECT_ID; records exceptions to the defined schedule.
• JTF.CAC_SR_SCHDL_OBJECTS (APPS synonym) — the APPS-level synonym through which application code and reports access the table.
• Associated template detail objects referenced by START_TEMPLATE_DETAIL_ID, used to trace schedules back to their generating templates.

Because the table participates in both a parent (schedule) and child (detail, exception) relationship, it functions as a central fulcrum in the scheduling data model and should be treated as a hub when modeling EBS schedule data for downstream analytics.