Jump to content


oneduality

Member Since 11 Sep 2008
Offline Last Active Oct 07 2008 06:22 AM
-----

Posts I've Made

In Topic: Worldship 10.0 issues

07 October 2008 - 06:27 AM

Yes, the MOM Forum would have gotten you an answer much quicker!

Why is your customer not using the integrated UPSLink, whereby MOM acts as UPS, picks, pack, scan, and ship all packages from within MOM and have instant tracking numbers in the system without the need for exporting and importing files? Ask MOM Tech Support about the integrated UPSLink HTTP Interface.

NOTE: I don't believe you can run UPSLink on any computer that has had UPS Worlship currently or previously installed on it.

For the limited international shipments they do, you would still have MOM export the international shipping file to Worldship. You have to properly map the appropriate fields in WorldShip to be able to read the file, and setup Keyed Import. Then the customer would enter the order number, and WorldShip will automatically fill in most fields. Upon End Of Day, it would then export a file back to MOM, which needs to be imported in MOM. Again, MOM can help with all of this, since there are so many details. Ask MOM for the WorldShip Integration Addendum. It sounds like whomever setup the UPS system set the file to Append, rather than Replace. That is probably whjy you are re-importing so many records.


I've been talking to UPS and Dydacomp about using UPS Online but I was told it may actually be more effort for the client.. doing the keyed import sounds best for right now, though it sounds like the keyed import rquires mapping directly to the MOM database, and that's where I've not been able to find any good information.. can we do a keyed import straight off the dbf file coming over now? if so then it sounds like we might just need to change the primary key on the import.

I've got a post on the official forums now as well, so we'll see.. I do appreciate the response! this is our first MOM integration.. aside from this whole worldship piece, everything else has been great.. www.estherprice.com if you are curious to see some of our sitelink modifications :)

In Topic: Worldship 10.0 issues

07 October 2008 - 05:48 AM

Not a pure mystery, but this board is very scarce. If you just bought MOM, then you just bought a service agreement and MOM's Support Forum is much busier than this one.

To narrow down my answer, please provide the following:
1). What version of MOM are you running?
2). What percentage of UPS shipments does this company do OUTSIDE of the United States?


We did just buy MOM but their support has been rather horrible .. to say the least .. I've not tried their forum, but I figured I'd try here since this seemed to be an outside community.

1) they are running MOM 6.0 XL, latest build
2) A very small percentage, so we're looking at UPS Online as an option, but UPS told me that it might actually be more time consuming for them.. not sure!

In Topic: Worldship 10.0 issues

07 October 2008 - 05:00 AM

I'm a web developer and recently we chose MOM + SiteLINK as a replacement system for one of our clients..

Customizing SiteLINK wasn't an issue, and everythign has gone very smoothly thus far.. but then came time to integrate UPS Worldship .. the instructions were pretty lengthy and in trying to make sure everything went right ... We called in our clients UPS contacts for anyone who's had experience integrating MOM and Worldship .. they sent out a guy who seemed like he could barely work a computer :)

He went through the UPS Worldship portion of the instructions and I handled the MOM configuration ..

Issue #1

After we export the shipping information from MOM and import it into Worldship, we do see the orders in there but there doesn't appear to be an order number or a customer id in that screen.. with their previous system, they said the order ID showed up in the customer id field as they were reviewing the order.

Issue #2

When we export back out, despite the fact we only had 2 orders imported for the test, it exported 197 items .. I suspect these are orders that they have processed before, but I'm not familiar with Worldship enough to know what that is about.. every time I run an export, it is always a large number.. it's as if it's constantly re-exporting the same thing..

Issue #3

After I've processed an order with Worldship (F10 and printed the label) .. and then I export those 197 entries ... then re-import back into MOM .. the information doesn't appear to go anywhere.. this lead me to open up the CSV file .. it had 3 fields, tracking number, reference 3 and reference 4 ... only the tracking number field had any data.. which tells me that MOM had no way to link that tracking number to a package .. which probably ties back to Issue #1 .. .. I would imagine at very least that there should be a tracking number and a box id or something?

Issue #4

Every time Worldship does an import from MOM, the same orders come in each and every time .. almost seems similar to Issue #2 .. or maybe it's doing this because the tracking information never came back? again I'm not familiar enough with this..

Any ideas or pointers? I would greatly appreciate it


Wow I guess my posting is a pure mystery to everyone :) most of these are still issues .. though now tracking is coming back into the system fine..

I do have ONE other issue.. in their previous order entry system, the worldship integration was such that they could export their shipments to worldship, print off a pack list with a barcode.. scan the barcode in worldship and bring it right up .. with MOM, they can't scan anything and bring up the order, they have to go to the history screen, find the order and edit/process it fine for 80-100 shipments a day, but in the holiday season, they do thousands per day..

In Topic: Error when printing

18 September 2008 - 06:28 AM

Well I don't know what the error means, but it references that it logged the error in a file. Have you drilled down to that file and looked to see if it logged any more detailed information?


Sorry for the delay, I didn't have it set to notify me of a response..

the log file wasn't very helpful, but it seems now that the error has stopped.. not sure what exactly was going on ..