Search Results csf_access_hours_b_u1

Overview

CSF.CSF_ACCESS_HOURS_B is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the CSF schema. The table stores the Access Hours definition for a task, meaning it records the specific time windows during which a Field Service or scheduling task is permitted to be performed for a given day of the week. Each row captures the operating-hours calendar that governs when a task can be executed, allowing the application to enforce time-based service constraints.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, while its indexes are stored separately in APPS_TS_TX_IDX. Based on the foreign key structure and the presence of descriptive, time-slot attributes keyed by a surrogate primary key, the recorded Data Vault classification is satellite-leaning. In modeling terms, this suggests the table behaves as a satellite attached to the Task entity, capturing context-specific, mutable descriptive attributes (the access-hour windows) rather than a standalone business hub.

Key Information Stored

The most significant columns fall into three groups: identity keys, flags, and the weekly time-slot definitions.

• ACCESS_HOUR_ID – The surrogate primary key (CSF_ACCESS_HOURS_B_PK). It is also the enforced business-key candidate exposed through the unique index CSF_ACCESS_HOURS_B_U1, which the user searched for. This index ensures no duplicate access-hour records exist for a given identifier.
• TASK_ID – Foreign key to JTF_TASKS_B, linking the access-hours definition to its parent task. A second unique index, CSF_ACCESS_HOURS_B_U2, enforces a one-to-one relationship between the task and its access-hour row.
• ACCESSHOUR_REQUIRED – Flag indicating whether access hours are required for the task.
• AFTER_HOURS_FLAG – Flag indicating whether after-hours service is permitted.
• MONDAY through SUNDAY slot columns – A paired set of FIRST and SECOND start/end columns for each weekday (for example, MONDAY_FIRST_START, MONDAY_FIRST_END, MONDAY_SECOND_START, MONDAY_SECOND_END), enabling up to two discrete time windows per day.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant row-level security.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) that support the standard EBS who-column audit pattern and optimistic locking.

Common Use Cases and Queries

The primary use case is validating whether a scheduled task occurs within permissible operating windows. A typical query joins the table to JTF_TASKS_B to return the access calendar for a task:

• Retrieve a full weekly schedule: SELECT * FROM csf.csf_access_hours_b WHERE task_id = :task_id;
• Locate a record by primary key: SELECT * FROM csf.csf_access_hours_b WHERE access_hour_id = :id;
• Flag-driven reporting: filter records where AFTER_HOURS_FLAG = 'Y' to report tasks authorized for after-hours work.
• Security-restricted access: restrict rows with WHERE security_group_id = :sg_id in multi-org deployments.

Because the table is a satellite to Task, reporting solutions frequently denormalize the weekday slot pairs to produce service-level calendars, capacity plans, and compliance audits of promised versus permitted service windows.

Related Objects

• JTF_TASKS_B – Parent entity; joined on CSF_ACCESS_HOURS_B.TASK_ID = JTF_TASKS_B.TASK_ID.
• FND_SECURITY_GROUPS – Security grouping; joined on CSF_ACCESS_HOURS_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• CSF_ACCESS_HOURS_B_U1 / _U2 – Unique indexes enforcing the surrogate key and the one-per-task constraint.
• CSF_ACCESS_HOURS_B_PK – Primary key constraint on ACCESS_HOUR_ID.

Together these relationships establish the table as the definitive source of task-level operating-hours data within the CSF module.