ECM: Errors and No Remittance Advice Emails When Uploading Acknowledgement File Using PAYMENT_ACKNOWLEDGE_FILE Service Operation
(Doc ID 2091220.1)
Last updated on JULY 22, 2020
Applies to:PeopleSoft Enterprise FIN Cash Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When Payment Acknowledgements are loaded via Integration Broker Service Operation PAYMENT_ACKNOWLEDGE_FILE, the Payment status changes to Paid as expected but there are no Remittance Advice Emails triggered, and the following error is received:
GetRecord: Record 'BSP_IMPORT_AET' not found in scroll level 0. (2,154)
PMT_DISPATCH.Dispatch.PaymentAcknowledgeMessage.OnExecute Name:ProcessPaymentAcknowledgements PCPC:21903 Statement:234
1. Set Financial Gateway Source for Cash Management to send Remittances
2. Set 820 payment layout for USBNK to Support Acknowledgements
3. Add Payment Acknowledgement layout PMT_STATV3 to USBNK Bank in Banking Integration Layouts
4. Activate PAYMENT_ACKNOWLEDGE_FILE Service Operation
5. Activate Handler
6. Activate Routing and Save
7. Create a new EFT Request
8. Add email address in Remittance Advise Attributes
9. Select and approve payment
10. Dispatch the payment: Status changes to Dispatched to Bank
11. Prepare the XML acknowledgement file to acknowledge the payment that was set to Dispatch to Bank
12. Go to Handler Tester, enter Handler Type and Name, click Provide XML and upload acknowledgement file
13. Execute event
In addition, when clicking on the Message Details link of the Review Acknowledgement Files page, the following error is displayed:
Class Record: assumed property IBPUBTRANSACTID is not a valid field name. (2,274)
PMT_DISPATCH.UI.PaymentFileInquiry.OnExecute Name:DoModalMessageDetails PCPC:19648 Statement:296
Called from:PMT_WRK.MSG_DETAILS_LNK.FieldChange Statement:8
The specified object property is assumed to be a field name, but the field is not found in the current object.
Use the PeopleCode Debugger or a PeopleCode trace to determine the point of the error, and correct the program.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document