Make material number in MM01 case sensitive

Hi Experts,
I got an requirement like to make MM01 transaction while creating material number it has to accept both Lower and Upper Case..
Say for example : "a12" as one material
"A12" as another one material
any suggestions please send.....
Thanks.
Preethi jose

First check conversion-exit of domain MATNR (something like MATN1) with Customizing behind, you will have to analyze your Customizing (and the list of extensions, solutions installed on your system) to find the actual field(s) which contains the external format of the material master id (e.g. MARA-MFRPN for a sample) AND look at table MATERIALID (domain MATNR_EXT is also not case sensitive), then you may, with a SSCR key for the object as it will be a change of the standard, change the domain(s) definition to allow lowercase. But consider before some problems like search help becoming case sensitive, it is usually (at least) not a good idea to have key fields case-sensitive...
If possible, my advice is to not make this change by a developement, but to look for Customizing, check
Regards,
Raymond

Similar Messages

How to modify material number in MM01

Hi Guru,
I want to modify material number in MM01 according to the material group selected by the user. For example if material group 100 is selected, the material number should be 100xxxxx, 200 is selected, number should be 200xxxxx. I tried coding in user exit MGA00001, everything is fine except the classification view was not updated by the generated material number. How can I achieve this?
Thanks a lot,
Tony.

Hi,
You have to make few configuration settings before you actually restrict at the object level. The solution is clearly discussed in the below thread:
how to restrict material master by material type t-code MM01
Hope this helps!!
Regards,
Raghu

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).

How to make material number field invisible in MM60?

Dear expert,
Is there any way to make material number field invisible in MM60 for one user?
Best regards

Hello,
You may create a transaction variant for MM60 and hide Material code using SHD0. Then create Variant group and assign users to this group.
Thanks,
Venu

What Changes should i do for taking material number in MM01.

Hi ,
I am recording Material Master 'MM01'. In that Material Number is not taking numeric values. Automatically its generating one number for one record. But I want to give my own number to that material. what changes I need to do. I want to use that recording in BDC program.
Plz..give me the solution.

That is due to functional settings. Here the internal and external no ranges are defined on the basis of material types.
Just go through spro tcode logistics general->material master->material types---> define number ranges for each material type. Here you can see a table control just check whether any material type is there with external check box as checked. Now at the time of recording just enter that material types which allows you to give a external material no( inside the defined range). Or just ask your functional.

Make Revision Level Case Sensitive

Hi,
I am creating a new revision level for a material under a change number. Under that same change number I am changing the BOM and routing for the new revision level of the material. We use the drawing number of the material as the Material Number. If client does some changes in the drawing they capture it as the "Alteration Index" (we have mapped it as Revision Level in SAP). Now the requirement from client is that we should have Revision Level as case sensitive i.e. A" and "a" should be treated as different entities. How can this be mapped in SAP as in the system the revision level is not case sensitive?
Any ideas please?

Let me add some more information, so that someone may find this thread interesting to reply :). My client is using alteration index (Revision Level in SAP) as both capital and small letters i.e. revision level is case sensitive for them. I cannot map their Revision Level in SAP as they will have two Revision Levels "A" and "a" as a different entity, but SAP will take both as one. I discussed this with my ABAPer and I got some pointers:
1) We can copy the revision level field, make a Z-field and make it as case sensitive. But this way we will have huge task to point to this new field where ever Revision Level field is referenced.
2)We can make this field itself as case sensitive i.e. make this SAP standard field as case sensitive.
I think that we can go with the second option, but do not know if it can cause any serious implication.
Can someone advice please?

How make IN operator not case sensitive ?

