Hi Rich,
You don't need Service Connect to export EDI data. The normal Report Data Definitions and Report Styles can be configured for this. This is what we use to export data for conversion into 810s, 855s, 940s.
For incoming 850s we used to use Service Connect and the supplied EDIDemand workflow, but processing through SC and then subsequently from Demand to Order was taking far too long, so we had a program written for us to import them - though I gather it's much improved in 8.03.407c.
But both import and export functions use data files, not EDI files. For all actual EDI <> data-file conversions we use eVision from Tie Commerce.
HTH,
Nigel.
You don't need Service Connect to export EDI data. The normal Report Data Definitions and Report Styles can be configured for this. This is what we use to export data for conversion into 810s, 855s, 940s.
For incoming 850s we used to use Service Connect and the supplied EDIDemand workflow, but processing through SC and then subsequently from Demand to Order was taking far too long, so we had a program written for us to import them - though I gather it's much improved in 8.03.407c.
But both import and export functions use data files, not EDI files. For all actual EDI <> data-file conversions we use eVision from Tie Commerce.
HTH,
Nigel.
--- In vantage@yahoogroups.com, "RICH WAGNER" <rwagner@...> wrote:
>
> Is anyone using Service Connect to export data and convert it to EDI 810 format or converting an EDI 850 into csv or xml to import it using Service Connect into Epicor?
>
>
> Thanks,
>
>
>
> Rich Wagner
>
>
>
> [cid:image002.jpg@...]
>
>
>
>
>
> 412-384-3100
>
> rwagner@...<mailto:rwagner@...>
>
> www.bawplastics.com<http://www.bawplastics.com/>
>
>
>
>
> [Non-text portions of this message have been removed]
>