When an outbound transaction is triggered from Maximo, it has to pass through lots of checks and updates, once it has passed through all that based on the endpoint (xml, csv, http…) defined, the object is delivered to the external system or common point of contact in case of flat files or xml files.
Similar, for inbound transaction, when data is pushed into Maximo, it makes sure the data complies to its set of rules and restrictions. Once it complies, then it has to go through the set of rules defined on the MBO level (java classes, automation scripts, DB config…) and once all clear is received, it is actually inserted into Maximo database. If there is an error it goes to reprocessing queue where once the error is rectified the record can retry.
These checks and balances as we all know are very important as it maintains the integrity of Maximo database and also it makes sure only data which Maximo is prepared to receive comes in.
In this article I will explain the processing rules from outbound transaction perspective. They will apply in a similar fashion for inbound if not completely same.