Workflow Java Error Agent Listener fails with XML-20150 error
(Doc ID 2680827.1)
Last updated on APRIL 18, 2025
Applies to:
Oracle Workflow - Version 12.1.3 to 12.2.9 [Release 12.1 to 12.2]Oracle XML Gateway - Version 12.1.3 to 12.2.9 [Release 12.1 to 12.2]
Information in this document applies to any platform.
Symptoms
The Workflow Java Error Agent Listener fails with the following error stack:
oracle.apps.fnd.wf.bes.BusinessEventException: org.xml.sax.SAXParseException; lineNumber: 198; columnNumber: 23; <Line 198, Column 23>: XML-20150: (Error) Element PROCESS_INVOICE not complete, expected elements '[INVALLWNCE, INVCHARGE, INVLINE, INVTAX]'. Error Type ERROR
Customer describes issue as limited to only one trading partner. No errors observed in XML Gateway. Events may show as expired in the WF_JAVA_ERROR queue.
Diagnostics to help triage this issue include:
--------------------------
$FND_TOP/sql/wfver.sql
Check $APPLCSF/$APPLLOG/FNDCPG* log files
Check the Transaction Monitor for inbound errors
Check the ecx inbound logs:
SQL> select il.MSGID, il.status, il.error_id, il.logfile, il.time_stamp, er.message,dl.transaction_type, dl.transaction_subtype, dl.document_number, dl.party_site_id,dl.payload, dl.status
from ECX_INBOUND_LOGS il,
ECX_ERROR_MSGS er,
ECX_DOCLOGS dl
where il.error_id = er.error_id(+)
and il.MSGID = dl.msgid(+)
and il.time_stamp >=
to_date('09-APR-2020 09:00', 'DD-MON-YYYY HH24:MI') and il.time_stamp <
to_date('22-APR-2020 09:10', 'DD-MON-YYYY HH24:MI')
order by il.time_stamp asc;
Changes
There are no changes noted in the system. Only one Trading partner is affected; all other XML messages are completed correctly.
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 |
| Applies to: |
| References |