View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:Distribution Orders/Functional Specification

Contents

Distribution Orders - Functional Specifications

This document holds the functional Requirements for the Distribution Orders functionality in Openbravo. Distribution Orders belongs to a larger scope of new functionalities in Openbravo aimed towards improving the Supply Chain Management. Apart from Distribution Orders, these functionalitis are:

Overview

Distribution Orders functionality (DO) is designed to plan and execute the distribution of goods between logistical units (stores, warehousses) that belong to the same legal entity.

The distribution of goods between logistical units (stores, warehousses) that belong to different legal entities is planned and executed by the typical Purchase Order / Sales Order pair. But when the receiving and sending sites belong to the same legal entity, this PO-SO pair cannot be used since there is no change of ownership hence no invoicing/payments. Still, the whole planning and logistical behavior is identical to the PO-SO pair. For that reason the Distribution Order functionality will be very similar to the functionality of the PO-SO pair, but excluding the change of ownership and subsequent functionalities:

Scope

The following functionalities are in scope:

The following functionalities are not in scope and can be considered Roadmap acceleration projects:

Design Considerations

Distribution Orders are aimed to become a 'Core Function' of Openbravo in the sense that it should be a module distributed together with the Core in most installations.

Distribution Orders shall be a transparent function. Organizations not requiring it should not be obliged to use it.

The C_Order structure should not be used, there are too many dependencies / reports that would need adjustment.

Functional Requirements

General Functional Requirements are listed below :

Business process definition

The process involving Distribution Orders will follow the process below :

  1. (Optional)Input of a Requisition/Proposition from a location that requires/proposes goods.
  2. (Optional) Conversion of this Requisition/Proposition into a Distribution Order.
  3. Picking is processed against the Distribution order lines.
  4. Shipping out of the origin warehouse to an intermediate location.
  5. Reception in the destination Warehouse from the intermediate location.
  6. Distribution Order is then closed

Advanced User stories (Roadmap acceleration projects)

Replenishment of a Store from a Central Warehouse (Pull Model)

The Central Warehouse and the Store belongs to the same Company "Happy Wines Shops"

Actors :

  1. Sophia realizes she will soon be out of Bottles of Cabernet Sauvignon 2013, thus she places a requisition for 36 Bottles.
  2. Marcus reviews the new requisition and agrees to this replenishment. Therefore he converts ('executes') the requisition which results in a DOr for 36 Bottles for Sophia's Store.
  3. In the same time, he verifies that he has currently 48 Bottles on-hand in the central so this replenishment is not a problem.
  4. Marcus does not need to create the mirroring DOi in the Central Warehouse since that is created automatically by booking the DOr.
  5. He selects a Distribution Route that defines that Goods will be transported by truck to Sophia's Store.
  6. William reviews the DOi and prints it.
  7. William creates thePicking Tasks (AWO) for that Distribution Order.
  8. 36 Bottles are picked from the warehouse and the Picking Tasks are confirmed.
  9. The Delivery truck picks the goods and a good movement is processed that sets the Picked Good to the "In transit" location (can be a vehicle).
  10. The Delivery Truck arrives at the Store. Sophia Counts the Goods and acknowlegdes the Reception according to the DOr.
  11. Distribution Order is then marked as Closed.

Replenishment of a Store from a Central Warehouse (Push Model)

The Central Warehouse and the Store belongs to the same Company "Happy Wines Shops"

Actors :

  1. Marcus is reviewing the Stock he has on hand in the Central Warehouse and realize that he has 48 bottles of Cabernet Sauvignon, which is 36 Bottles over is safety Stock.
  2. He therefore creates a Stock Proposition for these 36 Bottles.
    1. In the same time, he verifies a listing of current Store's stock and identifies that Sophia's store is currently short on this product, which also happen to be her best selling product on the last weeks.
    2. Alternatively he will see a window where the stock is mostly needed, including pre-suggestions for distribution. Marces accepts suggestions which creates the related propositions.
  3. Marcus executes the proposition which -in this case- results in a DOi from the Central Warehouse to push his Stock Proposition (note: whether a DOi or SO is created should be transparent for the end-user).
  4. He also creates the corresponding DOr for usage in Sophia's Store.
  5. He selects a Distribution Route that defines that Goods will be transported by truck to Sophia's Store.
  6. Marcus Books the Distribution Orders
  7. William reviews the DOi and prints it.
  8. William create a Picking Order for that Distribution Order.
  9. 36 Bottles are picked from the warehouse and the Picking Order is Processed.
  10. The Delivery truck picks the goods and a good movement is processed that sets the Picked Good to a "In transit" warehouse.
  11. The Delivery Truck arrives at the Store. Sophia Counts the Goods and acknowlegdes the Reception according to the DOr. A Good movement is created and processed that moves the goods from In transit to Sophia's Store's Warehouse.
  12. Distribution Order is then marked as Closed.

Replenishment of a Franchisee

The Store belongs to a Franchisee that also makes use of the same Openbravo Instance but has a separate Legal Entity. For the Planner this case is actually transparently similar to the Replenishment of any other store.

