Calendar-entry validations must fire the moment the user clicks Save in the calendar dialog.

According to the Time and Labor implementation flow, only a Time Entry Rule (TER) is evaluated at that exact event. Oracle instructs implementers to build the TER fast formula with the delivered Workforce Management calendar-validation subroutine (for example, HWMCALENDARENTRYVALIDATION) so the formula can interrogate the worker’s schedule and return a message.

The finished formula is attached to a TER rule, placed in a TER rule set, and that rule set is referenced by the worker’s time-entry profile. This configuration meets the stated requirement; none of the other rule types are executed from the calendar dialog’s Save action.

B – “All of the above” is false because several listed options execute at different events or on different devices.

C – A Time Submission Rule (TSR) fires on Submit, not when the calendar dialog is saved.

D – No standalone “calendar validation function” exists; Oracle specifies the calendar-validation subroutine, making this description inaccurate.

E – Time Card Rules (TCR) evaluate the whole time card during Save/Submit, not single-entry dialog saves.

F – Time Device Rules (TDR) are evaluated on physical/mobile devices, not the web calendar entry page.

1. Oracle Fusion Cloud Time and Labor 24B Implementing Time and Labor Guide, “Define Time Entry Rules – Example: Validate Calendar Entry Using a Time Entry Rule,” pp. 124–126, Doc ID F48341-01.

2. Oracle Fusion Fast Formula User Guide 24B, “Workforce Management Calendar Validation Subroutines,” Table 5-1 (HWMCALENDARENTRYVALIDATION), Doc ID F30629-01.

3. Oracle Fusion Cloud Time and Labor 24B Implementing Time and Labor Guide, “Rule Evaluation Events,” p. 30 (TER vs. TCR vs. TSR vs. TDR distinctions), Doc ID F48341-01.