Aleksandra Milic

KBA 04 · Time Management

When Leave Won't Save

Separate an absence collision from time-type eligibility, effective-dated employee context, and tenant configuration before changing a request.

Read time
About 6 minutes
Source
Public SAP Help
Level
Foundation
Reviewed
15 July 2026
By the end

You can distinguish a date collision from an eligibility or configuration question and package the right evidence for a Time owner.

01 · Model

“Won't save” is the result, not the cause.

The same user-facing outcome can sit behind overlapping time records, a time type that is not available in the employee's context, or collision behavior configured for the relevant record types.

Dates

What already occupies the period?

Inspect authorized time records that overlap the requested start, end, or partial-day interval.

Eligibility

Should this time type apply?

Confirm the employee's effective-dated Time Profile and the availability of the selected time type for that context.

Collision behavior

How should these records interact?

Collision resolution is configured. Do not infer the intended result only from what another time type or employee allows.

02 · Evidence

Read the calendar and employee context together.

Capture the smallest set of facts that can distinguish overlap, eligibility, and configured collision behavior.

  1. 01
    The employee, time type, exact interval, and displayed messageInclude only relevant detail and preserve the blocked behavior accurately.
  2. 02
    Existing records over the same intervalLook for approved, pending, or other applicable time records.
  3. 03
    Effective-dated Time Profile and time-type contextConfirm which profile applies on the requested dates.
  4. 04
    Expected collision rule and business ownerCompare the observed result with approved configuration and policy.
03 · First checks

Do not “clear the calendar” to diagnose it.

The safe goal is a reproducible evidence package, not a destructive experiment on employee time data.

Safe first checks

  • Confirm dates, duration, and selected time type.
  • Read the exact validation or collision message.
  • Inspect authorized overlapping records and their states.
  • Check the employee's Time Profile for the relevant dates.
  • Compare the pattern with current collision configuration guidance.

Stop before

  • Deleting an existing absence to see whether the new one saves.
  • Changing a Time Profile without assessing downstream effects.
  • Trying unrelated time types until one succeeds.
  • Assuming two employees should receive identical behavior.
  • Overriding policy or approval ownership through configuration.
Owner boundary

The Time Management owner and authorized HR administrator decide whether a record, employee assignment, time-type setup, collision rule, or business policy needs action.

04 · Reason

Keep overlap, eligibility, and rule separate.

Select the best first move for the fictional scenario.

Fictional scenario

What should happen first?

An employee cannot save a half-day absence. Another absence already covers part of that date. What should happen first?

Select an answer to reveal the reasoning.

05 · Source

Continue with current SAP guidance.

Time behavior varies with configuration, permissions, effective dates, and release context.

Independent summary

This KBA does not replace Time configuration, business policy, employee-data governance, or an authorized tenant review. Verify the current SAP documentation and local design.