EDI - Outbound orders, inbound invoices & ASNs

Epicor ERP 10
1

We are a manufacturer, but some parts we order from another manufacturer.

We are wanting to set up EDI with this other manufacturer. Specifically, EDIFACT (X12 in parentheses) types:

ORDERS (850 order) - outbound
ORDCHG (860 order change) - outbound
INVOIC (810 invoice) - inbound
ORDRSP (855 order ack) - inbound
DESADV (856 advance shipping notice) - inbound

It appears Epicor (our current version is 10.2.200.11) only has the exact opposite directions out-of-the-box for the document types above.

Can anyone put me onto the correct path of generating these documents? Also, into which module of Epicor would the inbound documents be placed? There seem to be some facilities of Demand Management that could be the answer, but I’m only scratching the surface so far.

We also have TIE Kinetix on-premise, so getting the Epicor-standard tilde-delimited version of files would be easiest to use with TIE.

Currently our buyers create purchase orders and print them to the APM, to be sent via email. I would imagine I could build report styles that could generate the tilde files, and use BPMs to populate them.

I’m fairly new to Epicor (7 months) so I apologize if I’m missing something obvious. I have looked (and am still looking) through the help and documentation, but thought I might get good results here.

thanks

2

I’ve come to the same conclusion you have.

Epicor EDI\Demand Management = customer<->you
You <-> Supplier = Custom

3

Hi Scott,

We find ourselves in the identical position you described in your post in May 2019. We have TIE on prem, and need to now reverse the direction of the our EDI documents to send orders to our supplier. Did you end up with a fully custom solution? Are you using your TIE platform in the process?

Thank you!
Sarah Crews

4

Custom for us too - we’re using EDIHQ.

The vendor document suite (850 out, 810 in, 856 in) was not available out of the box.

Customer document suite (same 3 in opposite direction) was available…but nothing for associated customer docs like the 753/754 routing set, 852/POS, 867/product activity data.