Intergration Error handling

[Shells]

I would like to get some input from other customers on how you handle integration errors and who is responsible for them. At our company, our otm support person(s) is responsible for monitoring the integration feeds for errors, communicating these to the customer and resolving the errors. It wasn't so bad when we only had 2 or 3 customers/domains in our environment, but now as we have over 10 customers and 80+ domains it has gotten a little out of control and much harder to manage - especially by 1 or 2 people.

I don't know if any of you are in this same scenario/situation, but I was curious as to how your group handles integration errors at your site. Is the customer responsible, does your i.t. group handle, do you have a special monitoring tool, what do you do with the errors when you get them, etc? I am trying to help make things better for both the people responsible for monitoring and the customer so any info you want to throw at me (good or bad) is greatly appreciated.

Shell

[bmclamb]

Re: Intergration Error handling

Hi Shell,
We struggled with that issue when we first started with OTM as well. We set up several reports that monitor the i_transaction and i_log tables for specific errors. We set the reports up on a schedule and have them sent to the business user responsible for the error. For example, if we get an edi response from a carrier for a shipment and the shipment id sent in the edi transmission is not valid, the relevant data will show up the report. This has been pretty effective for us and cut out the manual process of looking at the integration error messages.
Thanks,
Beth