TCURX Decimal Point Change

For certain currencies I have a conflict between the stated decimal places on inbound American Express transactions vs. what's stored on TCURX.  Because of this descrepancy I cannot load COP or HUF American Express transactions into the SAP system for use in the Travel Expenses application.
   American Express is assigning two decimal places to transactions originating in Columbia Peso (COP) and Hungary Forint (HUF) while SAP is assigning zero decimal places.  ISO 4217 states that both currencies are two decimal places.
   The credit card accounting currency and company code currency are both USD.  All SAP transactions have been posted in USD.  There are no exceptions.
   Based on this background I'm trying to determine the best approach for modifying TCURX so it properly reflects the ISO 4217 standard for COP and HUF.  Through my research I've determined that a currency code with two decimal places is not included in TCURX.  Should I delete the TCURX entries for COP and HUF or should I change the decimal place value to two for both of these currencies?  Or is another course of action required? 
    Thanks in advance for oyur help.
Paul Portella

The fillér, which was defined as a 100th part of a Forint, has long ceased to exist.
The same probably applies to Colombia.
However, history apart, I wonder why you cannot delete the two entries from the TCURX table (which takes its values from OY04). Maybe raise an OSS note and have SAP answer this for you. My client does not deal in Forints, so its not been maintained.
You cannot change the decimal value to 2, since that option has not been provided (assumed default).
Cheers.

