SD > Proof of Delivery

[Former Member]

In POD customisation, what is the function of partly automated POD?

Reward points for help

Regards

Siddharth Sridhar

[Former Member]

Hi Siddharth,

This is the path of POD

IMG-> logistics execution->shipping->delivereis->proof of delivery

Hope this is helps you

Prem.

[Former Member]

Hi Siddharth Sridhar,

POD:-

Proof of delivery (POD) is an instrument involved in business processes in which an invoice is issued only after the customer has confirmed the delivery's arrival. In addition to the proof of delivery itself, you can also record the POD date, POD time, the actual quantity that arrived and the reason for possible differences in quantities. This is especially important for deliveries where the delivery quantity varies because of the nature of the goods or for which the exact delivery quantity is unknown from the start. You are now in a position to issue an accurate invoice based on the customer's confirmation of goods received. You no longer need to create credit memos. The reasons for deviation that occur most frequently in "real world" scenarios such as stock shrinkage, theft, certain characteristics of goods (volatility, for example), and transportation damage are recorded and analyzed in the system. This analysis is especially valuable when you are negotiating with forwarding agents, vendors, or customers, since all deviations can be reflected.

Regarding POD,

It is an instrument with which invoices are issued

after customers have confirmed

delivery arrivals.

Advantage

It is possible to issue an accurate invoice based on the customer’s confirmation

of goods received

It is activated at 2 levels:

At Delivery Item Category Level (Configuration)

Alternative way to create/confirm PoD

Use transaction “Worklist Outbound Deliveries for PoD (VLPODL)”

Extended use of “Worklist Outbound Deliveries for PoD (VLPODL)”

Several criteria for selecting Delivery Notes

Possibility to Create and/or Confirm PoD from the worklist

At Customer Master Level

Set at Sales Area level on the Shipping tab.

Only the Ship To partner Master Data is checked when determining

if a Delivery Note is PoD relevant.

All Billable and Deliverable Item Categories will be flagged as PoD relevant.

Logistics -> Sales and Distribution -> Shipping and Transportation

-> Proof of Delivery”

It includes 5 transactions:

Change Single Document (VLPOD)

Display Single Document (VLPODA)

Worklist Outbound Deliveries for PoD (VLPODL)

Worklist Subsequent Processing for PoD (VLPODF)

Automatic PoD Confirmation (VLPODQ)

The PoD Status is on the Status Overview tab of Delivery Notes

blank = Not Relevant

A = Relevant

B = Differences Reported

C = Confirmed

Receiving the PoD with difference

Use transaction “Change Single Document (VLPOD)”

Confirming the PoD

Cancel Confirmation

Once confirmed the Delivery Note can be invoiced

Receiving the PoD without difference

Use transaction “Change Single Document (VLPOD)”

No Confirmation Needed

Once the PoD created the Delivery Note can be invoiced

Automatic PoD Confirmation & PoD Timeframe (VLPODQ)

Several criteria for selecting Delivery Notes

Possibility to confirm Delivery based on PoD Timeframe

! If “Display Selected Documents” is not ticked => All selected

Delivery Notes will be confirmed.

! If “Display Selected Documents” is ticked => Timeframe isn’t

taken into consideration anymore.

Worklist Subsequent Processing for PoD (VLPODF)

Provide a worklist to help the clearing of the Ship Not Bill a/c

Will be handle via a new Pricing Condition Type

Additional Notes

Existing Deliveries

Existing Sales Orders

No Collective PoD Cancellations Possible

-

---

POD – PROOF OF DELIVERY.

When you create a customer master record in XD01, in the sales area data shipping tab you will find this indicator “ Relevant for POD”

When you tick on this the field below this “POD Timeframe becomes active.

Purpose

This is required for deliveries where the delivery quantity varies because of the nature of the goods or for which the exact delivery quantity is unknown from the start. You can then issue an accurate invoice based on the customer's confirmation feedback of the goods received. The reasons for deviation can be stock shrinkage; certain characteristics of goods (volatility, for example), and transportation damage are recorded and analyzed in the system. Some volatile liquid may vaporize and the weight will come down. So exact weight has to be invoiced.

Timeframe for Confirmation of POD

Period in days, in which proof of delivery is expected from the recipient (customer). If there is no confirmation in this time, the delivery is confirmed automatically when this time period is up, without differences.

Process:

When the material is sent to the customer, the customer will confirm that he/she has received ‘X’ quantity of material ordered. Accordingly an accurate invoice is generated as per the quantity received by the customer. The timeframe mentioned in the customer master record is suppose 10 days. The material has already been delivered but if within 10 days or on the 10th day the customer doesn’t confirm any received quantity then it is accepted that the material has been received by the customer at his/her site and an invoice is generated and sent to the customer.

Transaction code VLPODL – Deliveries for proof of delivery.

Here you can select the delivery number, which is relevant for POD and accordingly process it for creating an invoice.

There are various selection criterias for selecting the deliveries relevant for POD.

OUTBOUND DELIVERIES:

Status

Not yet edited

Verified with differences

Verified (confirmed)

Display all

You can use the following transaction codes in relation with POD:

1. VLPOD – change single document

2. VLPODA – display single document

3. VLPODL – work list outbound deliveries for POD

4. VLPODF – work list subsequent processing for POD

5. VLPODQ – automatic POD confirmation

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula