Oracle Shipping Execution Multi-leg Consolidated Deliveries

An Oracle Distribution Topical Essay March 2001.

Multi-Leg Consolidated Shipments

- TABLE OF CONTENTS

1. 2. 3. 4. 5. 6.

OVERVIEW ...................................................................................................................................................... 3 DEFINITIONS................................................................................................................................................... 4 BUSINESS SCENARIO.................................................................................................................................... 5 CREATING TRIPS........................................................................................................................................... 6 CREATING LOCATIONS AND STOPS........................................................................................................ 8 EXECUTING THE SHIPMENTS. ................................................................................................................ 12 6.1. PICK RELEASING THE TRIP............................................................................................................................. 12 6.2. SHIP CONFIRMING THE TRIP .......................................................................................................................... 14 6.3. CHANGING STOP STATUS ............................................................................................................................... 15

Multi-Leg Consolidated Shipments

1.

Overview

This topical essay presents a solution in support of a process where items on a customer order are sourced from different geographical locations. The shipments containing the items are to be merged or consolidated at an intermediate location with the final delivery being made to the customers ultimate ship to destination. Release 11i data model supports the ability for a user to create a multileg shipment and to manage the activities at each stop along the shipments journey. The graphic below depicts the concept outlined in this topical essay .

Oracle Inventory Organization

Non Oracle Distribution Center

Customer Ultimate Destination.

Oracle Inventory Organization

Diagram 1 Consolidated Multi-Leg shipments

Multi-Leg Consolidated Shipments

2.

Definitions
The collection of packages to be either dropped-off in a set or to share transportation costs. Consolidations may include shipments for an individual Ship to location or for multiple different customers within the same vicinity.

Consolidation

ship confirmation

To enter shipped quantity and inventory controls for specific shippable lines. You can ship confirm the same delivery/trip repeatedly until you close the delivery/trip. Once it is closed, no more changes can be made into a delivery/trip.

ship-to location

The delivery point for consolidated shipments, gathered from multiple locations, that will be shipped to an intermediate and/or ultimate shipto location.

Delivery

A set of order lines to be shipped to a customers ship-to location on a given date in a given vehicle. Multiple deliveries can be grouped into a single trip. A single delivery may include items from different sales orders and may include backorders as well as regular orders.

Ship Confirm

A process in Shipping Execution which allows you to identify shipped quantities, assign inventory control information for released lines, assign freight charges, and specify whether or not to backorder unfulfilled quantities of released line items.

Trip planning

The process of planning the necessary vehicles and grouping the scheduled shipments that will be included in a given trip. Planning the trip requires consideration of vehicle load capacities, container capacities and, in certain cases, the loading order for the customers specified unload order.

Trip

An instance of a specific Freight Carrier departing from a particular location containing deliveries. The carrier may make other stops on its way from the starting point to its final destination. These stops may be for picking up or dropping off deliveries.

Multi-Leg Consolidated Shipments

Stop

A location at which the trip is due for a pick-up or drop-off.

Shipment

An individual package sent to a customer. Thus, a shipment might contain an entire order, if all items in that order are pick released and packed together. A shipment might contain just part of an order that is pick released and packed. A shipment might also contain only part of a released order line, where some of the items on the picking slip are not in stock. The final destination of a shipment.

ultimate ship-to location

3.

Business Scenario

A sales order is placed for two items: a desktop CPU and a monitor. The order lines are booked and scheduled in Order Management. The inventory for the desktop CPU resides in the M1 inventory organization and the Monitor resides in V1 inventory organization. The objective is to create a plan that enables the shipments of the individual items to be made from their respective inventory organizations, merge or consolidate at an intermediate distribution center location, and deliver to the customers ultimate ship to location as a single shipment.. (Refer to figure and description below)

Multi-Leg Consolidated Shipments

Warehouse 1

M1 Seattle, WA.

Trip 1

Distribution Center
Delivery 5641 Trip 3 Deliveries 5456 5641

Customer

Warehouse 2
Delivery 5456 Trip 2

Troy, MI.

Chattanooga, TN.

V1 New York, NY.

Diagram 2 Consolidated Deliveries business scenario

4.

Creating Trips

Once the order is booked, the order lines are imported into Shipping Execution where the Transportation Planner has visibility to the lines. At this point, the planner creates Trip 1 (consisting of Carrier and vehicle information) for the desktop CPU located in Warehouse 1 in Seattle, WA. The key element depicting the Trip is the ship method. The creation of the Trip can be done in a variety of ways depending on your business process. 1) Autocreate Trip When a Trip is created using the Autocreate Trip functionality, 2 stops are created. The first stop
Creates trips Creates pick up and Drop off stops, Autocreates deliveries. Assignes Deliveries to Trip

