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
  • Search Objects (Global)
  • Search Objects Attributes (Global)
  • Unified Search Scenarios
  • Search Objects (Scenario Specific)
  • Search Object Attributes (Scenario Specific)
  • Assign Delivery Types to Search Object (Scenario Specific)
  • Index Table Refresh
  • RF Menu Maintenance

Was this helpful?

  1. Configuration Guide
  2. Configuring PreBilt features

Unified Search Configuration

PreviousEmbedding Analytics into PreBiltNextInstallation

Last updated 5 months ago

Was this helpful?

The SPRO path to configure unified search is SCM Extended Warehouse Management > Extended Warehouse Management > Mobile Data Entry > TCT Mobility > Receiving > Unified Search Configuration.

Prerequisite

The PreBilt EWM Receiving App /TCTM/EWM_APP_RECEIVE must already be installed. Please refer to for app installation guidance.

Prerequisite

An application log sub-object must be maintained for unified search. In Transaction SLG0 and under object /SCWM/WME create the sub-object entry /TCTM/RECEIV_UNIFSRC as in the example below.

Search Objects (Global)

Objects must be defined at a global level. Note the document determination is BAdI driven, so there is no additional configuration required. However, the objects must be specified with the correct object texts, together with the relevant framework option, to be recognised. The description text can be amended if required.

The default implementation of the Unified Search uses the exact entries shown above. Customers can implement their own logic via an implementation of BADI /TCTM/EX_EWM_APP_RCV_USRCH_OBJ.

Search Objects Attributes (Global)

Search Object Attributes data is displayed in the unified search list view. As with search object attributes, these must be defined at a global level before they are assigned within a Unified Search Scenario. The attribute determination is BAdI driven, so no additional configuration is required to determine attributes.

The default implementation of the Unified Search uses the exact entries shown above. Customers can implement their own logic via an implementation of BADI /TCTM/EX_EWM_APP_RCV_USRCH_ATT.

Unified Search Scenarios

A Scenario at the top level defines by warehouse where Unified Search will be active. The following conditions can be set at this level.

  1. Minimum Characters: The minimum number of characters required to return a search result.

  2. Logical Transaction: The corresponding Logical Transaction for this Unified Search Scenario.

  3. Default Object: Default delivery object (typically EWM Inbound Delivery).

The sub criteria (objects, attributes and delivery types) are then assigned to a scenario to determine what information is displayed within the transaction, as well as under which conditions the information is displayed.

Search Objects (Scenario Specific)

Search Objects (already defined globally) are here assigned to the Unified Search Scenario. Past Days & Future Days (relative to the expected delivery date) can be defined by search object according to customer needs.

Search Object Attributes (Scenario Specific)

Search Object Attributes (already defined globally) are assigned to the Unified Search Object. This displays together with and underneath the configured Search Object description in the Unified Search list result. In the example below, this is shown for an ECC Inbound Delivery with Date and Supplier specified as Search Object Attributes.

Assign Delivery Types to Search Object (Scenario Specific)

Delivery document types are assigned to search objects. The standard delivery document search help can be called to select relevant delivery documents.

Index Table Refresh

The solution is designed to use an index table, which provides results to the front end with fast response times. The relevance of documents is evaluated during the create/change of the documents. It may be necessary to refresh the index to ensure correct results. This can be achieved by scheduling report /TCTM/EWM_APP_RECEIVE_UNFSRCH as a daily batch job.

RF Menu Maintenance

The SPRO path to configure the RF Menu is SCM Extended Warehouse Management > Extended Warehouse Management > Mobile Data Entry > Radio Frequency (RF) Framework > RF Menu Manager.

Assign the object RHZUDS to the menu for the relevant presentation profile.

PreBiltâ„¢ for EWM App Installer
Creating a sub-object entry
Object definition
Attribute definition
Scenario definition
Scenario Object definition
Scenario Object Attribute definition
In app example of applied Scenario Object Attributes
Scenario Object Delivery Type definition
Scenario Object Delivery Type selection help
Scheduling index table refresh