IBM BJ0NJML - Service And Asset Management - Error Research

Common Causes of Errors
Error Management 125
Error Research
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.
No XML Files Exist 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.
One or More XML Files
Exist
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.
No ER and IR Elements in
the Error File
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:
<?xml version="1.0" encoding="UTF-8"?>
<ERROR>
<ERRORMESSAGE>A major exception has occurred. Error on line
14: An invalid XML character (Unicode: 0x1b) was found in the
element content of the document.</ERRORMESSAGE>
</ERROR>
Communication error Caused by communication problems with the
external system from system failures or
network issues.
Restore communication with the
external system.
Message error Caused by erroneous message data values.
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 Type Description Actions