How B-COMM for Oracle Time and Labor connects to Oracle E-Business Suite
API and XML interfaces
B-COMM exchanges time records and master data with Oracle Time and Labor through documented API and XML interfaces, rather than direct table writes, so Oracle-side validation still applies.
Web Services BPEL
dormakaba lists Web Services BPEL as one of the supported integration paths. Which path you use depends on your EBS release and SOA setup, so confirm it in the design phase.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Oracle HRMS and Time and Labor | B-COMM | Employee, badge, assignment and eligibility master data | Scheduled sync or on change |
| Shop floor clocks | B-COMM | Clock-in and clock-out events, project or task codes where captured | Employee swipes badge |
| B-COMM | Oracle Time and Labor | Validated time entries ready for timecard processing | Scheduled transfer after validation |
| Oracle Time and Labor | B-COMM | Rejected or corrected entries and updated rules | Timecard validation or approval changes |
Setting it up
- 1Confirm version and interface pathCheck EBS release and choose between API, XML and BPEL paths with dormakaba before design.
- 2Align employee and badge identifiersDecide which Oracle field carries the badge number and how new hires and terminations reach B-COMM.
- 3Define validation rules in B-COMMSet grace periods, rounding, missed punch handling and shift rules to match Oracle time entry rules, so what B-COMM accepts Oracle also accepts.
- 4Map hours types and projectsMap clock transaction types to Oracle hours types and, for project or job costing, to project and task or work order references.
- 5Schedule transfersSet transfer timing around payroll cut-off and timecard approval so late punches are not missed.
- 6Pilot with one departmentRun in parallel with the current process for a full pay period and compare totals before cutover.
What usually breaks
- !Rounding and grace rules configured differently in the terminal system and in Oracle, so totals differ by small amounts that add up across employees.
- !Badge changes or rehires that leave an employee duplicated or unmatched between HR and the clock system.
- !Offline terminals holding punches that arrive after the payroll cut-off.
- !Missed punch corrections made in one system and not reflected in the other.
- !Hours type mapping gaps that cause entries to reject only for certain pay codes or shifts.
- !Time zone and daylight saving shifts creating split or overnight shift errors.
A private AI layer across both systems
Rejected time entry explanations
A private assistant reads rejected transfers and Oracle validation messages and explains in plain words which employees and rules are affected, then drafts the correction for a supervisor to approve.
Pre-payroll anomaly review
Before cut-off, ask which employees have missing punches, overlapping entries or unusual overtime, and get a list from both systems with the query visible.
Clock-to-timecard reconciliation
Compare terminal totals with Oracle timecard totals per department and flag where they differ, with the likely cause such as rounding or late transfer.
Try it here, free
Oracle EBS Item Lead Time Calculator
Compute total planning lead time for a make or buy item from preprocessing, fixed, variable and postprocessing days.
When something else fits better
- Oracle's own timecard entry (self-service) is enough where employees work at desks and shop floor punch accuracy is not critical.
- A broader workforce management suite may suit you if scheduling, labor forecasting and union rules matter, not just punch capture.
- Another Oracle-integrated time clock vendor may be a better fit for existing badge or terminal hardware.
Frequently asked questions
What interfaces does B-COMM use with Oracle?
dormakaba lists API and XML interfaces and Web Services BPEL, and describes the integration as Oracle-validated. Which path applies depends on your EBS release, so confirm with dormakaba which interface your version uses.
Does it replace Oracle Time and Labor?
No. Oracle Time and Labor remains the system of record for timecards and approvals. B-COMM collects and validates punches on the shop floor and transfers data to and from Oracle.
Can we collect job or project time?
Terminals can capture task or project codes, but they must map to valid Oracle references. Plan the code lists and validation with your project accounting team and test the rejection paths.
Pairing documented at www.dormakaba.com/in-en/offering/products/electronic-access-data/solutions-for-e . B-COMM for Oracle Time and Labor is a product of dormakaba; Netray is independent and not affiliated with either vendor.