Case sensitive text

Hi experts,
I have a below written query:
IF customer_name IS NOT INITIAL.
    SELECT SINGLE kunnr FROM kna1 INTO lv_kunnr
                           WHERE
                           name1 = customer_name.
ENDIF.
The issue is that some of the 'name1" in KNA1 are in lower case, so what happens is that the FM in which I am coding, by default searches for the upper case fields. Since it does not find it, the output is not as desired.
How to rectify this issue?
Thanks,
Ajay.

Createad a FM with the below code. Used Name as import parameter with
data element text30 (domain text30). Text30 is marked with lowercase indicator at the domain level.
""Local Interface:
*" IMPORTING
*" VALUE(NAME) TYPE TEXT30
DATA : lv_kunnr type kunnr.
SELECT SINGLE kunnr FROM kna1 INTO lv_kunnr
WHERE name1 = NAME.
Executed the FM in SE37 and passed value 'TeSt' it converts name mixedcase into uppercase and it does not work as expected
Created a program with the below code. Executed the program and entered the value 'TeSt' and it does not
convert to Uppercase in the FM.
PARAMETERS : p_test type text30.
CALL FUNCTION 'YTEST_K'
EXPORTING
name = p_test
If sy-subrc eq 0.
endif.
Regards,
LK.

Similar Messages

Setting in HR infotypes for case sensitive text

Hello - I have a custom infotype with a couple of free-text fields included within it. Right now all text that is entered into these fields is automatically converted to upper case. I would like to disable this feature and allow the data to be saved in the case it is entered with (either upper case, lower case or both). Can anyone tell me where this setting is so that I can change it?
Thanks!
Kristy

Hi Krishna - I'm not sure I am seeing things correctly in SE11. When I go into my PA9013 table I see the includes that were created during the infotype creation. I select the PS9013 include and then double click on one of the free text fields that I am interested in within the Data Element column. When I do this I can see that the field is using a Predefined Type of CHAR and not a domain. I don't see a domain tab so I have tried to assign it to a domain but I still do not see an option for lowercase text. I am assuming that I am in the wrong area all together. Can you please assist?
Thanks!!!

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

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

Enhacement for removing case sensitive of the short text entered in Me21n

Hi very one ,
i want to write a enhancement to remove the case sensitive of the short text entered in me21n transaction code for service Number . ie .. whether i enter the text in captain letter or small letters it should fetch the exact data accordingly to the short text entered ( the respective service number should be retrieved ) , i think there will be some function module that will remove this case sensitive thing . plz help me out
Regards
Syed Akbar

Thank you, Kappy, for your quick and helpful reply to my (admittedly) not very quick question!
It strikes me as odd that Apple would appear to make the use of both lower- and upper-case letters possible in the short user-name, leaving the possibility that upper-case letters might lead to some problems/conflicts down the line. It would be helpful if they'd provide some explanation about this. Anyway, as I said, I'm very far from being an expert in all this, and appreciate that people like yourself on these
forums are willing to provide helpful feedback.
Best regards,
Stephen

Case sensitivity for text fields

Does anyone know how to turn off case sensitivity for a text field??
Your help is appreciated.

Do you recommend another field type that can be used that does not use case sensitivity?
Thank you

Setting case sensitivity for text searches

I am trying to figure out how to set case sensitivity for text searches for Oracle. I am using 8.1.7 and the documentation keeps referring me to the Basic_Lexer object. Does setting the mixed_case parameter to 'No' remove case sensitivity for the index or is there something else I need to do?

Do you recommend another field type that can be used that does not use case sensitivity?
Thank you

Case sensitivity in Oracle Text

I am familiar with the mixed_case parameter, and in my setup it is set to no, so all searches are case-insensitive. This is what I want 95% of the time, but is there a way to specify (at a query level) that a contains search is case sensitive?

Hi,
Would be nice, but the tokens are converted to uppercase on indexing. For example:
SQL> create table test (col1 varchar2(20));
Table created.
SQL> insert into test values ('MixEd cAsE');
1 row created.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context;
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
CASE
MIXED
So, since they are actually stored/converted to uppercase there is nothing case-sensitive for your query to compare to.
On the flip side, if you index case-sensitive, the tokens are stored mixed-case.
SQL> drop index test_idx force;
Index dropped.
SQL> begin
2 ctx_ddl.create_preference('mylex', 'BASIC_LEXER');
3 ctx_ddl.set_attribute('mylex', 'mixed_case', 'yes');
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context
3 parameters('lexer mylex');
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
MixEd
cAsE
Now you can do something with your query to make it do what you want. You'd have to check performance to see if it is worth it.
Ron

Numbers: searching for occurences of text (case sensitive)

For biology class, I have a table for dihybrid genetic crosses. After I fill in all the table, I want another table to be able to count the occurrences of each letter combination.
Essentially, what I want to do is tell a cell to count how many occurrences of "BBHH" are in a range of cells. The COUNTIF function is not case sensitive. I tried nesting the EXACT function inside functions like COUNTIF, COUNT, IF, etc., but EXACT doesn't accept a range of cells.
Is there a way to do this (a.k.a. create a function that would have the same effect as a hypothetical case-sensitive COUNTIF)?

Matt,
I think you are giving up too soon. Create an additional column that tests each cell for your value using EXACT. Column A has your values, B2 has EXACT("BBHH",A2) and you have filled down as far as you have needed (say B11). In A12 use COUNTIF(B2:B11,"=true") to count matched values. Hide column B. Repeat for each value you want to search for.
Quinn

In ALV Report Filter selection should be case sensitive

Dear All,
since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying filter on that field its is simply fetching data with case description. if its in caps it should fetch caps data but in smaal case report showing no data
Regards,
Pankaj Vashista

Hi,
All text datas are case sensitive.
To make it work perfectly You have to Use the Keyword translate to Upper Case than display
Now filter can work.
Without Transalation to Upper Case filter will not work.
Regards
Arbind

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

Why Case-Sensitive while assigning tasks to other users??

I am trying to assign a task to another user through AdminUI.
While searching for users, I am supposed to provide case-sensitive search text to find actual users.
In previous installations it is not a problem. i.e only in production it happens.
Is there any place to modify this settings?
Please see the attached screenshot of the page.
Thanks,
Nith

Raghu,
thanks for the reply, you are right as per the audit .But suppose if it is for 200 users ,creating 200 CUP requests will be impractical right.
there should be some solution for this , because there will be many situations practically where we have to assign roles to N number of users.
Is this possible in GRC 10 ? any idea ?
Regards,
Jaags

SOAPAction HTTP header case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be exactly like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

> The value of the required verb attribute indicates the HTTP verb. Common values are GET or POST, but others may be used. Note that HTTP verbs are case sensitive.
This section does not say anything about HTTP headers. GET and POST are not headers, but HTTP methods.
> Acording to my Webservice vendor, the SOAPAction are indicated into this section.
This section has nothing to do with SOAPAction
> Also, I am working with SAP Support and got this repply:
> ... Yes, the value should be SOAPAction
> instead of SOAPACTION....
I do not comment this.
You have now following possibilities:
1. Convince your vendor to accept HTTP headers according to above mentioned RFC
2. Convince SAP that to change SOAPAction
Good luck.

SOAPAction Header field case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

Gourav,
This is W3 Standard:
HTTP verbs are case sensitive. (http://www.w3.org/TR/wsdl)
In my case, the webservice provider was implemented in JAVA code and in Linux server. Java and Linux are case sensitive.
I agree with you if we are working with .NET implementation.
I already have tried to consume a .Net asmx webservice and works fine.

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

Case sensitive text

Similar Messages

Maybe you are looking for