Sage 100

Going to upgrade a client from SAGE 100 ERP 4.30 to 2014. They ship 95% of their product via UPS and FedEx. In v4.30 they connected the Sales Order module to UPS Worldship and FedEx software for a one-way import. Does anyone know if the current UPS and FedEx programs will connect to SAGE 100 ERP v2014? Are any additional programs (i.e. Crossware) needed?

if the import is one-way FROM sage into world ship and FedEx then you will just need to point the ODBC Driver(s) to your new install when you are ready to go live with the upgrade. typically additions software like Crossware is only required if you want to send information such as tracking numbers or freight amounts. back into Sage

@DavidOverholt It has been awhile since I work at this client, but I thought both programs used ODBC to connect to Sage. Thanks for the confirmation.

Fastest way to connect to UPS world ship is via an Access PTQ. If you use the sotamas odbc driver, you run the risk of the connection crawling. Ever since being burned in v4.1, I have always used an Access PTQ. Will post instructions after lunch.

Original instructions were provided by Big Louie back in the day. Have been revised for the new business framework. I am always amazed that some people can get this to work using the sotamas ODBC. I spent the better part of a day once working with UPS only to throw up my hands. I finally found the power of PTQ's and have been a believer ever since.

@JeffSchwenk I too had issues back in version 4.1 and remember using the access steps you outlined. but recently I have not needed to. I setup an ODBC with a ""silent"" connection and speed has not been an issue since version 4.3 and forward even on my larger clients.

@JeffSchwenk Thanks for the PTQ reference document. I will include it in my upgrade file.

Thanks @JeffSchwenk. Very useful document.

Just the tip of the PTQ iceberg........ Will be glad to share more. Give me a shout if interested. FWIW, a fellow 90Minder wrote a script to writes back the Worldship information to MAS. Very reasonably priced. Client has been using it for nearly 18 months now. It could probably be modified to work with Fed Ex as well. I have also modified the Worldship PTQ pull to specify in Worldship type of shipment (red/blue/orange, etc) and whether to bill a third party or bill recepients UPS account. A little mapping involved but quite effective.

@RonGouveia - Survived the twin hurricanes???

Yes, didn't have much affect on Oahu. Big Island took the brunt of it and is still in the recover mode. The huge mountains of Mauna Kea and Moanaloa basically stopped the first hurricane it its tracks. The second hurricane missed the islands completely. Altogether, we were very fortunate!

@DavidOverholt - I always connect directly now, too. The latency issues do not seem to be around any more.

Hmmmmm. Most of my horror stories are from the pre v4.4 days. May try going without one of these days. Though I did run into a stamps.com connection issue in v4.5 which was easily solved with a PTQ....

I THINK what UPS used to do is open ALL 1100 files when it first started up and that was the issue. Now it just opens the file it is going to use.

So the sotamas didn't improve, Worldship did???

LOL - yes, I think so

I have a client going live today on 2014 - upgrade from 4.4. They read from SO Header when processing shipments in Worldship. No write-back to Sage 100. There is an Access DB intermediate, which is not working in the new version. Tried bypassing Access and set up new silent odbc connection using SOTAMAS. Mapped UPS to use it. When try to process a shipment, get this message: [Providex] [ODBC Driver] [FILEIO] Table is not accessible. They have a second shipping company that accesses MAS tables using an ODBC connection, which works fine, so I don't think the DSN is corrupt. Any thoughts? @Sage100UrgentSupportNeeded

Does a test of the silent ODBC return the correct number of tables?

It returns 1140 (I think). Is that the right number?

Close enough - sometimes it seems to connect but returns 0 tables

Each company has it's own silent DSN, and one works and one doesn't?

No, the other shipping company uses SOTAMAS90 - different DSN.

How is the Access DB connected? It sounds like the ODBC connection needs to be changed for the new Sage path. I have several clients pulling data out of v2014 via Access without issue. Is the Access DB using a PTQ?

And as @PhilMcIntosh indicated, you need a separate connection for each company.

@JeffSchwenk I don't know if it's using a PTQ (she winced, having attended one of your sessions on them and long forgotten what I saw). Umm, how do I know?

Better late than never. Call me.