IBM BJ0NJML Integration Guide - Page 139
Error Research, No XML Files Exist, One or More XML Files, Exist, No ER and IR Elements
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 139 highlights
Common Causes of Errors Error Type Communication error Message error Description Caused by communication problems with the external system from system failures or network issues. Caused by erroneous message data values. Actions Restore communication with the external system. 1 Change the transaction status to HOLD. 2 Correct the error XML file. 3 Change the transaction status to RETRY to reprocess the transaction. Error Research No XML Files Exist One or More XML Files Exist No ER and IR Elements in the Error File When you receive an error notification, look at the XML file in the Message Reprocessing application. Depending on the type of queue (sequential or continuous) and the number of messages in the queue, zero, one, or multiple error XML files might appear in the Message Reprocessing application. If no error XML file exists in the Message Reprocessing application, the message was retried and the error was not encountered again. The system deleted the error file. For example, an error occurs in an inbound receipt message due to an incorrect general ledger (GL) account. After the error occurs, an online user enters that GL account in the system. The system successfully reprocesses the message and successfully saves the data. In another example, an outbound transaction encounters a communication error. When the communication problem is resolved, the message is sent to the external system and the error file is deleted. When an error occurs in a sequential queue (inbound or outbound), processing of the queue stops until the error is resolved. One XML file exists in the error folder for the queue. When an error occurs in a continuous queue, processing of the queue continues and additional errors can occur before the initial error is resolved. Multiple XML files exist in the Message Reprocessing application. If the corresponding error file contains no ER or IR element, the integration framework encountered a major exception. The following example is an error XML file that the integration framework creates when it encounters a major exception: A major exception has occurred. Error on line 14: An invalid XML character (Unicode: 0x1b) was found in the element content of the document. Error Management 125
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/139.png)