EEX 9.2: Using The Receipt Split Feature On A Foreign Currency My Wallet Transaction In Expense Report Fluid User Interface Throws Decimal Division By Zero Error Message
Last updated on MAY 09, 2018
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When an Employee is creating a new Expense Report in Fluid User Interface, and using the Receipt Split feature on a Credit Card transaction defaulted from My Wallet, upon adding a second new row in the Receipt Split page, a division by zero Error Message is triggered by the system after tabbing out of the Description field. This is taking place when the My Wallet transaction is using Foreign Currency Code.
1.- Have in My Wallet a new Credit Card transaction in foreign currency
2.- Start creating a new Expense Report in Fluid User Interface
3.- Default from My Wallet, the item in question, into the Expense Report transaction
4.- At the Expense Report Line level, click on the Receipt Split button
5.- Add a new row into the Receipt Split page
6.- Define a new Expense Type into the new added, row, a Description, and when tabbing out of this last field, the system throws an Error Message
" Decimal division by zero occurred.
EX_RCPTSPLT_WRK.TOTAL_RCPT_AMT.FieldFormula Name: CalGridSumAmt PCPC: 1144 Statement: 17
Called from: EX_RCPTSPLT_WRK.TOTAL_AMT.FieldFormula Name: CalSplitAmt Statement: 32
Called from: EX_SHEET_LINE.TXN_AMOUNT.FieldChange Name: TxnAmountFieldChange Statement: 526
Called from: EX_SHEET_LINE.TXN_AMOUNT.FieldChange Statement: 529
A division by zero occurred. Review the PeopleCode being executed to determine why the error occurred. Make sure that zero values are checked for and that appropriate error handling exists. "
The Error Message prevents the User from saving the Expense Report transaction, which will delay the reimbursement of the expenses incurred, and in this case, involving Credit Card Vendors, possible delayed payment penalty fees.
The Fluid Expense Report creation page should allow the complete usage of the Receipt Split functionality without receiving such Error Messages.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms