Custom F4 search help is one of the customer-centric developments done in SAP SRM User Interface Add on. The framework utilizes the potential of the DDIC search helps which are the core of SAP applications.

SAP SRM UI Add on provides an extensibility framework and with this customers can easily enhance the UI5 views with minimal effort. For more information on extensibility refer to Extensibility in SAP SRM User Interface Addon 1.0 .

SAP SRM UI Add on received a tremendous response for the framework as it reduces implementation efforts by leaps and bounds. But implementation team may have faced more problems while writing the OData services for each search help added through extensibility framework. For reducing the implementation efforts SAP SRM UI Add on provides a new framework through which customer can easily create a F4 search helps for custom fields. A search help field can be added to UI5 view using extensibility framework and data can be retrieved using the potential of DDIC search helps. 

The below is an example of adding a new search help in Can’t Find view. Below is the screenshot of Can’t Find screen before adding the search help field:

 

For adding a search help follow the steps given below :

/wp-content/uploads/2014/05/1_461844.png

1) Execute transaction SPRO then click on ‘SAP Reference IMG’

/wp-content/uploads/2014/05/2_461845.png


  2) Goto SAP Implementation Guide -> SAP Supplier Relationship Management -> SAP SRM User Interface Add on -> Extension and Field Controls -> Configure Extension and Field Controls 

/wp-content/uploads/2014/05/3_461849.png

3) Add a new element/property into the ODATA Model using extensibility framework. Mark the field as ‘Search help’ and in ‘Search help Name’ field give the DDIC search help name, make sure this search help is elementary search help.

/wp-content/uploads/2014/05/4_461850.png

4) Open ‘Search Help Field Mapping’ in the left pane, and create a new entry with search help field name and to which model field the search help field has to mapped. Multiple entries can be maintained here.

  /wp-content/uploads/2014/05/5_461851.png

5) Click on Save button

Re-launch the application , a new search help field is visible in Can’t Find screen

/wp-content/uploads/2014/05/6_461853.png

On click on F4, the data is visible in an overlay from where the user can select the value

7.PNG

Note : Please note that you should add fields to model only if fields are not present in corresponding ODATA model, In case if you are adding properties to model then clear the gateway model cache using transactions /iwfnd/cache_cleanup and /iwbep/cache_cleanup and rebuild cache by executing /SRMNXP/REBUID_CACHE report.

To report this post you need to login first.

1 Comment

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

  1. Karthik Babu Pulluru

    Hi,

    Thanks for sharing the information.

    I have a query. I tried this. But this is creating an additional field on the screen. But if the field already exists in the screen, is there a possibility? Also, when I checked the ID for the newly generated field, it is prefixed with the view name, suggesting that the standard considered it as one of the custom fields even when bound to a std field.

    Best Regards,

    Karthik

    (0) 

Leave a Reply