Skip to Content
avatar image
Former Member

Approach for "Change in Decimal Places for Transactional Currency"

Hello,

As per our requirement, decimal place for LBP currency has to be changed from 2 to 0. LBP is transactional currency (not compnay code currency) for AE company codes. Request you to share the detailed approaches(especially migration impact) for this requirement. We don't want to take SAP SLO conversion service.We have already checked relevant Solution as provided in SAP note 434349(Change of decimal places of currencies) as below:


***********************************************
"For a currency that exists exclusively as a transaction currency or document currency in the system, you only have to rename the currency key to an alternative currency key. You can do so with the SAP SLO conversion service for currency key changes. The conversion occurs for all database tables in which currency keys have been defined. After renaming, you can recreate the now free currency key with another number of decimal places in the system. There is no conversion of the amounts in transaction currency because no reconciliation is possible for processing the rounding differences that may occur. After the conversion, you can handle the alternative currency key via the function of the currencies to be discontinued. This function enables you to still allow postings in this currency for a defined time period to be able to clear open items in this currency, for example. If foreign currency accounts exist, which can be posted exclusively in this alternative currency key, you can change the Customizing for these accounts. In this case, you should redefine the accounts as local currency accounts and you should define a validation for the posting that permits postings in old and alternative currency exclusively."
*********************************************
Now Queries are on the above solution:-->

1. How to rename an Existing Currency in spro?
2. In case we are able to rename an existing currency, does the conversion occur for all database tables for renamed currencies automatically?
3. If change in decimal place for LBP is successful, how to correct the amount already posted in LBP before this conversion?

Thanks in advance!!!

Soumya

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Apr 13, 2016 at 11:11 AM

    Hi Soumya

    IMG > SAP NetWeaver > General Settings > Currencies

    here you can rename existing currency (Description), Change Decimals, etc

    I am not sure if this will require a data conversion, but this will not make retro changes.. If you need that, contact SAP Support

    Ajay M

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 13, 2016 at 12:09 PM

    Hi Somya

    The configuration is straight forward under the cross currency application components. However, if you are looking for historical data, the only option is to use SAP SLO Service. You cannot do with out the same

    Regards


    Sanil Bhandari

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks Sanil. We don't prefer to go for SAP SLO service. Even SAP note 434349(Change of decimal places of currencies) does not provide the solution in details for already posted data(that we have to migrate). Any approach how to address same?

      Regards,

      Soumya

  • avatar image
    Former Member
    Apr 14, 2016 at 06:58 PM

    Hi Soumyadipta

    When I went through the OSS note 434349, they are saying to rename the currency key itself say LBP to LB1. I guess this cannot be done simple in SPRO but we may have to use SLO service. Once this is done, the LBP becomes free as if new and you can configure the decimals according to your wish.

    But since you don't prefer to go for SLO service, you can make LBP has a expiring currency and define a new currency from start of next year and use it. In this case, you have to maintain conversion ratio as exchange ratio (100:1) between these two currencies for any cross clearing.

    Also please consider this - If your requirement is not to post any decimals when using LBP currency, then you can simply create a validation in FI and/or CO for this purpose This can easily cater to your requirement, unless you have very huge amounts of postings occurring frequently in such case BSEG amounts field length could not accommodate.

    Hope this helps.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 15, 2016 at 08:25 AM

    Thanks Prakash for your analysis & approach. We are mostly concerned with approach for Historical Data Migration & already existing open transactions in LBP. Can you please help me with detailed approach in these cases?

    We thought of below approach:-->

    Reverse all the open documents currently with LBP, then change the decimal places, and Repost.

    But in this case, amounts in LBP for closed transactions might be displayed wrongly.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Soumyadipta

      This effect of changing decimal places may have the potential cause innumerable effects like:

      1. The existing documents will show the amounts wrongly in FB03 or any display or printing.

      2. Any invoices, purchase order with this currency will show wrongly

      3. Any ageing reports, tax statements, dunning, payments if re-run may produce wrong results

      4. Any CO allocations if done based on TC may also impact.

      5. Not sure of depreciation calculations in fixed assets due to change in TCs

      So depending on the functionality or modules you use and this currency involvement there, you can simulate these in a sandpit and can test it thoroughly on its impacts.

      Regards