Put Away WT not created in Embedded EWM S4 1809

[former_member788724]

Hello Experts

I am doing UD in QA32 transaction for EWM originated lot. I am not going inside 'EWM Inspection' button on QA32 screen.

After UD is accepted on first screen of QA32, Stock is posted to unrestricted stock, but put away WT is not getting created. However, when UD is rejected then all work fine.

I checked in S4 2020, it is working prefect. After UD is accepted on first screen of QA32, system posts material document as well as creates put away WT.

Any thing special to S4 1809?

follow up action EWM_A

However, If I go to 'EWM Inspection' and trigger follow up action from there, then put away WT gets created.

[former_member788724]

d.mz

May be you have some clue about this ?

[MohdRashid]

It is the system config where you complete you transaction with ud to accepted n rejected. It is complete d then wt is created because it will not be set for partially. When you hold something system wait to see the decision where it is the remaining stock so when it is accepted n. Rejected then it is completed and works fine

[Penmetsa]

Hi Aslam , Please check the EWM Queue, Some times Put away Tasks Corresponding to your inspection Lot UD gets strucked up in the Queue, if you Process it , System will Process the Stock to Unrestricted .

Regards,

Sudhakar

[Daniil]

WT creation and posting change created in one queue, both or nothing. So if stock completely posted, it should be no queue in the system.

[Daniil]

Hi Aslam,

Unfortunately I haven't implemented embedded yet.

I know there is a difference, like for example QM lot is checked with selection from QALS table.

But I do not remember any difference for UD.

It could be difference in the customising.

WT creation depends on different

Factors, like for example process in the HU, and (if I am not mistaken) delivery reference(process type is taken from dlv), if you need always to get a WT it can be done with follow-up

"Blocked stock" or something like this (do not have system now) + you need to set process type, and there (if I remember right) it depends on "posting in a same bin" in the proxy. But in such case you would get WT even if stock already at final storage type

BR,

Daniil

[former_member788724]

thanks for the response Daniil.

[Daniil]

Hi Aslam, any news on this?

I remembered that process oriented control is used to decide if it is product or HU WT, so shouldn't be relevant for you.

However, If I go to 'EWM Inspection' and trigger follow up action from there, then put away WT gets created.

It works there synchronously, maybe it depends somehow on user/authorisation?

To be honest it is not the cleanest interface, still little bit buggy, so no surprise if it works little bit unstable.

Just debug it 🙂 easiest way, I guess.