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?

Similar Messages

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

  • Case sensitive password in ECC6.0

    Hi All,
    I'm using the below code to connect to SAP ECC6 system. The below code works fine when the SAP Logon  password is all caps. But, when the password is mixed case I get an Error Message.
    *     SAPHD hd = SapConnc(argv, sapsys, client, cadsys, user, passw, langu, vers, msg);*
    As ECC 6 is case-sensitive, does anyone know any workaround to make sure that case-sensitive password login works from external application on ECC6.0 also.
    Thanks in advance,
    Naveen

    please check parameter
    login/password_downwards_compatibility
    according to sap help:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/d2/141fb593c742b5aad8f272dd487b74/frameset.htm
    Specifies the degree of backward compatibility to be achieved. The default value is 1, where the values have the following meaning:
    0
    Caution
    With login/password_downwards_compatibility = 0, passwords are stored in a format that systems with older kernels cannot interpret. The system only generates new (backward incompatible) password hash values.
    1
    The system also generates backward compatible password hash values internally, but does not evaluate these for password-based logons (to its own system). This setting is required if this system is used as the central system of a Central User Administration that systems that only support backward compatible password hash values are also connected to the system group.
    2
    The system also generates backward compatible password hash values internally, which it evaluates if a logon with the new, non-backward compatible password failed. In this way, the system checks whether the logon would have been accepted with the backward compatible password (truncated after eight characters, and converted to upper-case). This is recorded in the system log. The logon fails. This setting is to allow the identification of backward incompatibility problems.
    3
    As with 2, but the logon is regarded as successful. This setting is to allow the avoidance of backward incompatibility problems.
    4
    As with 3, but no entry is created in the system log.
    5
    Full backward compatibility: the system only creates backward compatible password hash values.
    Available after SAP NetWeaver 6.40

  • Case sensitive comparision in ABAP?????

    Hi Guys,
    Is there any way to do case sensitive comparision in ABAP. If not then what will be the work around?
    eg: Vinod should not be equal to vinod.
    Thanks,
    Vinod.

    As I tested, by default the equal sign comparison is case-sensitive. That is, below code shows some result:
    IF 'a' <> 'A'.
      WRITE / 'Comparison is case-sensitive.'.
    ENDIF.
    If you want the opposite behavior, then you need to use some other methods, such as suggested in previous posts, translate to upper case and then compare.
    However, SQL SELECT statement comparison is by-default case-insensitive. It is possible to configure the database server to make it case-sensitive, and there are other ways to work around that, too, such as reading the data into an internal table and do ABAP comparison. Internal table loop with where and read by key are both case-sensitive.
    Note however, that domains can be defined as case-insensitive. To make comparison always case-sensitive, you should always convert non-string to a string.

  • 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

  • Print Location Case sensitivity

    Hi all,
    Recently, we've engaged in a project and the server has 2 folders, FOLDER and folder. For which, FOLDER is where we wish the pdfs will be printed and the printer tags in the ini files point to the capitalized version. When we run the sh file to print however, the files are put into the lowercase folder and if we delete the lowercase folder, documaker simply cannot find the uppercase folder. Is there a way to make the path case sensitive and see the allcaps folder?
    Thanks!

    As you may realize, Windows does not have case sensitive directory names. That means you can't have a "FOLDER" and "folder" in the same  location. Since most users have Windows development workstations, there were often issues for users migrating files back and forth between Unix and Windows. No one liked having to modify INI files or other configurations when bridging these platforms. For this reason, Documaker decided long ago to treat all file and directories as lower case on Unix platforms. That way you don't have to worry when moving INI files or other configuration files between a Windows development environment to a Unix runtime environment. Just make everything lower case and you are golden.
    The short story is that you can't have the mixed case directory names on Unix, so you should choose another name for your output location. Perhaps "out_folder" or "pdf_folder".

  • How to make oracle is case insentive ( not case sensitive)

    SqlServer by default is NOT case sensitive (data content) while Oracle by default is case sensitive (data content).
    please help me to give the solution
    How to make oracle is case insentive ( not case sensitive)
    if there is anyway to make Oracle behave like SqlServer changing NLS settings or any other Oracle settings?
    I have solution for application level . it is working fine
    Possible solutions:
    1. You want to store data case insensitive: do an 'insert...
    values(upper('Abcd'))...'.
    This will put your data in upper case into the tables.
    2. Your data will be mixed-case and you want to select them case
    insensitive:
    create 'function based indexes' on every column you want to use in
    your where-clauses.
    Then 'select ... where <column_name> = 'ABCD'.

    What version of Oracle? Oracle 10g has a capability that can toggle this feature on and off at the session level. Prior versions do not.
    For prior versions you usually have to make use of the upper and/or lower functions in your queries. Sometimes a function based index, FBI, is used to handle this.
    HTH -- Mark D Powell --

  • How to make my program case - in sensitive?

    Hi,
    Iam writing a SELECT query in report for retrieving the address number by giving address details like street, city and post code.But my program is case sensitive such that if the user inputs either in Upper Case or Lower Case, it will not work.
    For eg: suppose the city is Cape Town. If the user inputs like CAPE TOWN or cape town ( via Selection Screen ), then it won't work.
    How can i  make my program case- in sensitive?? please suggest..

    This is possible. I have done something similar to it in my search programs.
    For this we need to make a subroutine. In this subroutine we first need to convert the case into upper case using
    TRANSLATE string TO UPPER CASE.
    then prefix and postfix this string with &,
    _and if this does not work then we have to break the srting entered by the user on basis of spaces and prefix and postfix it with &. _
    Now pass this string to the query and it will definitely get the result.

  • How to make PowerPivot case sensitive?

    Hi all,
    I just discovered that PowerPivot is case-insensitive, which is quite a big problem for me. The only discussion of this I found so far is here: http://dennyglee.com/2010/06/18/powerpivot-you-are-so-insensitive-case-that-is/ .
    That didn't fully answer my question though, is it possible to change this behaviour and make it case sensitive?
    The reason it's a problem for me is that I have a column (from external data source) used as an ID in a relationship, which contains a string of random characters. If it so happens that two entries have an ID which only differs by a case of a letter, everything
    blows up. More precisely, I can no longer import the data into the table where the column is used as a PK, because it is not unique.
    Thanks for any comments,
    Jurgis

    You can post bugs on Connect.
    Thanks!
    Ed Price, SQL Server Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • 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!

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

  • 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

  • Case sensitivity in domain level

    Dear all ,
    There is a z table with having some field and data .
    That field is not case sensitive at Domain level
    so we are able to put any data as the data type is char type ,
    but when im giving the same data while making the selection it is showing
    "NO DATA EXIXTS FOR THAT SELECTION"
    For ex.: i have a field value in table say "Reliance Comm", it is there in the table but if u came out of it.
    And give the same value "Reliance Comm" at the selection screen while making the enrty its saying
    "No table entries found for the specified key"
    but if im giving "RELIANCE COMM" it is showing me the valid result.
    As i have to pass some value to this table at run time and also fetching some data from the table
    based on selection screen in a report  ,so its creating problem .
    Please help <removed by moderator>.
    Edited by: Thomas Zloch on Jun 11, 2010 5:32 PM

    hi chandan,
    in domain there is one lower case indicator...if it is set then uppercase and lower case are distinguished when you enter values with screen masks.Otherwise if you dont check it, all the letters entered will be converted to upper case when you enter values with a screen mask.
    to convert to uppercase.....
    DATA text TYPE string.
    text = `Hello World`.
    TRANSLATE text TO UPPER CASE.
    hope this help you...
    thanks and regards,
    tanmaya

  • 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

Maybe you are looking for