Time-card approval rules reference the Repeating Time Period that you, as implementer, create with Manage Time Card Periods. Oracle Cloud Time and Labor lets you generate any repeating pattern (weekly, bi-weekly, 4-4-5, semi-monthly, monthly, etc.). When you build the BPM approval rule, you simply pick the required period from that list. Because the system accepts whatever repeating period exists, the set of valid approval time periods is not fixed but “any,” as long as the period is available in the Repeating Time Period lookup.

B – HCM groups determine who approves, not which time span a rule uses.

C – Excludes semi-monthly and monthly; rules aren’t limited to just weekly or biweekly.

D – Omits semimonthly and custom periods, so list is incomplete.

E – Omits biweekly and custom periods; not exhaustive.

F – Leaves out biweekly, monthly, and other possible patterns.

1. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Manage Time Card Periods” section, para. 1-2: “You can generate any repeating time periods, for example weekly, bi-weekly, semimonthly, monthly, or any other that suits your business.” (Document ID F40238-01)

2. Oracle Fusion Cloud Time and Labor Implementation Guide 24B, “Define Time Card Approval Rules,” step 3: “Select the Repeating Time Period … the rule applies to. The list comprises all repeating periods you created.”

3. Oracle Fusion Applications Help Portal, Topic “Overview of Time Card Approvals,” last paragraph: “The approval period is based on the chosen repeating time period; therefore, any configured period is valid for approvals.”