Restricting special characters

Hi All
I am currently doing the payment extract interface program for the bank. The point here is that the bank doesn't allow some characters which are considered as special characters like (#,$,%,^,*,&) etc..In most of the information like vendor name and invoice numbers they are using these characters.
In my interface program, i am removing this special characters and replacing it with space or '+' symbol as prescribed by bank through translate command.
translate(VENDOR_NAME,'/!;<>"{}[]|=_*&^%$@~#',' ')
But my question is how could i restrict them at the entry level itself?
In case of invoice creation form, when they enter #INV123 then i should intimate them that they have used special characters. Is that possible to do it in Forms personalisation?
Regards
Santhosh

Duplicate post see:
Restricting special characters
Gareth

Similar Messages

  • Restricted Special characters in KM Resource name

    Hi,
    While creating resources in KM, it is not allowing some special characters (ex: '?' , ':') in name.
    How do we know what are all the restricted special characters in KM?
    Please let me know.
    Thanks

    I think the file name restrictions which apply to naming of files on the PC apply to KM Resources as well since the file will have to be created on some file system itself.
    Do refer to [this|http://kb.wisc.edu/page.php?id=2533] link to peek at the list of restricted characters.
    Thanks,
    GLM

  • Restrict Special Characters in String Fields

    Hello,
    My Jdev version is 11.1.1.6 using ADF BC and ADF Faces as technology stack.
    I have a requirement to restrict special characters, html tags as input in String/Varchar2 fields.
    I have couple of thoughts that can be used in application but not sure which is the best approach:
    1. Implement <af:validateRegExp pattern="regular Exp"> inside <af:inputText> component
    2. Implement Entity based validator using Regular Expression
    Apart from picking the best out of above two, I would like to know if there is a better way to implement this validation.
    My application has custom framework extn classes and all Entities/View Objects extend those. Is there a possibility to implement this type of validation at some central place.
    I would highly appreciate expert inputs here.
    Thanks,
    Jai

    Hi,
    the answer to your question is *"use both"*. The entity level would be enough but then would make people subniitting a request afte which they see an error The RegEx validator in ADF Faces handles problems on the client side and thus before a submit is sent to the server (where it then would be also checked using server side validation in ADF Faces). Why not using RegEx validation in ADF faces alone? Because there are potentially many views accessing your entity through view objects and if only one developer forgets the RegEx validator you would be screwed.
    Frank

  • How to restrict special characters for a specific column

    Dear gurus,
    i have a table emp with a field field_1
    in this particular field_1 is an address column where data can be like '12 st first floor' but suppose mistakenly user has entered the data as '12 st first floor & ' it should be restricted (not using trigger but can this be possible by using constraints )so for this how can we restrict the special characters not to get entered into the column.
    regards,
    friend

    Another way of doing it.
    drop table test_table;
    create table test_table (col varchar2(50));
    alter table test_table add constraint chk_address check (NOT regexp_like(col, '[[:punct:]]+'));
    insert into test_table
    (select  'some text' col from dual);
    1 rows inserted.
    insert into test_table
    (select  'some text!' col from dual);
    Error starting at line 20 in command:
    insert into test_table
    (select  'some text!' col from dual)
    Error report:
    SQL Error: ORA-02290: check constraint (FDL_DEV.CHK_ADDRESS) violated
    02290. 00000 -  "check constraint (%s.%s) violated"
    *Cause:    The values being inserted do not satisfy the named check
    *Action:   do not insert values that violate the constraint.
    insert into test_table
    (select  'some text House#32' col from dual);
    Error starting at line 23 in command:
    insert into test_table
    (select  'some text House#32' col from dual)
    Error report:
    SQL Error: ORA-02290: check constraint (FDL_DEV.CHK_ADDRESS) violated
    02290. 00000 -  "check constraint (%s.%s) violated"
    *Cause:    The values being inserted do not satisfy the named check
    *Action:   do not insert values that violate the constraint.
    insert into test_table
    (select  'some text
    (with new line)' col from dual);
    Error starting at line 26 in command:
    insert into test_table
    (select  'some text
    (with new line)' col from dual)
    Error report:
    SQL Error: ORA-02290: check constraint (FDL_DEV.CHK_ADDRESS) violated
    02290. 00000 -  "check constraint (%s.%s) violated"
    *Cause:    The values being inserted do not satisfy the named check

  • Mac file name restrictions/special characters

    What are the Mac OS file name restrictions? What are the special characters to avoid?
    Is this a legitimate file name? Are the colons allowed?
    /Users/Joe/Desktop/MyDocument 3:2:06.xls
      Windows XP Pro  

    Thanks, Sagesse. I'm new to the Mac OS. Is it tied to Unix in such a way that the colons are allowed?
    A user tried to provide a file with a name similar to that in my original post (e.g. "name 3:4:07.rtf") using a web form, and I'm at a loss as to how they could have saved it with the colons. Thank you for your assistance.

  • OID/Portal - Restrict Special Characters to be used in Password

    Hi,
    Does anyone know how I can restrict the use of special characters ($, &, £...etc) in the OID password? I cannot see an attribute to achive this? orclpwdIllegalValues will stop certain words, but I just want to restrict the use of any of the special characters in any password. All suggestions or information would be much appreciated.
    Thanks

    Requires custom plugin (using PL/SQL) to add password value checking to OID password policy management capabilities. A description and example code for this is available in chapter 27 of the Oracle® Internet Directory Administrator's Guide, 10g Release 2 (10.1.2) entitled "Oracle Internet Directory Plug-In for Password Policies" available at http://download.oracle.com/docs/cd/B14099_19/idmanage.1012/b14082/plugin_pwdpolicies.htm#i122359

  • DRM validation to restrict special characters

    Hi can you please help.
    We are not supposed to use these special characters in DRM node name or description.
    dont allow the entry of special character in node names like @,#,$,%,^,&,*,+,-,{}.
    and also use of words like ALL,AND,ASSIGN,CALC,AVERAGE,EXCEPT.
    How can we restrict this.
    Please advise

    Hi,
    See if you can gather some help from one of my earlier posts- Given Below
    Special character Validation: error
    Thanks
    Denzz

  • How to remove special characters in xml

    Dear friends,
    How to remove the special character  from the xml. I am placing the xml file and  fetching through file adapter.
    The problem is when there is any special character in xml. i am not able to pass to target system smoothly.
    Customer asking schedule the file adapter in order to do that the source xml should not have any special charatcters
    How to acheive this friends,
    Thanx in advance.
    Take care

    Hi Karthik,
    Go throgh the following links how to handle special character
    https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
    Restricting special characters in XML within XI..
    Regards
    Goli Sridhar

  • CONSTRAINT rule of no special characters allowed? Help

    ALTER TABLE dbo.tblasset ADD CONSTRAINT
    CK_tblasset_HardwareNumber CHECK ([HardwareNumber]<>'' and [HardwareNumber] is not null)
    GO
    Is there away I can implement special characters being inputted on a NVARCHAR datatype using this?special characters like (* , . ,")Many thanks

    ALTER TABLE dbo.tblasset ADD CONSTRAINT
    CK_tblasset_HardwareNumber CHECK ([HardwareNumber]<>'' and [HardwareNumber] is not null)
    GO
    Is there away I can implement special characters being inputted on a NVARCHAR datatype using this?special characters like (* , . ,")Many thanks
    Your can create a Check
    Constraint on this column and only allow Numbersand Alphabets to
    be inserted in this column, see below:
    Check Constraint to only Allow Numbers & Alphabets
    ALTER TABLE Table_Name
    ADD CONSTRAINT ck_No_Special_Characters
    CHECK (Column_Name NOT LIKE '%[^A-Z0-9]%')
    Check Constraint to only Allow Numbers
    ALTER TABLE Table_Name
    ADD CONSTRAINT ck_Only_Numbers
    CHECK (Column_Name NOT LIKE '%[^0-9]%')
    Check Constraint to only Allow Alphabets
    ALTER TABLE Table_Name
    ADD CONSTRAINT ck_Only_Alphabets
    CHECK (Column_Name NOT LIKE '%[^A-Z]%')
    Source: http://stackoverflow.com/questions/25408483/create-rule-to-restrict-special-characters-in-table-in-sql-server
    web: www.ronnierahman.com

  • Restrict use of special characters in AD usernames

    I am planning to restrict use of any special characters including - "dash" when creating AD users in ADUC console.
    All are windows server 2008 R2 Domain Controllers
    Any suggestions.
    MCSE Certified

    You should change the thread to a question rather than discussion. 
    My recommendation would be to use PowerShell to do this. 
    You could edit this script
     http://gallery.technet.microsoft.com/New-User-Creation-tool-14fa73cd
    It will give you a GUI interface and you could edit this to prevent the characters you want from being used in usernames. 
    Regards,
    Denis Cooper
    MCITP EA - MCT
    Help keep the forums tidy, if this has helped please mark it as an answer
    Blog: http://www.windows-support.co.uk 
    Twitter:   LinkedIn:

  • Issue in creating a add link to a document content type on a doc lib name with , / special characters

    hi,
    i am having a  requirement to create/use "add link to a document" content type for a item in the document library.
    so i got  the code from below site :
    http://howtosharepoint.blogspot.in/2010/05/programmatically-add-link-to-document.html
    my issue is, if teh document  library names are single words - like MOM, model, procedures etc this  functionality is working fine and i am able to view the link to a document as an item. 
    but when the doc lib name contains special characters like , or  /  , this link to a  document  content type functionality is NOT working.
    can anyone pls point me whether this is the  actual  issue ? ie, if  the doc lib name contains special chars  like , or /  my
    add link to a document wont work? is there any restrictions/limitations for doc lib names in SharePoint ?
    for eg: my doc lib names are :
    1) Report and analysis, Data
    2) form / template
    3) map/ plot
    help is highly appreciated!

    hi,
     its talking abt the subsite names and  folders and NOT the document librraies.
     is there any link which gives the naming convention / restricted names for  document libs or  splists , from msdn / blogs.technet.
    thnx

  • Special characters in passwords

    Where can I get documentation for restrictions on passwords. Like what special characters can be used in
    passwords?
    Maximum length etc?

    Passwords follow the same rules as other identifiers in the database:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/sql_elements9a.htm#27566
    That means:
    - not case sensitive
    - 1 to 30 characters long
    - no Oracle reserved word
    - no quotation marks
    - must begin with an alphabetic character
    - only alphanumeric characters, underscore (_), dollar sign ($), pound sign (#)

  • Special Characters in KM Names

    Hello Experts,
    are there any restrictions regarding special characters in KM Properties or any other Km Objects? I have in mind i read somewhere about restrictions for search result set names / ids, are there are also in any other areas restrictions?
    Thanks for your help,
    Stefan

    >
    Raymond HENG wrote:
    > Thus..a quick conclusion if I may..
    > 1) Folder and file name: any of your choice but will impact your portal search if you choose to use special char's in the name
    > 2) Folder and file ID: No spacing or special char's as indicated by Bobu.
    >
    > Hope that helps.
    > Ray
    Wow, this is misleading.
    The confusion starts with saying "special", and then not define it...
    The KM UI uses display names, but this doesn't affect what you can or can't put into an identifier (the RID for resources, or the property name for properties).
    What RIDs can take depends on the repository manager. In the best case, it roughly allows everything that would be allowed in a Windows filename. In particular, some rules depend on position as well, such as no trailing whitespace.
    Property names by definition use the same rules as XML element names (thus no whitespace at all).
    BR, Julian

  • Multi languages and Special Characters in PI

    Hi gurus
    Different languages data will be coming from the source xml file and PI has to handle that data and send it to ECC  system throguh IDoc Receiver Adapter.
    .our scenario is MDM to R/3. Pi file adapter is picking the xml file from source directory path.
    the file encoding we have used is "ISo-8859" file type as "TEXT", we have also tried checking by giving the file name as"Binary", but we are still facing the issue.
    The special characters which are showing up are Å#ó
    i was trying to look at the below mentoined blog , but that blog was not availiale in sdn.
    http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9420 [original link is broken]
    thanx in advance

    > i tiried as you suggested, but i do not have the access for the RFC destination in R/3 server.
    I mean the RFC destination in PI, not in R/3
    > i have a doubt here
    > In the xml file received by PI, the entire data will be in English, only for two particular fields the data will be in Foreign Languages(russian,greek or any other langauge).The fields are maintained under International Version Segement.
    You have to split the XML, create different IDocs by language and choose an IDoc receiver channel with tied RFC logon language 
    see SAP note 745030
    The customer should consider to use a unicode R/3 system when he wants to use different language descriptions.
    In a non-unicode system the texts from other languages cannot be read, for example the greek characters cannot be displayed when logging on in russian. In a unicode system there is no restriction.

  • Vibe 3.2 problems with special characters?

    I'm not sure where the issue lies here, the client or Vibe, so I'll throw
    this out there to see if anyone has run into this problem. I have a user
    with a + sign in their password. If he tries to log in from either his
    Android phone or his Android tablet, he gets a bad password error. Using a
    different browser on the tablet, he was able to get logged in. Using my
    Android phone, he was also able to get logged in.
    Are there any known issues with Vibe not supporting certain browsers for
    special characters in passwords? I don't think he had the problem with Vibe
    3.1.
    thanks,
    Todd Bowman
    Senior Network Analyst
    University of Minnesota Physicians
    612-884-0744
    [email protected]

    Yes, you're right. Same issue here with a '' character. Found this:
    '6.2 Character Restrictions in Usernames and Passwords
    Do not use extended characters or double-byte characters in Novell Vibe usernames and passwords.
    This includes usernames and passwords that are synchronized from an LDAP directory into Vibe.
    This limitation is caused by the open source Spring Security (http://static.springframework.org/
    spring-security/site) that Vibe uses for authentication, in combination with the various authentication
    methodsboth basic authentication (http://en.wikipedia.org/wiki/Basic_a...authentication) and
    form-based authentication (http://en.wikipedia.org/wiki/Form_ba...tication)used by
    single sign-on products such as Novell Authentication Manager, by Web services, and by WebDAV.
    Only ASCII characters are properly interpreted in all combinations.'
    source: https://www.novell.com/documentation...dme_novell.pdf
    Extremely frustrating for anyone using strong passwords...

Maybe you are looking for