Making search non case sensitive

Hi,
I have implemented a search help which I have copied from standard help ‘PREM’. I have created a Database view, taking that View I have created an Elementary search help and I have assign the elementary search help in the collective search help ‘ZPREM’ which is copied from ‘PREM’. In the search help I have two fields (NACHN, VORNA), which are case sensitive fields.
How to make it Non Case Sensitive?
Regards,
Jitendra

Hi ,
without checking "Lower Case" , any case(upper/lower) u are entering will be converted to upper case internally and the respective data will be displayed .
With checking the lower case check box in domain , u will get the exact case data in which u have entered .
but if ur requirement is like , if u enter a* in VORNA FIELD and it should display
a*
A* - ie. all the names starting with the both 'a' or 'A' , then
You can go for Search Help Exit . Inside the function module catch the entered name and select required records from DB as per ur requirement and insert result into RECORD_TAB[] internal table , having standard search help result list .
Regards
DJ

Similar Messages

BI BEx & WAD F4 Search: How to search non-case sensitive

Dear Colleagues,
is there meanwhile a better and comfortable solution for this problem, or have'nt changed anything since "How to... Search non-case sensitive" paper from 2003.
Thanks and regards,
Wolfgang
Edited by: Wolfgang Taag on Aug 4, 2008 1:40 PM

Hi Gerhard,
I quote from OSS note 914303 :
The BI search requires the TREX Server as of 7.0 Support Package 06 or higher. If the search engine is not fully installed, you can still use the standard search that the system carries out in the database. However, as a result, the search takes longer, <u>it is case-sensitive</u> and it does not support the search for attributes.
Hope this helps,
Best regards,
Olav

How to ... Search non-case sensitive?

Hello,
prior to SAP NetWeaver 2004s we implemented the How to Guide "How to ... Search non-case sensitive" in SAP BW 3.5.
This solution is no longer valid in BI 7.
Does anybody know how to implement a non-case sensitive search in SAP NetWeaver 2004s BI?
Regards,
Gerhard

Hi Gerhard,
I quote from OSS note 914303 :
The BI search requires the TREX Server as of 7.0 Support Package 06 or higher. If the search engine is not fully installed, you can still use the standard search that the system carries out in the database. However, as a result, the search takes longer, <u>it is case-sensitive</u> and it does not support the search for attributes.
Hope this helps,
Best regards,
Olav

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,,,

Copying folders & files from case-sensitive to non-case-sensitive volume

I'm trying to copy a rather large (60+ GB), folder and all its enclosed items from a volume that is has case sensitive file names to one that does not. The copy operation always stops when it comes across a duplicate file/folder name differing only in the case of some of the characters. The folders/files in question are actually not duplicates, so I would like to change the file name of the duplicate by appending anything to the filename.
The copy operation does not provide any choice but to abort the operation when it finds the first identical file or folder name differing only in case..
Any suggestions?

Unfortunately, that is not a viable solution, as I am tring to convert a case sensitive volume to a non-case sensitive volume.
What I would like is a method to copy files and when a duplicate occurs it asks me what to do like rename the second duplicate. However this problem is now moot, as I painstakingly renamed each offending file/folder as each error occured, and then restarted the copy.
While the question is not answered, I am marking it as such because I am now past the problem.
Thanks for your response.

Portal content search still case sensitive in EP7?

Hi,
Is searching in portal content still case sensitive in EP7? In other words, if you go to Content Administration -> Search -> iView and type in the name, is this type of search still case sensitive? If not, how do I fix it?
Any help is greatly appreciated.
Regards,
Rick

Hi,
Yes, search in content admin is still case sensitive...
regards,
Senthil K.

Can i make the database passwords non case-sensitive ??

Can i make the database passwords non case-sensitive ??

