on 2018 Jun 22 10:17 AM
Hi All,
perhaps there is someone, who could help me to understand the STO process and especially difference handling between GI and GR. (SAP note 2190855)
My case is, I have in the sending plant one HU left with 20 PCE of product 4711, which i would like to move to another location. (both warehouses are EWM managed)
After GI posting in sending plant a respective ID will be created and replicated to the receiving plant.
During receiving and counting we have an overdelivery of 10 PCE. Using exception code "DIFE" (shipper fault) we increase the quantity to 30. The quantity will be transfered to ERP and difference of 10 PCE will be posted on "POD" storage location (-10 PCE).
After closing the inbound delivery in receiving plant, in ERP a correction outbound from the previous replenishment delivery should be created via RPOD output type and replicated to EWM. It will run in my case on failure because of deficit of 10 PCE in the sending plant.
Is it a GAP in the process or in my thinking?.
One remark: the overage of 10 PCE was not detected during GR process in the past.
Thank you for your inputs∝osals
Best regards
Bartosz
Request clarification before answering.
Hello Bartosz,
The correction delivery process combines the delivery processing (inbound/ outbound, depending on the kind of difference) with the physical inventory. The integration works via the difference 'bin'. The basic idea is that the differnce in the quantity detected in the receiving warehouse is somewhere available as a ohysical inventory in the sending warehouse.
In your sending warehouse there was a physical stock that was 10 more than the book stock. As your LE delivery (or inventory management, where ever the 'deficit in...' message comes from) does not allow negative stock, you will first have to do a physical inventory to increase the stock on the storage location. This stock will be removed by the correction outbound delivery.
Regards,
Katrin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Katrin,
thank you for your reply. It was also my feeling.
So, what I did: After I got the error message during the RPOD determination in ERP, I increased the stock in the sending warehouse by inventory posting. Then repeated the RPOD and created the correction delivery, which I also processed in the sending warehouse.
What is strange, the goods issue was posted but the stock stayed unchanged. (no error logs or unprocessed PPF actions). As result, I have more stock in receiving&sending warehouse.
During PCO GI posting 1 PCE was posted GI and during posting DIFF-ANALYZER posting 1 PCE was posted GR
Best regards
Bartosz
"It will run in my case on failure because of deficit of 10 PCE in the sending plant."
So the situation was that the physical stock was not equal to the book stock even before anything was done, isn't it?
The sending plant never had 30, they had only 20 and shipped them. And with your receiving of 30 you are actually trying to remove another 10 from the shipping plant. But since their stock is now zero you get the deficit message, right?
So you would need a physical inventory to find the 10 before you can process the reduction.
What do you actually want to say with "One remark: the overage of 10 PCE was not detected during GR process in the past." ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jürgen,
correct, the physical stock was greater than the book stock. Was a counting mistake during GR process for this particular HU in the sending plant in the past.
Yes, I can increase the stock in the sending plant by 10 PCE and repeat the output in ERP in order to create the correction delivery. But for some reason after posting it in sending plant the quantity will be moved to difference analyzer and after posting it nothing will happen.
The stock of 10 PCE will remain in sending plant unchanged.
| User | Count |
|---|---|
| 13 | |
| 7 | |
| 5 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.