Similar Messages

  • In a pages table change the decimal point to a comma

    I live in Italy and love it. However, there are issues. One that you might be able to help me with is changing the usual decimal point in a table to a comma. In Italy they use a comma for separating change from dollars instead of the usual decimal point.

    Scott Fox wrote:
    I live in Italy and love it. However, there are issues. One that you might be able to help me with is changing the usual decimal point in a table to a comma. In Italy they use a comma for separating change from dollars instead of the usual decimal point.
    I apologize but _*in many countries*_ the usual decimal separator is not the decimal point, it's the comma.
    It's time to understand that American habits aren't the universal rules or ways of life !
    I'm not saying that American habits are bad, just that they are local ones, not better than others.
    Yvan KOENIG (VALLAURIS, France) mercredi 30 septembre 2009 16:01:23

  • Change decimal points in SD Condition type from 2 to 3, for EU

    Hello,
    We have a slight problem with the amounts. We are using resource related billing in the project and to track some expenses, there are some condition types created. Since the currency is maintained as EU, the decimal places are maintained as 2 decimals in OY04 and we dont want to change that.
    We face an issue, when SAP Converts condition value from 3 to 2 decimals
    For example, when in Contract we have an Condition Value of 100.025, this is converted to 100.03 and tax is applied on this amount.
    When we create an invoice and subsequently a Credit Memo request, that will contain more than one item, and the sum of all items will have to sum up to 100.03, but this is never the case, as with the application of tax rate, the value comes to something like 100.02 or 100.04..
    With 3 decimal points, this amount adds upto correct value.
    So our ideal solution will be the have the Condition Values as 3 decimals and the Net value in 2 decimals.
    Is there something  that can be done for this?
    Hoping for a quick response.
    Regards
    Maddy

    SAP stores the 3 decimal value in XKOMV-kbetr and Xkomv-kwert is calculated based on this 3 decimal values...
    I had a similar scenario with currency conversion and rounding issue in sales Order and Invoice processing, in VOFM routines... so I used a Floating point  value and converted to character value and then used that 3 decimal value for calculation.

  • Help, please! I am suddenly being presented with CYMK colors to 2 decimal points.  What did I accidentally change and how can I fix it?

    This is driving me crazy. I am suddenly being presented with CYMK colors to 2 decimal points.  Too much info for me.  What did I accidentally change and how can I fix it?  I've been through all of the preferences, views etc. I can find but no luck.  Thinking this has something to with the color settings (obviously) but with all of the possible options there I could use some help.  Thanks, all!

    May have been a switch from RGB to CMYK.
    Or you moved one of the sliders with shift key pressed.

  • How to change decimal point in Rotate Tool.

    Hi,
    I use the rotate tool to design gauges, like clocks, a lot. I hold the ALT button and click on the center of my drawing and then a window pops up to enter in what degree I want my object to be. Currently the decimal point only allows for hundredths, ex. 45.25 degrees. Is there any way to change this to thousandths or even higher, ex. 45.25125? I've attached a screenshot to show you what I mean.
    Any help would be appreciated!
    Thanks,
    Laura

    Laura Belle,
    When you enter the full decimal value, that should give you the right rotation whatever the truncated value is.
    At least I hope that is still the case in your version.
    You may test it as follows:
    1) Create a square with W = H = 100;
    2) Rotate thrice, each time inserting 33.333333 degrees, then rotate by -100 degrees;
    3) Look at the W and H values;
    4) Repeat 1) - 3), only with 33.33 degrees and see what you get.
    You should get W = H = 100 in 3) and  something like 100.017 to 100.018 in 4).

  • Change decimal point

    Hi!
    How to change decimal point to '.' or ',' ,and how to do this only for current schema, session or user.
    Thanks in advance.

    Decimal separator is an NLS setting. By default it is determined by the value of your NLS_TERRITORY but it is easy enough to override...
    SQL> SELECT 0.98 FROM dual
      2  /
          0.98
           .98
    SQL> ALTER SESSION SET NLS_NUMERIC_CHARACTERS = ",."
      2  /
    Session altered.
    SQL> SELECT 0.98 FROM dual
      2  /
          0.98
           ,98
    SQL> Cheers, APC

  • Change decimal point dynamically

    Is there a way to change dynamically the decimal point used in numeric control without restarting application?
    With decimal point localized, that's work only when restarting the application...
    Thanks

    Yes, you can by changing the Format string:
    Changing it from '%.;%f' will use a dot as decimal sign. If you change the format string into '%,;%f' will use comma.d
    You have to do this for every control you want to change, so creating some framework is usefull.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • How do I Change decimal comma for decimal point

    Hello,
    I have an external USB keyboard and I don't know how do I change the decimal comma for the decimal point.
    I already set my region but anyway I can't change the decimal comma for the decimal point.
    thanks

    Thanks for the link, that help me a lot, because now when I'm in excel or a calculator I hit the point key on the numeric part of my keyboard and I get a point, but when I'm in word, safari or entourage and I hit the point key on the numeric part of my keyboard I get a comma instead a point.
    I have a windows Spanish ISO extended keyboard.
    Thanks a lot for your help

  • Change decimal points

    Hi gurus,
    My client wants to give( in conditions in the sales order ) the price of a material as 120.123 ( i.e.three numbers after the point ) but the system accepts only two numbers like 120.12.
    what are the settings needed to give three decimal points.
    regards,
    anand.

    Dear vas
    Go to OY04 and maintain decimals as 3 there.
    Thanks
    G. Lakshmipathi

  • Currency Decimal Points - Urgent

    Hi,
    I am facing a serious problem with currency decimal points. Unfortunately "Currency code" has been deleted from where we can maintain currency decimal points in OY04 Tcode and the currency code was maintained by zero decimal places. Before deleting the Currency from decimal points the document currency was showing $1000.00 which is correct. But after deleting Currency Code from OY04 Tcode the same amount is showing $100000 by combining decimals.
    I have again given same Currency Code in same transaction code. But still it is showing ($100000) the amount by combing the decimals.
    Please help me
    Thanks
    Ravindra

    You said someone "unfortunately" deleted an entry from table TCURX.  Has that someone seen all the following WARNINGS given by SAP!!!
    In a productive system, you must not delete the currencies in use or change the decimal places.  This could make amounts in documents already posted incorrect or invalid.
    Before you continue, please read the following text carefully.  If you do not heed this note, you can cause irreparable damage to the system with this transacton.  In the R/3 System tables currency fields are stored as decimal figures with a variable number of decimal places. The decimal point is not stored in the field in the database. Instead, each currency field refers to a currency key field. In this transaction you assign the number of decimal places to this currency key uniquely.  Example: If you have set currency USD to have two decimal places and you post an amount of 100 USD, an amount of 10000 USD is stored in the currency field in the database. Not until this amount is processed further or is output does the system use the currency key from the reference field to determine the number of decimal places via this table. In this way the table content can be interpreted correctly for further processing or formatted for output with the correct punctuation.  If after posting you changed the number of decimal places for USD, for example, to 3, the existing field content of 10000 would be interpreted for futher processing or output as 10 USD (10.000). This would mean that the contents of tables across the system would, for all currency fields containing an amount in USD, be interpreted incorrectly by 10 per cent. To        
    change the number of decimal places for a currency already in use, you must convert all the tables in the R/3 System that contain
    currency fields, so that the data integrity remains. This cannot, however, for both organizational reasons and under the runtime aspect be carried out in a productive system.  The following changes to the TCURX table can thus lead to the loss of data integrity if you        
    make the changes in a productive system or transport them into a productive system:
    o Change to the number of decimal places of an existing currency                                   
    o Deletion of an entry from the TCURX table (corresponds to changing the decimal places to the standard value of two decimal places)           
    o Insertion of an entry in the TCURX (corresponds to changing the standard value of 2 decimal places to a different value), if this is a currency code that already exists Uncritical changes are any made to this table during the Customizing of a new installation or the insertion of TCURX even during operations, if the currency codes have just been entered in the TCURC table using transaction OY03, signifying that no postings to these currency codes can have been carried out yet.
    Do you want to change the decimal places despite all recommendations?

  • HUF Currency decimal points

    Hello,
    I have a shopping cart that was created for 2200 EUR however a vendor that has a currency of HUF was used as the assigned source of supply, causing the currency amount to change to 606,983 HUF.  When the PO replicated to ECC it replicated with the 606,983.00 HUF dollar amount however the PO SmartForm printed out with 6,069.83 HUF.  Our developer here mentioned that it has to do with the TCURX table holding HUF with 0 decimal points and that it should be changed to 2 decimal places.  I am looking to see if anyone else has seen this issue and if there is a better way to resolve it other than changing the information held in the TCURX table.
    Thanks,
    Katherine Lee

    Hi,
    It looks just currency customizing. If HUF Hungarian Forint needs decimal point, please checnge the setting in the transaction OY04.
    Regards,
    Masa

  • Dynamic displaying of decimal points for currency field in ALV

    Hi,
            In ALV output there is a currency field and displaying data of different countries. It should display decimal point according to the country's currency. But at a time it can display data of different countries.

    Hi Dilip,
    I think your question is about currencies with different number of digits after decimal point. If you have the currency field in the ALV row, you have to give it's name as currency reference for the value field in the field catalog.
    After creating the field catalog, call a form and do something like this (change fielnames accordingly).
    <pre>
    *&      Form  alv_fieldcat_enhance
          Individual Enrichment of field catalog
    FORM alv_fieldcat_enhance
      CHANGING pt_alv_fieldcat TYPE slis_t_fieldcat_alv.
      FIELD-SYMBOLS:
        <alv_fieldcat> TYPE slis_fieldcat_alv.
      LOOP AT pt_alv_fieldcat ASSIGNING <alv_fieldcat>.
        IF <alv_fieldcat>-fieldname(5) = 'KBETR' OR
           <alv_fieldcat>-fieldname(5) = 'SKBTR' OR
           <alv_fieldcat>-fieldname(5) = 'DMBTR'.
    Company code currency
          <alv_fieldcat>-cfieldname = 'BWAER'.
    Document Currency for conditions, net value and taxes
        ELSEIF  <alv_fieldcat>-fieldname(5) = 'KWERT' OR
                <alv_fieldcat>-fieldname    = 'NETWR' OR
                <alv_fieldcat>-fieldname    = 'NPAX_MWST_AMNT'.
    Document Currency
          <alv_fieldcat>-cfieldname = 'WAERK'.
        ENDIF." <alv_fieldcat>-fieldname(5) = 'KBETR' or
      ENDLOOP." at pt_alv_fieldcat assigning <fieldcat_alv>.
    ENDFORM.                    " alv_fieldcat_enhance
    </pre>
    Regards,
    Clemens

  • Convert the money datatype to a 2 decimal point format.

    Whats the best way to convert the money datatype to a 2 decimal point format in ms sql 2005 for use in my applications.
    this?
    CAST(tr.depositReceivedAmount AS decimal(10 , 2))

    I respectfully disagree with the notion that you should change the SQL column from a 'money' data-type to something else.
    In most database servers, 'money' is a data type that is designed to provide very consistent behavior with regard to arithmetic accuracy.  In Microsoft Access, the representation is a scaled-integer.  In MS SQL Server, it is obviously similar.  Ditto Oracle and all the others.
    You want the money data-type in the database to have this accuracy, because "hell hath no fury like an accountant in search of one lousy penny."   The database column storage-formats are designed to satisfy accountants, and that is a Good Thing.
    Meanwhile, you also want to take care as to exactly how you deal with the values.  There are several points where rounding could take place.  You do not have at your disposal the strongest possible handling of floating data-types in ColdFusion.  You are also somewhat at the mercy of whatever interface software may lie between you and whatever SQL server you may use.  "It's okay to round values once, but not multiple times."
    I suggest rounding the value right before display, and stipulating that the user's input must be two decimal places.
    Then, you might have to do some things at the SQL server's end.  For instance, when you update a value in the table, you may need to use server-side logic to explicitly truncate the value to two decimal-points, so that an update of "$34.56" explicitly updates the column to "$34.5600."  (This sort of thing has to happen within the SQL server context.)  You know that the user's input has exactly two significant digits, but maybe (maybe not...!) the SQL server might not know this.  You want to ensure that the server's internally-stored value represents exactly two significant digits, when the value originates from a user-input.
    Don't err on the side of "your convenience" or "what looks good on-screen."  (If you do, get ready to get phone-calls from the accountants, always at inopportune hours of the night.)

  • Can't figure out how to solve the decimal point bug in this calculator code

    Hi guys, I'm new in flash and is currently learning how to build a simple calculator with multipliers (plus,minus,multiple,divide,decimal point and change sign) but I'm stuck on the decimal point and change sign.
    var multiplier_old:Number = 10;
    var multiplier_new:Number = 1;
    // .: Sets the multipliers so that new input numbers become decimals of a lower unit column
    action_point.addEventListener(MouseEvent.MOUSE_DOWN, function():void {
              multiplier_old = 1;
              multiplier_new = 0.1;
              point = true;
    // Takes intput from the input_ buttons and adds it to the input after applying the multipliers.
    // If `point` is true then the multiplier_new is divided by 10, also as described.
    function inputNumber(n:Number):void {
              input = input * multiplier_old + n * multiplier_new;
                        if (point) {
                                        multiplier_new *= 0.1;
                       trace(multiplier_new);
              output_txt.text = input.toString();
    Decimal point
    The problem is that when I input 2.7 in the calculator, it will display the values in output_txt correctly. But then when I input 2.78, it will display 2.780000000000000000000000002. This will also happen to other numbers if the input is too big.
    What I want is just 2.78. How do I change the codings to make 2.780000000000000000000000002 become 2.78?
    Change sign
    Any tips on how to start on this one?
    Thanks for your time,
    Zainu

    I think you misunderstand what I mean. The weird decimal doesnt comes out after I press the 'equals' sign. It comes out when im just pressing on the caculator number buttons
    First I click the no.2 button and then the decimal point button.
    So the caculation output display will show
    2.
    after that I press the no.7 button
    2.7
    and then no.8 button. It appears like
    2.7800000000000000002
    This is the code I use when the user press the decimal point button.
    // .: Sets the multipliers so that new input numbers become decimals of a lower unit column
    action_point.addEventListener(MouseEvent.MOUSE_DOWN, function():void {
              multiplier_old = 1;
              multiplier_new = 0.1;
              point = true;
    // Takes intput from the input_ buttons and adds it to the input after applying the multipliers in the method described above.
    // If `point` is true then the multiplier_new is divided by 10, also as described.
    function inputNumber(n:Number):void {
              input = input * multiplier_old + n * multiplier_new;
                        if (point) {
                                 trace(multiplier_new.toFixed(3));
                                  multiplier_new *= 0.1;
                                  //trace(multiplier_new);
              output_txt.text = input.toString();
    I think there is some code wrong in this function that makes this weird problem. I tried putting toFixed method but it's still not working.
    Sorry for this long reply but I have to try my bestto explain with my bad english.

  • How can I get the float variable in 2 decimal point?

    after running the following simply manipulation program,
    14.85 should be returned, but in stead, 14.849999.
    how can i change the precision? i want the returned number in 2 decimal point.
    public class TestC {
    public static void main(String[] args) throws Exception {
                   float var = 0.00f;
                   var = (float)4.95 * 3;
                   System.out.println(var);

    There is absolutely no way that you can change the precision. It is fixed.
    If you want to display two decimals places (which is not the same as changing the precision) then you can use the following.
      float var = 0.00f;
      var = (float)4.95 * 3;
      java.text.DecimalFormat f = new java.text.DecimalFormat("0.00");
      System.out.println("var=" + f.format(var));

Maybe you are looking for

  • XSLT mapping - 2 messages to 1

    Is it possible to map 2 xml files into 1 with only one XSLT mapping? I need to use XSLT because the target message is a xml with only one tag of type string, and inside this string I need to pass the content of both source messages. But the only way

  • Saving a PDF download

    I am trying to save a download using Adobe. I can open the file on my MacBook but can't save it. When I do save it and try to open it again, a window opens telling me "Adobe Reader could not open 'article2.pdf' because it is either not a supported fi

  • Sorting and formatting in Numbers with iPad 2

    I am going to send feedback to Apple about this, but I wanted to let the community help, if I am incorrect and these things are actually possible. 1. I can only sort by one column. I want to be able to create a sort priority. For example, I want to s

  • Itunes songs cut off

    Recently, some of the songs in my itunes library cut off at approximately 2:30 minutes into the song.  I thought it was a problem with my old ipod, but the same thing happens on a second ipod and on my iphone.  The problem does not happen on my PC. 

  • How can I add the new AP license to HA 5508 WLC?

    Hi, My customer has two 5508 WLC in HA mode and these devices have 250 AP license. Customer bought 50 AP and 50 AP license. But I could not add the license to WLC! When I check the Management>Software Activation> tab there are only two options under