Delivery Stop Based on Freight Cost Control

Freight cost control checkpoint

The purpose of the parameter 'Checkpoint for freight cost control' in (MWS010) is to set at which step in the dispatch flow the freight cost control should be activated. There are 4 alternatives:

0 = No control.
1 = Yes, control will be performed from release for allocation.
2 = Yes, control will be performed from release for picking.
3 = Yes, control will be performed at issue.

The checkpoint set is the first time in the flow when freight cost controls will be performed.

Selecting alternative 1 will activate control at release for allocation, at release for picking and at issue.
Selecting alternative 2 will activate control at release for picking and at issue.
Selecting alternative 3 will activate control only at issue.

The reason for this is that the freight cost setup could have changed between the steps and this would avoid incorrect invoices to customers and incorrect payments to forwarding agents.

Freight cost control

The purpose of the parameter 'Freight cost control' in 'Delivery Term. Open' (CRS065) is to set what to control regarding the freight cost. The alternatives are:

0 = No control
1 = Charges
2 = PO amount
3 = Charges and PO amount

The controls that will be performed is not only charge- and PO amount-specific. Controls will also be performed on any setup that is crucial to freight charge and freight PO processing.

Delivery stop based on freight cost

If a delivery is stopped, an application message with type 261 will be triggered.

In order to get beyond a delivery stop due to limited freight cost setup, the setup must be corrected.
Use related option '30-Trigger Delivery Stop Check' in (MWS410) to perform a freight cost control again. Related option 30 is only valid if there is a stop code on the delivery. If you use this option when no stop code exists, an error message will be displayed saying 'Option 30 is only valid for deliveries with stop code'.

Freight cost control functionality is available for both customer orders and distribution orders.

For customer orders a delivery can be stopped due to all delivery stop codes.

For distribution orders a delivery can only be stopped due to delivery stop codes B01-B06, B08, and B20-B21, because charges do not exist on DOs.

Delivery stop based on freight cost on shipment level

When a delivery on a shipment gets stopped due to inadequate freight cost setup, it will behave as if it was not connected to a shipment.

In order to get beyond delivery stops due to inadequate freight cost setup on a shipment, the user must correct the setup.
Use related option '30-Trigger Delivery Stop Check' in (DRS100) to perform a freight cost control again. Using the option in DRS100 will trigger freight cost stop check for all deliveries connected to a shipment.

Freight cost control at manual allocation

If the parameter 'Checkpoint for freight cost control' on the dispatch policy is set to 1='Yes, control will be performed from release for allocation', manual allocation will perform the same controls as automatic allocation. If allocation is not permitted, an error message will be displayed when the program is opened, saying that allocation is not permitted due to inadequate freight cost setup and that no allocation can be performed.

Limitations

The full functionality of freight cost control exists for auto level 3 on the dispatch policy. For auto level 5, this functionality is not allowed since picking lists do not exist for this auto level and that would be a way to avoid freight cost control at release for picking. Also, for auto level 5, issue of delivery is performed when order entry is completed, which would mean that the user would never have a chance to confirm the freight cost, which must be performed to enable a control of the PO amount.
For auto level 4 on the dispatch policy, the alternative 3-'Yes, control will be performed at issue' cannot be used for checkpoint for freight cost control. The reason for this is that issue is performed automatically when a picking list is created.
Automatic release for allocation cannot be used in connection with the alternative 1-'Yes, control will be performed from release for allocation' for checkpoint for freight cost control.