Search Results monday_first_start

Overview

The CSF_MAP_ACCESS_HOURS_VL view is a multilingual (VL) reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the CSF (Field Service) product family. It presents the access-hour definitions that govern when a field service technician is permitted or expected to access a customer site or location. These access-hour records drive scheduling, dispatch, and service-window validation logic within the Field Service module, and the view exposes them in a translation-aware form suitable for inquiry, reporting, and interface consumption.

Because it is a VL view, CSF_MAP_ACCESS_HOURS_VL joins the base table to its translation table and filters by the session language (USERENV('LANG')), returning the description text in the user's active language. This makes it the appropriate access point for any form, concurrent program, or custom report that must display access-hour descriptions in a multilingual deployment. In 12.1.1 and 12.2.2 the object is documented as VALID, indicating a correct and queryable definition.

Underlying Base Objects

The view is defined over two documented base objects, both surfaced through APPS synonyms:

• CSF_MAP_ACCESS_HOURS_B — the base (B) table holding the transactional access-hour data, including the per-day time windows and the customer/site/location mapping identifiers. This is the "A" alias in the view text.
• CSF_MAP_ACCESS_HOURS_TL — the translation (TL) table holding language-specific descriptive text. This is the "B" alias.

The two are joined on ACCESS_HOUR_MAP_ID, and the TL side is further constrained by B.LANGUAGE = USERENV('LANG'), which is the defining characteristic of a VL view. In addition to the translation join, the view exposes LANGUAGE and SOURCE_LANG from the TL table, enabling consumers to detect the language of the returned description.

Key Columns

The view exposes the full set of access-hour attributes:

• ACCESS_HOUR_MAP_ID — primary identifier linking the base and translation rows and the join key for the view.
• CUSTOMER_ID, CUSTOMER_SITE_ID, CUSTOMER_LOCATION_ID — the customer/site/location hierarchy to which the access-hour definition applies.
• ACCESSHOUR_REQUIRED and AFTER_HOURS_FLAG — control flags indicating whether access hours are mandatory and whether after-hours access is permitted.
• Per-day time windows: MONDAY_FIRST_START, MONDAY_FIRST_END, MONDAY_SECOND_START, MONDAY_SECOND_END, repeated for TUESDAY through SUNDAY. Each day supports up to two distinct windows (a split-shift pattern). The user's search term monday_first_start corresponds directly to the MONDAY_FIRST_START column, the beginning of the first Monday access window.
• DESCRIPTION, LANGUAGE, SOURCE_LANG — translation attributes supplied by the TL table.
• Standard Who columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus OBJECT_VERSION_NUMBER and SECURITY_GROUP_ID.
• ROW_ID — the ROWID of the base table row.

Common Use Cases and Queries

Typical uses include reporting the service windows applied to a customer location, validating that a proposed dispatch falls within allowed hours, and extracting access-hour data for integration into external scheduling systems. A common query retrieves all windows for a customer location:

• SELECT ACCESS_HOUR_MAP_ID, CUSTOMER_ID, CUSTOMER_SITE_ID, CUSTOMER_LOCATION_ID, MONDAY_FIRST_START, MONDAY_FIRST_END, MONDAY_SECOND_START, MONDAY_SECOND_END FROM CSF_MAP_ACCESS_HOURS_VL WHERE CUSTOMER_LOCATION_ID = :p_location_id;
• To find locations with a defined Monday morning window: SELECT CUSTOMER_LOCATION_ID, MONDAY_FIRST_START FROM CSF_MAP_ACCESS_HOURS_VL WHERE MONDAY_FIRST_START IS NOT NULL;
• To report after-hours-enabled sites: SELECT ACCESS_HOUR_MAP_ID, CUSTOMER_ID, AFTER_HOURS_FLAG FROM CSF_MAP_ACCESS_HOURS_VL WHERE AFTER_HOURS_FLAG = 'Y';

Because the view already applies the session-language filter, no additional translation join is required in such queries.