SAP SD SUPORTE: Proof of Delivery (LE-SHP-DL-POD)

General information

What means POD?

After goods issue, the customer can report differences in the delivery quantities.
The POD quantities are the original delivery quantities -/+ reported differences.
The POD quantities are the basis for the billing document instead of the delivery quantities that remain unchanged. POD process always starts after GI.

1.) POD - proof of delivery in outbound case

When the delivery item is relevant for POD?

the delivery item category is relevant for POD (TVLP-PODKZ = ‘X’)

SPRO -> Logistics Execution -> Shipping -> Deliveries -> Proof of Delivery -> Set POD-Relevance Depending on Delivery Item Category

and the ship-to party is relevant for POD (KNVV-PODKZ = ‘X’)

XD02 -> Sales Area Data -> Shipping Tab

or the sales order item is relevant for POD (VBKD-PODKZ = ‘X’)

VA02 -> Item level -> Shipping Tab

and the delivery item category informs us to take POD relevance from the predecessor document sales order (TVLP-PODKZ = ‘V’)

The POD relevance can be debugged in Include FV50XFLP_LIPS_FUELLEN_TVLP during delivery creation.

How to enter POD quantities or differences

POD quantities and/or differences are normally reported by the customer, coming through Idoc (FM IDOC_INPUT_STPPOD, message type STPPOD); evaluation of Idoc data takes place in Include LV50LF20, form delivery_pod_update.
Differences can be entered manually via dialogue transaction VLPOD (VLPODA is the analogous display transaction)
Differences are stored in table TVPOD.

POD relevance of delivery items (LIPS-KZPOD = …)

‘ ‘: not relevant for POD
‘X’: relevant for POD
‘A’: relevant for POD and reported without differences
‘B’: relevant for POD and reported with differences

POD confirmation

Differences reported from customer are not taken over into the billing without final check: this is the POD confirmation step that can be executed just by setting in transaction VLPOD or in mass transaction VLPODQ.

POD status (VBUP-PDSTA) is …

‘ ‘: if LIPS-KZPOD = ‘‘
‘A’: if LIPS-KZPOD = ‘X’
‘B’: if LIPS-KZPOD = ‘A’/’B’
‘C’: if LIPS-KZPOD = ‘A’/’B’ and POD confirmation is done

Deliveries that are relevant for POD: overview

Transaction VLPODL

POD timeframe

You can set a POD timeframe in customer master (XD02) data (KNVV-PODTG), e.g. 2 days. The customer has then to report differences within these two days. Differences that are reported later are not accepted any more.

In transaction VLPODQ (POD confirmation) you have the possibility to take the time frame into account, confirmation takes then place only after the time is over.

POD timeframe is checked in Include LV50LF20, form delivery_pod_update.

Adjust quantities and values …

This must be done manually with MB*/MIGO transactions and has no reference to delivery and POD. You only have the possibility to set indicators that quantity and value adaptation has been done, with mass transaction VLPODF.
Because this is only a manual follow-on-procedure, the stock-in-transit stock cannot be corrected. Therefore POD cannot be used for stock transfer order.

Defining POD reasons in IMG …

for overdelivery with ‘+’
for underdelivery with ‘-‘

Computations of POD quantities …

… take place in FM LE_POD_TVPOD_UPDATE

POD and batch split

POD differences can never be reported to batch main items, only to batch split items.
The batch split differences are cumulated internally to a batch main item related TVPOD entry.

POD and BOM’s

POD difference reporting to main items, but taking over corresponding POD differences for subitems into the billing is impossible in SAP standard.

2.) POD – proof of delivery in inbound case

What means POD for inbound delivery?

During inbound delivery processing, the system may collect differences between the original quantity and the changed quantity as POD difference. All POD differences and quantities can be reported via Idoc to the external vendor, normally during goods receipt.

An inbound delivery item is relevant for POD if

the delivery item category is relevant for POD (TVLP-PODKZ = ‘X’) and the vendor is relevant for POD (LFA1-PODKZB = ‘A’/’B’)

XK02 -> General data -> Control

the confirmation control key in the PO item is relevant for POD (T163L-PODREL = ‘A’/’B’) and the delivery item category tells us to take POD relevance from the predecessor document purchase order (TVLP-PODKZ = ‘V’)

The POD relevance can be debugged in include FV50XFLP_LIPS_FUELLEN_TVLP during inbound delivery creation.

Meaning of LFA1-PODKZB = ‘A’/’B’ and T163L-PODREL = ‘A’/’B’

Both contents are taken over into LIPS-PODREL
LIPS-PODREL = ‘A’ means: always relevant for POD
LIPS-PODREL = ‘B’ means: only relevant for POD with differences

How to enter POD quantities or differences

POD quantities and/or differences are normally entered manually in transaction VL32N within a pop up, or (with automatically found reason code) from WM, reporting quantities with differences.
TVLP-PODAU (not relevant for outbound deliveries!) stands for the level of automation of the inbound POD:

’M’: the reasons have to be entered manually
‘T’: the default reason (see IMG) is suggested automatically in the pop up
‘V’: the POD difference entry is done automatically with the default reason