Results for “jtf_cal_shift_cons_v”

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

Overview

JTF_CAL_SHIFT_CONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JTF – CRM Foundation product family. It is a pass-through view defined over the base table JTF_CAL_SHIFT_CONSTRUCTS, exposing the shift constructs that define the working and non-working time windows used by the CRM calendar and scheduling infrastructure. The view presents the physical row identifier together with the full set of descriptive, temporal, and descriptive-flexfield columns of the underlying table, without performing joins, aggregation, or filtering (no WHERE clause is present in the view text). Its principal role is to provide a stable, supported query interface for the shift-construct data that supports resource availability, appointment scheduling, and calendar resolution in Oracle CRM applications and in the Oracle EBS Time and Labor-adjacent scheduling models.

For the search term availability_type_code, this view is the documented access point. The column AVAILABILITY_TYPE_CODE is exposed directly from the base table and is the attribute that distinguishes the nature of a given shift construct — typically whether the time window represents available (working) time or unavailable (non-working) time for the associated shift. Reporting and integration consumers query this view rather than the table directly in order to remain consistent with Oracle's supported schema surface.

Underlying Base Objects

The view is defined exclusively over JTF_CAL_SHIFT_CONSTRUCTS, which is referenced in the ETRM documented view metadata as a SYSYNONYM in the APPS schema resolving to the JTF base table. The view text is a straightforward projection:

• SELECT of all business and audit columns of the table, aliased through table alias B.
• ROWID of the base row exposed as ROW_ID, providing a direct physical row locator.
• No joins, unions, or inline views are present; the relationship to the base object is strictly one-to-one at the row level.

Because the view carries no filter predicate, every row present in JTF_CAL_SHIFT_CONSTRUCTS is visible through the view, subject only to the grants and row-level security configured on the object itself. The view is reported as VALID, and because it is a simple non-complex view, Oracle may allow DML passthrough on the underlying table; nevertheless, developers are advised to treat it as query-only for integration purposes.

Key Columns

• ROW_ID – ROWID of the base record, useful for de-duplication and diagnostic tracing.
• SHIFT_CONSTRUCT_ID – Primary identifier of the shift construct; the join key to other calendar and shift objects.
• SHIFT_ID – Foreign reference to the parent shift definition to which the construct belongs.
• AVAILABILITY_TYPE_CODE – Classifies the construct as available or unavailable time; the column most frequently searched in this view.
• UNIT_OF_TIME_VALUE – Duration or granular unit associated with the construct.
• BEGIN_TIME / END_TIME – Start and end time boundaries of the shift construct window.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective date range governing when the construct is active.
• OBJECT_VERSION_NUMBER – Optimistic locking version, indicating the row is managed by the ORM/ADF entity layer.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield context and segments, available for customer-specific extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard who-column audit trail.

Common Use Cases and Queries

Typical usage centers on availability analysis and calendar validation. The following queries illustrate common patterns, including a targeted lookup by the searched column:

• Retrieve all constructs for a given shift, ordered by start time:
  SELECT shift_construct_id, shift_id, begin_time, end_time, availability_type_code FROM jtf_cal_shift_cons_v WHERE shift_id = :p_shift_id ORDER BY begin_time;
• Find currently active availability constructs by type:
  SELECT shift_id, availability_type_code, begin_time, end_time FROM jtf_cal_shift_cons_v WHERE availability_type_code = :p_avail_code AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• Audit recent changes to shift constructs:
  SELECT shift_construct_id, last_updated_by, last_update_date FROM jtf_cal_shift_cons_v WHERE last_update_date >= TRUNC(SYSDATE) - 7;
• Extract flexfield data for integration:
  SELECT shift_construct_id, attribute_category, attribute1, attribute2 FROM jtf_cal_shift_cons_v;

These queries are appropriate for reporting views, custom concurrent programs, and interface extracts that populate external scheduling systems. Because the view is a simple projection, performance is driven primarily by the indexing on JTF_CAL_SHIFT_CONSTRUCTS; queries filtering on SHIFT_ID or AVAILABILITY_TYPE_CODE benefit from whatever indexes the base table carries.