No experience with Worldship, but a suggestion may be to use a logical file with only the records I and N instead of sending them the Physical file. I have used this trick several times when sending files.


Dave B

Adam West adamster@xxxxxxxxx> 08/18/08 8:56 AM >>

UPS package shipping uses an application written in VB called Worldship. We are having some issues with their system. They say they cannot differentiate between our record types.
We have recently added some fields that they need anyway for example the weight of the item we know from our AS/400 files and don't need to have the user weight and key we can download this and a couple of others. However, what happens is their application wants thes new fields on all types of orders. We have orders from the web, and also other orders such as repairs or regular orders to small stores, these have more complicated weights and cannot be automated.
The internet orders are coded in the first position of the Invoice Number field, and can be differentiated from other types of orders that are not part of the new fields process.

We have asked UPS to allow their applcation some logic conditions to only worry as it were about the I and N orders in terms of the new fields, but they cannot make this happen.

I was wondering if anyone had expereinced this problem and came up with some kind of 'work around' or method of coding the fields sent to their Flat file that would help us. Or possibly, what defaults should I be using say for our numeric fields. It seems like it crashes even when I default to zero. The UPS fellow I am working with said he had Null fields, if so, what should I be using when I initialize my fields?

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].