Preprocessing method for inbound transactions

In the preprocessing method for inbound transactions, the input is the XML message that is delivered from the external system. If necessary, you can change data in the message to affect the processing logic in the processing class.

Inbound transaction customization can be done in the first exit by using the following method:

public StructureData setUserValueIn(StructureData erData) 

This method can perform the following processing:

• Validate data.
• Change external data by changing the ER record before it is mapped to the IR record and saved in the system.
• Stop further processing of the transaction by throwing an exception. For queue-based messages, the transaction remains in the queue to be reprocessed. For messages that are not queue-based, the messages are returned to the client that started the enterprise service.
• Stop the message from being processed into Maximo® Manage by throwing a SKIP_TRANSACTION exception. In this case, the message is not saved in the system. For queue-based messages, the message is removed from the queue.
• Log the transaction.