Shipping Transaction Form

Query Manager Enter criteria for lines to ship

Multiselect Lines

Click on Action, Select Autocteate Trips, Click on GO

Multi-Leg Consolidated Shipments

consists of the location where the shipment is picked up, (Ship From) and the second stop is the location where the shipment is dropped off (Ship To). In the business scenario were describing, an intermediate stop needs to be defined and assigned to the Trip 1.

2) Create Trip Manually

Shipping Transaction Form
Query Tree Click on Data Entry to expand Tree

Trip (New) Form

Double Click on Trip Data Entry Enter Name Ship Method Vehicle Info

Click on Done

Trip Form One of the two processes described above would need to be performed in order to create Trip 2 for the Monitor originating from Warehouse V1 located in New York, and an ultimate destination of Chattanooga, TN. In the case of a manually created Trip, deliveries could either be auto created or manually created and subsequently assigned to the Trip.

Multi-Leg Consolidated Shipments

5.

Creating Locations and Stops

Creating Locations In order to perform the merge or consolidation of the shipments originating from warehouse M1 and M2, a stop must be defined to represent the Distribution Center in Troy Michigan. In this scenario, this is a non-Oracle location. A stop is a location within your network where a shipment can be picked up or dropped off. The location of the Distribution Center also must be set up in inventory in order to be used when defining a stop. Navigation to Location definition is as follows. Inventory>Set up>Organizations>Locations>

Location Definition Form Enter a name description and inactive date if applicable. When you click in the Address field, another window will pop to allow the user to enter detail address information for the location. Once the location is defined, the Distribution Center can be define as a stop and ultimately assigned as intermediate stops to Trip 1 and Trip 2 Creating Stops Now that the Location for the Distribution Center is defined, it can be used when defining the intermediate stop for Trips 1 and 2.

Multi-Leg Consolidated Shipments

To create and assign Trip 1 with the intermediate Stop I.E. Distribution Center Location, the following process can be followed.
Shipping Transaction Form
Query Tree Click on Data Entry to expand Tree

Stop- (New) Form

Double Click on Stop Data Entry Select Loc from LOV Select Trip from LOV Enter Planned Arrival & Departure Dates

Click on Done

Stop definition form The same process should be followed for Trip 2. At this point of the consolidation solution, a delivery has been created for the material being sourced from Warehouse M1 and the delivery has been assigned to Trip 1. A delivery has also been created for the material being sourced from Warehouse V1 and the delivery has been assigned to

Multi-Leg Consolidated Shipments

Trip 2. The intermediate stop I.E. Distribution Center Troy Michigan has also been defined and assigned to Trip 1 and Trip 2.

A Stop consisting of the Location of the distribution center has been assigned to Trip 1 and Trip 2. The data at this point is represented in the following table. Trip Trip 1 Trip 2 Pick up M1 Seattle WA V1 New York NY Dropoff Troy DC Troy DC

The screen below represents similar data to Trip 2 described in our business scenario. The Trip is awaiting pick up at M1 warehouse.

The solution at this point is represented by a Trip 1 originating at warehouse M1 and dropping off at the Troy distribution center and Trip 2 originating from warehouse V1 and dropping off at the Troy distribution center stop. The final step is to create a Trip 3 that originates at the Troy Distribution center, assign the deliveries that are on Trip 1 and 2 to Trip 3 and have the final drop off be the customers ultimate ship to destination.

10

Multi-Leg Consolidated Shipments

Create Trip 3
Shipping Transaction Form
Query Tree Click on Data Entry to expand Tree Double Click on Trip Data Entry

Trip (New) Form

Enter Name Ship Method Vehicle Info

Click on Done

Assign Deliveries from Trip 1 and Trip 2 to Trip 3

Shipping Transaction Form
Query Manager Query Deliveries from Trip 1 & 2 Click on Action then select assign to Trip. Select Trip 3, check new location, PU Location=DC Do Location= Cust

The following screen shot depicts what the delivery from warehouse V1 would look like in the planned consolidation. At this point the entire process is just a plan. The execution steps are described in the next section.

11

Multi-Leg Consolidated Shipments

6.

Executing the Shipments.

6.1. Pick Releasing the Trip

Since the shipments are originating from two separate locations, it is assumed that the execution processes would be performed independently. However it is possible for the processes to orchestrated synchronously by a single user. What has been done up to this point is just a plan. The plan cannot take effect until actual inventory is allocated to the deliveries and Trips. At the highest level this can be accomplished by Pick releasing the Trip. The individual delivery can be pick released as well.
Shipping Transaction form
Click on Action, Select Launch Pick Release then click Go

Query Manager Query Trip 1

The same process is performed at warehouse V1 for Trip 2

12

