This posting is about how to activate the TM quicksearch, a nice way to access TM transactional documents directly from the NWBC search bar.

Basically it looks like this, enter a search string in the NWBC search bar, get a result list instantaneously:

Quicksearch Example

If you are interested in the functionality, you may check TMP033 ( http://podcast.tm-podcast.com/tmp033-tm-quicksearch/ ), the podcast episode about the topic.

Now, how to activate the TM Quicksearch for you:

1. Install note 2260864 which is available from 9.1 onwards and comes with the required classes

2. Check and/or activate the SICF service:

    To make the search classes available they must be accessible as a service. This is done in transaction SICF. The path is sap->bc. In there add a service      named tm_quick_search. The only tab where you need to maintain something is the handler list, in there enter the      class /SCMTMS/CL_QUICK_SEARCHPROVIDE. It should look something like this:

    SICF_setting.JPG

3. Activate the service

4. Enter the Search provider URL: The easiest way to test the service is to enter the search provider explicitely in the NWBC search provider list. This can be done from the NWBC menu:

    Search Provider Menu path

        The URL is composed as follows:

    First part:

    Your system url and port (you can get this from options->settings->connections in the NWBC menu)

     Important: Define the connection as an https connection, so you are on the save side for both functionality (non-https-connection are not working) as well as                          Transport Layer Security :->)

      Second part:

    /sap/bc/tm_quick_search?type=OpenSearchDescription

    Third part:

    Optionally you can add some parameters like restriction to a certain search class, here is the list of the currently available parameters:

  

Parameter Comment
&stopathit=X If one of the queries found at least one hit, the search is stopped and no other queries are executed -> Recommended for performance optimization
&minimumletters=n n stands for the minimum characters that must be entered before the query is really executed, e.g. &minimumletters=6 means, if the string entered in the search bar has less than 6 characters, the search is not done
&docflow=X Activates the inline document flow -> negarive performance impact, of course, but enables faster navigation if the target of navigation is not the found focument but e.g. a follow-up document of it
&class=classname1,classname2 Defines the class names or class-shortcuts to be used in the search, a list of classes/class shortcuts and the respective usage can be found below, example would be &class=TRQR,TRQ,CFIR to search for TRQ by ID and reference(defined by TRQR and TRQ) and for CFIR(defined by CFIR)

  

Here is the list of classes with the respective shortcuts and explanations, if nothing is defined for the class-attribute,all default classes are used:

Class name Class shortcut Explanation Active by default
/SCMTMS/CL_QUICKSEARCH_TRQREF TRQR Search for TRQ based on Reference ID from document reference node, not active by default
/SCMTMS/CL_QUICKSEARCH_TRQ TRQ Search for TRQ by ID or BASE_BTD_ID X
/SCMTMS/CL_QUICKSEARCH_TOR TOR Generic Search For TOR documents by ID X
/SCMTMS/CL_QUICKSEARCH_CFIR CFIR Search for CFIR by ID X
/SCMTMS/CL_QUICKSEARCH_SFIR SFIR Search for SFIR by ID X
/SCMTMS/CL_QUICKSEARCH_OCEAN OCEAN Search for Ocean bookings by Vessel ID or container ID X
/SCMTMS/CL_QUICKSEARCH_AIR AIR Search for Air Bookings by ULD-ID X

With this, you are done and can use the TM Quicksearch!

4b) You can also integrate the TM quicksearch in the PFCG-role, the required steps are described here

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Sayantan Pal

    hi ,


    We are trying to implement this functionality and did the changes as directed above.


    However we are getting an error. Can you please help us with this issue may be i have missed any steps while i was doing the changes.



    <?xml version=”1.0″ encoding=”UTF-8″ ?>

    <OpenSearchDescription xmlns=”http://a9.com/-/spec/opensearch/1.1/ xmlns:moz=”http://www.mozilla.org/2006/browser/search/“>

    <ShortName>TM Search</ShortName>

    <InputEncoding>UTF-8</InputEncoding>

    <Description>Transportation Management Objects Search TRC100</Description>

    <Url type=”text/html method=”get template=”https://:/SAP/BC/TM_QUICK_SEARCH?type=result&class=&stopathit=a&minimumletters=8&docflow=&q={searchTerms}” />

    <Url type=”application/x-suggestions+xml method=”get template=”https://:/SAP/BC/TM_QUICK_SEARCH?type=suggestionsXML&class=&stopathit=a&minimumletters=8&docflow=&q={searchTerms}” />

    <Url type=”application/x-suggestions+json method=”get template=”https://:/SAP/BC/TM_QUICK_SEARCH?type=suggestionsJSON&class=&stopathit=a&minimumletters=8&docflow=&q={searchTerms}” />

    </OpenSearchDescription>


    reagards,

    Sayantan






    (0) 
    1. Dragos Mihai Florescu

      Did you add the URL manually (It seems that the server part is missing), or per PFCG role? As per my other comment, try using a PFCG role, and implement the latest note as well. It should definitely work afterwards.

      (0) 
  2. Dragos Mihai Florescu

    UPDATE: implement SAP note 2354881 to bring in the latest fixes and enhancements (e.g. possibility to navigate into an external system).

    We strongly recommend to publish the quick search to the users via a PFCG role (follow the hyperlink posted by Bernd in the last paragraph). This way, the client (NWBC) derives automatically the server and port. Adding the URLs manually not only is cumbersome, but also requires maintenace for all relevant systems (e.g. one for test system, one for productive system).

    When defining the URL for the PCFG role, you must merely provide the service path (sap/bc/tm_quick_search) followed by parameters. Examples:

    • /sap/bc/tm_quick_search?type=OpenSearchDescription&stopathit=X&minimumletters=4 (search using default classes)
    • /sap/bc/tm_quick_search?type=OpenSearchDescription&stopathit=X&docflow=X&minimumletters=3&class=TRQR,TRQ,TOR,CFIR,SFIR,AIR,OCEAN (search using all classes, and additionally displays the document flow)

    QuickSearch.png

    Note that the document flow is displayed if and only if the search returns one hit only.

    Best regards,

    DragoČ™ Florescu

    SAP TM Development

    (0) 
  3. a rahim shaik

    Hi,

    we have upgraded our system from 9.3 to 9.4, and make related config for Quick search, but stil the quick search is not working.

     

    Regards,

    Abdul Rahim

    (0) 

Leave a Reply