This blog post details about extending the fields of Search Results of the Cross Catalog search of SRM UI Addon for Shopping Cart. For those who are not aware of the Shopping Cart UI Addon, I would suggest you to have a look here. The UI looks really cool and the addon provides multitude of functionalities including the cross catalog search option which helps the user to search across multiple catalogs.

Extensibility of Search Results:

The standard Search results contain the following details:

  • Product image
  • Product short description
  • Price
  • Average user rating
  • Supplier
  • Manufacturer
  • Internal catalog name
  • Manufacturer part number

This looks something like this in the UI: (This item is for representational purpose only)

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

If the customer wishes to add more fields here, this can be done easily using the Extensibility concept available for the addon. (More information regarding extensibility can be found here). To achieve this the customer must implement note 1962526 ( if in SP04 or below). We would now discuss the steps which the customer can follow in order to add extra fields in a series of snapshots.

1) Launch spro transaction and move to the following node: SAP Supplier Relationship Management > SAP SRM User Interface Add-on > Extensions and Field Controls > Configure Extension and Field Controls.

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

2) In this node, you would be able to see the following view if the manual instructions in the note 1962526 were followed.

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

3) By selecting the view and clicking on “Field Definition”, we would be able to see the custom fields which we have added to search results. This list is empty in the following image as we have not configured any custom field yet.

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

4) To add a custom field, select “New Entries” from the toolbar. This would open up the following view and we can enter a new field here. I have given a name ‘zfield’. As we can see, native support for extensibility is given to the following four controls in the dropdown.

13.PNG

5) Once control type is selected, we could select a binding element from the model. ( This model can also be enhanced with customer fields by using the addon extensibility support for OData models).

12.PNG

6) After the binding elements are selected, we must give an OTR field for Label and tooltip. This example uses an OTR named /ZOTR/MANUFACT_CODE which represents the text “Manufacturer Code”.

11.PNG

7) Once the changes are saved, cache is cleared and application is relaunched, the user can see the new field in the UI.

/wp-content/uploads/2014/05/10_461859.png

Extensibility of Search Filter:

The search results of the cross catalog search are associated with a dynamic and responsive filter, which the user can use to narrow down the search results based on the filter criteria. The standard filter criteria which are available are the following:

  • Price Range
  • Category
  • Catalog
  • Supplier
  • Manufacturer

Enhancing the filter is not straight forward like the search results and requires advance javascript knowledge due to its dynamic and responsive nature. But still the customers can enhance the filter criteria by implementing the notes 1962526 and 1951052. Once these notes are implemented, please follow the detailed instructions available in the files attached to the notes – Cookbook -New filter categories.pdf and Cookbook -New filter categories_frontend.pdf.

[ Edit: In addition to the above mentioned notes, note 2077528 might be required for search extensibility to work if the customer is on SP04 or SP05, please refer to the note for more details ]


Feel free to reach out with your feedback and queries. 


Riswan

mohamed.riswan.abdul.lathif@sap.com

To report this post you need to login first.

1 Comment

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

  1. Iliya Kaluzhny

    Hi.

    According to note 1951052 some code should be added to standard views and controllers. Does that mean that it is standard code modification?

    (0) 

Leave a Reply