JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

July 15, 2026 · 11 min read

SAP FSM Work Time Pattern

Work Time Pattern is FSM’s master record for a technician’s recurring weekly working-hours template — which days of the week a technician works, the start and end time of the working window on each of those days, and the break time deducted within it. It is configured independently at the tenant level, then assigned to Person/Technician records (FSM-A04-04) so that Planning Board, Assisted Scheduling, and Route Optimization all know which hours a given technician is actually available for dispatch. Work Time Pattern is the second object in the Technician Management domain (Phase 3, Zone C) covered in this series, alongside Skill (FSM-A04-01), Region, Person/Technician, Crew, Absence, and Skill Requirement. This article maps every field FSM consultants configure on a Work Time Pattern record, and how those fields connect to the Person/Technician master around it.

Part 1: Work Time Pattern — Core Concepts (All Modules)#

1.1 What Is the Work Time Pattern?#

A Work Time Pattern represents a single, named recurring weekly schedule template — the working days, start/end times, and break time a technician is expected to be available. It is a deliberately small, flat master carrying no organizational hierarchy of its own, and it means nothing in isolation: its purpose is entirely to be assigned to one or more technicians so that scheduling tools have an availability window to check dispatch requests against.

1.2 Pattern Design Variants#

Work Time Pattern carries no separate classification field of its own — Pattern ID and Pattern Name are free-text, and Work Days/Start Time/End Time/Break Time are configured directly. What varies in practice is how consultants combine those same fields to model different real-world working arrangements. Getting this design choice wrong doesn’t corrupt any field — it just produces a Planning Board availability view that doesn’t match how the workforce actually works.

Design principle: Work Time Pattern only defines the availability window Planning Board and Assisted Scheduling check against — it does not by itself guarantee capacity or qualification. Region and Skill still gate whether a technician is eligible for a specific job that happens to fall inside that window.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example (Zone C · Technician Management — tenant-level; FSM has no Company Code / Plant scoping above these objects)

Client (FSM Tenant)
   │
   ├── Skill SK-ELEC — Electrical Work L3               (configured independently; tenant-level catalog)
   ├── Work Time Pattern WTP-STD — Mon–Fri 09:00–18:00   (configured independently; tenant-level catalog)
   ├── Region RG-KAN — Kanto (Asia/Tokyo)                 (configured independently; tenant-level catalog)
   │
   └── Person / Technician P-001 — Hanako Yamada (Plannable)
          ── assigned to ──▶ Work Time Pattern WTP-STD
          ── assigned to ──▶ Skill SK-ELEC — Electrical Work L3
          ── assigned to ──▶ Region RG-KAN

Crew CR-TOK-A — Tokyo Team A (reference — groups technicians, does not own Person):
   Crew CR-TOK-A ── led by ──▶ Person P-001

Absence ABS-P001 — Annual leave (reference — blocks capacity within the Person's Work Time Pattern window):
   Absence ABS-P001 ── blocks ──▶ Person P-001

Skill Requirement SR-EQ001 — Requires a Skill on an Equipment (unrelated cross-object link, shown for zone completeness):
   Skill Requirement SR-EQ001 ── requires ──▶ Skill SK-ELEC
   Skill Requirement SR-EQ001 ── applies to ──▶ Equipment EQ-001 (Zone B)

Design principle: Work Time Pattern, Skill, and Region are independent tenant-level masters configured before Person/Technician — Person is assigned to Work Time Pattern via reference, not the reverse, and Work Time Pattern never owns Person. Its assignment sets the availability window Planning Board renders; Absence then subtracts from that same window on specific dates, rather than replacing it.

1.4 Integration with Other Master Data Objects#

Work Time Pattern does not stand alone. Every field on it exists so that Planning Board and the scheduling engines can determine, second by second, whether a technician is inside or outside their working window.

Part 2: FSM-Specific Field Details#

2.0 Scope of FSM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Core Identification#

These two fields are the whole identity of a Work Time Pattern record — FSM keeps this master deliberately lean, with the actual schedule detail living in the fields covered in the next two sections.

2.2 Weekly Schedule Definition#

These three fields together define the recurring weekly window that Planning Board, Assisted Scheduling, and Route Optimization all check before offering a technician a Service Call slot.

2.3 Break Time Configuration#

Break Time is the one field that reduces the working window defined in the previous section down to actual available capacity — it is easy to under-model during early data loads.

2.4 Assignment & Usage Linkage#

Work Time Pattern has no effect until it is picked up by at least one technician. These are the linkage facts consultants check most often when a Planning Board availability view looks wrong.

Prerequisite: A Work Time Pattern with zero Assigned Technician Count has no effect on scheduling — the pattern only becomes meaningful once referenced on at least one Person/Technician (FSM-A04-04) record.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction

Zone crop source: 04-fsm-a01-master-landscape.png (mtime: 2026-07-15 11:04)