The Config Team Ltd
Contact usDemo App
PreBilt™ for EWM
PreBilt™ for EWM
  • PreBilt for EWM
    • Overview
    • Functionality
    • Frequently asked questions
    • Release notes
      • v4.13 release notes
      • v4.12 release notes
  • Installation
    • Minimum requirements
    • Prerequisites and assumptions
    • Backend installation
    • Frontend installation
    • UI deployment
  • Configuration Guide
    • EWM RFUI requirements
    • Initial generation of EWM ITS screen templates
    • Overview screen of technical information
    • BC sets
    • Customising the screen layout
      • Logical Transactions and Step Header
      • Detailed screen fields customisation
        • Replacement field labels
        • Field type
        • Toggling a drop-down list
        • Hiding field borders
        • Hiding a field from display
        • Hiding a field from display when empty
        • Making a field read-only
        • Setting the display row for a parameter
        • Setting the visual length of a parameter
        • Setting the position of a parameter on the row
        • Maintaining table types for step-loop table functionality
        • Assigning field roles for table types
        • Maintaining a hint text
        • Defaulting a parameter value
        • Setting a parameter label's font style, size and colour
        • Setting a field value font style, size and colour
        • Adding a new screen field
        • Enhanced UoM selection
        • Defining Extra Screen Elements
        • Function code overrides
        • Menu extras
        • Function code extras
        • Exception code extras
        • Extra element types
        • Voice Fields
    • Translations
      • Downloading translations
      • Transforming the data
      • Uploading translations
    • Configuring PreBilt features
      • Communication Hub
      • Gamification
        • Competitions
        • Challenges
        • Game Monitoring
      • Voice
        • EWM RFUI requirements for Voice
        • Functional scope
        • Initial generation of ITS templates and customising for voice
        • Overview screen of technical information
        • Customising the voice flow for a screen
          • Maintain basic configuration
          • Maintain TCT mobility basic customising
          • Logical transaction and step header
          • Detailed screen field customisation
        • Master data
      • Analytics
        • Installation
        • Embedding Analytics into PreBilt
      • Unified Search Configuration
        • Installation
      • Image Capture
  • Using PreBilt
    • Screen elements
    • Process steps
    • Validation messages and troubleshooting
    • Operator messaging
    • Gamification
    • Troubleshooting
Powered by GitBook

Help

  • Can't find what you're looking for? E-mail us.

© The Config Team 1994 - Present Day

On this page
  • Password prefix
  • Password input
  • Welcome prompt
  • Password prompt
  • Password help prompt
  • Maintain voice utilities settings
  • Voice language
  • Bin verification using shapes
  • Bin name patterns

Was this helpful?

  1. Configuration Guide
  2. Configuring PreBilt features
  3. Voice
  4. Customising the voice flow for a screen

Maintain basic configuration

PreviousCustomising the voice flow for a screenNextMaintain TCT mobility basic customising

Last updated 5 months ago

Was this helpful?

Basic configuration settings for Voice are maintained in the customising node for EWM under Mobile Data Entry > TCT Mobility > Voice Execution > Maintain Voice Utilities Settings (below), against the previously created .

Password prefix

When an operator logs into a Talkman device and is asked for their SAP password, a predefined prefix can be automatically added. This is useful for companies with strict password guidelines, such as requiring a mixture of letters, numbers, and symbols. A business rule can be defined to ensure all voice operators' passwords start with the same prefix, while the operator provides a numeric suffix as their input. PreBilt combines the prefix with the spoken numbers and sends the full password to SAP for authentication.

Example

If the password for an SAP user is ‘P@ss67023’, where the prefix for all voice users is configured as ‘P@ss’, the operator simply says “67023” during logon.

Password input

Defines the type of input expected for the password:

  • GetBarcode – activates the device barcode scanner for input.

  • GetNumeric – expects a spoken numeric input.

Welcome prompt

Defines the welcome prompt spoken to the operator upon turning on the Talkman.

Password prompt

Defines the prompt spoken to the operator to request the user password.

Password help prompt

Defines the help prompt for password input when the “talkman help” voice command is invoked.

Maintain voice utilities settings

Certain voice settings like voice language key, bin verification using shapes, and bin name patterns are configured in the customising node for EWM under Mobile Data Entry > TCT Mobility > Voice Execution > Maintain Voice Utilities Settings.

These settings are explained in detail in the following sections.

Voice language

The default description for a product as maintained in the product master is not necessarily compatible for voice-directed operations. It may contain unreadable strings or words in uppercase, for example. To address this issue, a new language key for a ‘Correspondence Language’ can be configured in standard transaction I18N in ERP and EWM (if decentralised). See customising node under I18N Menu > I18N Customizing > Correspondence Language:

Creating a new correspondence language enables the maintenance of a parallel product description in the additional basic data view of the material master (transaction MM02 in ERP) that can hold a description which is more suitable to be spoken, as shown below.

The language key to be used to retrieve voice-friendly product descriptions must be assigned at Warehouse level in the customising node for EWM under Mobile Data Entry > TCT Mobility > Voice Execution > Maintain Voice Utilities Settings.

