Results for “cal_exception_assign_id”

22 results




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

Overview

JTF.JTF_CAL_EXCEPTION_ASSIGN is a CRM Foundation (JTF) intersection table within Oracle E-Business Suite 12.1.1 and 12.2.2. It records the assignment of calendar exceptions — non-working periods such as holidays, shutdowns, or special business hours — to specific calendars defined in the JTF calendar infrastructure. Because a single exception may apply to many calendars, and a single calendar may carry many exceptions, this table resolves that many-to-many relationship and effectively defines the effective exception set for each calendar.

The ETRM metadata classifies this object heuristically as a link (Data Vault model). This is a modeling suggestion: the table behaves as an associative entity whose composite business key is the pairing of a calendar with an exception. The table is owned by the JTF schema, carries a VALID status, and comprises 29 documented columns, including a descriptive EXCEPTION_REASON and a set of standard WHO audit columns.

Key Information Stored

The composite unique index JTF_CAL_EXCEPTION_ASSIGN_U2 (CALENDAR_ID, EXCEPTION_ID) enforces that any given exception is assigned to a calendar only once.

Common Use Cases and Queries

Typical uses include calendar-availability reporting, exception-utilization analysis, and troubleshooting missing holiday coverage. A frequent pattern joins the assignment to its two parents to resolve exception names against calendar names:

  • List all exceptions for a calendar: select from JTF_CAL_EXCEPTION_ASSIGN where CALENDAR_ID = :p_calendar_id and trunc(sysdate) between START_DATE_ACTIVE and END_DATE_ACTIVE.
  • Find calendars using a given exception: filter on EXCEPTION_ID = :p_exception_id, the exact query the user's search suggests.
  • Denormalized report: join JTF_CAL_EXCEPTION_ASSIGN a, JTF_CALENDARS_B c on a.CALENDAR_ID = c.CALENDAR_ID, and JTF_CAL_EXCEPTIONS_B e on a.EXCEPTION_ID = e.EXCEPTION_ID to surface descriptive names, reasons, and active windows.
  • Security-filtered queries: always constrain by SECURITY_GROUP_ID in multi-group environments to respect FND security-group isolation.

Related Objects

The table sits at the center of the JTF calendar model and references or is referenced by the following significant objects:

  • JTF_CALENDARS_B — Parent calendar definition, joined on CALENDAR_ID.
  • JTF_CAL_EXCEPTIONS_B — Parent exception definition, joined on EXCEPTION_ID.
  • FND_SECURITY_GROUPS — Security-group reference via SECURITY_GROUP_ID.
  • JTF_CALENDARS_TL — Provides translated calendar names for reporting joins on CALENDAR_ID.
  • JTF_CAL_EXCEPTIONS_TL — Provides translated exception names to complement EXCEPTION_ID.
  • Calendar/exception concurrent programs and the JTF calendar PL/SQL APIs that insert, end-date, and query these assignments.

When investigating an "exception_id" reference, the analyst should treat this table as the junction that binds exception definitions to calendars, filtering on EXCEPTION_ID and date-active ranges to determine current applicability.