Partilhar via


Cross docking from production orders to transfer orders

A new feature for cross-docking from a production or batch order to a transfer order has been released together with KB 3207958.

Input about this feature has come from manufacturers that produce in high volume – for example, food manufacturers. These manufacturers are constantly shipping their finished goods from the bay doors of the manufacturing site to distribution centers. This flow is reflected in the layout of the production floor, where the palletizers at the end of the production lines are located close to the bay doors. The transportation plan is based on the production plan. Therefore, in most cases, when a product is reported as finished, a transfer order is waiting, so that the finished good can be shipped to a distribution center right away.

This scenario starts at the end of the production line, where goods are reported as finished. When goods are reported as finished, work of the Finished goods put away type is usually created to guide the warehouse worker to pick the goods from the production output location and put to a location that is determined by the location directive for Finished goods put away. This feature enables a process where, during the process of reporting goods as finished, the system looks for an opportunity to cross-dock the goods to the bay door locations where there is transfer order demand. From a system perspective, the cross-docking opportunity is a transfer order that is released to the warehouse. This transfer order represents the transportation between the manufacturing plant and a distribution center. If a released transfer order exists, the system generates work of the Transfer issue type instead of the Finished goods put away type. This work suggests that the warehouse worker pick from the production output location and put to a location that is determined by the Transfer issue location directive for the Put work order type. The following illustration shows this process.

scenario

In the preceding illustration, the truck driver picks up the pallet at the end of the production line. If a released transfer order exists, the system directs the forklift driver to the bay door location. If there is no demand at the bay door, the system directs the truck driver to a location in the warehouse.

How to configure cross docking

You configure the cross-docking process in work policies. A work policy includes a work order type, a location, and a product. In the following example, cross-docking is configured for product X and location Y.

Work order types

  • Work order type: Finished goods put way
  • Work creation method: Cross docking
  • Cross docking policy name: Transfer orders

Inventory locations

  • Warehouse: 51
  • Location: Y

Products

  • Item number: X

Currently, cross-docking can be configured for only two work order types:

  • Finished goods put away
  • Co-product and by-product put away

In the cross-docking policy, you define which document types are applicable for cross-docking. Currently, the only document type that is supported is Transfer orders . The following example shows the configuration of a cross-docking policy.

Cross docking policy name: Transfer order

  • Sequence number: 10
  • Work order type: Transfer issue
  • Cross docking demand requires location: False
  • Cross docking strategy: Date and time

The sequence number indicates the priority of the document type. Currently, Transfer issue is the only type that is supported. Therefore, the sequence number will become relevant only when more work order types are supported.

The cross-docking policy also sets the policy for the prioritization of transfer order demand. For example, if multiple transfer orders exist for the same product, the scheduled date and time that are set on the load and associated with the transfer order determine the prioritization between the orders. The scheduled date and time can be set directly on the load, or they can be set on an appointment schedule that is associated with the load. The prioritization is determined by the cross-docking strategy. Currently, there is only one strategy: Date and time.

In the cross-docking policy, you can set up a criterion to require that transfer orders have an assigned location in order to be eligible for cross-docking. This criterion is set in the Cross docking demand requires location field. In this case, the location on the appointment schedule that is associated with the load is used as the final location for the goods that are being cross-docked. If the Cross docking demand requires location field isn’t set, the transfer order can be eligible for cross-docking even if a location isn’t set on the appointment schedule. In this case, the final location for the goods that are being cross-docked is determined by the location directive for Transfer issue for the Put work order type. You might find it useful to set the Cross docking demand requires location field in a scenario where the finished goods should be cross-docked only if a trailer is assigned to a bay door. In this scenario, the goods are moved directly from the production line into the trailer. When a trailer is assigned to the bay door, a user will assign the location to the appointment schedule and will therefore make the location applicable for cross-docking.

The following sections walk you through two examples.

Scenario 1 – Cross-docking to bay door locations

Finished good L0101 is reported as finished to production output location PRODRECV in warehouse 51. Transfer orders for L0101 are set up to manage transportation between location BAYDOOR in warehouse 51 and a receipt location in warehouse 61. If a released transfer order for L0101 exists, the product should be cross-docked to the BAYDOOR location when the product is reported as finished.

Scenario 2- Cross-docking to a bay door location assigned a trailer

Finished good L0101 is reported as finished to production output location PRODRECV in warehouse 51. Transfer orders for L0101 are set up to manage transportation between location BAYDOOR in warehouse 51 and a receipt location in warehouse 61. If a released transfer order exists for L0101, the product should be cross-docked to the BAYDOOR location when the product is reported as finished.

