Check Case sensitive values

A field value is coming in caps.
lf_tmp = u2018RMu2019.
I have to check this with another field lf_werks ,which always comes in small letters.
if lf_tmp   CN lf_werks .
    MESSAGE e002(zm) WITH 'The Path is wrong for the plant'
                           p_werks.
ENDIF.
This check always fails even if the values are like belowu2026
lf_tmp = u2018RMu2019.
lf_werks = u2018rmu2019.
How do I by-pass this case sensitiveness u2026.when I want to do the check.
thanks in advance

Actually, I'd do it the other way:
TRANSLATE lf_werks to UPPER CASE.
Since lf_werks can be a combination of upper and lower case, translating lf_tmp to lower case may not always work. This way you are always comparing upper case to upper case.
Rob

Similar Messages

How to select a case sensitive value in SQL with C#

Hello,
I have an application that at the begining a user will login with a user name and password which is stored in the database. The SQL statement is as follows:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' AND passWord='" + txtPassword.Text + "'";
For testing purposes I have set the password to the word test. The problem is, if the user enters in TEST or TeSt or TESt it will grant them access. How do I set it to force the correct case?
I am using SQL 2005 for the database.
Thanks!
~zero

You can also set Collation while comparing strings:
"SELECT id_employee FROM employee WHERE employee_number='" + txtUserName.Text + "' COLLATE Latin1_General_CS_AS AND passWord='" + txtPassword.Text + "' COLLATE Latin1_General_CS_AS";
All comments about not doing this type of quering using command string, instead of command with parameters, they are apsolutely right.
Nevertheless i will have only username as a parameter in the command and password will be return value from procedure. I will check for equality of entered password and returned one from command in C# code, and C# is case sensitive. There is a good security model implemented for password in AdventureWorks sample database for SQL Server 2005, in table Person.Contact.
That model use two fields for password, PasswordHash and PasswordSalt. PasswordSalt is randomly generated hash when password is modified and with that salt, password string is encrypted, which produce PasswordHash. So when you want to authenticate a user, execute a command that will return a row(PasswordHash and PasswordSalt) for entered username, and in application you will encrypt entered username with PasswordSalt. If generated string is equal with the one returned PasswordHash, then you have a valid login. If nothing is returned from command or they are not equal, you have invalid login.

Case-sensitive values in an Tabular Model with a Oracle Datasource

Hi,Lets use an Oracle Database as Datasource for my Project. I use a "Select distinct ColumnA from Table" to build up a LookupTable in my Tabular Model. But it returns Dublicates!! eg:
When I fire the query from Oracle SQL Developer I got 2 Records "1N" and "1n". In the Grid View in SSDT I see 2 times "1N". ??
Collation Case Sensitive. OK, but how to solve that?
KR

Hi KR,
According to your description, you encounter the case-sensitive issue when creating SQL Server Analysis Services Tabular model project, right?
Based on my research, Tabular models have the insensitivity problem by default. The workaround for this issue is creating a empty tabular model in tabular server using the xmla below and import the tabular in SSDT.
<Create xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<ObjectDefinition>
<Database xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300">
<ID>Collation test</ID>
<Name>Collation test</Name>
<Language>1033</Language>
<Collation>Latin1_General_CS_AS</Collation>
<DataSourceImpersonationInfo>
<ImpersonationMode>Default</ImpersonationMode>
</DataSourceImpersonationInfo>
<ddl200_200:StorageEngineUsed>InMemory</ddl200_200:StorageEngineUsed>
<ddl200:CompatibilityLevel>1100</ddl200:CompatibilityLevel>
</Database>
</ObjectDefinition>
</Create>
For the detail information about it, please refer to the link below.
http://blogs.msdn.com/b/cathyk/archive/2011/10/24/making-tabular-models-more-sensitive.aspx
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

WE19 (iDoc Test Tool) and case sensitive content

Hi experts,
I am not able to send case sensitive content via WE19. When I change a value of an existing iDoc (via WE19) all values of the segment are converted to uppercase (independent of the domain).
To reproduce:
1) Open transaction WE19
2) Use any existing iDoc as template
3) Open any segment
4) Fill any field with a lowercase text
5) Press ENTER
6) Re-open the segment and check changed field. -> The value is converted to upper case
This (translate to upper case) happens only on the segment that has been edited in WE19.
In my opinion, the transaction WE19 is not usable because it is not possible to edit/change case-sensitive values. In our customer setting we need to send case-sensitive data in iDocs to the receiver.
Question: Is there any other transaction to read an existing iDoc, change the data case sensitive and send it to the receiver.
Thanks in advance.
Björn

Hi,
yes - this is a "strange" behaviour ;o)
Only other solution I know you need an IDoc in status 51 for:
- go to bd87
- select the IDoc in status 51
- navigate to the needed data record
- double click it
- menu => display => change
- insert your data
After saving the status will be reset and you can process the IDoc in BD87.
I am not sure this will work for each IDoc and element - but you may give it a try.
For converting an existing to status 51 you can use this report: RC1_IDOC_SET_STATUS
Regards,
Kai

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.

