Delivery Value Check

This document describes how and when the delivery value check is controlled for customer order deliveries.

Outcome

When this functionality is activated, the expected outcome is a customer order delivery either ready for issue reporting or not. If the delivery value check is successful or if the delivery is manually approved the delivery is ready for issue reporting, but if the delivery value check is not performed or failed, issue reporting will not be available for the delivery.

How the system is affected

Before you start

Delivery value check must first be activated in 'Dispatch policy. Open' (MWS010), using these parameters:

The payer responsible must be specified in 'Customer. Open' (CRS610/F).

Credit limit 2 must be specified per payer in (CRS610/J).

The proper settings for a dispatch process must have been made, including the move to dock step.

Purpose

The functionality of the delivery value check is used to reduce the risk of providing high value deliveries to customers whose payers are not solvent. To achieve this, issue reporting of a delivery (or part of it) is prevented if the delivery value check has failed or not been executed.

When

The delivery value check functionality is activated in (MWS010/I).

Delivery value check point – decides how and when a delivery value check should be triggered.

The delivery value check could be triggered manually after all goods have been moved to a dock location. It can also be triggered either manually or automatically when all goods are moved to a dock location for all active picking lists.

The automatically triggered delivery value check is controlled by using ASJ in (MWS976). Each time a picking list suffix is set to status 60 (on a dock location), a record is controlled by ASJ. If all active picking list suffixes are set to picking status=60, a delivery value check is triggered.

Note: When a picking list suffix is deleted or zero-reported (set to picking status =60), an additional validation is triggered. If the remaining picking list suffixes are set to picking status=60 and the delivery value check has not been performed, the delivery value check is performed.

When validated

The result of a delivery value check is an update of the field issue reporting status.

These are the possible values:

If the functionality of the delivery value check is activated, the field issue reporting status is validated when any goods on a customer order delivery are reported as issued. This means that when a part of a delivery, a full delivery, or even a shipment including a delivery with this functionality activated is issue reported, the issue reporting status is validated. If the issue reporting status is not 00 (not activated), 80 (passed), or 90 (manually approved), issue reporting is not allowed.

The same validations are implemented when reporting issue through APIs.

How

To perform the delivery value check, these parts are required:

A delivery will pass the delivery value check if the following is fulfilled for the payers:

For issue reporting of goods from a delivery that failed a delivery value check, only these alternatives are available:

Application messages

The result of a delivery value check can trigger different application messages:

Limitations

Before activating the functionality of the delivery value check, note these limitations:

Related topics