Format Arguments for upper case in Documaker

Hi All,
I have a DAL scripts which uses the XPath for customer. The customer names are coming in upper and lower came and some time mixed. I would like to make the first letter of the name ( first name, Middle name and last name) uppercase.
from DAL reference book:
Enter <> to capitalize the first letter of the resulting text. This flag is valid for the following codes and ignored on all others: %<>p, %<>A, %<>b, %<>B For example, if %p results in AM, %<>p produces Am.
Cust_name_temp=" adam miline"
Cust_name_temp= format(Cust_name_temp,,"%<>p") - this is not giving the result as "Adam Miline".
Please help on the same.
Debasish

Hi,
DAL does not have a direct function to do this.
As an alternative,  the Move_It rule offers a Title Case format.
thanks

Similar Messages

  • Field validation only for UPPER CASE

    Hi Experts,
    my requirement is one field needed to be validate , it is coming from portal,
    and that string must be only UPPERCASE, if it is lower case error message is needed .
    like'only enter capital letters  ' .
    plz give me logic for upper case.
    Thanks.

    hi 
    you can go with following code...
    ITS A WORKING CODE WITH MY OWN DATA.
    you are getting w_source from portal
    data: w_char type string.
    start-of-selection.
    w_char = w_source.
    translate w_char to upper case.
    if w_char <> w_source.
      message 'only enter capital letters' type 'S'  display like 'E'.
    endif.
    regards

  • Calling Function Module for upper case to lower case in Transformation

    Hi all,
    We have the data load happening everyday for the Account Receivables data. The DSO activation is failing because of the invalid characters. It gives the messages as below
    "Value 'bdmg0808dm' (hex. '620064006D006700300038003000380064006D00') of characteristic ZINVNUM contains invalid characters"
    We understood that the character ZINVNUM is maintained only for uppercase letter wherein the lower case check box is not ticked. We have a function module which is build within BI which can be used to permit non permitted characters including space. Just want to know how can I call this function module in a transformation and which is the best option to call the function module(start routine/end routine).
    Regards
    Vijay

    You can use statement in end routine to convert text to upper case. No need of calling any function module. Just loop through records of RESULT_PACKAGE and for that particular field convert text using below statement.
    LOOP AT RESULT_PACKAGE.
    TRANSLATE RESULT_PACAKGE-/BIC/ZNAME TO UPPER CASE.
    ENDLOOP.
    Edited by: ABHIJIT TEMBHEKAR on Nov 14, 2008 2:22 PM

  • Unable to apply syntax for upper case in pdf form

    Hi All,
    I am unable to apply syntax in adobe livecycle design to conver the case automatic in upper case.
    Please help me how to do this as I am selecting form calc , clien and pasting the script but it does not work.
    or please share me your email id so that I can share my pdf form.
    Regards,
    Md Afsar

    The upper method needs a parameter.
    Use this script.
    $ = Upper($)

  • Search for upper case in Bex Queries

    Dear Gurus,
    I'm facing the following situation:
    I have a query from BW listing customers from a Infocube and it is displayed in uppercases, but when I click in the button filter in left panel from the characteristic Customer and type the customer name in lowercases it doesn't work anyway,
    What can I do to solve this problem?
    Thank you in advance,
    Fabio Purcino
    Brazil

    Hi,
    I've solved this problem by changing the function module RSD_CHA_BUILD_QUERY. I just added the following code before ENDFUNCTION.
      data: ti_where type table of rsdrs_s_where with header line.
      loop at e_sx_query-t_where into ti_where.
        translate ti_where-low to upper case.
        translate ti_where-high to upper case.
        append ti_where.
      endloop.
    Regards,
    Fabio Purcino

  • Special characters converted in wrong in Upper case ?

    Hello,
    In material description , some characters such as µ when converted into upper case it will be 'M' in stead of 'µ' . This is in SAP ECC unicode . But it's ok in R/3.
    So in this case, Is there any solution for this problem ?
    Thanks

    MAKT-MAKTG : For upper case characters , When our client search for values when pressing F4 in material , If there's material description that contain 'u03BC', It will be displayed as 'M' in the text . This will happen in ECC 6 not in R/3 ( in R/3 two texts are the same) .
    The different behavior you're observing between what you call R/3 and ECC 6 is not due to the different releases, but based on the fact that one system is Unicode enabled and the other not. I suspect that you are most likely logging onto the system with a language that's linked to code page 1100 (in the non-Unicode release). Code page 1100 is similar to the Latin-1/ISO-8859-1 code page, which is designed to have most characters for western languages, but does not contain all Greek letters (SAP would most likely use code page 1700 if you set a greek locale).
    Again, it may sound silly, but you have to distinguish between the symbol µ (Unicode code point U+00B5) and the lower case greek letter u03BC (U03BC). SAP code page 1100 contains only the symbol µ (U00B5), which represents the prefix micro as for example in 1µm = 1 micro meter = 0.000001m. Neither the greek lower case letter u03BC (U+03BC) nor it's corresponding upper case letter exists in code page 1100.
    The Unicode standard defines the greek upper case letter u039C (U039C) as the upper case to use for both the symbol  µ (U00B5) and the lower case greek letter u03BC (U+03BC), see for example the Unicode mapping chart for Greek (so that's why you see a different behavior in ECC 6).
    I'm not sure why, but for some reason SAP found it worthwhile mentioning that they actually also convert the symbol  µ (U00B5) to u039C (U039C), though that essentially just means following Unicode standard. Anyhow, if you're interested in further details, check out OSS note 1078295 - Incomplete to upper cases in old code pages.

  • Fetch data from IR to form in UPPER CASE format for text field items

    Hello,
    Can anyone please help with this issue. I have a IR report with form and I want to fetch the data to upper case when I go to the form level to edit the details from the IR report. I am using the Oracle APEX in built automatic row processing DML to update, create or delete the records. Is their any way, where I can convert the data to upper case whenever user creates a new record or updates the existing record using the in-built automatic row processing DML.
    Please help.
    Thanks,
    Orton

    Jari,
    I have tried your option but no luck. The thing is the text is getting converted from lower to upper case when i navigate from report to form level. But I want to save the data to the database all upper case, even if the user enters data in lower case and this applies for both inserts and updates. Whenever i tried to create or update a record, all the data should be converted to upper case before inserting or updating to the database.
    Please help.
    Thanks,
    Orton

  • Exporting as CSV loses upper case text format

    Hi Folks,
    When I format a column of text to upper case and export the sheet as .csv, It reverts to whatever random format it had before. The column is for states in a list of addresses.
    I also wish I could format text in lower case if needed.
    Any ideas?

    In iWork's components, applying a style "uppercase" or "lowercase" doesn't change the case of the data. It just display it as asked.
    So, when we export in a text only format, we lose the style and grab the data as it was typed.
    I understand that the developper feel safe to keep the original data intact but here it may appear as an annoying feature.
    This is why I already asked them for added feature alloying us to really change the case as we wish.
    Of course, I don't know if they will insert these features.
    Yvan KOENIG (from FRANCE mardi 29 avril 2008 18:12:53)

  • How to search for upper/lower case using string using JAVA!!!?

    -I am trying to write a program that will examine each letter in the string and count how many time the upper-case letter 'E' appears, and how many times the lower-case letter 'e' appears.
    -I also have to use a JOptionPane.showMessageDialog() to tell the user how many upper and lower case e's were in the string.
    -This will be repeated until the user types the word "Stop". 
    please help if you can
    what i have so far:
    [code]
    public class Project0 {
    public static void main(String[] args) {
      String[] uppercase = {'E'};
      String[] lowercase = {'e'};
      String isOrIsNot, inputWord;
      while (true) {
       // This line asks the user for input by popping out a single window
       // with text input
       inputWord = JOptionPane.showInputDialog(null, "Please enter a sentence");
       if ( inputWord.equals("stop") )
        System.exit(0);
       // if the inputWord is contained within uppercase or
       // lowercase return true
       if (wordIsThere(inputWord, lowercase))
        isOrIsNot = "Number of lower case e's: ";
       if (wordIsThere(inputword, uppercase))
         isOrIsNot = "number of upper case e's: ";
       // Output to a JOptionPane window whether the word is on the list or not
       JOptionPane.showMessageDialog(null, "The word " + inputWord + " " + isOrIsNot + " on the list.");
    } //main
    public static boolean wordIsThere(String findMe, String[] theList) {
      for (int i=0; i<theList.length; ++i) {
       if (findMe.equals(theList[i])) return true;
      return false;
    } // wordIsThere
    } // class Lab4Program1
    [/code]

    So what is your question? Do you get any errors? If so, post them. What doesn't work?
    And crossposted: how to search for upper/lower case using string using JAVA!!!?

  • Conditional Upper Case formatting

    Hi there, I need to be able to format the first letter of a word upper case or lower case depending upon whether or not it appears at the start of a sentence. There must be a method of doing this using the String class. Any ideas folks? All contributions greatly appreciated!

    It's a remarkably difficult problem to determine whether a sequence of chars constitutes a word, and what constitutes a sentence, especially considering that Java strings can be used to contain text in not only English but also Thai and Inuktitut and Coptic and all of the world's written languages. So perhaps it isn't all that surprising that the language designers didn't feel it necessary to solve that problem within the String class.
    However if you have a more restrictive problem domain then perhaps you have an easier problem.

  • Create user for CPS in _ UPPER CASE LETTERS _ if using JSM on SolMan

    only create users for CPS in UPPER CASE LETTERS if using JSM on SolMan
    Dear CPS Admins,
    If you plan to use Job Scheduling Management (JSM) on SAP Solution Manager together with CPS by Redwood please always create any users in CPS only with upper case letters to avoid issues in the communication between SolMan and CPS.
    The user creation for CPS is done in the UME (Java user administration, alias /useradmin).
    Actually the CPS user itself is only created in CPS during the first logon.
    Both CPS and the Java UME are case sensitive. So you can create users in uppercase, lowercase or mixed letters. But of course the system does still not allow duplicate names. So you can either create MUELLERP, MuellerP or muellerp - but not multiple of them.
    Now, if the SolMan communicates with CPS for Job Scheduling, the actual user name is taken in some kind of a "trusted RFC like" way and checked on the CPS system connected to the SolMan. If the current SAP user does not exist on CPS no activities are possible, neither in read mode (read existing CPS jobs) nor in write mode (change existing jobs or create new ones).
    Unfortunately the Solution Manager transmits the current user name to CPS only in upper case letter. So if the CPS user was not created in UPPERCASE letters in CPS the communication will fail. Therefore, think about creating CPS users in UME only in UPPERCASE letters. Changing this later is difficult to impossible.
    Best regards,
    Peter

    hi,
    I tried to reproduce your issue but I was not able to create a UME user with lower case letters.
    UME automatically converted the user name into upper case after saving. So even if I enter "cps" as user name UME stored the user name as "CPS".
    (maybe that happend because of the existing SU01-UME integration in our SolMan system)
    If UME would be case sensitive I would expect that it is possible to create the user "CPS", "cPs" and "cps".
    Regarding the SolMan-CPS connectivity:
    Transaction SU01 allows only upper case letters (in user name and alias). Since you're starting from an ABAP system only user names with upper case letters are supported. It's a technical constraint of the ABAP user management that user names consist of upper case letters only.
    Kind regards,
    Martin

  • Function Module for Translation of text from Lower to Upper Case

    Hi All,
    Can any one give me function module for translation of text from lower to upper case.
    If we use Translate statement for the program in the Extended Syntax check it is giving error.
    Thanks in advance.
    Regards,
    srinivas

    Hi Srinivas,
    You can use any of the Function Modules below.
    AIPC_CONVERT_TO_UPPERCASE
    2054_TRANSLATE_2_UPPERCASE
    HR_99S_CONV_UPPER_CASE
    Please reward if useful.
    regards,
    Raj

  • The hardest forum ive entered, and no remedy for the problem. where are my films ive paid for?? sorry for lack of upper case, just very angry with YOU apple

    the hardest forum ive entered, and no remedy for the problem. where are my films ive paid for?? sorry for lack of upper case, just very angry with YOU apple

    We are all itunes users just like you.
    No idea where your films are as you provide no information at all about your situation.
    If you want, help, then please explain your issue.

  • More on counting upper case characters

    (*This relates to a recent question I posted about counting upper case characters in a string. dev_sleidy responded with an applescript approach that works, but at 6 lines I was hoping for more compact code. So I played around with a one-line command line approach that so far seems reliable (tell me if you find it isn't). However, there are a couple peculiarities which I would like to understand. I know, I know, I should just shut up and use it. But I must be part cat and need to be killed.
    The code that appears to work:*)
    set T to "MY GraNd QuestioN A"
    set UCcount to do shell script "echo " & quoted form of T & " | tr -d [[:space:]] | tr -d [:lower:] | wc -m"
    (*The peculiarities:
    1) If I substitute >>sed 's/ //g'<< for >>tr -d [[:space:]]<<, the result always seems to be one count high. (Same thing appears to happen when executed in Terminal.) Why?
    2) When using regular expressions the format [[:class:]] has always worked for me, as it does for "space" in the code above. But for the second tr -d pipe (above code) those outside brackets mess everything up, and single brackets work fine. Same thing happens with both [[:lower:]] and [[:upper:]] but doesn't seem to happen when executed in Terminal. Why? Are there rules for bracketing character classes (I've seen different versions)?
    Or is all this a UNIX forum question?*)

    Hello
    Honestly I don't understand why such result is returned by CODE1.
    Its prototype [1] tested here works as expected.
    But I noticed CODE2 may return wrong result, for its prototype [2] actually returns wrong result with MacPerl 5.6.1r2 under OS9.1 when input string is read from file insead of being given as string literal. I didn't test that possibility. Sorry for that. Please disregard CODE2, for I think CODE1 will be enough.
    (The wrong result is caused by the fact that 'Ç' encoded in UTF-8 is counted as 2 chararcters by length function if it is read from file due to certain limitation of MacPerl 5.6.1r2. I don't know whether that applies to recent Perl under OSX.)
    [1]
    use utf8;
    while (<>){
    s/[^[:upper:]]//g;
    } continue {
    print;
    [2]
    use utf8;
    local $/;
    while (<>){
    s/[^[:upper:]]//g;
    print length;
    Re. your original question about peculiarities.
    As for 1), I think it is because 'echo' is adding trailing \n and "sed 's/ //g'" won't remove it. Try "sed 's/[[:space:]]//g'"  instead. Indeed "sed 's/[^[:upper:]]//g' will remove all non-upper case letters at once, I guess.
    As for 2), I think it is because 'tr' actually does not process regexp. Its character class support is based upon POSIX but the usage is different from regexp, i.e. [:class:] in 'tr', while [[:class:]] in proper regexp. Meanwhile, I think, the regexp syntax, [[:class:]], in 'tr' argument works in Terminal because in Terminal, 'bash' processes the regexp in its parameter expansion (path name expansion, in this case) and 'tr' receives the expanded result as its argument.
    cf.
    http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/tr.1.htm l
    http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/bash.1.h tml
    Hope this may be of some help,
    H

  • How to cast a fieldinput value to upper case.

    Im not a java programer I guess that this must be a silly thing.
    Im searching data in R/3 from 2 fields 1 numeric and the other alphanumeric. This alphanumeric fields if I put it in upper case works, if I wirte it in lower case doesnt works.
    In R/3 when I test the FM doesnt matter if I put it lower or upper case, it works fine.
    so I wanna know how can I in WD cast the value that I put in that fieldinput be converted to upper case when I hit the search button.
    Thx

    > Im not a java programer I guess that this must be a
    > silly thing.
    >
    > Im searching data in R/3 from 2 fields 1 numeric and
    > the other alphanumeric. This alphanumeric fields if I
    > put it in upper case works, if I wirte it in lower
    > case doesnt works.
    >
    > In R/3 when I test the FM doesnt matter if I put it
    > lower or upper case, it works fine.
    >
    > so I wanna know how can I in WD cast the value that I
    > put in that fieldinput be converted to upper case
    > when I hit the search button.
    >
    > Thx
    Hi,
    When you test the FM in SE37 in R3 there is an option at the top of the screen Called Uppercase/Lowercase - this controls whether the input is automatically converted to upper case for alphanumeric fields.
    The other option you have, if it is a custom FM, is to translate the input of the alphanumeric fields in the ABAP - it is quite common to have to translate or convert input data to make sure it is in the same format as the backend system.
    I prefer to do this sort of conversion on the backend system as usually you have a better guarentee that it will be in the correct format, than if you do it in the Java element.
    Just my opinion,
    Gareth.

Maybe you are looking for