When you open Team Schedule, the application first consults the scheduler profile assigned to the user to determine display options. The profile attribute Week Start Day controls which day appears first in all schedule views (Planned and Published). Any value set here overrides the week-start value defined in a repeating work pattern. Because your scheduler profile specifies Monday, the schedule grid therefore begins with Monday even though you expected Sunday.

A. Repeating-period settings are ignored once a scheduler profile exists; only the profile’s Week Start Day is honored for display.

B. Monday isn’t a hard-coded default; display day depends on the scheduler profile or, if absent, the repeating period.

C. Repeating-period week start is used only when no scheduler profile is assigned, so it can’t explain what you see.

1. Oracle Fusion Cloud Time and Labor 24A Implementation Guide, “Scheduler Profiles: Explained,” para. 3, bullet “Week Start Day” – states profile controls first day of week in Team Schedule.

2. Oracle Fusion Cloud Time and Labor 24A Implementation Guide, “How Schedule Display Settings Are Determined,” step 1 – notes scheduler profile overrides repeating period settings.

3. Oracle Help Center > Workforce Management > Manage Scheduling (23D), topic “Set Up Scheduler Profiles,” sec. ‘Display Preferences’, line 4 – confirms Week Start Day drives Planned/Published Schedule views.