Page tree
Skip to end of metadata
Go to start of metadata


The purpose of this page is to clarify the search possibilities in the SRM-MDM catalog.


There are two different search options on the SRM-MDM Search UI: the Keyword Search and the Advanced Search. While the Keyword Search searches through every search-enabled field, Advanced Search narrows the search to a single field. Hereinafter you can see the settings of these searches.

  1. MDM Console - Search settings
  2. Data Manager
    1. Search
    2. Named Search 
    3. Mask
  3. Configuration
    1. Config UI - Catalog UI settings 
    2. Customizing - Parameters
    3. BAdI (Initial Search Parameter)
  4. Catalog UI - Search test

MDM Console

The Keyword Search on the SRM-MDM Catalog UI searches through every search-enabled field, the activation of keyword search for a repository field is done via MDM Console. On the "Fields Detail" tab it is possible to choose "None" or "Stemmer". If "None" is chosen the given field will not be searched in case of "Keyword Search" (even if the field is listed on the Search UI).

MDM Data Manager

Search possibilities

The Search Parameters pane (left pane) contains the search tabs for drill-down search, each corresponding to a lookup field in the current table, and one additional search tab for Free-Form Search. At each step along the way, the system narrows down the choice of values for each search dimension to show only those that are valid given the current result set based on the previous search selections. With Free-Form Search, you can perform searches on any field that does not lookup its values from a subtable.

Free-Form Search also allows you to do “fuzzy” searches with various search operators.

Named Search

The MDM Data Manager includes the capability to save the search selections made on a main table to a record on the MDM repository’s Named Searches table. These named searches are available to any user who connects to the repository.

Before you can save search selections to a named search, you must first create a corresponding record on the Named Searches table and identify the main table for which the named search is to be available. The Named Searches table supports a maximum of 400 records (400 named searches). Each time you save to a specific named search record, you overwrite its previously stored search selections.

To use a Named Search on the SRM-MDM UI you have to add a parameter "namedsearch" to the catalog call structure (Detailed information in  SCN Wiki Define External Web-Services - Parameters and values in the Call Structure).

Named searches store the search criteria, and the item list will be created dynamically during each call. 

If the called Named Search doesn't exist in the repository the system gives back all items without filtering it.


Product masks allow you to partition a single master repository main table into as many customized, virtual subset repositories as you like. The main uses of masks are to edit an arbitrary subset of records as a group, and to publish custom “subset catalogs.”

To use a Mask on the SRM-MDM UI you have to add a parameter "mask" to the catalog call structure (Detailed information in SCN Wiki Define External Web-Services - Parameters and values in the Call Structure).

Masks stores a list of items statically.


Keyword Search

The Keyword Search is part of the SRM-MDM Catalog UI. Via this search UI can search all enabled fields of the repository (the activation of keyword search for a repository field is done via MDM Console). This search is to simulate in the MDM Data Manager as a Free Form Search with the 'progressive' search operator.

There is the possibility to deactivate the wildcard search using the asterisk on the left side or in the middle of a keyword search string through the customizing parameter lhwc_searc=false. See SAP Note 1147662 SRM-MDM Catalog: Usage of left-hand wild card. 

Advanced Search

All configuration settings for the search user interface are stored in a user-specific way on the Configuration UI (http://<J2EE_SERVER>:<PORT>/webdynpro/dispatcher/

1. General tab

On the general tab of the Configuration UI you can maintain the following:

  • enable or disable the Contract ID Search,
  • enable or disable the Attribute Search (if it is defined in the repository),
  • enable or disable the Search by all Look Up Fields.

2. Customize Search tab

  • here you can enable or disable the 'Advanced Search',
  • choose which repository fields should be available under the Advanced Search. Any one of the advanced search fields can be of type:
      • Range, which gives you the availability to use corresponding range operators during the search of this field,
      • Free Text where you can also choose the search operator (contains, starts with, etc.),
      • Dropdown.


  • Maximum of 4 free form fields allowed
  • Maximum of 2 dropdown fields allowed


It is also possible to choose the operations to use on the Search UI.

Related Content

Related Documents

Define External Web-Services - Parameters and values in the Call Structure

Related SAP Notes/KBAs

SAP Note: 1147662 SRM-MDM Catalog: Usage of left-hand wild card