EWM - Resource Execution Constraints (REC) not working as intended

[former_member702508]

Hello!

I am currently trying to make REC work in SAP EWM (embedded, 1909) but for a reason unknown to me this functionality doesn't seem to behave as intended: it allows more resources in an area than stated in REC customizing.

My case is as follows: there is a storage type Z032 where every bin is assigned to REC storage group ZLM3. There is an ID Group Resource Type Z4 assigned to resource type ZYLL with a number of resources = 1. This ID is assigned to REC storage group ZLM3. That is, only one resource of type ZYLL should be allowed to work in storage type Z032.

Labor Management is active, ELS are provided for time calculation of WTs and WOs, networks are set up for TDC both globally and in this particular storage type; resource type speed present as well. REC is activated for the combination of storage type Z032 and REC storage group ZLM3.

I have 2 WOs for picking from bins, located in storage type Z032. There are 2 resources of type ZYLL and they want to do the WOs. Using system-guided scenario, the 1st resource gets the 1st WO and the status of the WO changes to D (in process). Now, what I expect to happen next - when the 2nd resource goes to system-guided, they don't get the 2nd WO because one resource is already working in that area. However, the 2nd resource still gets the 2nd WO and the status changes to D.

Basically, I am not getting the expected result and I am out of ideas what could be missing in terms of settings and customizing, especially since I don't know how a successful outcome looks in practice. I would really appreciate any hints or advice.

Kind regards,

Nataliya

Edit 1: I found the note 2893801 and since there is no possibility to provide correction at the moment, I stated the standard bins for the resources. However, now I am getting an error in RFUI, which isn't exactly informative: "E: REC control: Missing Customizing for edge (storage type Z032, aisle 05)". What kind of customizing could be missing for an edge? I maintained excluded resource types for all edges in the storage type (put all of them there except ZYLL) just in case, but the error is still there.

[former_member702508 · Accepted solution]

After some experimenting I found out the following interesting detail: the aisle for bins was assigned as "05", while the aisle in TDC settings for edges - as "5". So, the system cannot find edges for aisle "05" leading to the error (in Edit 1). After changing bin aisle from "05" to "5" the error disappeared and the resource was able to get one WO (I assume changing the aisle in edges will work too). The 2nd resource didn't get a second WO, receiving an error "E: Suitable warehouse orders were not found".

In the end, I got the result I expected - the system doesn't allow another resource in the area where one resource is already working, while max of resources there = 1.

There is one more detail I've noticed: if the 1st resource exits the 1st WO without completing it (status changes from "D" to " "), the 2nd resource still won't get any WOs from that area until the time passes, calculated for 1st WO completion. During that time period the 1st resource can regain access to the 1st WO. After that time period, the 2nd resource can get either of the WOs.

[shamsul_arfeen · Accepted solution]

Hi Natalia,

Thanks for sharing the resolution. Do you know if this can be done without labor management? I am at the same error as you were but we don't have labor management. Any help/direction is highly appreciated.

Thanks!!!!!

Shamsul Arfeen

[martinprokop]

Hi Shamsul,

LM is not necessary for REC functionality. REC can reuse WO planned processing time from /SCWM/TLAST table.

Regards

Martin