Log in / create account
Openbravo.com
Issues
Forge
University
View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Projects/Distribution Orders/User Document AWO

Contents

Introduction

Distribution Orders

In a business environment with one or multiple distribution centers and a number of outlets/shops/local warehouses that all belong to the same legal entity, the replenishment (inter-warehouse replenishment) is to be executed with Distribution Orders (DO). For distribution of goods within a legal entity, a PO-SO (purchase order - sales order) pair can not be used since this implies a change of ownership and subsequent invoicing.

This implies the following characteristics:

It must be mentioned that, being part of the Advanced Supply Chain suite of Openbravo, the expected receipts and expected issues are only considered in the planning/MRP of the Advanced Forecasting and Planning module.

In Openbravo the DOi can be created first and it will automatically create the corresponding DOr. But also the DOr can be created first, this will create the corresponding DOi automatically. So it really does not matter where the distribution is initiated from, and this is done to facilitate both the Pull-model and the Push-model. This creation can be done manually or automatically with the Advance Forecasting and Planning software as mentioned here.

Group of Inventory- and Supply Chain Management functionalities

The Distribution Orders module has been created in order to enhance Openbravo with the ability to plan, organize and execute shipments from- and to sites (shops, warehouses, outlets) that belong to the same legal entity but are in a different physical location / address.

It is an important part of a set of functionalities that all together bring first class inventory management and supply chain capabilities. The complete set is:

Licences

Configuration

There is no specific configuration for Distribution Orders.

Configuration in combination with Advanced Warehouse Operations

Distribution Orders introduces three new Inventory Transaction Types (ITT) to Advanced Warehouse Operations (AWO):

The three new Inventory Transaction Types that come with Distribution Orders.

In-Transit Warehouse

Inventory that is moved with distribution orders will not change ownership and subsequently should always be visible, including after the issue / before the receipt of the corresponding warehouses. For this reason an "In-Transit" warehouse is configured directly under the organization that is the legal entity and thus owner of the issuing/receiving warehouses.

Each bin in the "In-Transit" warehouse represents a truck or vehicle so that in case there are multiple trucks, there is always visibility of which goods are in which truck.


The In-Transit warehouse will hold the goods while they are being distributed. It belongs to the same legal entity as the distributing warehouses.

Routings

The Routings for the ISS-DO and RCT-DO should be defined as "External Routings" because they connect two different warehouses.

Referring to the image above, the Routing for the 'Issue' should have configured the Issue warehouse and the InTransit warehouse, and the routing for 'Receipt should have configured the InTransit and the receipt warehouse.

The use of External Routings allow to connect 2 IRA in different warehouses.

Routing- and Warehouse Algorithm Assignments

With the exception of the below, this functionality is identical to the Routing Assignments of Advanced Warehouse Operations.

There are no Business Partners involved in a Distribution Order as both from- and to- are warehouses within the same legal entity. However, in order to be able to assign different routings for different Business Partners and/or Categories, it is possible to connect a Business Partner to an Organization in the below tab.

Connecting a Business Partner to the Organization
With the previous connection between the Organization and Business Partner, the Routing- and Warehouse Algorithm Assignments take advantage of the conditions for Business Partner and Business Partner Category.

Operation

The mandatory flow for Distribution Orders with Advanced Warehouse Operations is:

  1. Execute the Picking with the button "Pick" in the window Distribution Order Issue, or from the Front-End menu "Pick".
  2. Execute the Issue with the button "Issue" in the window Distribution Order Issue, or from the Front-End menu "Issue".
  3. Execute the Receipt with the button "Receive" in the window Distribution Order Receipt, or from the Front-End menu "Receive".

Create Distribution Order (of type) Issue

The DOi is created in status draft and after pressing "Book" will go to status "Confirmed". Not that the lines can be created in the Logistical Alternate unit of measure.

Creating first the DOi will leave the field Quantity Ordered empty. This to indicate that the initiative was at the Issuing side.

Note: When creating the DOi manually, the corresponding DOr is created automatically.

Create Distribution Order (of type) Receipt

The DOr is created in status draft and after pressing "Book" will go to status "Booked", awaiting that the issuing warehouse confirms the requested product. Note that the lines can be created in the Logistical Alternate unit of measure.

Creating first the DOr.

Note: When creating the DOr manually, the corresponding DOi is created automatically.

Confirm the quantities of the DOi

When the DOr is created manually and booked, the issuing warehouse must confirm the quantities before proceeding to the picking and issuing of the goods.

Confirming the requested quantities.

Pick and Issue the goods with AWO

Picking will create AWO-Tasks according to the PIK-DO configuration in AWO.

Confirming the Picking will automatically generate a task with status "Reserved" for the later Issuing. This is done to protect the stock in the IRA after picking against reservations or direct-issues from that IRA.

After the confirmation of the picking, a task in status Reserved is created to hold this stock for this order.
Issuing will create AWO-Tasks according to the configuration in AWO, in this case to be manually confirmed from the AWO Front-End.

Observe the goods In-Transit

When issued, the goods are visible in the in-transit warehouse 'vehicles' with the inventory status 'InTransit'.

Receive the goods with AWO

The receiving of the DOr has to be done in the receiving warehouse, either from the back-end or from the front-end. This process not only generates the AWO tasks but also updates the quantities in the DOi/r.

The Receipts process will check for confirmed tasks of the Issue-DO inventory transaction type and will receive all quantities that are found in these tasks, while matching the attributes if any. Tasks for all previous issues, regardless if the material was issued to different in-transit bins/trucks/vehicles, will be created. So in the case that material was issued to more than 1 bin/truck/vehicle, tasks will be generated showing the multiple from-bins and the operator should confirm with qty 0 those tasks that refer to a from-bin/truck/vehicle that was not received and cancel the corresponding delta. This is coherent with how the Reciept for Purchase Order works: Tasks are generated for all open quantities, regardless if the supplier delivered the product. As consequence, we strongly advice:

  1. Configure the Confirmed Quantity as not-defaulted.
  2. Configure the Routing as Manually Confirmed.


The Receipt Distribution Order will check for confirmed tasks of the corresponding Issue Distribution Order to ensure that the proper attribute values are received.

Receiving the goods will create AWO-Tasks according to the configuration in AWO.

References

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

This page has been accessed 4,118 times. This page was last modified on 5 March 2021, at 13:30. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.