The Planned and Published Schedules feature, which managers use to view team schedules, is designed to display calendar-based events with specific start and end times. A 'duration' work schedule only defines the total number of hours to be worked (e.g., 8 hours) without specifying the exact start and end times. Because this schedule type lacks the specific time-of-day data required by the calendar view, it is not supported and will not be displayed in the Planned and Published Schedules interface.

B. The worker’s work schedule is assigned to his primary assignment.

Assigning a work schedule to a worker's primary assignment is the standard and expected configuration; this action does not cause visibility issues.

C. Shift short name has not been set for the shifts that composed the worker’s work schedule.

A missing shift short name is a display attribute issue that might result in a blank label, but it would not prevent the entire schedule from being rendered.

D. Shift limits have not been set for the shifts that composed the worker’s work schedule.

Shift limits are constraints used for scheduling validation and planning, not for controlling the basic visibility of an already assigned schedule to a manager.

---

1. Oracle Cloud HCM: Implementing Workforce Management (Release 22D)

Chapter: Work Schedules

Section: Considerations for Creating Work Schedules

Content: The documentation explicitly states: "You can't use duration-based work schedules with the planned and published schedules that you manage with the Team Schedule." This directly confirms that duration schedules are incompatible with the view in question.

2. Oracle Cloud HCM: Using Time and Labor (Release 22D)

Chapter: Team Schedule

Section: Overview of Viewing Team Schedules

Content: This section describes how the team schedule displays shifts and absences on a calendar. The functionality relies on objects having defined start and end times to be placed on the calendar grid

a characteristic that 'duration' schedules lack by definition.