TEVEN table — TEVEN Time Events Table

One row in TEVEN represents a single raw time event for one personnel number: a clock-in, a clock-out, a break-start, a break-end, or a similar stamp captured on a given date and time, usually delivered by a time recording terminal, a badge reader interface, or manual entry via the time events infotype. This is infotype 2011, Time Events, and because the data volume for large workforces with multiple daily stamps is far higher than a typical infotype, SAP does not store it in a generic PA2011-style table. It is held instead in TEVEN, a dedicated pool table. Time evaluation (the schema-driven batch job) reads these raw events, pairs a clock-in with its matching clock-out, and produces rated time pairs and attendance or absence results downstream. TEVEN itself carries no rated hours, no wage types, and no approval status beyond basic processing status.

TEVEN is client-dependent and grows fast: every clock stamp for every employee on every day is a row, so a plant with thousands of badge readers can generate tens of thousands of rows a day. Never select without at least PERNR and a DATUM range; a full table scan on this object in a live system is a guaranteed performance incident. If investigating a single employee's day, restrict on PERNR, DATUM, and if possible ARTID to isolate clock-in versus clock-out events. STATUS is worth including in the selection when trying to separate events already consumed by time evaluation from ones still pending, since re-running evaluation against unprocessed events versus already-processed ones produces very different results.

An employee reports their clock-out did not register and their shift shows as incomplete. Select TEVEN for that PERNR and DATUM. If only one row exists for the day with an ARTID indicating clock-in and no matching clock-out row, the terminal event genuinely never arrived, confirming a hardware or interface gap rather than a time evaluation defect. If both rows exist but STATUS shows unprocessed, the problem is that time evaluation has not yet run or errored out for that day, not a missing punch.

TEVEN continues to exist on S/4HANA as the storage table for infotype 2011 time events, and the underlying purpose of holding raw clock stamps ahead of time evaluation has not changed. Consultants working with newer time recording integrations, including SAP Time Management or third-party workforce management tools connected via standard interfaces, should still expect raw events to land here before evaluation. Confirm on any specific S/4HANA release whether a compatibility view or a newer time recording data model is in use before assuming direct table access is still the intended path for reporting.

The time management configuration consultant owns questions about how events are generated, paired, and evaluated. The technical interface team or the vendor of the time recording terminal system owns questions about why an event failed to arrive at all. HR operations owns individual employee corrections and should use the standard infotype 2011 maintenance transaction rather than any direct table change.

PA0007 supplies the planned work schedule against which raw events are compared. PA2002 receives the rated attendance and absence results once time evaluation has paired events from TEVEN. PA0000 and PA0001 provide the employment status and organizational context needed to validate whether an event should have been expected at all. Time events are typically maintained through the infotype 2011 maintenance transaction or loaded automatically via a time recording interface, and reviewed through standard time evaluation result displays rather than direct table browsing.