SAP SD 交貨單明明已經做了PGI,為什麼還有Open Qty?

dicksonjyl560101發表於2019-06-17


SAP SD 交貨單明明已經做了PGI,為什麼還有Open Qty?


交貨單80024244,看其document flow, PGI 業務已經完成了,如下圖示:

SAP SD 交貨單明明已經做了PGI,為什麼還有Open Qty?

而其ITEM裡的open qty還是不為0,如下圖示,

SAP SD 交貨單明明已經做了PGI,為什麼還有Open Qty?

原因何在?


經諮詢專案上的SD顧問,由於專案裡對於交貨單有啟用POD功能,只有等POD完成後,才算物權的最終轉移給客戶方。該DN尚未完成POD事務,所以其Open Qty就不為0了。



SAP POD 功能是怎麼回事呢?這裡瞭解一下。


在某些行業,銷售發貨給客戶,運輸中途可能有損耗,就會發貨數量與客戶收穫數量不等的結果,例如液體或散裝物等等。在這種場景裡,最後開票的數量要根據客戶確認數量而不是發貨數量來定,而交貨成本還是根據交貨數量來算。


標準SAP系統裡,必須先完成POD事務(VLPOD)再Billing(VF01/VF04)。


SAP SD 交貨單明明已經做了PGI,為什麼還有Open Qty?

另外:POD不能做差異的沖銷,這個與沖銷PGI是不一樣的。沖銷PGI後是會形成庫存成品,而POD則是用於按客戶確認數開票,即庫存我們還是出的是Delivery的quantity,但做了POD後,invoice就會按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 in which 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. It is no longer necessary to create credit memos after the fact. The reasons for deviation that occur most often 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.

Prerequisites

You should make the following settings in the Implementation Guide under Logistics Execution --> Shipping --> Deliveries --> Proof of delivery:

Define for each delivery item category whether it is relevant for the POD process.

In this activity, you can set the proof of delivery (POD) relevance depending on the delivery item category.

We recommend that you flag all item categories that belong to a delivery type as POD-relevant. After setting the POD-relevant indicator in the customer master, you can activate the proof of delivery process.

When the system creates billing documents for the item categories that are marked as POD-relevant, it copies the verified quantity rather than the delivery quantity.

SAP recommends that you flag all item categories that belong to a delivery type as being POD relevant

Manually Confirming Proof of Delivery (POD)

1) Create delivery using VL10 or VL01N.

2) After performing picking and Packing activity save the delivery

3) Now execute VLPOD in order to execute the POD

For other Transaction Codes

Logistics -->Logistics Execution -->Outbound Process -->Proof of Delivery -->............

Also for further details you can search in the following path




2019-06-16 寫於蘇州市。


來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29829936/viewspace-2647857/,如需轉載,請註明出處,否則將追究法律責任。

相關文章