Results for “jtf_calendars_b”

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

Overview

JTF_CALENDARS_B is the base (non-translated) calendar master table owned by the JTF schema and delivered as part of the JTF — CRM Foundation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the fundamental identity, classification, descriptive metadata, and effectivity of every calendar defined in the EBS instance. Calendars registered here serve as the scheduling backbone for CRM resource management and for Oracle Projects scheduling activities, meaning that any functionality depending on working days, shifts, and exception periods will ultimately trace back to a row in this table.

Only calendar-independent attributes are held in the _B table; all translatable text (such as the calendar name and description) resides in the companion table JTF_CALENDARS_TL, which references JTF_CALENDARS_B.CALENDAR_ID. Based on the foreign-key structure mined from the documented metadata, this object is classified heuristically as a hub-leaning entity in Data Vault terms. That is a modeling suggestion rather than a shipped artifact: the table behaves as a business key hub, since it is referenced by many dependent tables but itself references only FND_SECURITY_GROUPS through SECURITY_GROUP_ID.

The documented physical schema for 12.2.2 records 27 columns and the primary key constraint JTF_CALENDARS_B_PK on CALENDAR_ID. A unique index, JTF_CALENDARS_B_U1, is also defined on CALENDAR_ID, confirming that the surrogate identifier doubles as the enforced unique key for the row.

Key Information Stored

The most significant columns in JTF_CALENDARS_B are the following:

• CALENDAR_ID — surrogate primary key (JTF_CALENDARS_B_PK) and the unique business-key candidate enforced by JTF_CALENDARS_B_U1. Every child record across shifts, exceptions, resource assignments, and Projects schedules joins on this column.
• CALENDAR_TYPE — classifies the calendar and drives which downstream engines apply it.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effectivity window during which the calendar may be used for scheduling.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org / security-group access partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework (OAF/BC4J) to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "WHO" audit columns maintained automatically by the EBS framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) columns, available for customer-defined extensions.

Note that the descriptive name and description are not physically present here; they are retrieved through JTF_CALENDARS_TL, which is the translated table keyed by CALENDAR_ID and language.

Common Use Cases and Queries

Typical scenarios include Q&A around which calendars are currently active, which shifts and exceptions belong to a calendar, and how CRM resource assignments map to calendars. A common pattern is resolving the translatable name via the TL table:

• Active calendars list: SELECT c.calendar_id, c.calendar_type, c.start_date_active, c.end_date_active FROM jtf_calendars_b c WHERE c.end_date_active IS NULL OR c.end_date_active > SYSDATE;
• Calendar with translated name: join JTF_CALENDARS_B to JTF_CALENDARS_TL on CALENDAR_ID and filter TL.LANGUAGE = USERENV('LANG').
• Shifts for a calendar: join JTF_CAL_SHIFT_ASSIGN on CALENDAR_ID to list all shift definitions bound to a given calendar.
• Exception periods: join JTF_CAL_EXCEPTION_ASSIGN to identify holiday or exception ranges.
• Projects scheduling calendars: join to PA_SCHEDULES, PA_PROJECT_ASSIGNMENTS, and PA_PROJ_ELEM_VER_SCHEDULE on CALENDAR_ID to reconcile calendars used against Projects schedules.

Reporting use cases center on auditing which resources, projects, and shifts consume each calendar, and validating effectivity windows before scheduling occurs.

Related Objects

The following tables are the most significant dependents and references, per the documented foreign-key structure:

• JTF_CALENDARS_TL — translated name and description; join on CALENDAR_ID.
• JTF_CAL_SHIFT_ASSIGN — shift definitions assigned to a calendar; join on CALENDAR_ID.
• JTF_CAL_EXCEPTION_ASSIGN — exception (holiday) periods assigned to a calendar; join on CALENDAR_ID.
• JTF_CAL_RESOURCE_ASSIGN — resource-to-calendar assignments; join on CALENDAR_ID.
• PA_PROJECT_ASSIGNMENTS — projects that consume the calendar; join on CALENDAR_ID.
• PA_SCHEDULES — Projects schedule definitions referencing the calendar; join on CALENDAR_ID.
• PA_PROJ_ELEM_VER_SCHEDULE — project element version schedules using the calendar; join on CALENDAR_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security-group partitioning.

Together these objects form the CRM Foundation and Projects scheduling chain, with JTF_CALENDARS_B acting as the centrally referenced calendar master.