CAT2 — CATS Time Sheet Entry
CAT2 is the classic Cross-Application Time Sheet entry transaction. It records working time for employees and can assign the hours to receivers such as cost centers, internal orders, WBS elements, Plant Maintenance orders, or other integrated objects according to the configured data-entry profile. Saving CATS data does not necessarily mean every target application has already received or posted it.
Verified practitioner reference for CAT2 — CATS Time Sheet Entry. The page covers the operational purpose, correct usage sequence, key data to capture, evidence-based diagnosis, S/4HANA context, frequent mistakes, ownership and related SAP objects.
Published 20 Sept 2026· 570 words
Esta página ainda não está disponível em português.
Purpose
enter working times in the Cross-Application Time Sheet for employees or personnel numbers according to configured profiles. The transaction should be understood as one point in the full operational process. Master data, status, validity dates and preceding execution steps often determine what can happen here, so preserve that context before changing the symptom.
When it is used
CAT2 is typically used when organizations use classic CATS to record time for HR, Controlling, Project System, Plant Maintenance or other receivers. It is also useful in project testing and support reproduction because it exposes a concrete process state. In production, keep the initial selection narrow and separate display/analysis from actions that mass-change, count, clear or post.
How to use it in practice
- Choose the correct data-entry profile and employee/time period.
- Enter hours with the intended receiver/account assignment.
- Validate totals and any attendance/activity type requirements.
- Save/release according to workflow.
- Check transfer to target components and correct rejected records.
Key data objects
These are the fields and objects most useful for explaining a CAT2 result. Record them in incident evidence and test scripts.
- data-entry profile — verify the exact value, validity/status, and relationship to this transaction's business object.
- personnel number — verify the exact value, validity/status, and relationship to this transaction's business object.
- work date/hours — verify the exact value, validity/status, and relationship to this transaction's business object.
- receiver such as WBS/order/cost center — verify the exact value, validity/status, and relationship to this transaction's business object.
- approval/transfer status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a CATS issue by capturing the personnel number, work date, hours, data-entry profile, receiver/account assignment, and processing status. Then follow the record through approval and transfer to the target component. Reconcile the receiving CO, PS, PM, or HR document/result rather than assuming a saved CAT2 line has already posted everywhere.
ECC vs S/4HANA
CAT2 remains important in classic CATS-based landscapes; S/4HANA deployments may also use Fiori time-entry apps and SuccessFactors depending on HR architecture. Where a classic component is legacy, the page explicitly keeps that context so readers do not mistake technical availability for SAP's strategic architecture for new implementations.
Common pitfalls and how to diagnose them
- Charging time to the wrong WBS/order/cost center. Confirm the exact status and process ownership before applying a correction.
- Assuming saved CATS data has already posted to every target component. Confirm the exact status and process ownership before applying a correction.
- Using a data-entry profile with different validation/approval rules from the employee's normal process. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the HCM SUCCESSFACTORS team, with adjacent functional, technical, Security, or integration teams joining only where the evidence crosses component boundaries. Escalate with the exact object/document, organizational keys, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cat2ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.