Select language:
Entering content frame!--a11y-->

Process documentation Proof of Delivery at Goods Receipt for Inbound Deliveries 

Implementation Options

The proof of delivery (POD) process lets you report the quantity that the ship-to party actually received to the vendor during goods receipt for inbound deliveries. You can record the goods-receipt quantity, the verification date and reasons for differences in quantity that may have occurred.

The ship-to party transfers the proof of delivery in IDoc format into the SAP System or into the vendor’s external system. In this way, the quantities are confirmed once for the entire inbound delivery. The current proof of delivery situation is reflected by the POD status:

Rel. w. difference , Rel. w/o difference or Not relevant . You can check the POD status at any time during delivery processing by using the Processing tab in the item view. The system does not make an entry in the document flow.

You can set the POD process in Customizing for automatic, partially automated, or manual creation of the reasons and quantities during goods receipt for inbound deliveries. In most cases, there are no quantity deviations, meaning that the proof of delivery process does not create any additional work for you. In these cases, verification occurs automatically via IDoc. Verification of the proof of delivery occurs via EDI using corresponding IDocs. The proof of delivery allows all partners involved to synchronize the quantities that are posted. SAP recommends that you use partially automated POD creation.

Business partners who both use SAP Systems can now use the system to process PODs (see also

Structure linkProof of Delivery).


Make the following settings for proof of delivery in the Implementation Guide (IMG) under Logistics Execution ® Shipping ® Deliveries ® Proof of Delivery:

  • Define
for each delivery item category whether it is relevant for the POD process. SAP recommends that you flag all item categories that belong to a delivery type as being POD relevant.

If you want to copy the POD relevance from a preceding document such as an MM scheduling agreement for inbound deliveries, select

Copy POD relevance from preceding document (V) for the item category. In this case, as the preceding document is being processed, the system already knows whether verification for an item should occur or is expected.

If you as ship-to party want to record POD data when processing inbound deliveries, in addition to the POD-relevance, you must also define the level of automation the recording process is to include for the item category. You can indicate whether you want the recording process to occur automatically, partially-automatically or manually in the dialog. You can only define this level of automation for inbound deliveries.

  • Define
reasons for deviation.

Define how the quantity is to be calculated (add or subtract the difference quantity, depending on whether you are dealing with an overdelivery or an underdelivery).

If you want to use automatic or partially automated POD data recording for inbound deliveries, you must select one standard reason for overdelivery and underdelivery. Otherwise, the system cannot generate POD data automatically.

Set the POD-relevant indicator on the Control screen for the vendor with whom you would like to carry out POD-processing in the Reference data part of the screen.

As the ship-to party, if you use an SAP System and record POD data in inbound deliveries, you must activate the POD-relevant indicator in the Reference data section of the Control screen for vendor data. This setting controls when you as the ship-to party send a proof of delivery (always, only when deviations occur, or never). You can fine-tune the POD process controls even further by setting up POD-relevance for the confirmation control key in Customizing for

confirmation control.

Process Flow

You can record proofs of delivery in inbound deliveries for which your vendor has sent shipping notifications and send them via IDoc. You have three different options for recording differences and reasons for deviation:

  • Automatic creation

When you change quantities an inbound delivery, the system generates the POD data, including the difference quantity and standard reason, in the background. In this case, it is not possible to change this data or create other data manually.

  • Partially-automated creation

When you change quantities in an inbound delivery, an input screen appears with the POD data that was generated by the system as suggested values. You can user this screen to add other data or change the reasons manually.

  • Manual creation

When you change quantities in an inbound delivery, an input screen appears in which you must enter all POD data manually.



Leaving content frame