Note

Bin verification using shapes

When traditional check digits are used for storage bins, warehouse operators can easily memorise them, especially in fast-moving locations. This may allow them to pre-verify a storage bin during warehouse task confirmation even if they have not reached it physically. This is far from good practice and unfortunately forces warehouse administrators to frequently having to re-generate and re-print check digit labels to minimise this occurrence. Of course, this puts an undesirable extra burden on the warehouse operation.

To address this problem, PreBilt has a storage bin verification solution which assigns random check digits and various associated shapes to each storage bin, which are printed on a label as per this example:

Example

When the voice system instructs the operator to go to a specific storage bin in the warehouse, it randomly chooses a shape for the operator to verify, such as, “Say check digits for circle”. The operator must read the digits for the requested shape, which in the example above corresponds to ‘983’. It is important to note that for every picking task the system randomly selects the shape to verify, so a different pick from the same storage bin might later result in “Say check digits for square” which would require a ‘078’ response to be correct. This method of advanced verification reduces the possibility of check digit memorisation.

In the customising node for EWM under Mobile Data Entry > TCT Mobility > Voice Execution > Maintain Voice Utilities Settings the following settings can be defined at under the Storage Type node:

  • Use Shapes – the use of shapes for bin verification can be activated for a storage type with this check box.

  • Check Digit Length – refers to the number of digits the generator will assign to each shape. The concatenated string of check digits for all shapes is saved into the standard field /SCWM/LAGP-PBV_VERIF in the storage bin.

  • Uniqueness – indicates the level of uniqueness required (if any) for check digits for each storage bin within a predefined range of bins around it, in terms of number of aisles and stacks on either side of the bin. This can ensure a check digit value assigned to a storage bin is unique for a specific shape, or across all shapes within an area. This eliminates the chance of two storage bins in close proximity having the same check digits, which could lead to accidentally picking from the wrong location, as the system would correctly verify the bin since the check digit matches.

  • Aisles for Uniqueness – refers to the number of aisles on either side of each storage bin where the generator will ensure the uniqueness of the check digits (if uniqueness is required).

  • Stacks for Uniqueness – refers to the number of stacks on either side of each storage bin where the generator will ensure the uniqueness of the check digits (if uniqueness is required).

Use the Shape Definition node for each storage type to configure the shapes to be used for verification. Enter a name for each shape, the position of the shape, the shape bitmap (defined in transaction SE78) and its voice description. Any type of visual shape or image can be used.

Note

The number of shapes defined for a storage type, times the check digit length must not exceed 18, which is the maximum length of the standard PbV verification field in EWM.

Shape Check Digit Generation

PreBilt offers a shape check digit generator for storage bins. This is delivered through a custom BAdI implementation (ZEWM_BI_CORE_SB_VERIFY) to fill the verification field in storage bins.

The check digits can be assigned for required storage bins automatically using standard transaction /SCWM/LX45, by selecting the ‘BAdI’ and ‘Edit PbV Verification Field’ radio buttons in the selection screen. The system will generate the check digits string for shapes against the selected storage bins according to the customising settings for each storage type.

Storage Bin Label Printing

PreBilt offers the following template storage bin label (Adobe Form) for shape verification: /TCTM/EWM_BIN_SHAPE_FORM. This can be further customised to match specific customer requirements.

This label can be printed using standard transactions /SCWM/PRBIN - Print Storage Bin Label or /SCWM/PRFIXBIN - Print Fixed Bin Label.

Bin name patterns

Storage bin names as stored in /SCWM/LAGP-LGPLA may contain certain characters which should not be considered when speaking a bin name during a voice flow. For this purpose, a bin name pattern can be defined at Storage Type level in the customising node for EWM under Mobile Data Entry > TCT Mobility > Voice Execution > Maintain Voice Utilities Settings.

Multiple patterns can be defined for each storage type, by assigning a sequence number. Define the following:

  • Source Bin Pattern – this is defined using Regular Expressions (RegEx). Only strings defined within brackets () are extracted to form the voice bin name.

  • Destination Bin Pattern – each string defined within brackets in the Source Bin Pattern is identified with &1, &2, &3, etc. and can be used to form the spoken bin name. Other characters can be added such as commas, to add a pause between strings (e.g. <aisle>, <stack>, <level>).

Note

To retrieve a product description using the voice language, use function MAT when configuring the voice prompt as described in . The system first tries to retrieve the product description using the defined voice language key. If no entry is found, the system retrieves the description using the logon language key.

When configuring a voice prompt that includes a bin name, use the function BIN as described in .

Display Profile
Using Functions as Voice Prompts
Using Functions as Voice Prompts
Correspondence Language Example for Voice Picking
Material Voice Description Maintenance
Voice Language Key Assignment
Sample Shape Verification Bin Label
Storage Type Settings for Bin Verification Using Shapes
Shape Definition for Bin Verification
Standard PbV Verification Field in Storage Bin Used for Shape Digits
Defining Bin Name Patterns