Ansicht
Dokumentation

/SCWM/RLM_EWL_PREPEOS - Creation of Indirect Labor Activities Based on Attendance

General Material Data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

Purpose

You use this report 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.

An executed workload for the end of a shift can be created when the worker must fulfil 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 4 hours.

Integration

The system does not prevent running the report in the same warehouse for the same time period in parallel, as this allows you to handle the creation differently, for example, for different processor groups or depending on the team leads.

We recommend that you ensure that you do not run the report for the same range of processors in the same warehouse for overlapping time periods. If you do run the report for the same range of processors with overlapping time periods, the system might create executed workloads twice. You can delete the duplicates in the warehouse management monitor.

Prerequisites

You have authorization for object /SCWM/EWLSfor executed workload special function C (Create Indirect Labor Activities Based on Attendance).

You have defined a warehouse number with active labor management. For more information, see Customizing for Extended Warehouse Managementunder Labor Management-> Activate Labor Management.

You have defined external steps assigned to internal step INDLand labor management is active for the external steps. For more information, see Customizing for Extended Warehouse Managementunder Labor Management -> Define External Process Stepsand Labor Management-> Activate Labor Management.

You have assigned the worker’s users to a processor master.

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.

If you are using RF-based executed workload creation, the processors need to be assigned to a warehouse. If the processors are not assigned to a warehouse, the RF logoff information is not determined.

For the time range for which you want to create the executed workloads, you need to have the time and attendance data in the system.

The time and attendance data for preparation and end-of-shift needs to use either a different event reason, for example, CLOCK-IN and CLOCK-OUT, or the same event reason, for example, WORK. In the second case, the event direction of the time and attendance data needs to be set as either ‘I’ or ‘O’ and must not be undefined.

You can activate the application log for sub-object EWLon the launchpad under Extended Warehouse Management -> Settings-> Application Log-> Activate Application Log(transaction /SCWM/ACTLOG). Depending on the settings, the report creates the application log that can be used later for analysis.

Features

Selection

Warehouse Number

Specify the warehouse number in which you want to create the executed workloads. Labor management must be active in the warehouse number.

Processor Selection

In the Processor Selectionscreen area, you can enter the processor for whom the system creates executed workloads. For example, you can run the report for only processors of certain processor groups, or processors for a certain team lead.

Time Period

Define the relevant time for which you want to create the executed workloads. Typically, you would run or schedule the report for yesterday or a time period in the past.

Preparation Based on Time and Attendance

If you want the system to create executed workloads for preparation, you select the Create Executed Workloadcheckbox in this screen area. If you are creating preparation executed workloads, you must enter a reason in the Event Reasonfield. This defines the time-and-attendance point in time for the work start. You must also enter an external process step to be used for the created executed workload. You may also want the system to check the maximum duration of the created executed workload. For this purpose, you can select the Check Duration with Warningor the Check Duration with Errorradio button. If you select one of these radio buttons, you need to enter a maximum duration, or the system will not perform the check.

End of Shift Based on Time and Attendance

If you want the system to create executed workloads for the end of a shift, you select the Create Executed Workloadcheckbox in this screen area. If you are creating end-of-shift executed workloads, you must enter a reason in the Event Reasonfield. This defines the time-and-attendance point in time for the work end. You must also enter an external process step to be used for the created executed workload. You may also want the system to check the maximum duration of the created executed workload. For this purpose, you can select the Check Duration with Warningor the Check Duration with Errorradio button. If you select one of these radio buttons, you need to enter a maximum duration, or the system will not perform the check.

Break Based on Time and Attendance

If you want the system to create executed workloads for the breaks based on time and attendance information, you select the Create Executed Workloadcheckbox in this screen area. If you are creating break executed workloads like this, you must enter a reason in the Event Reasonfield. This defines the time-and-attendance points in time for the break start and break end. You must also enter an external process step to be used for the created executed workload. You may also want the system to check the maximum duration of the created executed workload. For this purpose, you can select the Check Duration with Warningor the Check Duration with Errorradio button. If you select one of these radio buttons, you need to enter a maximum duration, or the system will not perform the check.

Break Based on RF Logoff Information

If you want the system to create executed workloads for the breaks based on RF Information, you select the Create Executed Workloadcheckbox in this screen area. If you are creating break executed workloads like this, you must enter the reason for movement that the processors use to log off from RF for the break. You must also enter an external process step to be used for the created executed workload. You may also want the system to check the maximum duration of the created executed workload. For this purpose, you can select the Check Duration with Warningor the Check Duration with Errorradio button. If you select one of these radio buttons, you need to enter a maximum duration, or the system will not perform the check.

Program Control

If you do not want the system to automatically save the executed workloads, select the Simulation Modecheckbox.

If you want the system to provide an information message for each time event in the application log, select the Detailed Logcheckbox. You can use this in the case of issues for analysis.

