Search Results csf_access_hours_b

Overview

CSF_ACCESS_HOURS_B is a Field Service (CSF) module table in Oracle E-Business Suite, owned by the CSF schema. It stores the access-hour definitions associated with service tasks, capturing the time windows during which a customer site, asset, or task can be serviced on each day of the week. The table is registered as VALID in the ETRM metadata for 12.1.1 and 12.2.2, and contains 40 documented columns.

Under the heuristic Data Vault classification mined from its foreign key structure, CSF_ACCESS_HOURS_B is identified as satellite-leaning. This suggests the table functions as a descriptive satellite attached to a parent business key (the task), rather than as an independent hub of business entities. The modeling implication is that access-hour records hang off the task entity and carry the descriptive attributes needed to support scheduling and dispatch decisions.

Key Information Stored

The table is anchored by its surrogate primary key, ACCESS_HOUR_ID, which is enforced through the CSF_ACCESS_HOURS_B_PK constraint and additionally surfaced as a unique index (CSF_ACCESS_HOURS_B_U1). A second unique index, CSF_ACCESS_HOURS_B_U2, is defined on TASK_ID, indicating that TASK_ID is a business-key candidate and that the relationship to the parent task is effectively one access-hour record per task.

The most significant descriptive columns fall into three groups:

• Task linkage: TASK_ID, which references JTF_TASKS_B and establishes the owning task.
• Scheduling flags: ACCESSHOUR_REQUIRED, AFTER_HOURS_FLAG, and DATA_CHANGED_FRM_UI, which indicate whether access hours must be observed, whether after-hours servicing applies, and whether the record was modified through the user interface.
• Daily time windows: MONDAY_FIRST_START, MONDAY_FIRST_END, MONDAY_SECOND_START, MONDAY_SECOND_END, with equivalent pairs for TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, and SUNDAY. Each day supports a first and second access window, allowing split-shift availability.
• Audit and security: OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID, which references FND_SECURITY_GROUPS for multi-org security enforcement.

Common Use Cases and Queries

The principal use of this table is to determine serviceable time windows when scheduling field service visits. Dispatchers, scheduling engines, and service entitlement checks consult the daily window columns to validate whether a proposed appointment falls within permitted access hours.

A typical query retrieves access windows for a given task:

• SELECT TASK_ID, MONDAY_FIRST_START, MONDAY_FIRST_END, MONDAY_SECOND_START, MONDAY_SECOND_END FROM CSF_ACCESS_HOURS_B WHERE TASK_ID = :task_id;

Reporting scenarios often join to JTF_TASKS_B to surface task context alongside hours:

• SELECT t.TASK_ID, t.TASK_NAME, a.ACCESSHOUR_REQUIRED, a.AFTER_HOURS_FLAG FROM CSF_ACCESS_HOURS_B a, JTF_TASKS_B t WHERE a.TASK_ID = t.TASK_ID;

Security-aware queries should filter on SECURITY_GROUP_ID to respect MOAC boundaries, and audit reporting may use LAST_UPDATE_DATE and LAST_UPDATED_BY for change tracking.

Related Objects

CSF_ACCESS_HOURS_B participates in a small but defined set of relationships:

• JTF_TASKS_B — the parent task table, joined via CSF_ACCESS_HOURS_B.TASK_ID = JTF_TASKS_B.TASK_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce organizational security.
• CSF_ACCESS_HOURS_B_PK / U1 / U2 — the primary key and unique indexes governing row identity.

Additional dependent objects in the Field Service scheduling and dispatch flow may reference this table indirectly through the task entity, but the documented metadata identifies the above as the primary relationships.