I got the automatic XML set up and working.
Is there no way to put package dimensions into supermanager that will transfer to UPS?
Thanks
Jason
Jason,
We have an alpha version that includes this capability. It will be released as a beta shortly. If you are eager to get access to it we can send it to you.
Thanks,
David
It will probably make the difference between me purchasing the SuperManager or not.
Jason
Jason,
I sent you a link to download the alpha version.
Thanks,
David
David,
I have installed version 1.3.2.3 a couple of days ago and I just can't get the UPS interface to work. I had an old version of WorldShip on disk and tried the ODBC way. After 3 tries and some creative mapping I got it to work, then I found this post. Does the newer versions of the SM send dimension info to WorldShip using the XML format?
I have tried it and I get this:
Dimensions and Dim Wt cannot be imported, Dimensions will be cleared
We do a lot of odd size boxes, if the system can't do this it would be a deal breaker for us too.
Thanks,
Harry.
Harry,
Sorry about this. This is the first feedback we have heard about this and the UPS specification does not spell this rule out. We will have to add a program setting of whether to use dimensional weight or not. We'll get right on that.
Thanks,
David
Harry,
I have released version 1.3.2.4 in which I added a setting for whether to use dimensional weight or not. By default it exports length, width and height and leaves out dimensional weight. Please use "Help" | "Check for Updates" in SuperManager to install the new version and let me know how it works.
Thanks,
David
David,
I just updated and tried to move the package info. This is what I get:
QuoteXML Auto Import Log - 01-May-2009 13:29:26
01-May-2009 13:29:26 - Starting Session
01-May-2009 13:29:28 - There are 2 record(s) to be imported.
01-May-2009 13:29:28 - Importing record 1
01-May-2009 13:29:29 - Truncated import data for Shipment Information::Width from '1593' to '159'.
01-May-2009 13:29:29 - creating package record: 1
01-May-2009 13:29:29 - Importing record 2
01-May-2009 13:29:30 - Truncated import data for Shipment Information::Length from '1450' to '145'.
01-May-2009 13:29:30 - Truncated import data for Shipment Information::Length from '1450' to '145'.
01-May-2009 13:29:30 - creating package record: 1
01-May-2009 13:29:30 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
Truncated import data for Shipment Information::Width from '1593' to '159'.
creating package record: 1
Importing record 2
Truncated import data for Shipment Information::Length from '1450' to '145'.
Truncated import data for Shipment Information::Length from '1450' to '145'.
creating package record: 1
Processed 2 record(s).
01-May-2009 13:31:59 - There are 2 record(s) to be imported.
01-May-2009 13:32:00 - Importing record 1
01-May-2009 13:32:00 - creating package record: 1
01-May-2009 13:32:00 - Importing record 2
01-May-2009 13:32:00 - creating package record: 1
01-May-2009 13:32:00 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
01-May-2009 13:32:20 - Starting Session
01-May-2009 13:32:42 - Starting Session
01-May-2009 13:32:43 - There are 2 record(s) to be imported.
01-May-2009 13:32:44 - Importing record 1
01-May-2009 13:32:44 - creating package record: 1
01-May-2009 13:32:44 - Importing record 2
01-May-2009 13:32:44 - creating package record: 1
01-May-2009 13:32:44 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
I tried one test order. It has 2 packages: 14 X 14 X 10 8.69 lbs and 12 X 9 X 6 25.13 lbs
It looks like something is just not lined up.
I also just noticed that after closing SM the package info in SM changed to:
307.25 X 593.97 X 0.03 8.69 lbs and Oversize is checked
337.96 X 225.31 X 0.02 25.13 lbs and Oversize is checked
It did this after I updated and re-opened SM and I didn't think much of it. I corrected the info and attempted the XML exchange, then when I closed and re-opened SM just now it did it again.
Treskel,
I found and fixed the problem. It amazes me sometimes how we can have bugs like this in there and we go for so long without someone having problems with it. Glad you helped us find and fix this problem!
There is now a version 1.3.2.5 available for update.
Thanks,
David
David,
It seems like part of the issue is resolved. After exporting the info to UPS it is no longer messing up the L, W & H that I had set, but is still not giving me a shipment.
I got the same kind of log:
QuoteXML Auto Import Log - 01-May-2009 13:29:26
01-May-2009 13:29:26 - Starting Session
01-May-2009 13:29:28 - There are 2 record(s) to be imported.
01-May-2009 13:29:28 - Importing record 1
01-May-2009 13:29:29 - Truncated import data for Shipment Information::Width from '1593' to '159'.
01-May-2009 13:29:29 - creating package record: 1
01-May-2009 13:29:29 - Importing record 2
01-May-2009 13:29:30 - Truncated import data for Shipment Information::Length from '1450' to '145'.
01-May-2009 13:29:30 - Truncated import data for Shipment Information::Length from '1450' to '145'.
01-May-2009 13:29:30 - creating package record: 1
01-May-2009 13:29:30 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
Truncated import data for Shipment Information::Width from '1593' to '159'.
creating package record: 1
Importing record 2
Truncated import data for Shipment Information::Length from '1450' to '145'.
Truncated import data for Shipment Information::Length from '1450' to '145'.
creating package record: 1
Processed 2 record(s).
01-May-2009 13:31:59 - There are 2 record(s) to be imported.
01-May-2009 13:32:00 - Importing record 1
01-May-2009 13:32:00 - creating package record: 1
01-May-2009 13:32:00 - Importing record 2
01-May-2009 13:32:00 - creating package record: 1
01-May-2009 13:32:00 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
01-May-2009 13:32:20 - Starting Session
01-May-2009 13:32:42 - Starting Session
01-May-2009 13:32:43 - There are 2 record(s) to be imported.
01-May-2009 13:32:44 - Importing record 1
01-May-2009 13:32:44 - creating package record: 1
01-May-2009 13:32:44 - Importing record 2
01-May-2009 13:32:44 - creating package record: 1
01-May-2009 13:32:44 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
01-May-2009 15:54:14 - Stopping session.
01-May-2009 15:54:14 - Imported shipments: 2 Successful shipments: 0 Failed shipments: 2
01-May-2009 23:54:57 - Starting Session
01-May-2009 23:55:00 - There are 2 record(s) to be imported.
01-May-2009 23:55:00 - Importing record 1
01-May-2009 23:55:01 - creating package record: 1
01-May-2009 23:55:01 - Importing record 2
01-May-2009 23:55:01 - creating package record: 1
01-May-2009 23:55:01 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
01-May-2009 23:55:35 - Stopping session.
01-May-2009 23:55:35 - Imported shipments: 2 Successful shipments: 0 Failed shipments: 2
01-May-2009 23:56:30 - Starting Session
01-May-2009 23:56:32 - There are 2 record(s) to be imported.
01-May-2009 23:56:32 - Importing record 1
01-May-2009 23:56:32 - creating package record: 1
01-May-2009 23:56:32 - Importing record 2
01-May-2009 23:56:32 - creating package record: 1
01-May-2009 23:56:32 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
01-May-2009 23:57:10 - Stopping session.
01-May-2009 23:57:10 - Imported shipments: 2 Successful shipments: 0 Failed shipments: 2
01-May-2009 23:58:33 - Starting Session
01-May-2009 23:58:34 - There are 2 record(s) to be imported.
01-May-2009 23:58:35 - Importing record 1
01-May-2009 23:58:35 - creating package record: 1
01-May-2009 23:58:35 - Importing record 2
01-May-2009 23:58:35 - creating package record: 1
01-May-2009 23:58:35 - Processed 2 record(s).
Importing from sm-worldship.xml
Importing record 1
creating package record: 1
Importing record 2
creating package record: 1
Processed 2 record(s).
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
Treskel, Inc.
1. The Service is not a supported UPS Service Type.
Am I correct in the that there is no place I have to match up variables like in ODBC? Is there a decimal place off somewhere? Since I am the only one complaining about this I am concerned that I am doing something wrong.
Guys,
I fiddled with the XML file manually and it looks like the service is not being imported and the package type for "Your Packaging" should be "package" not "pkg" if you can get that fixed and check through the other services that will kill the bug.
Thanks.
Jason,
As far as I know SuperManager is not printing "pkg" or "package" it uses the tag <PackageType>CP</PackageType> to set the package type. Are you using the function "Export..." | "WorldShip XML" or "XML Exchange... WorldShip" to export the order(s)?
Looking more closely at the log file it appears that the service type might be what it is having problems with. Do you have all your ship methods mapped for WorldShip? To do so go to "View" | "Store Settings..." and go to the "Custom Fields" tab. Double click on each ship method, select "XML Exchange - Worldship" on the list and set the dropdown for the ship class. Once these are all mapped I am guessing it might fix the problem.
Thanks,
David
I just verified that all of my shipping is mapped, and I was using XML Exchange... WorldShip.
I have done another test file. I will send the XML.
Treskel,
The service type on the xml you sent was blank. This would normally mean the service types were not mapped for the WorldShip XMl export. Please note the steps to map the service type are:
1. Go to "View" | "Store Settings..." and select the "Custom Fields" tab.
2. Double click on the ship method you need to set it for (you'll need to set each ship method you plan to export to worldship).
3. Select "XML Exchange - WorldShip"
4. From the Ship Class dropdown select the service type it should use in WorldShip for this ship method.
5. Click "OK"
6. Repeat for remaining Ship Methods.
After verifying this can you please send me a screenshot of the ship method details window as shown below
Thanks,
David
David,
Thanks. That did take care of the shipping service issue. I didn't realize there were more than one place to map, I had done it for the ODBC and just skimmed right over that in the XML section. It is still sending the "Package" as "PK" and not working. Is there some place to map that too?
Thanks
Harry.
Harry,
I think we're almost there! The package types work the same as the ship methods. The steps to map them are:
1. Go to "View" | "Store Settings..." and select the "Custom Fields" tab and select the "Package Types" tab on the left.
2. Double click on the package type you need to set it for (you'll need to set each package type you plan to export to worldship).
3. Select "XML Exchange - WorldShip"
4. From the Package Type dropdown select the package type it should use in WorldShip for this package type.
5. Click "OK"
6. Repeat for remaining Package Types.
Attached is an example.