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

Automatically assignable WO for GR or deconsolidation?

martinprokop
Participant
0 Kudos
251

Hello all,

in standard EWM there is no preceding WO to plan a step of inbound packing and GR posting or for deconsolidation. This means these steps can be performed in RF only based on manual selection of respective logical transakction in RF menu by the user. It is not possible to assign this type of work to a user automatically (system-guided), as it is possible for putaway or picking, for example. The reason for this is, the WT in available status (in decon) or WT at all (for GR) is missing at the timepoint, when these steps are about to be performed. These WT's and WO's are then created (and immediatelly confirmed) during the processing of these steps. E.g. they have no planning purpose, they only document finished processing of these steps.

But, even in the GR process, there can be LSD's and priorities, which should prioritize some particular GR againts other ones (for example it is cricial to speed up the GR process for this PDI, including some missing quantity for an uncomplete outbound process). The same can apply to deconsolidation.

So, my question is: Have you ever tried to solve this?

In Deconsolidation, I tried this:

  1. I used an existing WT for deconsolidation (on Hold) 164734
  2. I create a WO manually (as an entry in /SCWM/WHO) and to populate important fields there (incl.
  3. I add a referece in respective /SCWM/ORDIM_O-WHO
  4. I create new entries in /SCWM/WO_RSRC_TY with CONTENT = 06 - Spreading

During WO assignment, I skip the hardcode in function /SCWM/RSRC_WKBSYS_INITIAL (row 703), which would start lv_ltrans = 'PTWOSY'. I change the value lv_ltrans = 'SPEXSY'.

Then, I am able to process deconsolidation of the assigned WO in RF.

Why is this not designed and supported by standard EWM?? Why these proces steps cannot be included in a complete workload in the warehouse, which needs to be optimised as a whole?

Regards

Martin

Accepted Solutions (0)

Answers (0)