PSA: Customers with no territory do not show in Material Queue

Our users were saying that there were only a few customers showing in the EKW app for picking.

So we went to the Material Queue (Manager) and observed that there were indeed some missing spots there also.

Turns out that the Cust. ID only populates if the territory is populated on the Customer setup.

OK, so we don’t use territory security or much like that. So maybe this is even trickier if you do.

But I know that at a minimum, when we populated the Customer’s territory, then the IDs started showing.

This feature does not seem to exist in Classic; all IDs populate in the material queue there. But regardless, the EKW app is affected. (Maybe they use a different method now?)

3 Likes

In 2024.2, in our Classic screens, Territory is required for a customer.

2 Likes

Well, in Kinetic, not so much:

1 Like

At a previous company, during our initial Epicor install, the CRM module didn’t install correctly. All of our customers were migrated before the issue was discovered. Once Epicor fixed the CRM installation, every customer essentially disappeared from visibility because no territory had been assigned.

To fix it, I used DMT to bulk-assign a territory to all customers, and once that field was populated they immediately became visible again. This was all in classic.

At my current company we have crm installed but most companies do not have territories assigned but do show up. This is all in kinetic.

1 Like

thats strange they would get rid of that. I double checked this isnt a custom directive.

2 Likes

I oddly enough noticed that it didn’t matter yesterday trouble shooting a different problem with sales orders when looking at the customer record and seeing it blank.

I just loaded the Kinetic screen for Customer and its still requiring it.

1 Like

Thickens My Friend GIF by Reservation Dogs

I don’t change-log the territory field, but my whole customer database is intermittent on the territory. Even in 2017. :man_shrugging:

Perhaps it based on a Module being installed. certain modules require you to do extra steps.

Interesting; we do NOT have CRM, for example.

we do. maybe thats it.

2 Likes

I can’t check ours as we fixed all of them yesterday when I found the problem.

1 Like

At one time I felt special being the first or only person to discover a bug/feature. Now I’m rather sick of it lol.

We are the only Epicor users at the intersection of using EKW and not using CRM and not caring about territories. Magic. :unicorn:

We are the only users that use multi-level pegging as part of MRP -and- have looked at the log files.

Amazing. We are pioneers!

4 Likes

you could probably make a method directive and copy the BO and method epicor is using in that error i posted.

2 Likes

CRM is what requires it based off my experience at my last company. No records had it and when crm was installed they became hidden because the territory didn’t exist. Once that field was updated they were visible. I think ours may have actually existed also but someone had made a customization that made them not appear correctly, at my current company.

1 Like

Good insight, everyone.

Irony now is that even though it is “not required” if you do not have CRM, functionally it basically is required since it is hampering other functionality.

The issue is with EKW?

Yes, but it is mirrored in the Material Queue also.

Here we are not “picking” all orders on EKW; only internal customers for now.

Well we have a new internal customer, and our people here noticed that those orders were not in some EKW screen for picking where you can select by customer (obviously I do not use the app much myself). But the older internal customers were available.

That then led me to the material queue, and here we are.

1 Like

do you have access to the CRM tab in Company Config?