R12: IBY: Send Separate Remittance Advices Errors Out If One Recipient Is Missing Email
(Doc ID 805534.1)
Last updated on FEBRUARY 19, 2019
Applies to:
Oracle Payments - Version 12.0.4 to 12.1.3 [Release 12.0 to 12.1]Information in this document applies to any platform.
Symptoms
Send Separate Remittance Advices errors out if one recipient is missing email.
ERROR
delivery API.
at oracle.apps.iby.scheduler.SRAAndPayerNotif.doElectronicProcessing(SRAAndPayerNotif.java:709)
at oracle.apps.iby.scheduler.SRAAndPayerNotif.runSRA(SRAAndPayerNotif.java:346)
at oracle.apps.iby.scheduler.SRAAndPayerNotif.runProgram(SRAAndPayerNotif.java:170)
at oracle.apps.iby.scheduler.FDSeparateRemittanceAdvice.runProgram(FDSeparateRemittanceAdvice.java:45)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Error: an error occurred while calling XML Publisher delivery API.
An error occurred. Roll back any changes.
Done roll back changes.
Request completed in error.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1) Run an AP Batch using a 'Payment Process Profile' having the 'Reporting' tab 'Separate Remittance Advice' section set to 'Delivery Method' = E-mail and the 'Override Payee Delivery
Method Preference' check box checked.
2) Ensure one of the payee's in the batch has a null E-Mail field in their supplier record under 'Payment Details' 'Separate Remittance Advice Delivery' section as well as under the Supplier Site level.
3) Send Separate Remittance Advice job will Error out.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |