SAP SuccessFactors time clock integration

SAP SuccessFactors Time Tracking accepts clock-in and clock-out events from terminals. This page explains how biometric attendance terminals send those events to SuccessFactors, either directly or through your SAP partner's integration.

SAP SuccessFactors

Where the punches have to go

SuccessFactors is SAP's cloud HR suite, used by large employers in many countries. Its Clock In Clock Out feature records time events from terminals and pairs them into worked time. The hard part is getting events from many terminal brands, in many sites and time zones, into it without a custom middleware project.

An integration removes the file in the middle: every punch travels from the terminal to the Cams cloud and on to SAP SuccessFactors by itself, from every site, whatever the terminal brand.

What reaches SAP SuccessFactors

Punch by punch

With the direct route, every punch is sent to SuccessFactors as it happens. SuccessFactors pairs clock-in and clock-out events itself and values the time under your time rules.

  • The employee whose assignment ID equals the terminal user ID
  • In or out
  • Punch date and time, with the terminal's offset
  • Terminal serial number
  • A punch reference

Choose your route

Ways into SAP SuccessFactors

RouteHow it worksOn camsbiometrics.com
Direct to SuccessFactors Time TrackingEvery punch goes straight to Clock In Clock Out as a terminal time event, at its own time with the terminal's time zone offset. SuccessFactors pairs the events and values the time.Details
Through your SAP partnerIf your SAP partner runs its own integration layer, every punch goes there in the Cams 3.0 format, using the address and keys the partner gives you.Details

Setup

How to connect SAP SuccessFactors

Connect the terminals to the Cams cloud

Cams terminals connect out of the box. For terminals you already own, check the model for free at developer.camsbiometrics.com: supported models connect directly over the internet, older ones as a Cams Open Terminal.

Line up the employee IDs

The employee is the person whose assignment ID equals the user ID on the terminal.

Add SAP SuccessFactors in the Cams console

Open Configurations, then Connectors, add SAP SuccessFactors and enter what it asks for (list on the right). Choose which terminals send to it.

Punches flow

From then on every punch reaches SAP SuccessFactors, usually within a minute. Failed deliveries are retried and listed in the console, so problems are visible instead of silent.

What you need

  • Your API server and company ID
  • An OAuth client: its API key and private key
  • An API user
  • Your time event type codes for clock-in and clock-out

Good to know

  • Sign-in uses SAP's OAuth with a SAML assertion that Cams signs with your client's private key; the key stays with Cams, stored encrypted.
  • The time event type codes must match those configured in your Time Tracking.

Hardware

Which attendance machines work with SAP SuccessFactors

Every Cams terminal, and terminals from ZKTeco, eSSL, Hikvision, Suprema, Anviz and many of the 90+ other brands that connect to the Cams cloud. Fingerprint, face, palm and card punches all reach SAP SuccessFactors in the same form, so you can mix technologies and brands across sites.

Choosing new terminals? Start with the types of attendance machine. Keeping the ones you have? See connecting existing machines to the cloud.

Set it up with Cams

The SAP SuccessFactors integration is one of 70+ ready-made integrations on the Cams Biometric Gateway. The page on camsbiometrics.com lists every field, the licence that applies and the price.

FAQ

SAP SuccessFactors attendance integration: questions

Which SuccessFactors module receives the punches?

Time Tracking, through its Clock In Clock Out feature. SuccessFactors pairs clock-in and clock-out events and values the time under your rules.

Do we need SAP Integration Suite or other middleware?

Not for the direct route: Cams sends the time events straight to SuccessFactors. If your SAP partner prefers to pass punches through its own layer, use the partner route instead.

How are time zones handled?

Each event carries its own time and the terminal's time zone offset, so terminals in different countries report correctly into one SuccessFactors instance.

Can we connect the terminals we already have?

In most cases, yes. Check the model for free at developer.camsbiometrics.com. Supported models connect straight to the Cams cloud; older or LAN-only models connect through the Hybrid Connector, a small program on a PC on site. Either way the SAP SuccessFactors integration takes the punches from there. See keeping the machines you have.

What does it cost?

Each terminal needs a Cams API licence: a one-time activation plus a yearly fee, with no per-employee or per-punch charge. Some integrations are included with that licence and some are paid; the SAP SuccessFactors page on camsbiometrics.com shows which applies and the price.