The correct answer is B. Time Week .
In Workday Time Tracking, the business object you choose depends on the level at which the calculation needs to evaluate time . Since the requirement is to count all hours in a week for system-generated break time blocks, the calculation must operate at the weekly level , which makes Time Week the appropriate business object. Time Week is used when Workday needs to total, compare, or evaluate hours across an entire workweek rather than looking at only one block or one day at a time.
This is especially important for time calculations involving accumulated weekly values, such as total break hours, weekly overtime thresholds, or weekly premium eligibility. Because the requirement explicitly says all hours in a week , Workday must evaluate the data in a weekly context, not as isolated entries.
The other options are not correct for this scenario. Time Block is too granular because it evaluates individual entries or blocks of time rather than the total for the week. Time Day would only support daily accumulation, not a full weekly count. Worker is too broad and is typically used for eligibility or worker-level attributes rather than time aggregation logic.
So, for counting break-related system-generated time block hours across a full week, the correct business object is Time Week