If you want to see a list with information about the executed workloads to be created, select the Display List of Created EWLs checkbox.

If you start the report in dialog mode, the report behaves as follows:

You have selected the Simulation Modeand Display List of Created EWLscheckboxes

The system does not save the executed workloads immediately, but displays them in a result list. You can still decide to save the executed workloads from the result list. You can also display the message log using the Message Logs(Ctrl+F1) function on the result screen.

You have selected the Simulation Modecheckbox but not the Display List of Created EWLscheckbox.

The system simulates the executed workloads and displays a message log with information about the simulation and the results. You cannot save the simulated executed workloads from the message log.

You have selected the Display List of Created EWLscheckbox but not the Simulation Modecheckbox.

The system creates executed workloads immediately and displays a result list with the information about the created executed workloads. You can also display the message log using the Message Logs (Ctrl+F1) function on the on the result screen.

You have not selected the Simulation Modeor the Display List of Created EWLscheckbox

The system creates executed workloads immediately and displays a message log as a result.

If you start the report in background, the report behaves as follows:

The system ignores the Display List of Created EWLssetting and always creates a message log as result.

If you select the Simulation Modecheckbox, the system simulates the executed workloads but does not save them to the database.

If you do not select the Simulation Modecheckbox, the system saves the created executed workloads.

Standard Variants

Output

In dialog mode, the system displays either an application log or a list of the determined executed workloads, depending on the Display List of Created EWLssetting. If you have selected the Simulation Modecheckbox as well, the executed workloads are not saved immediately, but you can still decide to save them from the result list.

In batch mode, the system ignores the Display List of Created EWLssetting. The system always displays the message log.

In dialog and batch mode, the system writes an application log of the success and error messages from the execution, depending on the application log settings. The system writes the application log when the executed workloads are saved.

In dialog mode, if you have selected the Display List of Created EWLscheckbox, the result list contains the information about the processor, the external step, the start date and time, the end date and time, and the duration. In addition to that, it includes status information, which provides more information about the created or existing executed workload. The status is set as follows:

Workload Can be Saved: The system sets this status if the report was run in simulation mode, and it proposes an executed workload to be created.

Workload Saved: The system sets this status if the report was not run in simulation mode and executed workloads have been created by the system, or if the report was run in simulation mode and you have saved the executed workloads using the menu function.

Workload Exists: The system sets this status if an executed workload with the corresponding external step already exists.

Workload Cannot be Saved: The system sets this status if an executed workload should be created, but cannot be saved due to error messages.

In addition to the status, the system displays a status for the maximum duration check. Note that the duration checks are performed for executed workloads to be created and existing executed workloads. The results of the check can be as follows:

No Maximum Duration Check Done

Maximum Duration Check Successful

Maximum Duration Check with Error

Maximum Duration Check with Warning

Activities

You can display existing logs related to the transaction in the warehouse by using the Message Logs(Ctrl+F1) function on the selection screen.

Example

You run the report for yesterday and a single processor for your warehouse.

The worker assigned to the processor has performed the following actions on the selected day:

Event	Time
Clock-in to start work	08:00
RF logon	08:05
Start warehouse order processing	08:10
End warehouse order processing	11:40
Logoff RF for reason break	11:45
Clock-out for break	12:00
Clock-in after break	12:30
RF logon	12:40
Start warehouse order processing	12:50
End warehouse order processing	17:50
RF logoff	17:55
Clock-out for end of shift	18:00

In the system, you have the following information is available for the selected day.

Time and Attendance Data for the Processor

Event Time	Event Direction	Event Reason
08:00	I	WORK
12:00	O	BREAK
12:30	I	BREAK
18:00	O	WORK

Executed Workloads Processed by the Processor

Start Time	End Time	External Step
08:10	11:40	Picking
12:50	17.50	Picking

RF Logon/Logoff Information for the Processor

Time Event	Time
Logged on	08:50
Logged off reason BREA	11:45
Logged on	12:40
Logged off	17:55

If you run the report with the settings to create preparation (event reason WORK, external step PREP), end-of-shift (event reason WORK, external step EOS), and break executed workloads (event reason BREAK, external step BREA) based on time and attendance, the system creates the following executed workloads for the processor:

Start Time	End Time	External Step
08:00	08:10	PREP
12:00	12:30	BREA
17:50	18:00	EOS

If you run the report with the settings to create preparation (event reason WORK, external step PREP), end-of-shift (event reason WORK, external step EOS), and break executed workloads, and break executed workloads based on RF information (reason for movement BREA, external step BREA), the system creates the following executed workloads for the processor:

Start Time	End Time	External Step
08:00	08:10	PREP
11:45	12:50	BREA
17:50	18:00	EOS

PERFORM Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.

Length: 20760 Date: 20240426 Time: 123441 sap01-206 ( 337 ms )

Ansicht Dokumentation