Maintaining Time and Attendance

You can upload time events into EWM in the following ways:

• You use the methods of the application programming interface for time and attendance /SCWM/IF_API_LM_TATT to send time events from an external system to EWM.

  You can use this API for the integration with an external time and attendance system or to build a new user interface to enter time and attendance data. For details how to use the API, open the interface documentation in the class builder (transaction SE24).

• You use the Upload Time and Attendance Data application to upload time events into the system from a .csv file.

  You can upload the data manually or schedule a batch job to regularly upload the data from a specific location on the application server. You can use the batch job to set up integration with an external time and attendance system that can export data to a CSV format. If you are using the batch job to upload time events from an external time and attendance system, you can indicate that this is external data, which cannot be changed in the warehouse management monitor. The columns of the input file must conform to the structure of DDIC structure /SCWM/S_LM_TATT_UPLOAD. The report ignores the first line of the input file as a header line. You must fill the EVENT_DATE and EVENT_TIME fields using the ABAP formats YYMMDD for the date and HHMMSS for the time. The data in these fields must be in the time zone of the warehouse.

With the transaction Create Indirect Labor Activities you create executed workloads (EWLs) for preparation tasks, breaks, or end-of-shift tasks.

An executed workload for preparation can be created so the information that a certain worker has performed some preparation tasks before he or she has performed the first physical task in the warehouse is available in the system. For example, this could be the preparation of the resource before the processor can start working. Executed workloads for preparation tasks are based on time and attendance data and existing executed workloads.

An executed workload for a break can be created for breaks that are considered part of the working time. Executed workloads for breaks can be created either based on time and attendance data or based on radio frequency (RF) logoff information. If you are using the creation of executed workloads for breaks based on time and attendance data, the time and attendance data for the breaks needs to have the same event reasons and an event direction O for the break start and I for the break end. If you are using the RF-based creation of executed workloads for breaks, you have defined a logoff reason for the RF that the worker can use when logging off from RF.

An executed workload for the end of a shift can be created when the worker must fulfill additional work in the warehouse between the end of the last physical task and leaving the warehouse. The executed workload ensures that this information is available in the system. For example, the worker might have to put the resource back in a certain place in the warehouse. Executed workloads for the end of a shift are based on time and attendance data.

The system creates executed workloads with a maximum duration of four hours.

• To know who is actually available, you can store time and attendance events (clock-in and clock-out) in SAP Extended Warehouse Management (EWM).
• You can upload time events into EWM in the following ways: you use the methods of the application programming interface for time and attendance /SCWM/IF_API_LM_TATT to send time events from an external system to EWM, or you use the Upload Time and Attendance Data application to upload time events into the system from a .csv file (manually or by scheduling a batch job).
• With the transaction Create Indirect Labor Activities you create executed workloads (EWLs) for preparation tasks, breaks, or end-of-shift tasks.