cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

POSC Deconsolidation process Final Bin not determining

Former Member
0 Likes
1,927

When i doing Deconsolidation process POSC.

Till deconsolidation i'm able to confirm WT and process /scwm/dcons to deconsolidate and repack it to other HU. but after closing the pack and when i refresh the screen in /scwm/mon system is placing the package back in decon bin itself.

please help.Refer below screenshot.

Accepted Solutions (0)

Answers (2)

Answers (2)

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

"IB03 -> DECON to Final storage bin ( use rule based) and map proper storage type PACI."

Why would you set up that? You don't enter anything for IB03 in POSC, there is not rule based, and you don't need any PACI.

But I agree to the point: Anray, you need to show your customizing settings, otherwise it is not really possible to help.

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

Former Member
0 Likes

Hello Anray,

Few things to note to make Decon process simple...

    Keep the external steps as follows :
  1. IB01 -> Door to GR area
  2. IB02 -> GR area to DECON
  3. IB03 -> DECON to Final storage bin ( use rule based) and map proper storage type PACI.

I believe in your case the system system config in IB01,IB03,IB02 manner and that why system again pick the source as 901D_GR when it call step as IB02 after DOCON( IB03).can you share the screen shot related to external step mapping?

BR

Nitin

    Former Member
    0 Likes

    HI Nitin,

    Please fine the Screenshots of my setting1.jpg

    Former Member
    0 Likes

    Attachement 2

    2.jpg

    Former Member
    0 Likes

    Attachement 3

    3.jpg