Timeout Errors In Journal Approvals when using COA attributes -The journal approval process has stopped due to a system error. Contact your help desk. (FUN-720342)
(Doc ID 2612813.1)
Last updated on AUGUST 19, 2022
Applies to:
Oracle Fusion General Ledger Cloud Service - Version 11.13.19.04.0 and laterInformation in this document applies to any platform.
Symptoms
Journal Approvals are failing
ERROR
-----------------------
The journal approval process has stopped due to a system error. Contact your help desk. (FUN-720342)
com.oracle.bpel.client.BPELFault: faultName: {{http://xmlns.oracle.com/bpel/workflow/taskService}operationErroredFault} messageType: {{http://xmlns.oracle.com/bpel/workflow/taskService}workflowErrorMessage} parts: {{ payload=findJournalBatch30083WorkflowServiceEngine request to SOA mesh failed. Request operation findJournalBatch from default/FinGlJrnlEntriesApprovalComposite!11.13.19.04.0/FinGlJournalApproval to JournalApprovalBCServiceForHWF failed with error: ORABPEL-30083 WorkflowServiceEngine request to SOA mesh failed. Request operation findJournalBatch from default/FinGlJrnlEntriesApprovalComposite!11.13.19.04.0/FinGlJournalApproval to JournalApprovalBCServiceForHWF failed with error: Unable to invoke endpoint URI "http://fa-internal.oracleoutsourcing.com:10663/fscmService/JournalApprovalBCService" successfully due to: javax.xml.soap.SOAPException:
Message send failed: Read timed out after 300sec.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enter Journals
2. Submit for Approval
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 |
| Cause |
| Solution |
| References |