Basic Delivery Value Check Settings

This document describes how to define the basic settings for a delivery value check.

Delivery value check can be used in different scenarios but is of the highest value in industries with long lead times between order date and delivery date for high value products or in situations where the payers ability to pay a specific delivery is uncertain.

The functionality of the delivery value check is used to prevent issue reporting of deliveries of reference order category 3 (Customer Order) unless the payer is solvent.

Basic delivery value check settings are defined. This enables you to create deliveries with the functionality of the delivery value check activated.

Parameters to set

Program ID/Panel Field The field indicates…
(MWS010/I) 570 Delivery value check point

…how and when the delivery value check is performed.

0-Delivery value check not activated.

1-Only manually triggered delivery value check.

2-Delivery value check is triggered automatically when all goods on all picking lists for a delivery is moved to a dock location for the first time. The delivery value check can also be manually triggered.

(MWS010/I) 580 Delivery value check method

…how the delivery value is calculated.

0-No calculation.

1-Value calculated per line as sales price – line discounts, multiplied with transaction quantity (same logic as on a pro forma invoice). For more information about the net price calculation method, see (CRS701).

(MWS010/J) 540 Delivery Consolidation field 1 … which object to use as an additional field for use in delivery consolidation. In order to use the functionality of the delivery value check, there can only be customer orders with the same payer in one delivery. When activating the delivery value check, it is mandatory to use the OAPYNO object in either of the delivery consolidation fields: 1 or 2.
(MWS010/J) 545 Delivery Consolidation field 2 … see above.
(CRS610/J) Credit Limit 2 …the highest credit limit permitted for outstanding invoices. The credit limit 2 amount is needed to verify that the payer is solvent to allow the specific delivery to be issued. A delivery will always pass the delivery value check if credit limit 2=zero.

Follow these steps

  1. Open 'Dispatch Policy. Open' (MWS010). Go to the I panel.

  2. Set the 'Delivery consolidation field 1' or 'Delivery consolidation field 2' to OAPYNO to ensure that only customer orders with identical payers are connected to the same delivery.

  3. Set the 'Delivery value check point'. Set alternative 1 or 2, which indicates how the delivery value check is triggered (0-'Delivery value check not activated', 1-'Only manually triggered delivery value check', 2-'Delivery value check is triggered automatically when all goods on all picking lists for a delivery is moved to a dock location for the first time'.

  4. Set the 'Delivery value check method'. Set alternative 0 or 1, which indicates how the delivery value is calculated (0-'No calculation', 1-'Value calculated per line as sales price deducts line discounts, multiplied with transaction quantity (same logic as on a pro forma invoice)'). See other settings in CRS701 and CRS729.

  5. Three different application messages can be configured for usage based on the outcome of the delivery value check. These application messages are:

    Application message type 276 – Delivery value check failed.

    Application message type 277 – Delivery value check passed.

    Application message type 278 – Delivery value check manually approved.

    Application messages are sent to the responsible set for the payer in 'Customer. Open' (CRS610).

    See Set Up the M3 Application Message System for more information.

Related topics