Rethink Epicor Service Connect And BPMs When Importing EDI
Updated: September 15, 2016
A client had a large number of EDI transactions that needed to be imported into their Epicor 9 ERP system. However, these also required a decent amount of processing logic, including inventory transfers, adjustments and customer shipments. The client also needed a way to see the information that had been processed as well as possibly resubmitting transactions if there had been an error and was recoverable.
Because Epicor Service Connect (ESC) is slow and making complex processes within ESC can be problematic, we built our service connect workflows to take the incoming files and store the data into a UD table. By utilizing the UpdateExt method of the business objects, we were able to store the incoming information quickly into the Epicor system without having to process each record line by line.
Once the information is within Epicor®, we wrote BPMs that executed on the UpdateExt method of the UD table. Using this base functionality, we were able to do complex data processing, including material transactions and completing customer shipments.
All of this processing was done after the original records were saved so that:
1) ESC wouldn’t be caught up waiting to save each record as we processed the backend information
2) We would have all of the information within the Epicor 9 ERP system for reference even if there had been an error in processing
Because all of the information is within the Epicor 9 ERP system it was a trivial matter to display the processing results to the users through dashboards and occasionally updatable dashboards if reprocessing was necessary.