Backorders when a Picking List is Reported from an External System

It can be challenging to define how to manage backorders when a picking list is reported from an external system or partner.

In the API transactions to report a pick line, three parameters are important when managing backorders:

What should happen to a delivery line after it is reported when a shortage has occurred?

The main rule is that the M3 core logic should decide whenever the pick shortage should be backordered or not. Then the 'Flagged as completed' parameter should always be set to zero and a deviation acceptance limit is defined in the program 'Item. Connect Order Line Completion Limit' (MMS425). However, if backorders are not used, the parameter should be set to 1.

To manage partial reporting of a pick line, a good rule is to always set both the allocated and delivered quantity as the picked quantity.

See the example in the following figure to understand the different outcomes of a reporting transaction.

Back order handling at pick reporting - standard scenario

A pick line of ten pieces is downloaded to an external system. If partial reporting of four pieces is done, both the allocated and delivered quantity should be set to four. The result is a partial reported line in status 46 with six pieces left on the picking list.

If the allocated quantity is set to ten and the 'Flagged as completed' parameter is zero, M3 will decide if the pick line should be closed or backordered. If no acceptance limit is set, the line will be backordered.

If the allocated quantity is set to ten and the 'flagged as completed' parameter is one, the pick line will be closed and the status will be 69.
Note: The parameter 'Completion endmark' in 'Settings - Deliveries' (CRS721) may affect whether a backorder is created, or if the line is completed.