When a return happens a route segment is created to show that it came back in the same shipping stream. The added code then puts it in a holding areas in the facility for future deposition. Once the CRM is completed, then the shipment is re-stocked an the refund it issued, or a new shipping segments are generated with a re-ship status. so the order has the history of the shipping history in tack. Yes the code is not in the SVN or OTTB.
Craig Ambrose sent the following on 1/10/2012 4:18 PM: > BJ, > > We have a similar scenario on our hands. We send out our shipment using UPS > and it is not received by the customer for any number of reasons and the > package is returned to our facility. We typically do as you suggest and it > enters a CRM workflow and in most cases we want to re-ship the order. I > don't want to handle it as a return with the stock going back into inventory > in case the inventory gets reserved by a subsequent order. > > In any case, what do you mean by "re-ship"? Will this result in a new > Shipment entity and all of it's relationships? Or will it just be a new > ShipmentRouteSegment or some other addendum. > > I've been poking around the Facility and Order applications and haven't seen > anything that looks like a "re-ship" operation. I'd like to maintain the > history of this order in terms of the Shipment being sent and the UPS > tracking ID that was generated and used and that subsequently it left the > facility again with a new UPS tracking ID. > > Thanks for the insights. > > -craig > > -- > View this message in context: > http://ofbiz.135035.n4.nabble.com/How-to-handle-Returns-from-the-Post-Office-tp1677185p4283972.html > Sent from the OFBiz - User mailing list archive at Nabble.com. >
