Show TOC

Function documentationWorking with RF for Pick by Voice Locate this document in the navigation structure

 

The pick by voice transaction has no selection screen; only system-guided work is possible. This means that the system assigns the next warehouse order to the resource. The validation fields are customizable and can be switched on and off according to user preference and knowledge, and the current process data. You can make these settings in Customizing for Extended Warehouse Management under   Mobile Data Entry   Verification Control  .

Features

The main pick by voice procedure consists of the following steps:

  1. Warehouse order overview (PVHUIN)

    The user is informed that there is a new warehouse order and gets the activity area where the picking takes place, and the amount and type of pre-assigned pick-HUs. The user can confirm the information and continue with the next step, or trigger printing using a command. The text of the packaging material given to the user is the short product description of the packaging material from the product master. A maximum of two different packaging materials are supported in the prompt text. Entries without a HU number are ignored.

  2. Source storage bin for product WT (PVMTTO)

    The user gets the source storage bin information (separated into storage type, aisle, stack, and level), the product, the quantity, and the destination pick-HU. If the user has more tasks to pick for this warehouse order, this step is repeated until all tasks are picked.

    The user is guided to the source storage bin and must enter the verification value of the storage bin master. In the standard setup, the product is not validated. For the stack, the validation is either the value or the verification value from the storage bin master. For the storage bin validation, the user only has to validate the difference between one storage bin and the next.

    If there is a difference, the user can use the command “Difference”, and then speak the actual quantity that is in the bin. The difference quantity is calculated from the requested quantity minus the entered quantity. If the default difference type does not match, the user can trigger a different difference exception from the exception code list screen. You can maintain a default difference exception code for the internal exception which decides the kind of difference in Customizing for Extended Warehouse Management under   Cross-Process Settings   Exception Handling   Assign Internal Exception Codes to Exception Codes  .

  3. Destination storage bin for HU-WT (PVPLHU)

    The user gets the destination storage bin information (separated into storage type, aisle, stack, and level), and the pick-HU which has to be put away. If the user has more pick-HUs to put away in different destinations, this step is repeated until all of them have been put away.

    The validation of the destination bin depends on the storage bin master data. If the master data contains aisle, stack, and level information, this is used for the validation. If the user has to put more than one HU at the same destination, the system does not require the user to validate each HU separately; the user can place the HUs in one step.

The following screens are also voice-enabled:

  • Source storage bin for HU WT

    Guides the user to the correct source storage bin to take the HU.

  • Destination storage bin for product WT

    Guides the user to the correct destination storage bin to put away the appropriate quantity of a product.

  • Stock check

    The system has determined a low stock check situation for the current storage bin. This screen is displayed and the user has to enter the remaining quantity.

  • Change destination bin

    The user realises that the proposed destination storage bin is full or cannot be reached, and enters a new storage bin or lets the system propose a new storage bin.

  • Semi-system guided picking

    The system identifies that the queue of the resource contains several HU moves from a particular area. The user is guided to this area and must select a HU there. Then the picking process starts as normal.

HU Validation

The voice-enabled transaction has a specific verification logic for the HU. To avoid the user having to speak the complete HU number, the system determines the minimum number of digits from the end of the HU number that are needed to get a unique result in the storage bin. The amount of digits is spoken to the user. The user has to say at least two digits, regardless of how many are needed to make the HU number unique in the bin. For example, instead of saying the entire HU number “376170137518461130”, it could be sufficient to say “30”.

Split Storage Bin into Separate Fields

Instead of telling the user the complete storage bin, such as “0010-01-05-B”, it is easier to split the storage bin into storage type (0010), aisle (01) , stack (05), and level (B). For storage type, aisle, and stack there is one-to-one validation. For level, the validation field of the storage bin master is used. The system only tells the user the difference between the storage bins of the previous WT and the current WT, for example, if the next bin is in the same aisle as the previous one, the system starts with the stack and not with the storage type. If the aisle, stack, and level are not maintained in the storage bin master, the system speaks the entire storage bin to the user.

More Information

Exceptions