As a key object in the goods receipt process, the inbound delivery supports all activities such as packing, putaway, and goods receipt. The inbound delivery stores information on the planning of the delivery, and it also monitors the status and records the data that is accumulated during processing. The creation of the inbound delivery automatically initiates activities such as goods putaway or scheduling, and also the recording of data that is generated during inbound delivery processing.

As a key object in the goods receipt process, the outbound delivery supports all shipping activities such as picking, packing, and goods issue. The outbound delivery stores information on the shipping planning, and it also monitors the status and records the data that is accumulated during shipping processing. The creation of the outbound delivery automatically initiates the shipping activities, such as picking or delivery scheduling, and also data that is generated during shipment processing is recorded.

If the decentralized scenario is used, inventory postings are not directly processed in Inventory Management (IM). Instead, whenever a goods movement is created in Inventory Management (IM), the system generates inbound or outbound deliveries and passes them on to the decentralized WMS.

In the WMS, the goods are put away or picked based on the existing delivery. As a result of the goods movement posting in the WMS delivery, the system sends the completion verification to the ERP system and then uses the delivery to post the actual goods receipt or goods issue in inventory management.

Deliveries with a purchase order or a sales order as a source document are handled in the same way.

A distributed delivery is deleted when the confirmation is executed with quantity 0.