For employees who do not record their working time via time recording terminals, actual times for processing type M can also be entered using which SAP HR infotype?

Introduction / Context:
In SAP Time Management, employee working times can be captured in different ways. Some employees use time recording terminals or interfaces to record actual clock-in and clock-out times. Others, especially salaried employees without detailed time recording, have their times derived from planned working time and manual entries such as overtime. Processing types in time evaluation, such as type M, influence how the system handles these times. This question asks which infotype can be used to enter actual times for processing type M when employees do not use time recording, focusing on manual overtime entry as a way to provide time data for evaluation and payroll.

Given Data / Assumptions:
- The employees in question do not use terminal-based time recording or clock times.
- Actual times relevant for processing type M need to be recorded in an HR infotype.
- SAP provides various time-related infotypes, including one specifically for overtime.
- The question lists generic names such as Interval, Wage, Identity, and Overtime infotypes, and asks which one is appropriate for recording actual working times in this scenario.

Concept / Approach:
When employees do not record their working time via terminals, SAP Time Management often uses planned working time from infotype 0007 as the base and then supplements this with manual entries for exceptions, such as absences and overtime. The Overtime infotype (commonly infotype 2005) allows HR or line managers to record completed overtime hours manually, including start and end times or number of hours. These entries can then be processed by time evaluation and payroll, for example under processing type M for certain actual time valuations. Other infotypes such as personal identity or generic wage data are not designed for recording individual time events or overtime hours.

Step-by-Step Solution:
Step 1: Recognise that the scenario concerns employees without detailed time recording; therefore, actual worked times must be input manually where needed. Step 2: Recall that overtime is a typical example of additional actual working time that exceeds planned working time and needs to be recorded in the system. Step 3: Identify that the Overtime infotype, usually infotype 2005, is the SAP HR infotype used to store completed overtime hours, with time details and compensation information. Step 4: Compare this with the other listed infotypes, which do not correspond to standard SAP HR time infotypes for recording actual hours. Step 5: Conclude that the Overtime infotype is the appropriate infotype for entering actual times relevant for processing type M in this scenario.

Verification / Alternative check:
In a SAP HR system, you can display the list of time-related infotypes via PA30 and observe that infotype 2005 (Overtime) is specifically designed for recording overtime hours. Time evaluation schemas and rules often refer to this infotype when calculating premium payments and overtime wage types. Employees without time recording terminals may have only planned working time in infotype 0007 plus absences, attendances, and overtime entries in the 2000 series infotypes. Documentation on time evaluation also indicates that processing type M can be used to handle time wage types generated from such entries. This supports the conclusion that the Overtime infotype is the correct answer.

Why Other Options Are Wrong:
Option A is wrong because there is no standard SAP HR "Interval" infotype used in this way; actual time data is captured in specific time infotypes like attendance or overtime, not a generic interval record. Option B is incorrect since wage infotypes such as Basic Pay (0008) store pay amounts and related information but do not hold individual time entries or overtime hours. Option C is wrong because identity or personal data infotypes store information such as name, address, and identification numbers, and have nothing to do with recording working times or processing type M.

Common Pitfalls:
A common pitfall is to assume that all time-related processes require terminal-based time recording, overlooking the fact that manual entries via infotypes can also drive time evaluation. Another mistake is to confuse overtime with general payroll data, assuming it belongs in wage or basic pay infotypes rather than a dedicated time infotype. Understanding that the Overtime infotype is the correct place to record manually entered additional working time for employees without terminals helps ensure that time evaluation and payroll calculations for overtime are accurate and auditable.

Final Answer:
The correct answer is The Overtime infotype, where completed overtime hours can be recorded manually, because for employees who do not use time recording terminals, manual entries of actual additional working time, such as overtime, are stored in the Overtime infotype and processed under the appropriate processing type in time evaluation.