We are running RosettaNet conversations on IS 4.6 using TN. We receive status update transactions that need to be processed in the order received. The problem is that we sometimes receive multiple status updates (meaning multiple TN conversations) to the same record in our backend in a span of 5 seconds or less. By the time the transactions are written out to an Oracle table that is being used as an interface to our backend, the transactions aren’t necessarily written in the order received.

I’ve looked at all of the options on the conversations and services being called and don’t see a method to ensure first in, first out.

Any ideas?