# dormakaba B-COMM with Oracle Fusion Cloud Time and Labor

> Source: https://netray.co/stack/dormakaba-b-comm-oracle-fusion-cloud-hcm-time-and-labor
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

B-COMM collects punches from time clocks, mobile, IVR and web clocks and posts them to Oracle Time and Labor time cards through Oracle web services. Validation data stays in Oracle. It fits manufacturers that already run a mix of clocks and want one collection layer feeding Fusion.

## Erp

Oracle Fusion Cloud HCM and ERP

## Erp Key

oracle-fusion

## On Prem

false

## Product

B-COMM for Oracle Fusion Cloud HCM

## Vendor

dormakaba

## Category

Time and attendance

## Integration

**Method:** Oracle web services into Time and Labor

**Detail:** 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.

**Method:** Multiple clock types as one source

**Detail:** 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.

## Data Flows

**From:** Oracle HCM

**To:** B-COMM

**Data:** Worker and validation data

**Trigger:** Scheduled refresh

**From:** Time clocks, mobile, IVR, web

**To:** B-COMM

**Data:** Raw punches

**Trigger:** Each punch

**From:** B-COMM

**To:** Oracle Time and Labor

**Data:** Time card entries

**Trigger:** Near real time or batch, per configuration

**From:** Oracle Time and Labor

**To:** B-COMM

**Data:** Entry errors for correction

**Trigger:** After Oracle validation

## Setup

### Inventory every punch source

**Detail:** List terminals, IVR lines, mobile and web clocks per plant so each has a defined path into B-COMM.

### Create the Oracle integration user

**Detail:** Use a dedicated service account with only the Time and Labor roles needed, and keep its password rotation on the calendar.

### Load validation data

**Detail:** Confirm which worker, department and reason values are pulled from Oracle and how often they refresh.

### Define the time card mapping

**Detail:** Match time attributes and reporting categories in Oracle to what each clock can capture.

### Test error handling

**Detail:** Send bad punches on purpose and confirm who sees the rejection and where it is corrected.

### Parallel run

**Detail:** Run for one pay period beside the existing process and reconcile hours per worker.

## Pitfalls

- 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.

## Ai Layer

### Punch to time card reconciliation

**Description:** 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

**Description:** Ask who is missing a punch on second shift or which terminals show rising rejects, answered from both systems.

### Draft corrections

**Description:** Prepare the corrected time entry text for a supervisor to approve, never writing to Oracle on its own.

## Alternatives

- 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.

## Faq

### Where does the time data live after posting?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Source

https://www.dormakaba.com/us-en/offering/products/electronic-access-data/time-clocks-labor-collection-solutions/b-comm-for-oracle-hcm-cloud--ka_231059

## Search terms

dormakaba b-comm oracle time and labor, oracle fusion time and labor time clock integration, kronos alternative oracle hcm time clock, oracle hcm cloud punches web services, ivr time clock oracle hcm, oracle time card import clock

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json