PSA - 2025.2.7 PO Entry broken

Kinetic ERP
1

After 2025.2.7 update we are getting ‘Duplicate Record’ upon save new in POEntry.

Support was quick to respond this is a known issue on some customers.

And conversion 790 is the fix.

Problem is we now have a stuck Process Suggestions process and restarting Task Agent via CMP doesn’t fix it.

2 Likes
2

Might need to kill the task via data fix FX_Del_SysTaskTables…we had to request/download it, generic version but expires in a year. Run the Data Fix Report, search for Active jobs via parameter, then terminate the one(s) that are hung.

1 Like
3

I’m not seeing that error in my PILOT system on 2025.2.7, but if you need to cancel a stuck process like that I’d recommend requesting data fix “FX_Del_SysTaskTables” from the EpicCare support team.

2 Likes
4

Also, vote for:

Allow removal of dead tasks from the System Monitor without Epicor Support - Idea 4767

7 Likes
5

Apparently it’s not a dead task as I don’t see any sysTask record related to this. Exact error is upon Process Suggestions buttton (not generate suggs process)

Business Layer Exception

Buyer HOUSE is currently processing suggestions since 12/1/2025 11:56:55 AM for user username.

Error Detail

Correlation ID: 4cb3c367-9155-4acf-b4b1-6e5d77e330a5
Description: Buyer HOUSE is currently processing suggestions since 12/1/2025 11:56:55 AM for user username.
Program: Erp.Services.BO.POSugg.dll
Method: LockBuyerUpd
Table: undefined
Field: undefined

1 Like
6

Let me guess, I’m stuck due to poor QA on patch release, delaying go-live tests for a whole implementation team + consultants, wasting support resources, waiting for two days on a simple datafix like:

UPDATE Buyer
SET Locked = 0
WHERE BuyerID = 'HOUSE'
7

@klincecum posted a BAQ you can run to fix it yourself.

Edit: I guess that’s just for stuck tasks. Which sounds like it’s not your problem.

2 Likes
8

Thanks yeah I saw that. Didn’t compile but BAQ showed my prob is not a systask rather it’s a locked buyer.

1 Like
9

Table PurAgent…look for fields prefixed ProcPOSugg

10

We seen this in our Pilot for 2025.2.7 there is a hotfix from Epicor to fix it.

11

looks like kinetic PO Suggestions has a built-in Unlock Buyer feature. who knew?

image
image1910×360 30.3 KB

prob solved.

2 Likes
12

Fix available in EpicCare KB0142365

3 Likes
13

Nice…didn’t know it existed either but here we are. Good to know.

image
image222×483 6.37 KB

3 Likes
14

Thanks, I knew of the fix but not the KB to reference it

1 Like
15

support tech learned something too. got notice from above after trying two datafixes…

16

Yes, it’s a nice upgrade to Kinetic PO Suggs.

17

What’s interesting is that in my open support case with Epicor, I was advised to first run the 790 conversion and then a custom hot fix within the Datafix Workbench. I will include a reply in my open case to this KB article. Thanks for sharing!

1 Like
18

imagine how many tiny ‘datafixes’ could be implemented as Actions like that… support-hrs-straight-to-profit, cust-satisfaction-to-moon

1 Like
19

So to clarify, conversion 790 fixed the underlying problem caused by 2025.2.7 which broke PO Entry & PO Suggs (Duplicate record error on save new PO). IF you ran Process Suggestions btn on PO Suggs in the meantime, you;d also have a locked buyer. Unlock Buyer action was the fix to that related issue. No datafix needed.

3 Likes
20

we were first advised to run this but didn’t help as this 2025.2.7 was not a case problem. AFAIK, it was an identity field prob fixed by conv790.