Case sensitive attribute in variant

There is a way to set up a variant not to change the input to uppercase but to keep it case sensitive.
I forgot which attribute it is.
Help!
Thanks.

Janet, you might want to try to specify lowercase in your parameters/select-options statement.
report zrich_0001.
tables: makt.
parameters: p_check type c lower case.
select-options: s_matkx for makt-maktx lower case.
Doing so may control the way the variant is stored.
Regards,
RIch Heilman

Similar Messages

Unique IDs- Case sensitive

In my directory, for user UID is my DN(Distinguished Name). So no one should be able to have the same UID. Yet, if you change the case, the directory still allows it. I cannot find the attribute in the config that prevents this. Any suggestions?

First, I think you'll need to use DSEE 7, as previous versions don't enforce any syntax checking. That is, previous version won't complain when you import some data that doesn't comply with the schema. You'll be able to have strings values for integer attributes with those versions.
Then, you need to use a case sensitive attribute as RDN. Since uid is not case sensitive, DSEE 7 treats uid values without distinction between lower and upper cases.
Another option that I would not recommend would be to change your schema and modify the standard uid attribute definition to make it case sensitive. Rather consider creating a brand new attribute of your own .

How can I deal with case-sensitive filenames referred to inconsistently inside other files?

I have downloaded into Dreamweaver an existing web site that I'll be taking over from someone else. The site was built with Microsoft Front Page and apparently now runs on a Windows web server. While redesigning the site, I'd like to upload it to a web server belonging to me, where I can maintain a work in progress that is accessible to others (so they can give me input as I go along). But my site is running on a Unix system, where filenames are case-sensitive.
In the site I've inherited, I've discovered at least one file that is referred to in other files sometimes with one character in upper case and other places in all lower-case. The actual filename contains the upper case character and locally, on my Windows system, it doesn't matter. But on the server the file is not found when it is referenced in all lower-case.
Of course, I can create an all lower-case symlink on my Unix server for the mixed-case file that I know about. But I don't want to look through every file on the site for other files which may vary, case-wise, in how they are referenced. Is there any way that Dreamweaver can help me; for example, by going through and changing all mixed-case filename references inside files, to be consistent with the actual filenames?
I know this is a lot to ask of Dreamweaver and I'm not optimistic. But if anyone knows of a solution, I'd appreciate it.

he means that if you use the file > find function
(on windows this can be called upoon using CTRL + F)
you will be able to go through all the files which are cauing you a problem and change their names so that they are all in the same case
be warned thou
if case sensitivity is your problem,
and
if some code references to your files are written in one case and some are written in the other case, simply changeing the case of the file names will not help.
what you are trying to do will only work if
> ALL of the file names are in one case
or
> ALL of the files names are the same case
bcause this will mean you can change the one which does not always match using CTRL + F
if there is a mix and match on both sides then you are in for a lot of work, if this problem involves multiple names then i would advise you to simply start over!

Case Sensitive External Drive for iTunes

My iTunes Library is currently stored on a case sensitive external drive. I am moving it to another drive that I found out is formatted as a non-case sensitive (both areJournaled). When I tried to move my iTunes Library, it would not copy because there are apparently some duplications that are different in case and this causes a problem when duplication to a non-case sensitive drive.
I figure I have two options:
1) Reformat the new drive to be Journaled and Case Sensitive
2) Go through the tedious process of identifying which files in the iTunes Library would be duplicates in a non-case sensitive drive. There could be just a few or hundreds (or even thousands).
What is the disadvantage of using a Case Sensitive drive for iTunes (option #1)? I may also store some other files on this drive.
I noticed that all my other drives, on both my desktops and external are formatted as non-case sensitive.

If you can get to the two metadata files that iTunes keeps on the old PC, then you have several options. See: What are the iTunes Library files?
1) Use the 'iTunes Library.itl' file on the old PC to completely recreate your Library. You will have to place all the music files/folders in the exact same location on the new PC as they were on the old PC. That drive letter and directory path. Then copy the older ITL file over the current one on the new PC. Open iTunes and you'll have a clone of the old PC's Library. As you have been using an ExHD to store the music, this would be my preferred choice. It's easy to remap the drive letter of an ExHD, if needed.
2) The other way is to 'File=>Import' the XML file and recover the Playlists from there. They will not be in any folder structure as they were in the previous iTunes. Also, any playlists that depended on ratings, play counts and last played will be changed, as those attributes have not been carried over using this method.
Post back if you have questions.

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.

