Your customer wants to use badge readers as a time collection device. You have added your device supplier to the lookup as BADGE_READERS_INC. While…

Oracle Time and Labor requires each time-device event code to follow the syntax .

After you add a new supplier to lookup ORAHWMTCDSUPPLIERS (here: BADGEREADERSINC), you create the corresponding IN and OUT events in lookup ORAHWMTCDSUPPLIEREVENTS by prefixing the supplier with the event type.

Therefore the valid codes are

• INBADGEREADERSINC – identifies an on-site (badge-in) punch

• OUTBADGEREADERSINC – identifies an off-site (badge-out) punch.

Codes that place the supplier name first or merge both events into one string don’t match the required pattern and won’t be recognised by the Time Device Integration process.

B. BADGEREADERSINCIN – Supplier precedes event; naming convention invalid and will not load.

C. BADGEREADERSINCINOROUT – Combines two events in one code; not supported.

E. BADGEREADERSINCOUT – Supplier precedes event; naming convention invalid and will not load.

1. Oracle Fusion Cloud HCM: Time and Labor Implementation Guide 24B, “Create Device Supplier Event Lookups”, pp. 487-489, step 3 (“Use the format IN, OUT …”).

2. Oracle Fusion HCM Cloud Time Collection Device Integration White Paper, Rev. 1, 2023, p. 10, Table 2 (“Event Code Naming Rules”).

3. Oracle Support Doc ID 2415437.1 “Fusion Time and Labor – Adding New Time Device Supplier and Events”, Section ‘Required Lookup Code Pattern’.