Incompleteness in the Delivery (SAP Library - Goods Receipt Process for Inbound Deliveries)

Incompleteness in the Delivery

Use

When you are creating and processing deliveries, it is often necessary to check the completeness of the delivery. A delivery is considered to be incomplete if fields relevant for the delivery have not been filled, or if certain settings defined in Customizing have not been taken into account. The delivery incompletion log ensures that this completion check is executed automatically.

In the delivery, you can check the following levels for completeness:

Header data of the delivery
Item data of the delivery
Partner data
Texts

You can either display a list of all incomplete deliveries or go directly from delivery processing to the incompletion log. See also Processing Incompletion Log

Integration

The incompletion log controls whether the next subsequent functions are allowed in the case of an incomplete delivery:

Inbound delivery	Outbound delivery
Putaway	Picking
Packing	Packing
Goods receipt	Goods issue
	Billing document

Also, it is possible to set the system so that incomplete deliveries cannot be saved to the database. If, in such a case, the delivery is created in a collective processing run, the reasons for the incompleteness are printed in the collective processing log and the delivery is not created by the system.

Example

For example, you can detect the following situations through the incompletion log:

Batches for an item were not assigned completely

Too many items were picked or put away

Required description texts are missing