Case Sensitivity in Search

I'm not sure exactly where to look for a solution for this.
But in Quotation search BT115QS_SLSQ if I search by a field say "Customer Request #" or any field for that matter.
and search for OZ I got 100s of records.
But if I search for oz I only get one record.  It appears search is done using case sensitive search, that is SAP CRM thinks:
Joz Doe is not the same as JOZ Doe.  Is there a way to change this so that the search does not care about whether letters are upper case or lower case ??
Thanks!

Hi Murali,
<li> Go to Layout of the screen
<li> Double click on input field - Field attributes popup is displayed.
<li> You will see Upper/Lowe case Checkbox. If you select that checkbox, It keeps the data entered as it is. If you do not select that check box, It always converts to Upper case.
I hope that it solves your problem.
Thanks
Venkat.O

Similar Messages

  • CSS cookieurl: case sensitive?

    Hello,
    As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
    The settings look like this:
    content stickyCookie
    advanced-balance cookieurl
    string prefix "SESSION_ID="
    On the HTTP header the cookie field looks like this:
    Set Cookie: SESSION_ID=ABCDEF
    But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
    http://localhost/Info/index;session_id=ABCDEF?page=home.
    Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
    So I am afraid there is no way of making this work on a CSS?
    Any help will be much appreciated!

    Hi Javier,
    The Cisco CSS is case-sensitive when searching for this string.
    When configuring the CSS 11000 and 11500, determine first if you need a server cookie string. If the string operation under the content rule is match-service-cookie, which is the default setting, this parameter must be configured. In this case the service cookie string is matched against the cookie contained in the HTTP header for load balancing decision.
    If the string operation under the content rule is set to the hash method, this parameter is not needed. In order to select one of the available servers, the cookie contained in the HTTP header is mathematically processed using a hashing algorithm. If available, the hash algorithm assigna the connection carrying a certain cookie to the same server. This example focuses on the match-service-cookie case.
    Note: Cookies are case sensitive.
    Configuring the Service
    training4(config># service server_g
    training4(config-service[server_g])# string LV2KJK (the server cookie text)
    training4(config># service server_h
    training4(config-service[server_h])# string AARIKA
    Configuring the Content Rule
    Note: Cookies require a Layer 5 rule.
    You can create a Layer 5 rule by adding a URL.
    For example, .
    A Layer 4 rule can be promoted to a Layer 5 rule by issuing the advanced-balance cookies command.
    Choose the advanced-balance method.
    training4(config-owner-content[cookie-layer5])# advanced-balance cookies
    Configure the string operation.
    training4(config-owner-content[cookie-layer5])# string operation ?
    match-service-cookie (DEFAULT)
    hash-crc32
    hash-xor
    hash-a
    Define the starting/ending bytes.
    training4(config-owner-content[cookie-layer5])# string range 1 to 200
    Start byte position of cookie/url after header (Range:1-600)
    Specify the prefix located in the string range.
    training4(config-owner-content[cookie-layer5])# string prefix "ASPSESSION"
    "Quoted textual information"(Len: 0-32)
    Indicate how many bytes to skip after the starting prefix.
    training4(config-owner-content[cookie-layer5])# string skip-length 9
    "Quoted textual information"(Len: 0-32)
    Indicate how many bytes after the prefix/skip-length make-up the string.
    training4(config-owner-content[cookie-layer5])# string process-length 6
    Integer value(Range: 0-64)
    If no string process length is configured, search after end of string character.
    training4(config-owner-content[cookie-layer5])# string eos-char "&"
    "Quoted textual information"(Len: 0-5)
    Specify the failover in the event that a server goes down or is suspended.
    training4(config-owner-content[cookie-layer5])# sticky-serverdown-failoversticky-srcip
    sticky-srcip-dstport
    sticky-srcip
    balance (Default)
    redirect
    reject
    Below is an example of a cookie string, and how some of the parameters work.
    ASPSESSIONJJKKJJKK=LV2KJK44444444
    !--- The string prefix = ASPSESSION.
    !--- The string skip-length = 9. Skip
    !--- nine characters after the prefix.
    !--- The string process-length = 6, which would make
    !--- the string LV2KJK matching service server_g.
    ASPSESSIONSQPMMJHK=AARIKAMDESLD
    !--- Matches service server_h.
    Below is a sample configuration for the cookie strings.
    !************************** SERVICE **************************
    service server_g
    ip address 172.17.63.240
    string LV2KJK
    active
    service server_h
    ip address 172.17.63.241
    string AARIKA
    active
    !*************************** OWNER ***************************
    owner braden
    content server-cookie
    protocol tcp
    vip address 172.17.63.199
    port 80
    advanced-balance cookies
    string range 1 to 200
    string prefix "ASPSESSION"
    string skip-length 9
    string process-length 6
    add service server_g
    add service server_h
    active
    Kindly tell if this information is of any use to you.
    Sachin garg

  • Task - Incase Sensitive for Searching User in popup

    In Task Details page, Is it possible to make the 'Filter Value' text field "*Incase sensitive*" right now the its <case sensitive> while searching for First Name/Last Name/Email in Search a User in popup window.
    Thanks, appreciate your help.

    Mahesh, in R16 this will not be case sensitive.

  • Is a Full Text Index search case sensitive or not in SQL Server 2012?

    I setup full text index on my contact table and am attempting to run a search on it using the following query:
    SELECT *
    FROM sysdba.Contact C
    WHERE CONTAINS(C.FirstName, 'Test')
    OR CONTAINS(C.LastName, 'Test')
    The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
    1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
    Case sensitivity
    Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
    is not supported.
    1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
    Full-text queries are
    not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
    Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
    (Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
    Thank you for your time and help,
    Hanan

    Whats the collation setting for the columns? try using a case insensitive collation as below
    SELECT *
    FROM sysdba.Contact C
    WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
    OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • How to get Case Sensitive Check Box at Search Page

    Hi Everyone,
    I am trying to get case sensitive check box at the bottom of the search page, for that we have to set any propert or we ahve to do anything else.
    Please Help!!!!
    Thanks,
    Amit

    Have never really thought of it. One thing you need to do is set the Case Insesitive Searching Option correclty in PeopleTools Options. I can't find any other setings. But it might have to do with the fields that are on your Search record. My guess is if any of the Search Fields are of type Character and format Mixedcase then the Case Sensitive check box will be displayed automatically.

  • Business Partner search (case sensitive)

    I create a Business Partner with the following details
    FirstName - Vikram
    LastName - Chandna
    When i search the created Business Partner via Tcode-FPP3 by name, the
    search is case In-Sensitive(i.e Font case doesn't matter)
    But, when i search the same in the Database table-BUT000 directly or in
    the SAP Query/Reports , the search is Case-Sensitive.
    Why?
    Thanks & Regards,
    Gagan

    Hi Gagan,
    The field BU_SORT1 in Table BUT000 which is for search option has data type as Character without Lowercase.If the Lowercase option (in the output characteristicks)  is ticked in the table, the sytem will allow you to search based on Lowercase as well.
    Regards
    Amitav

  • Case sensitive and case insensitive Search

    Hi friends,
         Iam doing an Search RFC which will search records based on the search parameters provided at the portal side.
    One of the search parameter is a field with 40 character which holds the description(title) of the record.
    With this search paramter iam facing case sensitive problem.
    Example:
    Values in Database Table: ( Can be in any case)
           Record 1:  Sensitive
           Record 2:  SENSITIVE
           Record 3:  SensTive
           Record 4:  sensitive
           Record 5:  sensTive
         Input to RFC:  sens*
         Output: Getting only 4rth and 5th record but not all the records.
           The same is the case with the remaining search parameters(Like user name..).
           Is there any way of getting all the records when searching from the data base (with case insensitive).
           Kindly let me know if there is any possibility.
    Thanks in advance.
    Regards,
    Swarna Munukoti.

    Generally, no.  So, you'll either have to use EXEC SQL, or add more fields to the table.  You can do this using APPEND structures, which is the SAP approved way of adding fields.  If there are suitable user exits in the standard SAP code, then you'll be able to populate the additional fields there, as new records are created, or amended.
    Alternatively, create your own Z table with the same key as the standard table and a "search field" which contains the uppercase version of the field you're wanting to search.  You can either, again populate in suitable user exits, or, in worst case, have job that runs regularly populating your Z table.
    matt

  • How do I make search case sensitive

    I created a search region of type "query" using a simpleSearchPanel. The instructions say the search is case-sensitive when running the page but it appears it is not. Can anyone tell me how to make the search case sensitive?

    Please check if you have followed these guidelines
    Rule 2 : If your view attribute is of type String(VARCHAR2), and if the item has the Selective Search Criteria property set to false, then OA Framework generates a case-insensitive simple WHERE clause based on the CRITERIA_CONDITION and the CRITERIA_VALUE.
    Rule 3: If your view attribute is of type String(VARCHAR2), and the item has the Selective Search Criteria property set to true, then OA Framework generates a case-insensitive WHERE clause using a four-way join to ensure that the index is used.

  • Change Case-sensitivity of field ASKTX in Search Help ASMD

    Hi experts,
    In Collective Search help ASMD, there is a elementory search help /SAPBOQ/ASMD_MITEM where field ASKTX is Case sensitive.
    How can I remove the case-sensitivity of this field ?
    Thnks in advance,
    Goutam

    owngoal wrote:
    You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
    Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
    See #C13 in Time Machine - Troubleshooting for details.
    And by this stage is it too late to recover anything?
    Sometimes.    Sometimes they can be repaired by Disk Utility.  Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them.  Sometimes nothing can.  Sometimes you can restore some individual items, sometimes not.  Sometimes you can do a full system restore from some backups, other times not.
    does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
    Probably -- you won't have WIFI interference.
    But if you have an iMac, why not just connect the external HD directly to your Mac?  That's much faster and more reliable (and supported).
    You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup.  Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

  • Case Sensitive problem in Select Option for wild card search

    Hi,
         Can anyone please let me know how to make the wild card search in any select-option non case-sensitive. What I mean by this is for eg. we want to find out all the POs with short text containing the word  'process', what we do we populate a range with OPTION = 'CP' and LOW = 'process' and select EKPO with short text in this range. This select is however case-sensitive and POs with short text containing 'Process' is not retrieved. But my requirement is that this should be non case-sensitive and both the POs should be in the result set.

    Hi,
    Hope this helps you
    CS:
    You can select characters in operand2 for a direct comparison by adding the escape symbol "#" before the required characters. For these characters, upper/lower case is taken into account, wildcard characters and the escape symbol itself do not receive special treatment, and trailing blanks in operands of type c are not cut off.
    Covers Pattern: True, if the content of operand1 fits the pattern in operand2. Wildcard characters can be used for forming the operand pattern, where "" represents any character string, and "+" represents any character. Upper/lower case is not taken into account. If the comparison is true, sy-fdpos contains the offset of operand2 in operand1, whereby leading wildcard characters "" in operand2 are ignored if operand2 also contains other characters. If the comparison is false, sy-fdpos contains the length of operand1.
    Regards
    Krishna

  • Query Variable: F4 search by Text is case sensitive in Web Templates.

    Hello Guru's,
    I have a problem, when I am trying to search the variables in Web Templates the search by text is case sensitive.
    For example If I have the customer name as "King", I have to search the text as King or Ki*, But If I search as king I will not get any results.
    I need to have my text search as case insensitive.                                                                    
    When I checked in my BEx queries the search is case insensitive. I have the problem in my Web Templates only. Please let me know do I need to change any variable settings ing the web templates or let me know how do I fix this issue.
    Many Thanks,
    Vamshi Krishna

    Hi,
    So the only workaround for this would be to goto RSD1 -> enter info
    -object as xxxx, and press maintain, then goto master data/text
    tab and select the check box, 'with text', now save and activate the
    infoobject. After this regenerate the query using tcode rsrt.
    To regenerate goto rsrt enter query name and press 'generate report'
    button.
    Now the F4 help screen should show the options search by key and search
    by text. So that you can select serach by key to have a case insensitive
    search.
    Thanks,
    Venkat

  • Case-sensitive search for equipments

    Hello gurus,
    when looking for certain equipments using F4 (program RIEQUI20), I can search for all equipments of a certain manufacturer (field HERST).
    Unfortunatelly this search is always case-sensitive, i.e when I enter "BOSCH", equipments with manufacturer "Bosch" are not found and vice versa.
    Is there any way to change this behaviour?
    Thanks in advance
    Alicia

    Alicia,
      Oops ..Sorry about that. I had misread it. You will not be able to accomplish the same in standard enhancement.You could remove the case sensitive check box on the HERST data element.But that would be considered A modification.That might however do the trick and save all the new contents in CAPS.The search help will then pick everything.(You may have to go into change mode on existing records and re save them for this change to be updated in DB )
    However you could achieve the same, without modification and with a little bit of custom development.
    What you could do is, create a Custom elementary search help(SE11) with the standard fields HERST(Input) and EQUNR(Output) fields .Create and Attach a  custom Search help exit to the same by copying F4IF_SHLP_EXIT_EXAMPLE. In here modify the STEP SELECT to append a translated (Upper and lower case) selection condition to the query or a appropriate wild card search.Then select the same from EQUI.This should pull all your records. After testing this out , append this search help to the standard collective search help EQUI.
    Hope this helps.
    Regards
    Narasimhan
    Edited by: Narasimhan Venugopal on Jan 7, 2010 10:24 AM

  • Case-Sensitive Search

    Hi all,
    I'm having a stupid problem. We use Robohelp 7.0 for Word.
    When people search using the search tab (compiled version), they
    seem to only find words according to the case (i.e., search for
    Quickbooks and Quickbooks shows up, but QUICKBOOKS doesn't return
    anything). Is there a way to turn off case-sensitivity?
    Any help would be greatly appreciated.
    Thanks,
    Jeff

    Search on a MIXED_CASE index is case-sensitive. Either re-index and build a case-insensitive index or consider using the ABOUT query operator.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Tosh Miller:
    Have a table with FILE_DATASTORE field and primary key of course.
    Index is case-sensitives (MIXED_CASE = YES).
    How create insensitive query to this table?<HR></BLOCKQUOTE>
    null

  • Search help is case sensitive

    Hi,
    I have created one z-'elementary search help' with selection method as a z-view.
    View consist of following tables:
    COMM_PRODUCT
    COMM_PRSHTEXT
    COMM_PRPRDCATR
    COMM_CATEGORYT.
    I have attached this elementary help search to 'COM_PR_COLLECTION' collective search help which we used for searching products.
    The search help we have created shows the result which is 'case sensitive'.
    If I search for 'Product Description' = 'button' I get
    the output with all products with only small letter 'button' which is not required.
    I must get the all product with description 'button' and 'Button'.
    I haven't attached any of 'Search help exit' for elementary search help.
    Please help.
    Regards,
    Dhanraj Dange

    Need to select fields which SAP provides for Search help.
    These fields is with LONG TEXT.

  • Explorer Search Case Sensitive?

    The search functionality in Explorer is case sensitive.  Is there a way to make the search functionality be case insensitive?

    Hi Karen,
    Thanks for the reply.  This isn't about Bex though it is about Business Objects Explorer.  I originally posted this in the Other Business Objects forum but a forum Admin moved it here because they said I had posted to the wrong forum.  It was in the correct forum to begin with.  If SAP were more thoughtful about how they named products they would not have created this confusion by renaming Polestar to be the same name as an exisating product.
    Tom

Maybe you are looking for