Restricting Search Operators in any Search View

Transcription

1 Restricting Search Operators in any Search View Applies to SAP CRM 2007 and SAP CRM 7.0. For more information, visit the Customer Relationship Management homepage. Summary The purpose of this article is to make aware of the Configuration steps required to achieve the functionality of restricting the search criteria for any Search View. Author: Siddhartha Sengupta Company: Mahindra Satyam Computer Services Ltd Created on:1 st Dec, 2010 Author Bio I am a Systems Analyst in Mahindra Satyam Computer Services Ltd working on CRM for the past 4 years, have worked on from CRM 4.0, CRM 5.0, SAP CRM 2007 and currently working on SAP CRM SAP AG 1

2 Table of Contents Overview... 3 Pre-Requisites... 3 Scope Usage Understanding the Requirement... 3 Solution... 4 Related Content... 6 Disclaimer and Liability Notice SAP AG 2

3 Overview We often face problems in adjusting the Operators of the search Criteria. The aim of this article is to guide all the consultants to meet the requirement with simple configuration steps. There are predefined search operators like is, between, starts with etc. Now if we have a specific requirement to restrict it to one or only two operators then we need to follow the below mentioned steps to achieve this instead of going for ABAP development. Pre-Requisites The pre-requisites of this requirement are as follows: 1. You are using SAP CRM version of CRM 2007 and Higher. 2. You have enabled SAP CRM Web UI for Business Users to do their daily jobs. Scope The scope of this document describes the activities to be undertaken in order to restrict search operators in any search view for any attribute, when using SAP CRM Web UI. For reader s better understanding we will take the example of Territory Search to illustrate the functionality. The steps are as follows: Go to Transaction SM34 Open View cluster CRMV_DQ in Maintenance mode. Find the Dynamic Query object you use in the entry list. If not found, then insert a new entry there with component and dquery search object. Insert a new entry and adjust as per new requirement. Usage This document is meant to guide the reader to meet the requirement of restricting search operators in any search view for any attribute. Understanding the Requirement First we need to understand if this document is helpful in meeting the reader s requirement, hence please go through this section and see if the output matches to the desirables. When we log in to the Web UI with a specific Role (e.g. SALESPRO) and we want to search territories then we get the below screen: As we can see that the Territory ID has five operators for search IS, IS NOT, and so on. This Document will help you restrict these operators to one or two operators as desirable per requirement SAP AG 3

4 Solution Go to Transaction Code SM34 Try to find out the search object (in this case it is TERRSEARCH for Component TM). If not found then Insert an entry with the required component and dquery object. The above entry only suggest as a whole search which all operators would be used e.g. for example if there are 10 attributes then for all those attributes this settings would be enough to control them. If we need to make it Attribute specific, e.g. in this case if I want to restrict the Territory ID to be searchable with IS only, then follow the next step SAP AG 4

5 Select the Entry made for TM (Component name) and then Double click on the left hand side folder Exceptions per Attribute and make the entry as below After making the above mentioned changes you should be able to see the following screen in the search view for attribute Territory ID 2010 SAP AG 5

6 Related Content SAP Community Network Forums: Thread describing the same problem as above. Wikis for SAP CRM Web UI Related Topics: SAP CRM Web UI related Wikis. SAP CRM Web UI Guidelines: Guidelines for SAP CRM Web UI For more information, visit the Customer Relationship Management homepage SAP AG 6

7 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 7