Adding the four optional attributes as Row-Level Detail columns keeps them off the main grid. Workers expand the detail pane for each row, enter the values once, and the attributes automatically apply to every daily cell in that row. Because only the two mandatory fields remain as grid columns, the overall width of the start/stop time card is unchanged and virtually no extra horizontal scrolling is required for the weekly view.

B – Daily Details open a separate page for each day, forcing seven page visits per row and more navigation, not less scrolling.

C – A multi-attribute field still occupies at least one extra column and loses individual field validation and LOVs; scrolling is only slightly reduced.

D – Shrinking column widths does not remove columns; users still scroll to see all six fields, especially on smaller screens.

E – Freezing columns keeps mandatory fields visible but doesn’t eliminate the width added by four optional columns, so horizontal scrolling remains.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Configure Row-Level Detail Attributes” (Chapter: Design Time Card Layouts, p. 257–258): “Use row-level detail attributes to capture additional information while reducing the number of columns and horizontal scrolling in the time-entry grid.”

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Comparing Row-Level Detail and Daily Detail” (p. 259): explains that Daily Detail “requires users to open a day-level window for each date and is therefore not optimal for minimizing navigation.”

3. Oracle HCM Cloud Release 22B – What’s New, Feature: “Enhanced Row-Level Detail for Time Entry” (Doc ID 2869450.1): notes that placing optional fields in row-level detail “reduces the horizontal footprint of time cards.”