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
  • Display profile
  • Presentation device
  • Assignment of TCT data entry mode
  • Determination of RF menu
  • Assignment of presentation device

Was this helpful?

  1. Configuration Guide
  2. Configuring PreBilt features
  3. Voice

EWM RFUI requirements for Voice

PreviousVoiceNextFunctional scope

Last updated 5 months ago

Was this helpful?

Display profile

To use PreBilt and customise the voice flow of a screen, a new Display Profile for VoiceDirect must be generated in the standard RF framework.

To generate a Display Profile, see standard customising node for EWM under Mobile Data Entry > Radio Frequency (RF) Framework > RF Screen Manager.

The standard profile ** can be copied to a new key, available in the customer namespace as shown below.

  • Template Location – use TCT template function group ZTCTM_EWM_RFUI_TEMPL with screens 1000 and 1001 as shown in Figure 1.

Presentation device

A Presentation Device for VoiceDirect must be created in transaction /SCWM/PRDVC, such as ZV05 shown in Figure 2, and assigned to the relevant Display Profile.

Assignment of TCT data entry mode

A PreBilt-specific data entry mode ‘1 – Voice Only’ must be assigned to the Presentation Device in transaction /TCTM/EWM_SETTINGS.

Determination of RF menu

If the same operator uses a voice device or an RF device based on the warehouse processes to execute, it may be desirable to have a different RF menus for each case.

PreBilt offers the ability to determine a different Personalization Profile and main menu based on the User, Warehouse Number, Resource Group, and TCT Data Entry Mode.

If the User, Warehouse Number or Resource Group fields are left blank, they behave as wildcards.

Example

Voice users should only have access to ‘System-Guided’ menu, whereas RF users should have access to all RF menus and transactions.

The TCT Data Entry Mode (Screen Only or Voice Only) can be used to determine a different Personalization Profile/Main Menu as shown below.

Example

RF users should have access to different menus and transactions based on the Resource Group they are assigned to.

The Resource Group and TCT Mode can be used to determine a different Personalization Profile/Main Menu as shown below.

Assignment of presentation device

The Presentation Device must be assigned in the VoiceDirect Task Package Settings in parameter SAPEWMPresentationDevice, as shown below. This ensures it is defaulted and not required as an input in the standard resource logon RF screen.

Generating a New Display Profile
Maintaining a Presentation Device
Assigning the TCT Data Entry Mode to the Presentation Device
Determining Different RF Menus
Presentation Device Assignment in VoiceDirect Task Package Settings