JAXB : case insensitive attributes

I frequently receive an XML file which I do not have control over. ( It is generated outside of my organization)
I derived a XML schema by analyzing the document structure and used the schema to generate a set of JAXB generated classes.
Nevertheless, the file sometimes comes with some minor "mistakes" in the attributes names of some entities by having the wrong uppercase or lowercase. (Vgr. myAttributeName vs myAttributeNAme )
Is there any way to tell JAXB to be case insenstive on the attribute names ?
Unmarshalling the file fails at the attribute with the wrong case.
Thanks.

Unlikely. XML itself defines all element and attribute names to be case-sensitive, and likewise Java defines class and variable names to be case-sensitive. So it wouldn't make sense for JAXB to have a "case-insensitive" option.
If you can't get the supplier to provide the correct information in the XML file (e.g. they are an important customer and you can't point out to them that they are a bunch of donkeys) then you could pre-process the XML file yourself to correct the errors.

Migration from OS/400 (iseries) case in-sensitive OS to UNIX (AIX) case sensitive

Apparently as400 is not case sensitive OS, AIX is so this is causing issues after the migration to UNIX (AIX). What do you recommend for analysis of what will need correction in SAP system - config / tables entries / variants / code? Is there a way to make UNIX files case insensitive?

Hi Vinoth,
Source System:
SAP Application:     Solution Manager 7.1
Database          :     DB2 UDB for iseries 7.1
OS                   :     OS/400
Target System:
SAP Application:     Solution Manager 7.1
Database          :     DB2 LUW 9.7
OS                   :     Rethat Linux 6
Above migration path is possible and support in SAP. For more details on compatibility please refer PAM www.service.sap.com/PAM
To perform this migration refer to Heterogenous system copy guide available at SAP service marketplace.
Useful documents on SCN
Heterogeneous ABAP System Copy - Technical Overview
FAQ - System Copy and Migration
Hope this helps.
Regards,
Deepak Kori

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.

Web Dynpro & case sensitive selection of Adobe Forms

Hi Community
how can I solve this issue:
I have a Web Dynpro View with a button. Clicking this button generates a Adobe form and displays it.
So long everything's fine.
Here's my problem:
There are 4 different case sensitive forms in dependence of the user's selection. How can I solve this?
The form is assigned to the view via layout, so do I have to create 4 views,related to the amount of forms? And additionally the pdf's are displayed in dialog windows, so do I have to create 4 windows additionally where I have to embed a view for each of them?
Is there any other way to solve it? It looks for me like a not very nice solution.
Thanks in advance,
Tan

Hi Tan,
Solutions that i am proposing may not be the best solution but you need to take a call on the best one:
Solution 1 :
1. Try Creating only one view and one window for pop up ( in addition to your existing view with button )
2. in the view add an interactive form and bind it to one of the form.
3. in WDDOMODIFYVIEW method , depending on the situation try to change the mapping to this interactive form
4. This embedded view in the pop up window is always called, only based on the conditions the adobe forms changes.
Solution 2:
1. in your view add 4 Interactive forms , bind them to different nodes as per its mapping requirement
2. create 4 Visibility context attributes , bind them with each of the forms
3. depending on the condition , hide or make visible the adobe forms.
4. show this view in the pop up window.
My suggestion would be to go with Solution 2 , since it does not involve dynamic modifications at runtime.
Regards,
Ashish Shah

Case Sensitive Problem in the query

Hii All
Good Day
I have created zperson infoobject & has lowercase letters tick marked.
This is the navigational attribute of 0activity infoobject.
The user wants to have the functionality of
"The text field should be non-case sensitive so when it is used in a query to search the name can be typed in whichever case a person wants"
How to do this? can any one suggest?
regards
Jana.

Hello,
I dont have a solution to convert the value automatic in the selection variables. but as an alternate solution: When you load data for zperson, use formula or routine to translate to upper case. Then the user can always use uppercase in the selection.
Happy Tony

ALV grid case-sensitive edit field

Hello,
i've a editable field on a alv grid.
The field is case-sensitive in the domain.
But when i enter a field an click rturn, the letters get uppercase.
What's the problem?
Best regards,
TomSd