Actors :

  1. Francesca realizes she will soon be out of Bottles of Cabernet Sauvignon 2013, thus she places a requisition (Probably a Purchase Order actually) for 36 Bottles.
  2. Marcus reviews the new Purchase Order and agrees to this replenishment.
  3. In the same time, he verified that he has currently 48 Bottles on-hand in the central so this replenishment is not a problem.
  4. Marcus creates the corresponding Sales Order based on the data in the requisition.
  5. He selects a Distribution Route that defines that Goods will be transported by truck to Sophia's Store.
  6. Marcus Books the Sales order
  7. William reviews the sales order and prints it.
  8. William create a Picking Order for that sales order.
  9. 36 Bottles are picked from the warehouse and the Picking Order is Processed.
  10. The Delivery truck picks the goods and a good movement is processed that sets the Picked Good to a "In transit" warehouse (or status).
  11. The Delivery Truck arrives at the Store. Francesca Counts the Goods and acknowlegdes the Reception. Goods are counted in her Store. A Goods Receipt (to the Store) and a Goods Shipment (from the In transit Warehouse) are created at the same time.
  12. Sales Order is then marked as Closed.
  13. Franck Creates the Sales Invoice corresponding to the Shipment and Sends it to Francesca. Payments are processed and the Deal is closed.

Replenishment with a Purchase

The Central Warehouse and the Store belongs to the same Company "Happy Wines Shops". (MTR: also here the end-user 'executes' transparantly the REQ or PROP.)

Actors :

  1. Sophia realizes she will soon be out of Bottles of Cabernet Sauvignon 2013, thus she places a requisition for 36 Bottles.
  2. Marcus reviews the new requisition and agrees to this replenishment. Therefore he converts the requisition which results in Distribution Order of type receipt of 36 Bottles for Sophia's Store.
  3. In the same time, he verifies that he has currently 12 Bottles on hand in the central so this replenishment is not directly possible.
  4. A Sourcing Process is started that results in placing a purchase order of 108 Bottles to the Supplier 'La Cave Du Marché".
  5. Marcus completes the matching by selecting the new POS as an indirect Supply. As the order will arrive in the Central Warehouse it is defined as the Departure Warehouse for the Distribution Order.
  6. He selects a Distribution Route that defines that Goods will be transported by truck to Sophia's Store.
  7. That Process created the Distribution Order of type issue. After booking it is a status "Waiting for Goods"
  8. The Purchase Order is delivered to the Central Warehouse.
  9. William reviews the Distribution order of type issue and prints it.
  10. William create a Picking Order for that Distribution Order.
  11. 36 Bottles are picked from the warehouse and the Picking Order is Processed.
  12. The Delivery truck picks the goods and a good movement is processed that sets the Picked Good to a "In transit" warehouse.
  13. The Delivery Truck arrives at the Store. Sophia Counts the Goods and acknowlegdes the Reception against the Distribution Order of type receipt that she received earlier. A Good movement is created and processed that moves the goods from In transit to Sophia's Store's Warehouse.
  14. Distribution Order is then marked as Closed.

Functional requirements based on business processes

Distribution Orders
Id Requirement Importance
1 Have a Table and Window modelizing Material Propositions Out of Scope (push planning)
2.1 Have a new Transaction modelizing Distribution Orders of both types (issue and receipt) Must Have
2.2 Have a new process to convert Requisitions into DOr Nice to Have
2.3 Have a new process to convert Propositions into DOi out of scope (push planning)
3 Have a Process allowing to create a Distribution Order of type receipt from a Distribution Order of type issue and vice-versa. Must Have
4.1 Have a Form 'Plan Distributions' View/Parameter Window allowing the process of creating Orders based on the Propositions or Requisions Must Have
4.2 The Form creates indifferently DOi / DOr / PO or SO based on the legal entities involved in the transaction. Must Have
4.3 The Form View allows to plan Distributions based solely on the vision of available Stocks and incoming receipts. Must Have
4.4 The Form View allows to plan Distributions based on requisitions and propositions on top of Stocks. Nice To have
5 DOi and DOr can be printed out Must Have
6 DOi can be picked and DOr can be received through AWO module. Must have
7 Control by Status that a Distribution can't be executed if the Matching Document is not existing Must have
8.1 Provide a process, allowing the user to execute Goods Movements accordingly to a Distribution Order couple. Must have
8.2 Provide a process, allowing the user to execute Goods Shipments / Receipts automatically based on a PO/SO Couple created in the context of Distributions. Nice To have
8.3 Provide a global vision of currently active Distributions and their status. Allowing to Trigger the next steps. Nice To have
9 Provide a way to configure and execute Distribution Routes with intermediary point Nice To have

Open Discussion Items

Closed Discussion Items

References

Retrieved from "http://wiki.openbravo.com/wiki/Projects:Distribution_Orders/Functional_Specification"

This page has been accessed 1,329 times. This page was last modified on 1 November 2016, at 09:10. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.