Get case sensitive spell check to flag rg174

Here are some words that have been added to spelling dictionary:
CD
CDs
FS237E
George
MS417D
RG174
and also many other product numbers that our company wants to follow our capitalization rules.
For the following sentence:
You might find what george has to present in download format on fs237e, but if you prefer cd format then you should consider ms417D.
Case sensitive spell chcek of this sentence only flags "george" and "cd" as misspellings. but not the two products.
Hopefully Indesign can handle this and simply I am doing something wrong.
Thanks, Edward

I was hoping somebody who actually uses spell checking would pick this up overnight...
I suspect that the problem is ID ignores words with numbers, and I don't see any settings to make that a user choice. You might want to add these to the auto-correct list (smething else I never use).

Check links as case sensitive

I can't remember, and I don't have dreamweaver right now (I'm on vacation):
Does DW support check links site wide as case sensitive?
e.g. does it recognize the difference between ../Images/myImage.gif and ../images/myimage.gif?
or, is there an option to enable/disable that kind of check?

I trust you, and I vote as the right answer, before I even
see it with my own eyes
Thank you Murray

Paramenter Value Case Sensitive Setting

Is there a setting in the pref.txt file (or any place else) to change the actions of the case sensitive setting for entering parameter values? Turning it off/on. Changing the case sensitive setting in the condition that contains the parameter does not modify the parameter value entry window functionality.
Thanks,
Jerre

Hi Jerre
I'm afraid there is no preference that can be set to control the casing of the values keyed in a parameter. You would have to do this yourself by embedding the value of the parameter into a calculation and use UPPER or LOWER accordingly.
The option you are referring to controls whether Discoverer should literally take the value keyed in the parameter as the filter for the condition or not. It does not change the casing of the parameter for other uses.
Best wishes
Michael

How to make Values in Table maintenance to be case sensitive

Table has only one field called link which is used to store the URL along mandt.
Table is maintained thru table maintenance
When I give value say http://www.abc.com/ipr/input into the table thru table maintenance, by default the contents are changed to caps
HTTP://WW.ABC.COM/IPR/INPUT like this
I pass this link to the email content and it doesnu2019t navigate thru the path mentioned.
While clicking the link in the content, it is changing to
http://www.abc.com/IPR/INPUT and asks to go to index page.
Can you help me to change all the values to be maintained as case sensitive ?
Thanks

Hai,
Use this Domain for yur URL data element TEXT150 or TEXT120 .
Yur probelm solved.
reward If usefull.
Thanks,
Durai.V

Retrieve values, irrespective of case sensitive

Hi all,
How to retrieve values, irrespective of case sensitive. For Examle,
column_value = "name" when i try to retrive by using
select * from table where column_value = 'NAME'
But when i use the following query it is working
select * from table where column_value = Lower('NAME')My request will contain upper or lower values, so irrespective of the case sensitive i need to retrieve values. How could this be possible.
Thanks

You need to apply the upper/lower function on both sides to ignore case
select * from table where lower(column_value) = Lower('NAME')
//OR
select * from table where upper(column_value) = upper('NAME')

Is there a way around Case Sensitive on Parm's? & Multiple Value Entry in Parms

Post Author: DennisC
CA Forum: General
Using Ver 10.0 with Lotus Domino -
I have a parmeter setup to pull in ALL records or by a selected value. Many of the values are in CAPS but some are not (they are mixed). From everything I have researched it appears the user must enter the value exactly like it is on the database making it Case Sensitive ---> is there a way around this. I would like to have the user just enter the value regardless of caps or no caps also
they can enter the value of "All" (pulls in all records) or "XYZ" that only pulls in records with XYZ. Is it possible (without creating an additional parm) to give the user the capability to enter "ABC" and "XYZ" and pull in all records with the value of ABC or XYZ in the data field...
thanks in advance for any help!!!!!!!!!!!!!!!!!!!

Post Author: pvierheilig
CA Forum: General
There are a couple options, along with the previous post.
First, and not sure if CR 10 has this as an option, but in XI, you can specify in the Options and Report Options to enable case-sensitivity.
Another option is to create a formula, such as UPPERCASE({table.field}) and reference the formula in the record selection. Such as ?parm = UpperCase({table.field})
I haven't had to deal with this lately, but it seems like it should work.

Case Sensitive Check

Hi,
Is there any way, java could differentiate case sensitive file names or folder names on a windows machine, i think its possible on a linux box. can anyone help me on this
thanx

Java on windows and Java on Linux are the same. The operating systems on the other hand are not: windows is case insensitive and Linux is case sensitive. So there is no need to differentiate case sensitive filenames on windows as you cannot have two files with the same name in the same folder.

Case sensitive statement in the select-statement

Hi All,
i have a table in the abap-dictionary filled with names...when i try to select them with the select-statement with condition:
table-name_column like 'some_name'
I have encountered some problems...the inquiry is case-sensitive. What i want to do is to read the value from the abap-dictionary table uppercase or lowercase and compare it with the needed value also translated in uppercase or lowercase.
The only idea i have is to select all values of the dictionary table into an internal table and to translate the values there in uppercase or lowercase and then to loop trough it. But this approach would cost a lot of performance.
Do someone has an other proposal?

check...
Select statement
It would be difficult , because it is based on how data is stored in the data base , now consider the scenario of the system i am using , we can material description as 'test' or 'TEST' , 'Test' .
If in your system there are only stored in either caps or small the you can perform the select twice .
But i myself dont find it to be such a good solution , but you can give it a try
There is one more solution specific to material description ,and that is in the table MAKT there is a field MAKTG , which stored the description in uppercase , so for this you can first convert the description to uppercase and then perform select on this field

Are idoc fields case sensitive?

Hello, there has been an error during idoc processing. The trading partner field was filled in lowercase and this is bringing me error Message no. FB279 ' Company dp0017 is not defined'. The other idocs had DP0017 filled in and were processed fine.
Any input on this? thx.
Edited by: Antish Awootar on Jun 7, 2011 8:02 AM

Hi Antish,
It actually depends on the value that is stored in the IDOC, if the IDOC has company code in lower case then that is exactly how it will be used in the program for all purpose and no automatic conversion is applied. The below message is thrown in the FM - FI_COMPANY_CHECK This FM will look up the table T880 - If you check the entry in this table will be DP0017 and not dp0017. Hence it is throwing the error message.
If your question is it works fine when i try in SE37 with the FM "FI_COMPANY_CHECK" or if i input "dp0017" in WE19 or in SE11 against T880, then the reason for that is a conversion is applied automatically and it is changed to DP0017.
To answer your question "Are idoc fields case sensitive?", it depends on the context, does it retain the case when it is filled in, yes it does.
Regards,
Chen
Edited by: Chen K V on Jun 7, 2011 4:10 PM

Jdbc bug in executeUpdate(sql, int[]) when table name is case-sensitive;

I have found a bug in oracle's jdbc (ojdbc6.jar), can someone tell me how to submit it so that it can be fixed?
The BUG: using executeUpdate(insert_sql_stmt, int[]) to retrieve the generatedKey generated by before-insert trigger using a sequence results in error when the tablename is case-sensitive (but OK if table name in uppercase).
Steps to reproduce:
1a. create table "mixCase" (f1 integer, f2 varchar2(20));
1b. create table upperCase (f1 integer, f2 varchar2(20));
2a. create sequence mixCase_seq start with 1;
2b. create sequence upperCase seq start with 1;
3a. create or replace trigger mixCase_trigger before insert on "mixCase"
bq. for each row \\ begin \\ select mixCase_seq.nextval into :new.f1 from dual; \\ end;
3b. create or replace trigger upperCase_trigger before insert on upperCase
bq. for each row \\ begin \\ select upperCase_seq.nextval into :new.f1 from dual; \\ end;
4a. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into \"mixCase\"(f2) values('aa')",new int[]{1});
4b. String url = "jdbc:oracle:thin:@//localhost:1521/orcl";
bq. conn=DriverManager.getConnection(url,user,password); \\ Statement stmt = conn.createStatement (); \\ int rc=stmt.executeUpdate("insert into upperCase(f2) values('aa')",new int[]{1});
When you run 4a or 4b in a java jdbc program:
4b runs OK and rset=stmt.getGeneratedKeys() returns the correct f1 value of 1.
4a results in error:
bq. h6. java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist \\ + at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)+ \\ + at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)+ \\ + at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)+ \\ + at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)+ \\ + ...+
+Notes:</</em>
# If Statement.RETURN_GENERATEDKEYS is used instead of "new int[]{1}" in 4b, there is no error but the rset=stmt.getGeneratedKeys() returned in a ROWID such as 'AAARUyAAEAAAAGQAAL', not what is expected. Other database's jdbc return the correct generated integer value.
# Same 4b error if new String[]{"f1"} is used as 2nd argument for executeUpdate.
# The only difference in 4a and 4b is that 4a has case-sensitive table name. All sequence names, trigger names, column names are implicitly deemed to be uppercase by oracle in both cases.
bq.
Edited by: user10343198 on Oct 2, 2008 5:50 PM
Edited by: user10343198 on Oct 2, 2008 6:34 PM

Please patch one fo your machines to 10.2.0.3 and then try and duplicate. You do not have to go through the complete registration of the XSD process thoguh you can check and see if the c based parser will validate on the command line using the
schema executible under your oracle_home bin directory.
schema 1.xml 1.xsd
for example
if it dupes in 10.2.0.3 open a TAR with support so that we may bug it.
regards
Coby

Check Case sensitive values

Similar Messages

Maybe you are looking for