Yes: set instance parameter SEC_CASE_SENSITIVE_LOGON to FALSE ( http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams220.htm#I1010299).

Would like for URLs to be non-case sensitive

How can Contribute 6.5 make URLs to be non-case sensitive?

What do you mean exactly? What are you trying to accomplish?

Ho to reformat to a non case sensitive file

How to reformat to a non case sensitive file

If you want quotes around all the fields, and you currently
have quotes around
none of the fields, you could probably do this using
find-and-replace in a word processor.
Open up the CSV file with 'word' or a similar word processor.
The important thing is that the word processor must be able to do a
find and replace on 'special' characters, like 'return'.
Use find and replace to:
Replace all 'comma' characters with the sequence: quote comma
quote
Replace all 'return' characters with the sequence: quote
return quote
You should then find that your CSV text has quotes around
every record, but you'll have an extra quote character at the very
start and very end of the file (on separate lines), which you'll
need to delete by hand.
Of course, make a backup of your data first - and this won't
work if some of your columns already have quotes, or if some of
your fields actually use the 'comma' character inside the field
data.
- Ben

Firefox CTRL+F Search bar searching with Case Sensitive

is this only for me or all ?
Fiefox search bar is working with case sensitive.. if i type in capital.. it is only showing the results with capital.
for example. Type "vishnu" in search bar. it will only show you the small vishnu below.
VISHNU vishnu
is it a bug ? or is it a feature ? if it is a feature, i want to disable it :(

You can remove the check-mark on Match Case if you open the Find bar via Ctrl+F (Edit > Find).

Default Search is Case-sensitive

I go to contributor mode and try to choose an image. A window that contains alll the image content items show up. I type the name of the content item (an image) in the small search text box on the top right side of the window.
It seems that when I enter a value in the text box, it performs a Case-Sensitive search. Is there a way I can make this case-insensitive search. For eg; Let us assume that we have a content item called 'IM_ABOUT_US_ICON'. if I enter 'im' in the text box, I do not get any result. But, if I enter 'IM', I get all content items that starts with 'IM'
Thanks

This is discussed in the following posts:
Case Insensitive Search in UCM
Where is Case Insensitive Search Component in UCM 11g?
Jonathan
http://jonathanhult.com

Time Machine suddenly refuses to backup to non case-sensitive drive

There is another thread on this which for some reason is marked as resolved, so I thought I'd post a new thread. Suddenly after months of no complaints I get the following error:
*+Time Machine Error+*
+A volume you are backing up is case-sensitive, but the backup volume is not.+
+To Select a different backup volume, or to choose not to back up the case-sensitive volume, open the System Preferences and choose Time Machine.+
The only thing I've changed is that yesterday I ran Software Update. Unfortunately I can't remember exactly what was updated, but I suspect Quicktime was one of them since I needed to reboot. So now I'm at 7.4.5 in Quicktime.
Time Machine refuses to backup my drives now complaining about the case sensitive filesystem. The thing is, *NONE of my drives are case sensitive.* Looking at the Change Drive window in Time Machine, I see that most of the drives on my system say "reforat required" if I am to use them with Time Machine. All drives on my system are *Mac OS Extended (Journaled)*. The fact that some drives are not requiring a reformat and some are, even though they all are the same format is quite puzzling.
I took a spare drive and allowed Time Machine to reformat it for it's use. It has now reformatted the drive as Mac OS Extended (Journaled, Case-Sensitive).
Can anyone shed any light as to why TM would suddenly require my backup drive to be case sensitive when none of my drives are?
This make no sense...
-K

Ok - Running Disk Utility Verify on both the system disk and the TM disk seems to have magically stopped this error. Note that Disk Utility didn't actually find or fix any problems with either disk. The problem just went away....
It doesn't make any sense.
-K

Search without case sensitivity??

I am trying to create a search function that displays a report based on the search. I have the following query:
select
date_participated "Date Participated:",
highschool_attended "Highschool Attended:",
attending_college "Attending College:",
college_attended "College currently attending:", participate_intercollegiate "Participating intercollegiate:",
what_sport "What Sport:",
what_position "What Positions:",
financial_help "Financial Help:",
financial_help_kind "Financial help kind:",
additional_comments "Additional Comments:",
name_and_address "Name and Address:"
from bcombine_survey where HIGHSCHOOL_ATTENDED like NVL(REPLACE(:P3_Highschool|| '%','0',NULL) ,'%');
My first question is:
1. How can I make that query so that it is not case sensitive.
2. Can i create a query that will search the database for any string that the client puts in? For exanple, if a highschool is named Athens and the client searches for "thens" I want it to pop up the Athens.

Hi BlackMamba11
Try something like:
WHERE UPPER(MY_VARCHAR_COLUMN) LIKE '%' || UPPER(:P3_MY_TEXT_ITEM) || '%'
Hope this helps.
Cheers,
Patrick

Copying Files from Case-Sensitive External to Non-Case-Sensitive Internal?

+(Sorry if this is the wrong sub-forum, I didn't know which one this question fit in)+
I just got a new iMac today and I'm trying to transfer some of my old files (specifically iTunes & iPhoto). My old computer was an MBP & only had an 80 GB HD, so these files were run off an external drive.
I know basically how to copy these files onto my new computer. The problem is that my external drive is formatted as Mac OS Extended (Case-Sensitive, Journaled). So when I try to copy the iTunes or iPhoto folder, I get the following message:
+You can’t copy “iTunes” because it has the same name as another item on the destination volume, and that volume doesn’t distinguish between upper- and lowercase letters in filenames.+
The only option I know of is to reformat my iMac's drive as Mac OS Extended (Case-Sensitive, Journaled). Since Macs ship with the drive formatted as Mac OS Extended (Journaled), I assume that's the best option, and would prefer not to reformat if I don't have to. I've also read that some programs won't run on a case-sensitive drive.
*Do I have any easy alternatives to move my iTunes/iPhoto folders?*
*If not, what negatives do I need to consider when reformatting my iMac's drive to a case-sensitive one?*
Thanks.

Joel-X wrote:
I've solved the problem for iTunes, but it was a bit tedious.
Yes, I'll bet! It would be sooo much easier if the Finder would produce a list somewhere.
*Assuming that I solve the "case-sensitivity problem" for my old "iPhoto Library" folder, will a simple drag and drop of that folder to my new iMac allow me to just open iPhoto 9 and have all my photos be there?*
I believe so, as that's how Apple tells you to move it: [Moving your iPhoto library|http://support.apple.com/kb/HT1229].
I don't want to spend too much time on the case-sensitivity problem until that question is answered, just in case.
It may not be as easy to solve, though. That library is a "package," kind of like an app -- actually a folder, but treated as a single object for most purposes. If you right-click it via the Finder and select +Show Package Contents,+ you'll see the file/folder structure.
See the note in the link above -- it sounds like changing file names will break the structure; it may only affect the files you change, but it might be worse.
If you can find the duplicates, you may be better off exporting them via iPhoto, deleting them via iPhoto, then re-importing them under different names. That should keep the structure intact.
At the very least, make a full copy somewhere before touching it.
Good luck!

Time Machine Case Sensitive Restore to Non-Case Sensitive

I have a MacBook 2.4GHz white laptop with OS X 10.5.5. Previously I formatted the drive as Mac OS Extended Journaled Case Sensitive. I have determined that I cannot install Photoshop CS3 onto this drive without doing some fairly tricky work-arounds.
To fix this problem "fast", I used my Time Machine backup to restore my primary drive after I had reformatted it as Mac OS Extended Journaled. However, as part of the restoration process, time machine formatted the drive again (as case sensitive) and copied the software. This puts me back where I started.
Is there a way to alter the settings of time machine such that it does not format the drive or does not format the drive as case sensitive?
Is the only way for me to do this to reinstall OS X 10.5 on the formatted drive (not case sensitive) and copy the files over from time machine? Is is possible to copy (not restore) files from the time machine drive?
I would appreciate any help. Thanks for your time.

Glenn Carter wrote:
Unfortunately, an Erase and Install is probably the only way you are going to fix this. As you have discovered, it appears that "Restore System From Backup..." reformats the destination drive to match the state in which the backups took place.
The TM backup may not have the ability to rename dupes that might occur if some files have identical names save their case.
Even a reformat and reinstall may not work unless any pseudo-identical files are first renamed.

Making search non case sensitive

Similar Messages

Maybe you are looking for