> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-ewm/configuration-guide/configuring-prebilt-features/voice/customising-the-voice-flow-for-a-screen/maintain-basic-configuration.md). # Maintain basic configuration 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 [Display Profile](/prebilt-ewm/configuration-guide/overview.md#display-profile). ## 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. {% hint style="info" %} **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. {% endhint %} ## 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`:

Correspondence Language Example for Voice Picking

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`.

{% hint style="info" %} **Note** To retrieve a product description using the voice language, use function `MAT` when configuring the voice prompt as described in [Using Functions as Voice Prompts](/prebilt-ewm/configuration-guide/configuring-prebilt-features/voice/customising-the-voice-flow-for-a-screen/detailed-screen-field-customisation.md#using-functions-in-voice-prompts). 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. {% endhint %} ### 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:

{% hint style="info" %} **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. {% endhint %} 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).

Storage Type Settings for Bin Verification Using Shapes

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.

{% hint style="info" %} **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. {% endhint %}

Standard PbV Verification Field in Storage Bin Used for Shape Digits

{% hint style="info" %} **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. {% endhint %} ### 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*>). {% hint style="info" %} **Note** When configuring a voice prompt that includes a bin name, use the function BIN as described in [Using Functions as Voice Prompts](/prebilt-ewm/configuration-guide/configuring-prebilt-features/voice/customising-the-voice-flow-for-a-screen/detailed-screen-field-customisation.md#using-functions-in-voice-prompts). {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.theconfigteam.com/prebilt-ewm/configuration-guide/configuring-prebilt-features/voice/customising-the-voice-flow-for-a-screen/maintain-basic-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.