CONVERT_TO_LOCAL_CURRENCY Error

[former_member70282]

Dear experts,

We are working on an on-going project for payroll. Previously, we have used country grouping 99 for a country which was not localized, and now we want to carry on using 99 for another country which is not localized either. We have customized the system and tables and everything is working fine, however, a new error occured. When we want to run the payroll for the old country (which was working properly), we get this error:

Error when converting a constant amount MAXBT in T511P
CONVERT_TO_LOCAL_CURRENCY has been called
Data used:
Validity end date: 28.02.2019
Constant: MAXBT
T511P currency MAD
Currency of payroll driver IQD

The new country's payroll program is working properly, and we would like to know if we can solve this issue without ABAPer. Is it possible to fix this issue?

In addition, we can't use MAXBT for both countries since their currencies are different and we can only maintain MAXBT for only 1 currency for country grouping 99. Can we do it without an ABAPer?

[former_member630342]

Hi Ali,
It depends on what you call "this issue" here.

FM CONVERT_TO_LOCAL_CURRENCY uses table TCURR for currency conversion.
The most probable reason for this error is an absent entry for the MAD-IQD pair for the given day. Once the entry is created, you'll get rid of the error.

But I'm not sure if it solves the issue. I don't even realize its volume.
I personally not sure whether it makes sense to use molga 99 for two real country versions (even for a custom driver).

Also on low-level, speaking about that conversion case itself - convert_to_local_currency in case of retro will take the paydate of FOR-PERIOD what won't always be suitable
Generally, having such conversion from non-local currency MAD doesn't look good in general in IQD payroll driver, as should not have taken place at all.

Kind regards,
Alex