Multi-Leg Consolidated Shipments

Pick Slips will print at each of the warehouses indicating the items to be picked for their respective Trips. There are many options as part of the Shipping Execution set up steps to allow each organization to set up how picking is done. For example, Pick Slip Grouping Rules can be used to determine how released lines are grouped on to Pick Slips. (See Implementation Manual Setup Steps). Once the Trips from each warehouse are released, a bill of lading and Packing List can be generated for each delivery in the Trip. The Bill of Lading can be generated at Ship Confirmation as part of the Ship Confirm Doc Set or it can be generated before Ship Confirm using the following process.
Shipping Transaction form
Query Manager Query Delivery Click on Details Button Click on Delivery Legs Tab Click on Generate BOL

Note: Document Categories and Document Sequences must be Set up before Bills of Lading or Packing Slips can ge generated, (See Implementation Manual) The Bill of Lading for Trip 1 and Trip 2 will indicate the Ship From Address as the M1 and V1 locations and the Ship To Address of the Distribution Center. The actual intermediate ship to field has limited functionality in release 11i. In order to take full advantage of it, the order line must already contain the intermediate ship to information before being imported into shipping execution. I.E. If the Shipment from Warehouse M1 had the intermediate ship to information on the line prior to its being imported into shipping execution, and there wasnt an intermediate stop assigned to the M1 trip, the bill of lading would print with three addresses. 1) The Ship from Address of warehouse M1, The intermediate address indicated on the shipment line, and the ultimate ship to of Chattanooga TN. In the scenario were defining, if intermediate ship to was used, the bill of lading for Trip 1 would print with the Ship from address of warehouse M1, an intermediate address of the Troy DC and the final ship to of the Troy DC. For Trip 1 the ultimate destination for Trip 1 is the Troy DC. A packing list can be generated prior to ship confirmation similar to the Bill of lading. The following process can be used to generate the Packing List.

13

Multi-Leg Consolidated Shipments

Shipping Transaction form
Query Manager Query Delivery Click on Details Button Click on Packing List Tab Click on Generate Packing List

6.2.

Ship Confirming the Trip The next step in the consolidation process is to Ship Confirm Trip 1 and Trip 2. This must be done at inventory organization M1 and V1 in order to recognize revenue, decrement inventories, update Order Management and initiate the receivables interface to generate invoices. The following screen depicts how the Trip originating in the V1 warehouse would look prior to Ship Confirmation and closing the stop at V1. In this example the Trip is named Guys Trip

Query Manager Query Trip 1

Click on Action, Select Ship Confirm click Go

Ship Confirm Dialog Box Select close Stop

Closing the stop sets the trip to an Intransit status.

14

Multi-Leg Consolidated Shipments

6.3.

Changing Stop Status At this point in the process it is assumed that the delivery from the M1 warehouse and the delivery from the V1 warehouse are on the carriers truck and intransit to the Troy Distribution Center. In order to perform the next step in the process, a communication mechanism must be in place that lets the Oracle user know that the shipment has reached the Troy Distribution Center. When the user is notified that the shipment has reached the Distribution Center, The following process can be used to update the stop

Query Manager Query Stop Distribution Center

Click on Action, Select Update Status click Go

Select Arrive then OK

The Same process should be performed for Trip 2 once it reaches the Troy Distribution Center. The Arrive step indicates the Drop off of the Trip. The deliveries from M1 Warehouse and V1 warehouse are now at The Troy Distribution Center. Since the deliveries were assigned to Trip 3 in the planning process, All that has to be done is print the new Bill of lading for the final leg from the Troy DC to Chattanooga TN. To Generate a Bill of Lading to The Final Destination the following process can be used.

Query Manager Query Trip 3

Click on Contents By Delivery

Click on Click on Detail Tab

Click on Legs Tab

Click on Generate BOL

Once the Bill of Lading from the Troy Distribution Center to The Final Drop off in Chattanooga is printed, the Troy Distribution Center Stop can be closed . Updating the status of the stop closes the stop. Use the following process to close the stop.

15

Multi-Leg Consolidated Shipments

Query Manager Query Trip 3

Click on Stops

Select Stop Troy Distribution Center

Click on Action, then select Update Status then Go

Select close.

16

Multi-Leg Consolidated Shipments

Multi-Leg Consolidated Deliveries March 2001 Author: Michael Cummings Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 Web: www.oracle.com This document is provided for informational purposes only and the information herein is subject to change without notice. Please report any errors herein to Oracle Corporation. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document. Oracle is a registered trademark, and Oracle Shipping Execution is a trademark(s) or registered trademark(s) of Oracle corporation. All other names may be trademarks of their respective owners. Copyright Oracle Corporation 2000 All Rights Reserved

17