Your customer has asked you to define a weekly time card period and a bi-weekly approval period. How should you configure this?

Oracle Time and Labor lets you create separate repeating periods, each tagged with a different Usage. Define one repeating period with Usage = Time Card Period and a weekly length; define another repeating period with Usage = Time Card Approval and a bi-weekly length. You then attach the weekly period to the time-processing/entry profile and the bi-weekly period to the approval profile, yielding weekly time-card creation but bi-weekly managerial approval. No delivered option exists to make a single period definition serve two different cycle lengths.

A. Time-card and approval periods are independent usages; Oracle explicitly supports different cycles.
C. One period definition can’t drive two distinct approval-cycle lengths; “every two weeks” can’t be set inside a weekly period.
D. Mid-period approval isn’t configurable; using one bi-weekly period would also create bi-weekly, not weekly, time cards.

1. Oracle Fusion Cloud HCM Time and Labor Implementation Guide 24A, “Create Repeating Time Period Definitions,” steps 4–6, Example: Weekly Time Cards, Biweekly Approvals (Doc ID F24372-01, pp. 79–80).

2. Oracle Fusion Cloud HCM Time and Labor Implementation Guide 24A, “Time Card Period and Approval Period Usage,” Table 7-2 (pp. 75–76).

3. Oracle Learning Library, HCM Cloud Time and Labor Configuration Course, Module 3 “Managing Time Periods,” slide 14 (Usage = Time Card Period vs Time Card Approval).