Mailing-List: contact ofbiz-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ofbiz-user@incubator.apache.org
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=UIbZYuRuQ//HtFUchSi+U6jKynCKRs3hrDh2mtavH58tpuhwSnZtyRcV+mXKq5f0DPyfBX27G41F2IGlygffzwGKK94VGyedSXgQjV1GOkOHQMe5FiVQFF7iVJ7lpgS3q19gwe4rvxlxEuIVgj9pasWRMLYQkPkz9i949MKjDp4=
Message-ID: <3a57849a0610041135u3c6484b2x5fffe8bb571af1a6@mail.gmail.com>
Date: Wed, 4 Oct 2006 14:35:59 -0400
From: "John Martin" <pbwebguy@gmail.com>
To: ofbiz-user@incubator.apache.org
Subject: Correct functionality when Deleting or Voiding DHL Shipment Package
 Route
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm in the process of implementing the Void Shipment functionality in
the DHL ShipIt API (see
http://issues.apache.org/jira/browse/OFBIZ-350) and have run across a
situation that I'm not sure how best to handle.

So I am looking for some feedback on two issues:

1) How to handle unconfirmed VOID transactions?

A few facts:

- With DHL's API you can only void a shipment the day that it was
generated up until 10pm local time.

- Under certain circumstances, I have found that the API returns in
appropriate Result Codes so you can't confirm that the shipment was in
fact cancelled.

Given this, when I attempt to void a label and I'm not 100% certain, I
am wondering if I should handle things differently?  One thought is to
create a new Status "Void Unconfirmed".   This would allow the shipper
to identify packages that are questionable which should be reconciled
with the DHL billing.

I spoke with our DHL representative and she stated that typically
shipments are not billed unless the label was scanned by DHL during
shipping but there have been situations when shipments have been
billed even though never shipped.

2) Disabling the Delete button?

Once a label has been generated, I'm thinking that the Delete button
should be disabled since the shipment is now a potential real cost to
the business.  An employee could abuse the system by shipping
something personal and then deleting the transaction.  My
recommendation is that once the label is created/shipment is
confirmed, that it can only be voided.  This will at least leave
evidence of some sort of transaction.

Any thoughts or suggestions?

Thanks,

John