Skip to Content

payroll run error if the basic pay above 10,000,000

Jul 03, 2017 at 05:45 AM


avatar image


Can anyone help me payroll run error if the basic pay above 10,000,000

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

antoine foucault Jul 03, 2017 at 12:39 PM

Hi Saif:

Could you please provide more details on your actual issue? could you share a screenshot?


10 |10000 characters needed characters left characters exceeded
Saif Al-Khateeb Jul 09, 2017 at 07:42 AM

Hi Antoine,

When I hiring new employee and him basic bay above the 10,000,000 (10 Million) and complete the hiring, When I run the payroll error occur because the basic pay is above the 10 Million , and this screen shoot for error.

payroll-error.jpg (550.3 kB)
Show 1 Share
10 |10000 characters needed characters left characters exceeded

hi Saif:

It looks like the issue is being raised while performing operation "multi" in a payroll rule of your scheme.

I am guessing the result of the multiplication is too much for the payroll to handle since the result exceed the maximum amount SAP has set.

From experience I have seen amount of salary larger than 10.000.000... It's not uncommon to see this kind of mount in countries like Indonesia or Qatar for instance

Most probably the multiplication operation trigger the exception can be somehow modified depending if it happens during the evaluation of a standard or custom rule.

The content of the dump you have passed is not enough to determine which rule is raising this exception only that it is happening in form OPMULTI (operation multiplication). Maybe you could lookup for operation MULTI ANA o ANN o ARA or whatever combination in your scheme that could trigger the exception.

Another option would be open the debugger after the dump and examine the state of the runtime environment to determine which rules was being performed.

Another operation also could be to set a break point at exception CX_SY_ARITHMETIC_OVERFLOW (if possible) so that way you could analyze the run-time environment as the dump occur.

If the dump occur in a custom rule then you can modify it in PE02. If the exception is being triggered in a standard rule you could maybe divide by 10 or 100 the amount before it's processing.

Hopefully my comments are helping you in finding the origin of your issue and solving it.