Skip to Content

Decimal places & currency key- sideffect

Client was posting in currency BHD and amounts are displayed in 2 decimal places. As per ISO standards, currency BHD should be in 3dp.

Upon checking t code OY04, I saw that BHD wasn’t maintained. I maintained it to 3dp, tested it, moved it to Production. Seemed to work fine. Later, it was discovered that the postings prior to OY04 change got affected where the decimal point moved back by 10%.

I read note 434349 which talks about creating alternate currency key with decimal places. I don’t understand how this can solve it.

Can someone please help me?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 05, 2017 at 06:24 AM

    I had reversed the changes in OY04 upon informing the client. Entries made after the 1st change had to be reversed and redone.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 14, 2017 at 08:09 AM


    Well, it's a pity that you didn't take seriously system message, that warns you while using OY04, that no change to decimals in a productive system should be performed. Creating alternative currency won't solve this particular problem. It should've been used instead changing the decimals. This is also stated in aforementioned OSS note, that a prerequisite of its usage is not to have the situation where decimals were already changed.



    Add comment
    10|10000 characters needed characters exceeded

    • Since I never experimented with this due to its dangerous effect, I'd suggest you to replicate the situation you have now in some test environments or sandbox. There, you can try and reverse the settings and see what effect it will produce on the figures.