Projects/DropShipment/Functional Documentation

Contents 1 Drop shipment 1.1 Overview 1.1.1 Scope 1.1.2 References 1.2 Design Considerations 1.2.1 Assumptions 1.2.2 Dependencies 1.2.3 Constraints 1.3 Functional Requirements 1.3.1 Business process definition

Drop shipment

Overview

This process transfers customer orders and shipment details to either the manufacturer or a wholesaler, who then ships the goods directly to the customer

Scope

This flow will begin when a customer order (sales order) is received. The order will be indicated as drop shipped at header level. This information would exclude it from production demand and from being used to create a (normal) shipment from sales order When indicated as drop shipped, purchase order lines will be generated automatically through a process that will be launched manually. The purchase order in such a case must be able to contain a ship-to-location that is the customer ship-to-location derived from the sales order Even though the goods are shipped from the supplier to the customer, it becomes necessary to record the purchase order receipt internally and at the same time, the shipment, for the sake of accounting. The purchase order receipt would give us the inventory value (goods receipt), which would then be recorded as COGS with the goods issue (shipment goods). That is - there is a different "financial flow" than there is a "physical flow". The receipt and simultaneous shipment of the goods need to be triggered by some kind of event. Perhaps the customer confirms receipt or the vendor sends a confirmation of the shipment with the details included.

References

Existing feature request for this functionality https://issues.openbravo.com/view.php?id=18035

Design Considerations

Assumptions

Dependencies

Constraints

Functional Requirements

Business process definition

1. New window Drop Shipment Configuration
   1. Relation ship can be defined for vendor, customer and product. (TBD:To be defined)
2. Sales order window
   1. Ability to distinguish a sales order as a drop shipment at header level or line level. (TBD)
   2. Ability to select one or several drop shipment orders and generate purchase orders based on Drop Shipment configuration. New button
   3. The schedule delivery date of the sales order must be the schedule delivery date of the purchase order
3. Purchase order window
   1. Ability to distinguish a purchase order as drop shipment order
   2. Ability to define a drop ship customer, drop ship address and a drop ship contact at header level
   3. Ability to print the document and send via email with above details to the vendor
   4. Products, quantities and attributes instances must be the same in both documents
   5. Traceability among documents at line level. New field sales order line
4. Goods receipt window
   1. When processing a goods receipt where its lines come from a PO drop shipment it automatically creates the corresponding goods shipment associated with the SO drop shipment
   2. Traceability among documents: Goods receipt and goods shipment at line level must be related
   3. Products, quantities and attributes instances must be the same in both documents
5. Purchasing plan and MRP
   1. Sales orders and purchase orders marked as drop shipments must not be taking into account
6. New process that generates PO drop ship based on SO
   1. One purchase order per customer and drop ship address
   2. Button in sales order window