How B-COMM for Oracle Fusion Cloud HCM connects to Oracle Fusion Cloud HCM and ERP
Oracle web services into Time and Labor
dormakaba documents that B-COMM posts collected time into Fusion Time and Labor time cards using Oracle web services. Worker and validation data (for example valid departments and reasons) are kept in Oracle, so the clocks validate against current Oracle values.
Multiple clock types as one source
Terminals, mobile, IVR and web clocks all report through the same B-COMM layer, so Oracle sees one stream of punches rather than one integration per device type.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Oracle HCM | B-COMM | Worker and validation data | Scheduled refresh |
| Time clocks, mobile, IVR, web | B-COMM | Raw punches | Each punch |
| B-COMM | Oracle Time and Labor | Time card entries | Near real time or batch, per configuration |
| Oracle Time and Labor | B-COMM | Entry errors for correction | After Oracle validation |
Setting it up
- 1Inventory every punch sourceList terminals, IVR lines, mobile and web clocks per plant so each has a defined path into B-COMM.
- 2Create the Oracle integration userUse a dedicated service account with only the Time and Labor roles needed, and keep its password rotation on the calendar.
- 3Load validation dataConfirm which worker, department and reason values are pulled from Oracle and how often they refresh.
- 4Define the time card mappingMatch time attributes and reporting categories in Oracle to what each clock can capture.
- 5Test error handlingSend bad punches on purpose and confirm who sees the rejection and where it is corrected.
- 6Parallel runRun for one pay period beside the existing process and reconcile hours per worker.
What usually breaks
- !Validation data that is stale on the clock lets a worker pick a department that Oracle has already end-dated.
- !Punches posted after a time card is approved can land in a locked period and need manual handling.
- !Different clock vendors use different badge formats, so a single person number mapping is needed.
- !Daylight saving and time zone settings on terminals versus the Oracle location time zone cause shifted hours.
- !Oracle web service credential expiry silently stops posting; monitor the queue, not only the clocks.
A private AI layer across both systems
Punch to time card reconciliation
Compare B-COMM punch logs against Time and Labor entries per worker and period, and list differences with the probable cause for a payroll clerk to review.
Plain-language attendance questions
Ask who is missing a punch on second shift or which terminals show rising rejects, answered from both systems.
Draft corrections
Prepare the corrected time entry text for a supervisor to approve, never writing to Oracle on its own.
Try it here, free
Oracle Fusion Kanban Card Calculator
Size a kanban loop: how many cards or containers you need for a given demand, replenishment time, container quantity and safety factor.
When something else fits better
- Oracle Time and Labor's own web and mobile entry may be enough for salaried or low-volume sites.
- A tablet-based kiosk product with an Oracle connector suits plants without legacy terminals.
- If labor must tie to production orders, use an MES labor collection feature instead of a separate time clock layer.
Frequently asked questions
Where does the time data live after posting?
In Oracle Time and Labor. B-COMM collects and posts the punches as time card entries, and validation data is kept in Oracle. Approval, pay rules and payroll transfer remain Oracle functions, so reports for auditors should come from Oracle rather than from the clock layer.
Does it work with existing terminals?
dormakaba positions B-COMM as a collection layer across time clocks, mobile, IVR and web clocks. Whether a specific older terminal model is supported is a question for dormakaba, so send them the model list before you commit to reusing hardware.
Is there an on-prem version for Oracle?
This page covers Oracle Fusion Cloud, which is a cloud service. dormakaba also has a separate product page for Oracle E-Business Suite, which is the more typical on-prem pairing, so check that listing if you run EBS in your own data center.
Pairing documented at www.dormakaba.com/us-en/offering/products/electronic-access-data/time-clocks-lab . B-COMM for Oracle Fusion Cloud HCM is a product of dormakaba; Netray is independent and not affiliated with either vendor.