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
Similar Messages
-
Conversion from a case-sensitive to case-insensitive disk configuration.
Being an old Unix user, I configured my disks to be case-sensitive. I've discovered that patches and updates to some applications fail due to changes in the case used for file names.
Is there a painless way to convert a case-sensitive file system to one that is case-insensitive?I don't have current version of SoftRAID 4.0 but I thought that was one of its features, just as it can change the block size for arrays from 16-32-64-128k etc on the fly.
I haven't used it, but iPartition claims to be able to convert in-place between case-sentitive and case-insensitive HFS+ formats.
The trouble is, even then, a restore may not work properly.
http://www.dslreports.com/forum/r19614460-Convert-hard-drive-to-HFS-that-is-not- case-sensitive -
I need help setting up the wireless router for my iMac. I did not know the WEP password when I first turned it on to set things up. Now that I know the WEP password I cant get Network Diagnostics to accept it. I know it is case sensitive and was very careful when I entered the password. What should I do?
Hi, unfortunately WEP is about as secure as a bar of gold lent to a Gang Den! It can be broken in under 30 seconds these days!
If the PW is ASCII, try enclosing it in qoute marks, if Hex try preceding it with the & or % sign.
Also, is the Router set to only allow connect ion to MAC addies of the Interface? -
I joined a website with my id in all small letters. Firefox has automatically made it with an initial cap. The website is case sensitive and will not allow me in. How do I remove the automatically set id password and start over so that I may have access to that web site? Thanks.
I have decided to dedicate this thread to the wonderful errors of Lion OSX. Each time I find a huge problem with Lion I will make note of it here.
Today I discovered a new treasure of doggie poop in Lion. No Save As......
I repeat. No Save As. In text editor I couldn't save the file with a new extension. I finally accomplished this oh so majorly difficult task (because we all know how difficult it should be to save a file with a new extension) by pressing duplicate and then saving a copy of the file with a new extension. Yet then I had to delete the first copy and send it to trash. And of course then I have to secure empty trash because if I have to do this the rest of my mac's life I will be taking up a quarter of percentage of space with duplicate files. So this is the real reason they got rid of Save As: so that it would garble up some extra GB on the ole hard disk.
So about 20 minutes of my time were wasted while doing my homework and studying for an exam because I had to look up "how to save a file with a new extension in mac Lion" and then wasted time sitting here and ranting on this forum until someone over at Apple wakes up from their OSX-coma.
are you freaking kidding me Apple? I mean REALLY?!!!! who the heck designed this?!!! I want to know. I want his or her name and I want to sit down with them and have a long chat. and then I'd probably splash cold water on their face to wake them up.
I am starting to believe that Apple is Satan. -
HT5096 Format required is Mac OS Extended (Case sensitive and Journaled)
In step 4 of this article, the disk must be formatted as Mac OS Extended (Case sensitive and Journaled) or the system won't copy Backups.backupdb.
Really why not just check the box that says ignore ownership on the volume.
-
CASE STATEMENTS AND CASE EXPRESSIONS IN ORACLE9I PL/SQL
제품 : PL/SQL
작성날짜 : 2001-11-13
CASE STATEMENTS AND CASE EXPRESSIONS IN ORACLE9I PL/SQL
=======================================================
PURPOSE
아래의 자료는 Case 문에서 oracle 8.1.7과 Oracle 9i의 New Feature로 8.1.7에서는
sqlplus 에서만 가능했고, 9i 부터는 pl/sql 까지 가능하다.
Explanation
1. Oracle 8.1.7 Feature
Oracle 8.1.7 에서 Case 문은 Decode 문과 유사하지만, 기존의 decode 문을 쓰는 것보다
더 많은 확장성과 Logical Power와 좋은 성능을 제공한다. 주로 나이와 같이 category 별로
나눌때 주로 사용하고 Syntex는 아래와 같다.
CASE WHEN <cond1> THEN <v1> WHEN <cond2> THEN <v2> ... [ELSE <vn+1> ] END
각각의 WHEN...THEN 절의 argument 는 255 까지 가능하고 이 Limit를 해결하려면
Oracle 8i Reference를 참조하면 된다.
The maximum number of arguments in a CASE expression is 255, and each
WHEN ... THEN pair counts as two arguments. To avoid exceeding the limit of 128 choices,
you can nest CASE expressions. That is expr1 can itself be a CASE expression.
Case Example : 한 회사의 모든 종업원의 평균 봉급을 계산하는데 봉급이 $2000보다 작은경우
2000으로 계산을 하는 방법이 pl/sql을 대신하여 case function을 사용할 수 있다.
SELECT AVG(CASE when e.sal > 2000 THEN e.sal ELSE 2000 end) FROM emp e;
Case Example : 나이를 column으로 가지고 있는 customer table을 예로 들어보자.
SQL> SELECT
2 SUM(CASE WHEN age BETWEEN 70 AND 79 THEN 1 ELSE 0 END) as "70-79",
3 SUM(CASE WHEN age BETWEEN 80 AND 89 THEN 1 ELSE 0 END) as "80-89",
4 SUM(CASE WHEN age BETWEEN 90 AND 99 THEN 1 ELSE 0 END) as "90-99",
5 SUM(CASE WHEN age > 99 THEN 1 ELSE 0 END) as "100+"
6 FROM customer;
70-79 80-89 90-99 100+
4 2 3 1
1 SELECT
2 (CASE WHEN age BETWEEN 70 AND 79 THEN '70-79'
3 WHEN age BETWEEN 80 and 89 THEN '80-89'
4 WHEN age BETWEEN 90 and 99 THEN '90-99'
5 WHEN age > 99 THEN '100+' END) as age_group,
6 COUNT(*) as age_count
7 FROM customer
8 GROUP BY
9 (CASE WHEN age BETWEEN 70 AND 79 THEN '70-79'
10 WHEN age BETWEEN 80 and 89 THEN '80-89'
11 WHEN age BETWEEN 90 and 99 THEN '90-99'
12* WHEN age > 99 THEN '100+' END)
SQL> /
AGE_G AGE_COUNT
100+ 1
70-79 4
80-89 2
90-99 3
Example
2. Oracle 9i Feature
Oracle 9i부터는 pl/sql에서도 case문을 사용할 수 있으면 이것은
복잡한 if-else 구문을 없애고, C언어의 switch문과 같은 기능을 한다.
아래의 9i pl/sql Sample 및 제약 사항을 보면 아래와 같다.
Sample 1:
A simple example demonstrating the proper syntax for a case
statement
using a character variable as the selector. See the section entitled
'Restrictions' at the end of this article for details on which PLSQL
datatypes may appear as a selector in a case statement or
expression.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
begin
case achar
when 'A' then dbms_output.put_line('The description was Excellent');
when 'B' then dbms_output.put_line('The description was Very Good');
when 'C' then dbms_output.put_line('The description was Good');
when 'D' then dbms_output.put_line('The description was Fair');
when 'F' then dbms_output.put_line('The description was Poor');
else dbms_output.put_line('The description was No such Grade');
end case;
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 2:
A simple example demonstrating the proper syntax for a case
expression
using a character variable as the selector. See the section entitled
'Restrictions' at the end of this article for details on which PLSQL
datatypes may appear as a selector in a case statement or
expression.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
description varchar2(20);
begin
description :=
case achar
when 'A' then 'Excellent'
when 'B' then 'Very Good'
when 'C' then 'Good'
when 'D' then 'Fair'
when 'F' then 'Poor'
else 'No such grade'
end;
dbms_output.put_line('The description was ' || description);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
NOTE: The above simple samples demonstrate two subtle differences in the
syntax
required for case statements and expressions.
1) A case STATEMENT is terminated using the 'end case' keywords; a
case
EXPRESSION is terminated using only the 'end' keyword.
2) Each item in a case STATEMENT consists of one or more
statements, each
terminated by a semicolon. Each item in a case expression
consists of
exactly one expression, not terminated by a semicolon.
Sample 3:
Sample 1 demonstrates a simple case statement in which the selector
is
compared for equality with each item in the case statement body.
PL/SQL
also provides a 'searched' case statement as an alternative; rather
than
providing a selector and a list of values, each item in the body of
the
case statement provides its own predicate. This predicate can be any
valid boolean expression, but only one case will be selected.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
begin
case
when achar = 'A' then dbms_output.put_line('The description was
Excellent');
when achar = 'B' then dbms_output.put_line('The description was Very
Good');
when achar = 'C' then dbms_output.put_line('The description was
Good');
when achar = 'D' then dbms_output.put_line('The description was
Fair');
when achar = 'F' then dbms_output.put_line('The description was
Poor');
else dbms_output.put_line('The description was No such Grade');
end case;
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 4:
This sample demonstrates the proper syntax for a case expression of
the
type discussed in Sample 3 above.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
achar char(1) := '&achar';
description varchar2(20);
begin
description :=
case
when achar = 'A' then 'Excellent'
when achar = 'B' then 'Very Good'
when achar = 'C' then 'Good'
when achar = 'D' then 'Fair'
when achar = 'F' then 'Poor'
else 'No such grade'
end;
dbms_output.put_line('The description was ' || description);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 5:
This sample demonstrates the use of nested case statements. It is
also
permissable to nest case expressions within a case statement (though
it
is not demonstrated here), but nesting of case statements within a
case
expression is not possible since statements do not return any value.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
anum1 number := &anum1;
anum2 number := &anum2;
answer number;
begin
case anum1
when 1 then case anum2
when 1 then answer := 10;
when 2 then answer := 20;
when 3 then answer := 30;
else answer := 999;
end case;
when 2 then case anum2
when 1 then answer := 15;
when 2 then answer := 25;
when 3 then answer := 35;
else answer := 777;
end case;
else answer := 555;
end case;
dbms_output.put_line('The answer is ' || answer);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 6:
This sample demonstrates nesting of case expressions within another
case
expression. Note again the absence of semicolons to terminate both
the
nested case expression and the individual cases of those
expressions.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
declare
anum1 number := &anum1;
anum2 number := &anum2;
answer number;
begin
answer :=
case anum1
when 1 then case anum2
when 1 then 10
when 2 then 20
when 3 then 30
else 999
end
when 2 then case anum2
when 1 then 15
when 2 then 25
when 3 then 35
else 777
end
else 555
end;
dbms_output.put_line('The answer is ' || answer);
end;
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Although PL/SQL anonymous blocks have been used in all of the examples
so far,
case statements and expressions can also be used in procedures,
functions, and
packages with no changes to the syntax.
The following samples are included for completeness and demonstrate the
use of
case statements and/or expressions in each of these scenarios.
Sample 7:
This sample demonstrates use of a case statement in a stored
procedure.
Note that this sample also demonstrates that it is possible for each
of
the items in the case body to consist of more than one statement.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace procedure testcasestmt ( anum IN number ) is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
end;
exec testcasestmt(&anum);
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 8:
This sample demonstrates the use of a case statement in a stored
package.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace package testpkg2 is
procedure testcasestmt ( anum IN number );
function testcasestmt_f ( anum IN number ) return number;
end testpkg2;
create or replace package body testpkg2 is
procedure testcasestmt ( anum IN number ) is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
end;
function testcasestmt_f ( anum IN number ) return number is
begin
case
when anum = 1 then dbms_output.put_line('The number was One');
dbms_output.put_line('In case 1');
when anum = 2 then dbms_output.put_line('The number was Two');
dbms_output.put_line('In case 2');
when anum = 3 then dbms_output.put_line('The number was Three');
dbms_output.put_line('In case 3');
when anum = 4 then dbms_output.put_line('The number was Four');
dbms_output.put_line('In case 4');
when anum = 5 then dbms_output.put_line('The number was Five');
dbms_output.put_line('In case 5');
else dbms_output.put_line('The description was Invalid input');
dbms_output.put_line('In the else case');
end case;
return anum;
end;
end testpkg2;
exec testpkg2.testcasestmt(&anum);
variable numout number
exec :numout := testpkg2.testcasestmt_f(&anum);
print numout
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
Sample 9:
This sample demonstrates the use of a case expression in a stored
package.
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - -
set serveroutput on
create or replace package testpkg is
procedure testcase ( anum IN number );
function testcase_f ( anum IN number ) return number;
end testpkg;
create or replace package body testpkg is
procedure testcase ( anum IN number ) is
anumber number := anum;
anothernum number;
begin
anothernum :=
case
when anumber = 1 then anumber + 1
when anumber = 2 then anumber + 2
when anumber = 3 then anumber + 3
when anumber = 4 then anumber + 4
when anumber = 5 then anumber + 5
else 999
end;
dbms_output.put_line('The number was ' || anothernum);
end;
function testcase_f ( anum IN number ) return number is
anumber number := anum;
anothernum number;
begin
anothernum :=
case
when anumber = 1 then anumber + 1
when anumber = 2 then anumber + 2
when anumber = 3 then anumber + 3
when anumber = 4 then anumber + 4
when anumber = 5 then anumber + 5
else 999
end;
dbms_output.put_line('The number was ' || anothernum);
return anothernum;
end;
end testpkg;
variable numout number
exec testpkg.testcase(&anum);
exec :numout := testpkg.testcase_f(&anum);
print numout
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - -
제약 사항
다음의 databasetype은 case 문에서 지원되지 않는다.
BLOB
BFILE
VARRAY
Nested Table
PL/SQL Record
PL/SQL Version 2 tables (index by tables)
Object type (user-defined type)
All of these types except for object types face a similar restriction
even for if statements (i.e. they cannot be compared for equality directly) so this is unlikely to change for these types. Lack of support for object types is simply an implementation restriction which may be relaxed in future releases.
Reference Ducumment
Oracle 8.1.7 Manual
NOTE:131557.1I have done the following code but doesn't
like the statement of - "case(butNext)". What do you mean "doesn't like" -- did you get an error message?
I'm guessing it won't compile because you're trying to switch on a Button.
I tried something
like "g.fillOval(100,50,70,90, BorderLayout.NORTH)"...no that doesn't make sense. You only use BorderLayout.NORTH when you're adding components to a BorderLayout layout manager. An oval is not a component and fillOval isn't adding a component and Graphics is not a Panel or layout manager.
Would appreciate it if someone could tell me how to position
shapes using the graohic method. I think the problem is that you're confusing shapes with components. -
i would like to know how can i compare a switch case 1 and case 2 in C# is it possible to do that? obs i am a begginer :) I tried to do it with search and sort but it did not go well
let me give you an example if you add a word case 1( lagg ord) how can i compare that word with case 2 words ( in case 2 already exist 5 words)
here is the my program
using System;
namespace ConsoleApplication1
class Program
static void Main(string[] args)
//Meny
Console.WriteLine("\n HÄNGA GUBBE\n");
Console.WriteLine(" 1) Lägg till ord");
Console.WriteLine(" 2) Lista alla ord");
Console.WriteLine(" 3) Spela");
Console.WriteLine(" 4) Avsluta");
bool utgång = false;
do
int Valet;
Console.Write("\n\tVälj 1-4: \n ");
try
Valet = int.Parse(Console.ReadLine());
catch (Exception)
Console.WriteLine("Du skriver fel character!\n" +
"\nSkriv bara mellan 1 och 4");
continue;
switch (Valet)
case 1:
Console.WriteLine("\n lägg ett till ord! ");
var input = Console.ReadLine();
break;
case 2:
Console.WriteLine("\n Lista med alla ord :\n");
string[] array = { " Lev", " Skratta", " Gledje", " Gråt", " Njut" };
Array.Sort<string>(array);
foreach (var c in array)
Console.WriteLine(c);
Console.WriteLine("\n");
break;
case 3:
string guesses, bokstäver;
Console.Write("\n Hur många fel får man ha? ");
guesses = (Console.ReadLine());
Console.WriteLine(" Utmärkt, då spelar vi!\n");
Console.WriteLine(" Felgisningar :" + "0/" + guesses);
Console.Write(" Gissade bokstäver ");
bokstäver = (Console.ReadLine());
Console.WriteLine("Aktuellt ord");
Console.Write("Gissa bokstav : " + bokstäver + " \n");
break;
case 4:
Console.WriteLine("\n HEJ DÅ! \n");
Console.Beep();
utgång = true;
break;
//avbryter while loopen, avslutar spelet
} while (!utgång); -
Case-Sensitive to Case-Ignorant
I am working on restoring a Time Machine backup from Leopard to a clean installation of Snow Leopard. The only problem I'm facing is that the Leopard backup is on a case-sensitive drive (and the Snow Leopard drive is set up, by default, as case-ignorant).
I have scoured the Web the last two days and have not found a definitive answer to my question: Is there a way to transfer the data from the Time Machine backup on the case-sensitive drive to the case-ignorant Snow Leopard drive?
Yesterday I ran across a tutorial explaining how this might be accomplished using SuperDuper! but a commenter explained that Disk Utility could be used and was much easier. I tried the Disk Utility method but it didn't work, and I ran out of time to give the SuperDuper! option a try. Does anyone know if it, or even Carbon Copy Cloner, might solve my problem?
Thanks for any help.nodgih wrote:
I am working on restoring a Time Machine backup from Leopard to a clean installation of Snow Leopard. The only problem I'm facing is that the Leopard backup is on a case-sensitive drive (and the Snow Leopard drive is set up, by default, as case-ignorant).
Hi, and welcome to the forums.
What kind of restore do you want to do? Surely not a full system restore, as that would revert you to Leopard.
Do you want to use +Setup Assistant+ or +Migration Assistant,+ or do selective restores via the "Star Wars" display?
Was the drive that was backed-up case-sensitive, or case-ignorant? -
Hi,
An order will have both Case 1 and case 2 types.
Case 1 :One ordered_item_id has multiple package _id which we call Ship Alone
Case 2: One package_id has multiple ordered_item_id which we call Normal
Requirement: I will give packing_id or ordered_item_id and how do I find out whether that packing_id
will fall in Case 1 or Case 2.
Sample Data: *Ship Alone*
Ordered_item_id Ord_quantity Packing_Id packing_quantity
5858 3 102,103,104 1,1,1
*Normal*
Packing_Id packing_quantity Ordered_item_id Ord_quantity
110 2 5111 2
110 3 5112 3
110 1 5113 1
110 1 5114 1 I have tried this code but it is not giving me expected result.
CURSOR c_count
IS
SELECT oi.ordered_item_id
,oi.quantity_ordered
,SUM(pd.quantity)
,COUNT(packing_id)
FROM ordered_items oi
,packing_details pd
WHERE oi.ordered_item_id = pd.ordered_item_id
AND oi.ordered_item_id = v_ordered_item_id
GROUP BY oi.ordered_item_id
,oi.quantity_ordered;
OPEN c_count;
LOOP
FETCH c_count
INTO ord_itm_id
,order_qty
,package_qty
,count_pack_per_item ;
EXIT WHEN c_count%NOTFOUND;
IF count_pack_per_item =1 THEN
--ddooo something
SELECT COUNT(*)
INTO v_shipalone_count
FROM packing_details pd
,packing p
WHERE pd.ordered_item_id = ord_itm_id
AND p.packing_id = pd.packing_id
AND p.status = 'C';
If (count_pack_per_item > 1) AND (v_shipalone_count >= 1) THEN
--do somethingthis is not complete code but the part which i trying to get the result
Suupose I give packing_id 103 then it should say it will come in Case 1.
Thanks in advance.
Sandy
Edited by: sandy162 on Jun 4, 2009 3:34 PM
Edited by: sandy162 on Jun 4, 2009 3:40 PMThanks as you said Select are woking perfectly fine and seleting cases proeprly but I have problem how to implemet
those selects in my code.. here is my code and at step 6 & 7 im finding out ship_alone or normal case.
Please help me to resolve it.
--Stpe 5 find out number of packages in given order
SELECT count(*)
INTO package_count
FROM packing
WHERE client = v_client
AND order_number = v_order_number
AND status IN ('A','C');
--Step 5a. If only one package for a given Order UPDATE Order status = 'B' else Order status will remain 'S'--
IF package_count = 1 THEN
UPDATE orders
SET status = 'B'
WHERE order_number = v_order_number
AND client = v_client;
END IF;
-- -Step 5b. for all Orders (single or multiple packages) UPDATE ordered_items SET status = 'B'---
UPDATE ordered_items
SET status = 'B'
WHERE client = v_client
AND ordered_item_id = v_ordered_item_id;
IF package_count > 1 THEN
--Step 6. Check ordered_item_id count and packing_id count in given order_number
OPEN c_count;
LOOP
FETCH c_count
INTO ord_itm_id
,order_qty
,package_qty
,count_pack_per_item ;
EXIT WHEN c_count%NOTFOUND;
--Step 6a. package has one/multiple order items
IF count_pack_per_item =1 THEN
cmn_backorder_pkg.create_new_backorder (ordrec); -- Create backorder from backordered items for ordrec.order_number.
END IF;
---Step 6b. Ship-alone means order item has multiple pacakges
SELECT COUNT(*)
INTO v_shipalone_count
FROM packing_details pd
,packing p
WHERE pd.ordered_item_id = ord_itm_id
AND p.packing_id = pd.packing_id
AND p.status = 'C';
---Step 7a Ship alone Order items has already one/more package cancelled
If (count_pack_per_item > 1) AND (v_shipalone_count >= 1) THEN
UPDATE ordered_items oi
SET oi.quantity_ordered = order_qty+package_qty
WHERE ordered_item_id = ord_itm_id ;
------step 7b Canceling Ship Alone package for first time
ELSE
OPEN c_back_order;
LOOP
FETCH c_back_order
INTO ordrec;
EXIT WHEN c_back_order%NOTFOUND;
--Step 8a: Adjust original order items quantity --
p_new_qty := (order_qty - package_qty);
UPDATE ordered_items oi
SET oi.QUANTITY_ORDERED = p_new_qty
WHERE ordered_item_id = ord_itm_id;
---Step 8b: adjust packing detail quantity
v_tran := 'U';
v_line_status := 'S';
v_new_qty := p_new_qty;
OPEN c_adj_item (v_order_number, v_client);
LOOP
FETCH c_adj_item INTO itemrec;
EXIT WHEN c_adj_item%NOTFOUND;
.l
END LOOP;
CLOSE c_back_order; --c_back_order
Thanks
Sandy -
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,
AmitHave 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.
-
Change in SQL from case sensitive to case insensitive
Hi Experts
We have to change the collation setting for one of my clients databases (SAP doc at the time was erroneous) I am wondering if I can change at the same time the DB from being case sensitive to being case insensitive?
thx,
RichardHi Richard,
Are you upgrading from SQL2005 to 2008? We had this problem as it was installed w/SQL2005. What we did was install SQL2008 concurrently with 2005 so we could do a test to ensure fixing the collation would solve some problems with core functionality as well as add-ons, which it did.
Even though all the databases were CI/case insensitive, because the server was CS/case sensitive, it caused problems. You probably have the same. And if you don't, when you upgrade to SQL2008 it seems to do this for you.
Heather -
Username - case sensitivity and embeded period
I have been asked to investigate the impact of syncing our oracle user names with our AD names .. which would mean putting a period (dot) in the username. (example - john.doe). First attempt to create one returned an error which lead to the following testing:
SQL> conn system/****
Connected.
SQL> --
SQL> -- create a user with a dot in the name
SQL> --
SQL> create user ed.stevens identified by tiger;
create user ed.stevens identified by tiger
ERROR at line 1:
ORA-01936: cannot specify owner when creating users or rolesOk, the '.' is seen as a delimiter, so must be quoted, probably leading to case sensitivity.
SQL> create user "ed.stevens" identified by tiger;
User created.
SQL> grant create session to ed.stevens;
grant create session to ed.stevens
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> grant create session to "ed.stevens";
Grant succeeded.
SQL> select username
2 from dba_users
3 where upper(username) like 'ED%'
4 order by 1;
USERNAME
ed.stevens
1 row selected.Now let's do it with an upper case name
SQL> --
SQL> create user ED.STEVENS identified by lion;
create user ED.STEVENS identified by lion
ERROR at line 1:
ORA-01936: cannot specify owner when creating users or roles
SQL> create user "ED.STEVENS" identified by lion;
User created.
SQL> grant create session to ED.STEVENS;
grant create session to ED.STEVENS
ERROR at line 1:
ORA-00933: SQL command not properly ended
SQL> grant create session to "ED.STEVENS";
Grant succeeded.
SQL> select username
2 from dba_users
3 where upper(username) like 'ED%'
4 order by 1;
USERNAME
ED.STEVENS
ed.stevens
2 rows selected.Everything to here makes sense. Now lets' try to connect as these two nefarious characters!
SQL> --
SQL> conn ed.stevens/tiger
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> select user from dual;
SP2-0640: Not connected
SQL> conn "ed.stevens"/tiger
Connected.
SQL> select user from dual;
USER
ed.stevens
1 row selected.
SQL> --
SQL> conn ED.STEVENS/lion
Connected.Whaat?? Why wasn't the '.' seen as a delimiter here? This is the question that this example was leading to.
SQL> select user from dual;
USER
ED.STEVENS
1 row selected.
SQL> conn "ED.STEVENS"/lion
Connected.
SQL> select user from dual;
USER
ED.STEVENS
1 row selected.
SQL> --
SQL> spool off
SQL> conn system/****
Connected.
SQL> drop user "ed.stevens";
User dropped.
SQL> drop user "ED.STEVENS";
User dropped.Centinul wrote:
Ed --
I saw different behavior in my environment:
SQL> CREATE USER "cen.tinul" IDENTIFIED BY mynx;
User created.
SQL> CREATE USER "CEN.TINUL" IDENTIFIED BY mynx;
User created.
SQL> GRANT CREATE SESSION TO "cen.tinul";
Grant succeeded.
SQL> GRANT CREATE SESSION TO "CEN.TINUL";
Grant succeeded.
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> CONNECT cen.tinul/mynx
Connected.
SQL> SHOW USER
USER is "CEN.TINUL"
SQL> CONNECT CEN.TINUL/mynx
Connected.
SQL> SHOW USER
USER is "CEN.TINUL"
"This just gets curioser and curioser."
This is the system I used for the test posted above - running on 32-bit OEL under vmware on my laptop
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE10.2.0.4.0Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5 rows selected.So I ran the test against our prod datbase, running under 64-bit HP-UX Itanium
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5 rows selected.As for what about the two is not shown, the 32-bit Linux was built with the 10.2.0.1 base install, then the 10.2.0.4.0 patchset, then the Oct 2009 CPU - all before creating the database. The database was created from scripts using CREATE DATABASE, as generated originally by dbca (not the 'restore database' scripts from dbca when using one of their pre-defined templates.)
The HP-UX system was built as a 10.2.0.1 database, upgraded to 10.2.0.4, and has all CPU's through Jan 2010.
Both systems gave exactly the same results, which are obviously different from yours ....
A mystery wrapped in an enigma .... -
I did not have my backup with me when my hard drive failed and was replaced at the Apple store. Now it will not download to my new hard drive. A message says that "the volume has the worng case sensitivity for a backup". How can I resore my data from the backup?
Thank youThis is a user-supported board. You are not addressing Apple here. Nor is it a good idea to post your private information to a public forum. You should edit your post immediately.
Unfortunately no one here can access your support history. You must respond to the emails directly. -
Computer desk case openings and case heat
I was reading on Antec's web site the other day about how to beat the summer heat for computer case temperatures and it said to take the computer out of the opening in the computer desk to help it cool better.
I have a nice oak desk that has a computer opening down below and I was wondering if this will be a problem for my new system when I get it going? I never have had a cooling problem before but then again I am only running a 400MHz Celeron at this time. I could cut air holes in the desk opening on one side to help it cool if that ever became necessary, but don't want to if I don't need to.
Have any of you ever had any problems with overheating in these computer desk openings or do you have the computer out in the open?
Thanks
MikeQuote
Originally posted by twistedbrowntucker
Nice case like that I would have it up on top showing it off.Maybe with the side open.LOL
I wish I could TBT, but unless I went at this desk with a saw I am stuck with it being in the desk opening. :(
Seems kind of a waste to buy a case with a see-through window when I can't even see it. lol
Mike -
Name search with and with out case sensitive including * also.
there is an urgent reuirement for name search .
i am having 6 fields all are related to name like name prefix ,firstname, lastname etc. now i want select query so that i can search the person name with case ,with out case sensitive and ' * ' also.
and one more thing
i am having multiple selection for first name,lastname etc.
so i must write select query for >=, = , <= etc also along with ' * ' .
so can any one help me, requirement is urgent.
i cannot add one more field in database.Hi, I did not understand your problem exactly, but I am sending you an sample query according to my understanding.
select <fields names> from <tablename> where name = '%xxx'.
here % is used for searching for all the names which ends with 'xxx'
If you give some more details briefly then I can try for you.
Maybe you are looking for
-
Duplicate pricing conditions printed in the invoice
The values returned in the table parameter "TKOMVD" of the function module "'RV_PRICE_PRINT_HEAD"used in the program RVADIN01, causing some duplicate pricing conditions in the script printing. Also this table parameter is not always returning the sam
-
Hello, i have a strange problem with "strange characters" (such as "à", "ö" etc). I have to edit pdf files produced with Adobe Acrobat by other people. In some cases, when i try to "copy and paste" text from this file into a "note" (within the same f
-
I recently downloaded Lightroom 4. The Jpegs I exported from LR4 are cut off when I click on the full size photo after upload to the creative cloud. Anyone else dealing with this?
-
Character encoding in jtextpane
hi, this is regarding the character encoding in a JTextPane. I need to display UTF-8 charcters in a JTextPane and i'm able to do it. But when i read the data back from the JTextPane using getText() method i'm loosing the encoding.. The characters are
-
How do I talk to someone about cancelling my order?
I am having a difficult time downloading Elements. It is very confusing, and I would rather just forget it and cancel my order and purchase. How do I do that? Is there a customer care phone number? I am having a lot of difficulty navigating.