What Can Exit Point Events Do for You?

Every business is looking to improve efficiency in daily operations.  With improved efficiency – costs will be cut and time will be saved.  The old saying “Time is money” still applies and this is exactly what exit point events can help you do.  When activated – the event waits in ready status.  When the activity occurs – an event is raised.  This event is what can save time and money in problem resolution.

The official definition for exit point events is the following:

Exit Point processing raises events in EBI when certain transactional activities occur.

This feature alerts you to these activities, provides relevant data, and helps you quickly identify and address errors.

As in previous releases of EBI – all translation errors continue to be logged in the EBI Auditor.  This new feature gives a form of action to these isolated conditions that normally are deep within the audit log / translation process.  The event alert should be customized to your needs with either email notice or launching a business process.  This feature could nearly eliminate the time previously required to search and find translation problems ultimately saving time and money!

Each of the six EXTOL-shipped exit point events provides a way to isolate a common translation issues or errors.  A review of each event will be done to expose the benefits it can provide a business.  I will also provide a relevant example or business case for each.  Please note this feature only supports inbound EDI transactions at this time (EBI 2.5).

1.  The one positive exit point event that occurs early in translation is the “Interchange Processed”. If the EDI document passes the interchange validity tests – this event is raised.  It is important to realize a processed status does not mean the translation is complete.  Also – due to the potentially large number of interchanges – EXTOL suggests a selective filtering to minimize resource usage.  An example of this would be to filter the event based on a specific trading partner to obtain frequency data.  The EXTOL-shipped event produces an email with the interchange# and payload data.

2/3.  Two similar events in functionality are the “Endpoint Not Found” and the “Collaboration Not Found”. The endpoint data points to the collaboration information.  If endpoints are missing – only the endpoint event will be triggered.  If endpoints are found – then the collaboration is checked.  Both events provide interchange data and a total count of failed messages within an interchange.  An example would be if a trading partner upgraded to a new document type without giving notice to all partners – this could potentially lead to either of these errors.

4.  The “Duplicate Interchange” event validates its unique status against the Interchange Log.  The endpoint source tab contains a true/false option to Process Duplicate Interchanges.  This option must be false for this event to raise an alert.  The EXTOL-shipped event produces an email with the Interchange Control# and payload data attached.  An example producing this event could be processing the same batch multiple times, your trading partner sending the same data multiple times, or your trading partner sending different data but with the same interchange control number of a previously received batch.

5.  The “Collaboration Errors” event is raised when matching errors occur at the collaboration level of translation that equal the predefined Error Codes in Collaboration Profile.  This event enables the customer to monitor for specific errors without having to dig deep into the EBI Auditor to find them.  Examples of collaboration errors include invalid date and time at interchange and group levels.  The EXTOL-shipped event produces an email with Interchange Control#, Collaboration Name, and a list of errors.

6.  The “Acknowledgement Error” event is exclusively used for the evaluation of inbound acknowledgements when errors are found.  The EDI Data is scanned for Edifact (4) = ACTION, CODED or X12 (P), (R), (M), (W), (X).   The event is launched at Message level.  This quick notice can save a lot of time and money!  For example – an acknowledgement from a failed batch of invoices due for collection is money due in your pocket.  This immediate alert enables a quicker resolve.

Each of the exit point events offer improved efficiency in daily operations.  The old saying “Time is money” will always apply!  Let EBI 2.5 exit point events help you achieve it!

Please note that EXTOL is open to customer suggestions and ideas on future exit point events.  Your feedback will drive future development on this feature!

Leave a Reply

Your email address will not be published. Required fields are marked *


*