Effects of Labor Management Activation on the UI 

Use

You activate Labor Management (LM) for a warehouse number and external process steps in Customizing for Extended Warehouse Management (EWM). Due to the activation, some functions behave differently to those in an EWM system where Labor Management is not activated. This means that in functions that are relevant for Labor Management, entries for the processor and start and end time of the work are required to be able to evaluate the data properly.

Recording the Data

Depending on whether you enter the data in an RF environment or on the desktop, the activation has an effect on the respective UIs and transactions. If the original document is LM-relevant, the system automatically writes workload documents for planned and executed workload.

●      In desktop transactions that you use to post work done by processors, you must enter the processor and end time.

●      You do not have to enter anything for work centers. Either the system sets the processor and start and end time automatically, or you enter the data explicitly using a pushbutton.

●      No additional entries are required in the RF environment. The system determines the times automatically, apart from the time for indirect labor (transaction SCWM/ILT). In this transaction you enter the start and end time yourself.

Features

Planned and Executed Workload

LM activation affects the planned and executed workload: the system writes the planned workload when generating a document. The system writes the executed workload during confirmations. The planned workload is then deleted.

The system writes workload documents for reference documents. The type of the original document is identified through the object reference document category.

For some original documents, additional entries are required if the document is relevant to Labor Management. In the following desktop functions you must enter the processor that performs a particular task. In the RF functions and in transaction SCWM/VASEXEC, the processor matches the system user.

EWM Functions

In addition to the processor, you enter the start and end date/time for the listed functions. You must always enter the end date/time. This is needed for Labor Management to be able to assign the executed workload to the evaluation period of a performance document, and therefore to calculate the time a processor requires to execute an activity.

We recommend that you enter a start date to obtain detailed actual data.

Affected functions:

●      Warehouse order with goods movement

Confirm warehouse task (transaction /SCWM/TO_CONF). You can also enter the processor and the start and end times.

●      Warehouse order with physical inventory items

Process physical inventory document (/SCWM/PI_PROCESS and /SCWM/PI_COUNT). Enter the processor and the end time. Entering the start time is optional.

●      Indirect labor (transaction /SCWM/ILT)

Enter the processor and the end time. Entering the start time on the desktop is optional.

●      Maintain value-added services (transactions /SCWM/VAS_I, SCWM_VAS_O, SCWM_VAS_KTS, SCWM_VAS_KTR, SCWM_VAS_INT, /SCWM/VASEXEC). You can use the workload documents in the warehouse management monitor to perform analyses and create performance documents.

○       You can create or delete workload documents for activities of a VAS order for a processor

○       You can create workload documents when confirming activities of a value-added service order.

●      Functions for quality management

○       Process product inspection document (transaction /SCWM/QIDPR)

○       Process HU inspection document (transaction /SCWM/QIDHU)

○       Process delivery inspection document (transaction /SCWM/QIDDH)

○       Work center: quality inspection and counting (transaction /SCWM/QINSP)

○       Inspection document and inspection element: entering the processor and end time

●      RF function (transaction /SCWM/RFUI)

Example

A VAS order exists for an inbound delivery item in the goods receipt process. This order has two activities, which are to be executed at two different work centers.

●      After unloading and goods receipt, the delivered product is taken to the first work center before putaway, where it has to be oiled. This process is described in the first activity of the VAS order. As soon as the product arrives at the work center, an employee selects the respective VAS order at his or her work center using transaction /SCWM/VASEXEC. As soon as he or she starts the activity Oiling, they choose the Start pushbutton for the corresponding activity on the Workload tab page. By doing this, he or she tells the system the time at which they started the activity. After completing the activity, he or she chooses End. He or she then records the amount for which they performed the activity, and saves their entries. By doing this, he or she has created an executed workload document in the system, which they can evaluate using the corresponding monitor node, and with which they can create a performance document.

●      The product is then moved by a corresponding warehouse order to the next work center, where the second activity is performed. The employee at this work center creates the executed workload document in the same way as for the first activity. By doing this, the second employee has also created an executed workload document in the system, which he or she can evaluate using the corresponding monitor node, and with which they can create a performance document.