cancel
Showing results for 
Search instead for 
Did you mean: 

WT telegram (resource/bin tasks) not triggered automatically in SAP EWM MFS

ramani28
Discoverer
0 Kudos
634

LOSC setup is in place for putaway in an automated warehouse, there are two WPT's one is for Internal warehouse movement, which places the HU pallet from conveyor onto an intermediate bin(Z001), another WPT is for putaway - which splits in to two task - 1. Movement from Intermediate Bin (Z001) to Crane PLC (Resource Task) 2. From Crane PLC to Final putaway destination bin.

The first internal warehouse movement triggers via a telegram (SC teletype) which posts the GR and triggers WT from EWM to PLC for both the tasks (1. Resource Task 2. Bin Task)

Currently this trigger of WT is not happening incase of inbound from production order, but it works well incase of inbound from external vendor

For WT triggering in case of production order, currently we are triggering it manually from Monitor
/scwm/mon - Enter Warehouse No. and Monitor > Material Flow System > Conveyor Segment Group > Resource > Select the resource, Click on More methods > Recalculate WT's & Trigger Telegram Processing
Once this is done the WT telegrams can be seen in monitor


Is there any way in which the resource availability can be controlled based on storage process/WPT?

Accepted Solutions (0)

Answers (2)

Answers (2)

Ajit_Routray
Active Contributor
0 Kudos

Hi ramani28,

Is there any way in which the resource availability can be controlled based on storage process/WPT?

Did you assign each crane as unique resource and unique queue ? then queue to resource ? Are you using standard FM ? What is the FM used for outbound telegram?

Assignment Flow=> WTs -> Queue Determination->MFS Queue->Resource-> PLC

Did you check any BADI implemented in your project? Could you check enhancement spot /SCWM/ES_MFS ?

Kind Regards,

Ajit

nikhilnegi1
Participant
0 Kudos

Hi Ramani,

For triggering the telegram automatically, The resource should not be assigned to any open warehouse task and should be available. Try cancelling all the open WT's for that resource and then create the new WT.

Regards,

Nikhil Negi

ramani28
Discoverer
0 Kudos

Hi Nikhil,

Thanks for responding. Its ensured that there are no open WT's still I face the same issue

nikhilnegi1
Participant
0 Kudos

Hi Ramani,

Is the communication channel in running status?

Regards,

Nikhil Negi