We have this working in one of our companies. I think it's with WorldShip v11 or v11.5 but the principles should be the same for v12.
We on Vantage v8 on Progress, so we setup a Linked Server in MS-SQL and then created a view to pull just the relevent fields from Vantage as a single row. By using the view we've filtered it to that specific company, thereby getting around the WorldShip one-field-link limit.
From the users' perspective, it works like you said: they enter the SO# into Keyed Import and Worldship pulls the data and maps it into a new shipment.
We only pull in data like the shipping address, contact, email. We're currently missing the Service Level and Billing Code(?) but we make do with the defaults we setup in WorldShip.
I can email you the view code if you like.
Nigel.
We on Vantage v8 on Progress, so we setup a Linked Server in MS-SQL and then created a view to pull just the relevent fields from Vantage as a single row. By using the view we've filtered it to that specific company, thereby getting around the WorldShip one-field-link limit.
From the users' perspective, it works like you said: they enter the SO# into Keyed Import and Worldship pulls the data and maps it into a new shipment.
We only pull in data like the shipping address, contact, email. We're currently missing the Service Level and Billing Code(?) but we make do with the defaults we setup in WorldShip.
I can email you the view code if you like.
Nigel.
--- In vantage@yahoogroups.com, "howco22" <agortman@...> wrote:
>
> Thanks for the reply.
> We were (are) trying to set up to use the keyed import, so when the shipping clerk goes to ship an order in WorldShip, he would key in the Order number, & it would pull in the shipping address, & associated fields so they wuold not need to key that info into WorldShip.
>
> I know about the differnt shipping method by release, We would probably pull most info from the orderrel table.
>
> Problem We came across is, we could not even get one simple field to pull into WorldShip. We tried pulling the SO number only, but It reported to worldship that the field is only 4 charactors wide, while Epicor shows it as (i think) 14 charactors wide.
>
> I had our UPS tech support guy here for a couple of hours yesterday, could not get it figured out.
>
>
>
> --- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@> wrote:
> >
> > Hello,
> >
> > >Has any one here sucessfully integrated Epicor9 with UPS WorldShip (Ver 12) via ODBC?
> > >I have been trying to set up the ODBC but cannot get WorldShip to connect. even using the sysprogess logon..
> >
> > Of course, the Epicor solution is the Insite Manifest system.
> >
> > There are several ways to integrate WorldShip: Key-Import, Batch Input, and I believe "directory watching"
> >
> > Connecting via ODBC has other issues:
> >
> > - A sales order can have a different shipping method by release.
> >
> > - Keyed Import only allows one Key.
> >
> > You could write a BPM that exports the shipping information but you generally lack the UPS Tracking Number before you can export it. So you'll have to go back and post those.
> >
> > I was working on a BPM that exported each release to a SQL Server table and then would use Keyed-Import to update the table. The problem is that not all of the tables are viewable from the BPM order dataset. (OrderUPSHed IIRC)
> >
> > So I currently have a VB.Net program that reads the order and updates the database but there is a small window of time where the two don't match...
> >
> > Mark W.
> >
>