Hi,
Add the attribute lowercase = 'X' while preapring field catalog for this field.
Regards,
Gopi.
Reward points if helpfull.

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

Apache is so case sensitive

I have no html on my server so everything is indexed. When you try to get to a specific Volume/Folder you can only do it by typing in everything exactly as it is typed in the file structure with intial caps.
I cannot duplicate this on two other backup XServers and I need to eliminate it from my production server.
Any suggestions would be most welcome!

Thats the way mac OS is. I just tried on my test server to allow me to view the directory on my raid from the web and I got the same error, although i just typed in http://ipaddress, I wonder if I try the whole path if that will work, even though in the config that is where I am pointing it to, so imo no it will not work.
Sorry to ramble, is there a way to fix this? How is the folder locally? Art or art? have you tried to change that?
Also here just dug this up in my files:
How can I make all my URLs case-insensitive with mod_rewrite?
You can't! The reasons are: first, that, case translations for arbitrary length URLs cannot be done via regex patterns and corresponding substitutions. One needs a per-character pattern like the sed/Perl tr|..|..| feature. Second, just making URLs always upper or lower case does not solve the whole problem of case-INSENSITIVE URLs, because URLs actually have to be rewritten to the correct case-variant for the file residing on the filesystem in order to allow Apache to access the file. And the Unix filesystem is always case-SENSITIVE.
But there is a module named mod_speling.c in the Apache distribution. Try this module to help correct people who use mis-cased URLs.
So Mac is built off NIX so no... That should solve it..
EDIT: You can make SAMBA handle you www requests but I wouldn't for security. Or make a redirector...

Table filtering is case sensitive

ADF Version: Oracle JDeveloper 11 g Update 2 (Build 5205) (11.1.1.0.2)
We are using an older version of ADF / jDeveloper for our application. We have run into the issue where all of the filter fields on our tables seem to be case sensitive. I am aware that in more recent versions of ADF you can simply use the FilterFeatures attribute of a column to control this behavior. Unfortunately our version of ADF does not support this feature.
Is there anyway in our version of ADF that I can make it so the filtering is not case sensitive? What do I have to do, or what classes do I have to override to get the desired behavior? Is it even possible in this older release? Thanks in advance.

Hi,
you can create a custom query listener on the table, intercept the filter criteria and turn them as you need them. See example #30 at http://www.oracle.com/technetwork/developer-tools/adf/learnmore/index-101235.html . All you need to do is to intercept the table filter setting and execute a query on the WS so that the filter criteria values are used case insensitive
Frank

How to display case sensitive elements in an adobe interactive form

Hi Experts,
I'm not sure if this is the correct section for my problem or if I should post it in Web Dynpro section...
Out of an Web Dynpro Component I'm starting an Adobe Interactive Forms and filling it's elements by Web Dynpro Context Nodes. So long everything's fine.
Now I need to display some elements depending on cases of my Web Dynpro.
In other words for example:
if x = 1 show some elements in my interactive form,
if x = 2 don't show them but show other elements
and so on....
Is there any function in interactive forms to realize that?
I had a similar problem before, depending on Web Dynpro cases different Forms are executed and displayed as shown here
[Re: Web Dynpro & case sensitive selection of Adobe Forms] but in this case I need to handle with the elements of my interactive forms.....
Any ideas?
Thanks in advance,
Tan

Hi,
back again, had to handle other issues, sorry.
Just to get a little more concrete. The condition depends on the context node attributes. So if an attribute is initial, it's field should not been shown, if it's not initial, it should ne shown. There are 6 context attributes and therefore 6 fields in the form. How can I get the attributes' value?
And can I put them into the same subform or do I have to create 7 (6 conditions + blank-condition) subforms?
I put the fields (textfield and context node value) that should be shown depending on conditions in a subform. So how can I adress this subform?
I'm not so familiar with JavaScript, so please help me. I need something like:
if (context_node_attribute X is initial) {
subform_1.presence = "hidden" ;
I tried it with
if ( ARB_STUNDEN.rawValue != null) {
Beratungsstunden.presence = "hidden" ;
but it didn't work....
Thanks,
Tan

Case sensitive attribute in variant

Similar Messages

Maybe you are looking for