There are EDI related fields on certain Epicor elements, like ShipHead.EDIASNDate, for example, that seem to indicate they can be tied to EDI document transmission:
Does anyone have any experience using these fields that can speak to what they represent and what needs to be done to get them populated with data?
Not sure, but I’m exploring ASNs in the future so I’ll let you know when I do.
I believe those only show data if you use Epicor’s EDI solution. We don’t, and they have never populated. They added a whole bunch of new EDI fields in 2025.1 or .2 - I believe this is giving those new fields a home, but for those outside the Epicor EDI ecosystem, they don’t populate.
May depend on what EDI you’re using…could it be a remnant to TIE/Kinetix eVision? We’re doing outbound EDI ASNs and those values aren’t propagated here.
EDIT - or yeah what @spaceage said lol
They are useful fields, and I’d love to populate them with the data we’ve been storing in UD fields for years for visibility within a doc instead of having to rely on BAQs.
Yeah our inbound maps are leaning into the UD fields to capture data and then passing back on the outbound…varies from partner to partner. I’ve tried not to make any changes since we started - all of our maps were built out by Epicor.
We do use Epicor EDI. The field help does say ‘EDI Mapping configuration required to update field with EDI translation date.’