Scenario 1 – Cross docking to bay door locations

Use company USMF.

2. Enable a new number sequence for cross-docking

Go to the Number sequences page, and select the Generate button. A wizard will guide you through the process.

wizzard

2. Create a Cross docking policy

Go to the Cross docking policy page, and create a new policy that is named Cross docking to transfer order.

crossdockpolicy

Note that the only work order type that you can select is Transfer issue, and the only cross-docking strategy that is available is Date and time.

3. Create a Work policy

Go to the Work policies page, and create a new work policy that is named Cross Dock L0101.

workpolicy

4. Set up loads so that they are created automatically for transfer orders.

In the warehouse parameters, set up loads so that they are created automatically when transfer orders are created. A load is a prerequisite for making the transfer order eligible for cross-docking.

warehouse-parameter-auto-load

5. Set up the item load mapping.

Go to the Item load mapping page, and set up a standard load template for the CarAudio item group. This mapping will automatically insert the load template on the load when the transfer order is created.

itemloadmapping

6. Create a transfer order

Create a Transfer order for item number L0101

transferorder2

7. Release the transfer order from the Load planning workbench

On the Ship tab, select the menu item for the Load planning workbench.

releaseload1

Release the transfer order from the load by selecting Release to warehouse on the Release menu on the load line.

releasemenu1 releaseinfo1

An open wave line of type Transfer issue now exists for the transfer order.

8. Create a production order

Go to the production order list page, and create a production order for product L0101.

prodorder2

Estimate and start the production order by using the settings in the following screenshot. Note that the Post picking list now field remains set to No.

start1

9. Report as finished from the mobile device

Go to the mobile device portal and select menu item: Report as finished and put away. Now report as finished L0101 from the hand held device.

raf_flow1

Note that the put location is BAYDOOR. This location is found from the Transfer issue location directive for the Put work order type.

locdirective

Also notice that work of type Transfer issue has been created and completed. Go to the transfer order Work details to verify the work.

workdetails

Now try to start 20 pieces more on the production order

start2

Now try to report 20 ea as finished by using the handheld device.

raf_flow2

This time, location LP-001 is suggested as the put location. This location is found from the location directive for Finished goods put away. This location directive is being used, because no opportunity for cross-docking exists. The transfer order for LP-001 was completely fulfilled by the first cross-docking activity.

Work of type Finished goods put away was created and processed

rafwork

Scenario 2- Cross-docking to a bay door location assigned a trailer

Use company USMF.

1. Change Cross-docking policy

Change the cross-docking policy that you created in scenario 1 by selecting the Cross docking demand requires location check box.

crossdockpolicy2

2. Create a new transfer order

Create a transfer order, and go to the Load planning workbench. transferorder3

Open the Load planning workbench.

loadplanworkbench2

3. Create an Appointment schedule.

From the Load planning workbench, go to the Loads section, and select Appointment schedule on the Transportation menu.

Create a new appointment schedule. Note that the appointment schedule has a reference to the transfer order in the Order number field. In the Planned start date/time at location field, you can set the date and time for the appointment. This date and time will be used when cross-docking demand is prioritized during the cross-docking process. The date and time that you set in this field will update the Scheduled load shipping date and time field on the corresponding load. The location on the Shipping details FastTab determines the location that the transfer order is shipped on.

appointmentschedule

Back on the Load planning workbench release to the warehouse

releaseload2

4. Create a production order

Create a production order for item number L0101, and set it in status Started, as you did in scenario 1.

createprod2

5. Report as finished from the mobile device

Go to the mobile device portal, and select the Report as finished and put away menu item. Now report item L0101 as finished from the handheld device.

raf_flow3

Note that the put location is now BAYDOOR 2. This location is found from the appointment schedule instead of the Transfer receipt location directive.

Flow diagram

The flow is explained in below flow chart diagram:

flow-diagram

Additional information

  • The cross docking scenario is supported for batch and serial controlled items, both with the batch and serial number dimensions defined above and below location, in the reservation hierarchy.
  • The quantity that is being reported as finished cannot be split to a transfer order demand that is lower. If, for example, 20 pieces is being reported as finished and a transfer order exist for 5 pieces, then the transfer order will not be found applicable for cross docking.

Comments

  • Anonymous
    March 16, 2017
    Thx Frank - cool Feature and very well explained ;-)
    • Anonymous
      March 16, 2017
      Sorry - not Frank - Johan :-)