create table Payment_Methods (
Payment_Method_ID number primary key,
Payment_Method varchar2(11)
check (Payment_Method in ( 'Cash','Check','Credit Card' ) ));
the problem here .... if I insert in the Payment_Method column
by lower case or by upper case , the error will appear like this :-
SQL> insert into Payment_Methods values (
2 1,'cash');
insert into Payment_Methods values (
ERROR at line 1:
ORA-02290: check constraint (DE.SYS_C0010420) violated
and if upper case :-
SQL> ed
Wrote file afiedt.buf
1 insert into Payment_Methods values (
2* 1,'CASH')
SQL> /
insert into Payment_Methods values (
ERROR at line 1:
ORA-02290: check constraint (DE.SYS_C0010420) violated
only initcap case working (like I wrote in create table statement )
SQL> ed
Wrote file afiedt.buf
1 insert into Payment_Methods values (
2* 1,'Cash')
SQL> /
1 row created.
How can I make the Payment_Method column NOT case sensitive ??!!!!

I don't understand this check constraint at all. What is the purpose?
You have a table to hold all possible payment methods. At the same time you are not allowing any new payment methods but the ones defined in the check constraint.
Either use a check constraint to check the correct spelling without checking the values, like check (InitCap(Payment_Method) = Payment_Method) or use a database trigger and a unique key constraint to transform all new values to the correct spelling method (UPPER or INITCAP).

How to get material number in smart form driver prog attached to MM01:NACE?

Hi,
I have attached driver program of smart form to MM01 usinfg nace.
On save smart form should get generated.
Can anybody guide me how to get material number from MM01 in driver program on saving MM01.
as of now am not getting values in smart form.
What additional lines to be coaded in driver program to get material number.
Thanks.

hi,
use nast table in your import paramaters of smart forms.
In the Nast table you can find a field with object key which holds the Material Number.
Hope this helps.
Thanks,
subash

How do I make the my login page username field not case-sensitive?

Can anyone tell me how to make my username field not case-sensitive?
This is my code
<html>
<body>
<%@ page import="java.sql.*" %>
<%
String username = request.getParameter("username");
String password = request.getParameter("password");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
Connection login = DriverManager.getConnection("jdbc:odbc:Testing","abc","abc");
Statement stmtLogin = login.createStatement();
String sqlLogin = "SELECT UserName, UserPassword FROM Users WHERE UserName='"+username+"'";
ResultSet rsLogin = stmtLogin.executeQuery(sqlLogin);
while(rsLogin.next())
String suser = rsLogin.getString("UserName");
String spass = rsLogin.getString("UserPassword");
if(username.equals(suser) && password.equals(spass))
HttpSession mysession = request.getSession(true);
mysession.setAttribute("username",request.getParameter("username"));
response.sendRedirect("hello.jsp");
else if(!(username.equals(suser) && password.equals(spass)))
response.sendRedirect("index.jsp?message=Invalid%20Username%20or%20Password");
login.close();
%>
</body>
</html>

if(username.equalsIgnoreCase(suser) && password.equals(spass))Hope this helps!

Material Number mandatory for PR exceptP for Service Purchase Requisition

Hi All,
Our client's new requirement is we need to give material number mandatory for Purchase Requisition. But it should not affect for Service Purchase Requisition (as we don't have material number with material type DIEN. Till now, we were using Acc Assignment Category K and Item Category D with only Short Text description). We have separate document type for Service Purchase Requisition(ZSRV).
In order to make Material number mandatory, in PR, we need to give in "Define Screen Layout at Document Level for PR",right? Is there any way to give, "Material Number Mandatory at Document Type Level"?
Please suggest.
Regards,
rosh

hi sridhar,
Thank you for your answer. So as you said, there is no possibility to make material number as mandatory at DOCUMENT TYPE level through Customzining, right?
Regards,
Rosh

How to display an Image corresponding to it Material Number.

Dear All,
I have a question .. Is it possible to display a Material image .. corresponding to a Material Number in MM01.
EX: matn = 123 and for which there's a corresponding material image.
How can i achieve this ?
Can u please provide me with some links or any clue .. ?
Looking forward to your replies .
Thanks.
Best Regards,
Jitesh pamnani.

http://wiki.sdn.sap.com/wiki/display/ABAP/AssigningImageusingDocumentManagement+System
Dear,
Please check the useful links:
Upload a graphic in material master
Screen exit for MM01 to add additional fields to basic data tab .
Button on Material Master
Upload Article Images and Map to Master Data in SAP Retail 6.0
http://wiki.sdn.sap.com/wiki/display/ABAP/AssigningImageusingDocumentManagement+System
Regards,
Syed Hussain.

Login - is it case sensitive?

Hi everyone,
I'm using WLS4.0 SP2 with iPlanet LDAP server, and seeing a peculiar thing.
When a user login to the portal, and types username with different case
(lowercase in place of uppercase and vice versa), the portal let the user
login (can see the "customize portal" and "logout" button), but shows no
portlets but the initial welcome page before login. The caching realm setup
for the LDAP server is not case-sensitive. Our network admin also says that
the LDAP server is not case-sensitive.
My question is - where could the source of this peculiar case sensitivity
be? Any insights?
Thanks!
Makoto

You can make only user account login case sensitive but not password.
SQL> create user "Test" identified by "tEST";
User created.
SQL> grant create session to "Test";
Grant succeeded.
SQL> conn test/test
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> conn "Test"/test
Connected.
SQL>

Nautilus case sensitive ordering

Hi,
Just wondering if it's possible to make nautilus order files without case sensitivity when they're sorted by name.
I've tried a few searches but turned up nothing, except that the gnome documentation says it isn't case sensitive (here)
There's nothing in gconf either, as far as I can see.
If I recall correctly, it wasn't case sensitive when using nautilus in other distros...
Sorry if this has come up before, but I couldn't find anything in the forums.
thanks
Fishonadish[/url]

Sorry to dig this out, but I have the same problem here. Maybe it has something to do with a Locale setting?
EDIT: Indeed, changing the Locale did fix the problem. Add this to your ~/.bashrc
export LC_COLLATE="en_US.utf8"
Note: Now most programs will sort files insensitive including the "ls" command.
Last edited by IceHand (2007-05-07 18:37:59)

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?

Making user account logins/passwords case sensitive?

Hi, just a quick question. Is it possible to make user account login/passwords be case sensitive? At the moment they are case insensitive.
Thanks :)

You can make only user account login case sensitive but not password.
SQL> create user "Test" identified by "tEST";
User created.
SQL> grant create session to "Test";
Grant succeeded.
SQL> conn test/test
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> conn "Test"/test
Connected.
SQL>

Make material number in MM01 case sensitive

Similar Messages

Maybe you are looking for