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
  • Available Parameters
  • Allowed Value Types
  • Relevant Authorisations

Was this helpful?

  1. Configuration Guide
  2. Customising the screen layout
  3. Detailed screen fields customisation

Extra element types

PreviousException code extrasNextVoice Fields

Last updated 6 months ago

Was this helpful?

Prior to Extra Elements being inserted into an existing screen, they must first be defined. This step can be performed with assistance from the plugin provider, based on a web service’s required parameters. This configuration step is typically performed by a technical team in accordance with the plug-in developer’s requirements.

This ensures the functional team can use the Extra Element Type in the correct way.

Transaction code /TCTM/EWM_CUST - TCT is provided for this purpose. See customising node for EWM under Mobile Data Entry > TCT Mobility > Maintain TCT Mobility Basic Customizing.

The examples below would differ based on the available plugins:

This node allows customisation of additional functionality where available. Element type and description are defined at this level, with additional configuration held at the subsequent lower-level nodes.

Available Parameters

Available parameters are defined per element. The relevant plugin/web service provider should be contacted to understand the available parameters and values needed.

Allowed Value Types

Each Extra Element parameter must also be configured with the permitted types of field maintenance. This ensures that functional consultants abide by the rules of usage for a service.

Relevant Authorisations

Additional screen elements can be assigned SAP authorisations, applying any necessary restrictions during execution.

The relevant authorisations and the application of restrictions ultimately depends on the back-end processing logic built in SAP.

Defining an extra element type for screen usage
Defining the possible parameters for an extra element
Defining the technical type for each parameter
Defining the authorisation requirement for interacting with an extra element