Regarding BAdI /scwm/ex_core_pts_nbin_nrm for Multiple WT putaway into same destination bin

[yaping_wang2]

Hi All,

I am pretty new to EWM. In our manufacturing plant, we have designed the putaway for manufacturing Semi-FGs into one common storage bin.

If the semi-FG has no need quality inspection, it will go to the bin using PPF action directly. If semi-FG needs quality inspection, it will use the quality usage decision follow-up action to create WT and putaway into same bin.

We found sometimes when there are 2 usage decisions made at the same time, system normally locks the bin then 2nd UD didn't create the WT successfully. One of the suggestion is to implement the BAdI and set the EV_Abort = X. We have implemented but somehow system still tried to find next available bin thus it is always failed because we only have search strategy to put into this storage type and there is only one storage bin in this storage type.

Do you have better way to resolve this issue? or I have create 1 or more bins in this storage type in case of described situation happens again which is not ideal way to resolve this.

Thanks all.

Yp

[JuergenPitz]

Hi,

"For the putaway strategy, we are use storage type search strategy only for this specific issue."

That is not what I meant. In the storage type settings, there is a putaway strategy. What have you selected there?

Brgds

Juergen

[yaping_wang2]

Sorry Juergen for late reply. In the storage type master data, we have following settings:

1. Putaway rule : 4 - General Storage Area

2. No storage section check

3. No putaway HU

4. WT Generic- blank

5. Putaway Storage control - blank Dynamically evaluated

6. Always need to confirmation

[yaping_wang2]

Mixed storage with no limitations,

[Angelhpp]

I have the same problem with the WT, when I have 3 differents materials, the system only creates the WT for 1 becuase there is only storage bin, for the other materials, the sistem does not create any WT. How Did you fix this issue?

[yaping_wang2]

In storage type, set the “capacity check” field to 4 and this will not lock the storage bin for capacity checking any more.

[yaping_wang2]

Thanks Juergen / Ajit your feedback! Sorry I didn't aware that you are answer my question.

For the putaway strategy, we are use storage type search strategy only for this specific issue. It has been mapped to this storage type properly because normal putaway all successful while this issue only happens when there are 2 QC making usage decision at the same time. 1st WT always blocked the only in this storage type. We only have one bin in this storage type.

For WT generic setting in Storage type, it has been setup as blank (Not generic - storage type, storage section and storage bin).

Please let me know if you need further information.

Thanks

Yp

[Ajit_Routray]

Hi YP,

Addition to Juergen,

Please check the option of WT Generic in Storage type master setting putaway control.

1Storage Type and Storage Section

2Only Storage Type

Kind Regards,

Ajit

[JuergenPitz]

Hi,

"We have implemented but somehow system still tried to find next available bin thus it is always failed because we only have search strategy to put into this storage type and there is only one storage bin in this storage type."

What is the putaway strategy in this storage type?

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!