If you are able to get them to connect to your machine Adam you are doing
better than us....I cannot even get worldship to hook to the damn
PF......have been working on this for three months now.
From: Adam West <adamster@xxxxxxxxx>
Date: 08/18/2008 09:13 AM
Subject: UPS WorldShip issue
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 is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this
transmission in error, please immediately contact the sender and destroy
the material in its entirety, whether in electronic or hard copy format.