Oracle advises that you never change a rule that is already deployed and used in production because any edit forces the system to recalculate all historic time cards that referenced that rule, possibly creating new errors.

Instead, duplicate the rule, fix the input and output parameter values in the copy, and replace the old rule with the new, corrected one in the rule set. Finally, resubmit the affected time cards so that they’re processed by the updated rule.

A. Requires enabling HWMALLOWRULEEDITS and edits the live rule; Oracle guidance says to avoid editing deployed rules to prevent retroactive recalculation risks.

B. Same direct-edit approach as A (even keeps the rule in the set), violating recommended practice and still needing the profile option.

C. Deletes rule from set but still edits the deployed rule, contradicting Oracle’s “duplicate, don’t edit” recommendation and ignores profile requirement.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24A, “Maintain Time Processing Rules – Best Practices,” Note: “Duplicate the rule and make changes; don’t use Edit Deployed Rule in production” (Part No. F30546-01, chap. 16, p. 247).

2. Same guide, “Profile Options for Time and Labor,” table entry HWMALLOWRULEEDITS – default No; only needed when you insist on editing a deployed rule (p. 433).

3. Oracle Support Doc ID 2175672.1, “Guidelines for Editing Time Repository Rules,” section 2: “Recommended method is to duplicate and replace, not edit.”

(Only official Oracle documentation is cited; no commercial prep material used.)