A secured or licensed column is referenced by a table relation from

Kinetic ERP
1

Recently I started getting this error in the BAQ designer.
Severity: Warning, Text: A secured or licensed column is referenced by a table relation from (PartRev Type: Table) to (PartOpr Type: Table). Associated data will not be returned

This happens when I add partrev and partop tables into my layout. I fix the issue by removing two of the pre-defined table relations. I remove AltMethod, and ProcessMfgID from the relations for both tables, and then the error goes away.

What’s going on with this?

2 Likes
2

Epicor added a new field ProcessMfgID as part of the key structure, but you can’t access it if you don’t have it licensed. The “fix” is to go into the join criteria and remove it. I submitted a ticket to Epicor on this, is already a known issue PRB0250431. Probably will get fixed in a future release, but for now the “workaround” is pretty quick.

10 Likes
3

Actually, this problem got closed without getting fixed. Looks like the workaround is going to be a permanent part of the solution.

1 Like
4

“Functioning as expected”

2 Likes
5

2 Likes
6

If it’s documented, then I buy it.

7

I typically get “That’s by design” or “Working as expected”. LOL.

2 Likes
8

Thanks for posting the fix, @SimsTrak. This got me with PartRev today. Still not fixed in 2023.2. I can’t imagine Epicor wanting BAQ’s to crash with their auto-created joins is on Working As Designed. But yet here we are.

What % of Epicor customers have ProcessMfgID licensed anyways? We have most of the modules licensed, but not this one.

@Chris_Conn - Can you create a W.A.D. song to debut at Insights 2025? :smile:

3 Likes
9

I ran into this earlier this year, I didn’t get the full message about the licensed column though, it just returned zero rows until I removed that field. Weird.

2 Likes
10

Ask and you shall (sometimes) receive.

Submit another ticket to the void
Another error message to avoid
“Have you tried turning it off and on?”
The same response since time unknown

CHORUS:
W! A! D!
Working as Designed!
Your suffering’s been pre-defined
W! A! D!
Working as Designed!
Trapped in digital chains that bind

Enterprise Resource Planning hell
Each module’s got its own story to tell
Click through screens of endless forms
“This behavior follows platform norms”

CHORUS:
W! A! D!
Working as Designed!
Your suffering’s been pre-defined
W! A! D!
Working as Designed!
Trapped in digital chains that bind

BREAKDOWN:
Error code 5-0-9
They say the system’s working fine
Deadline’s breathing down my neck
Support just sent another tech

(Spoken with growing intensity)
“According to our documentation…
This is expected behavior…
The system is performing…
WORKING! AS! DESIGNED!”

CHORUS:
W! A! D!
Working as Designed!
Your suffering’s been pre-defined
W! A! D!
Working as Designed!
Forever trapped in ERP’s grind

(Guttural scream)
WORKING! AS! DESIGNEEEEEED!FINAL CHORUS:FINAL CHORUS:

8 Likes
11

Beavis And Butthead GIFs | Tenor

3 Likes
12

You nailed it, Chris!!! Time to share that with our entire IT department.

1 Like
13

Dumb question but how do you remove ProcessMfgID manually from the BAQ?

Update:
Nevermind, figured it out. It’s in the join itself. BAQ designer auto added that field. Which I didn’t notice but that makes sense. Removed the field and all is well.

Thank you for posting this.

1 Like