I have a user getting the following error after the update, seems to be only impacting this particular user and is also sporadically occurring for them when using CTP function. I reset that users personalization to base, and we also have no BPMs related to the method/tables that I can see for this. I am not able to interpret the error well enough to see if there’s any other actions I could take… Any ideas?
Please contact Support on this and create a case.
Well I supposed with a ticket in I’ll just update this thread with what our issue was in case anyone else experiences this!
Hi Alex - Were you able to resolve this issue?
If so, what was the resolution?
@timshuwy I really think CTP code and functionality really needs a code review and overhaul. I have had so many Epicor Support Cases regarding CTP giving generic, unhelpful technical errors. Things like Nullable values and even the error on this post. And the root cause issue is rarely the same thing. It can be an issue with a Method, unapproved Revision or some random type of ‘data corruption’ where one of the scheduling values on a JobOpr record is null or not set properly or even an issue with the ResourceTimeUsed records. Each time it seems to take awhile to get anywhere and usually support is not helpful at all and I end up fixing it with a Data Conversion (750, 760 or 770 for example). It would help if CTP could just handle these issues or at least provide an error message that better indicates where the issue actually is.
Additionally, the way CTP works does not align with the documentation and not even when the application enables the CTP option in the Actions menu. According to the documentation only the Need By Date is required for CTP, and that is when it is avaiable in the Actions menu. But if you try to run CTP without the Ship By Date, you get a Nullable Value error (again doesn’t say that the issue is a missing date). Regardless, the point of CTP is to determine when the order can be promised… what the Ship To Date could be… So there seems to be a misalignment between the frontend/backend and documentation. Everytime I have brought this up to Support, they send it to Development and development just says it’s working as intended, but it’s not, and doesn’t make sense. I just keep running into CTP being unreliable and it’s frustrating to users.
I even tried to create an Epicor idea on this type of issue… but it’s expired now.
I just think fundamentally, CTP has some poor design issues that should be addressed to smooth out the use of CTP.
Restore Proper CTP Handling When No Ship | Epicor Kinetic Ideas Portal (aha.io)
rant over
@Rick_Bird, the idea shows “expired”. If you re-submit it, do the marketing thing and add it onto the “Frideas” list every now and then so we remember to vote on it!
if you are getting null errors, then this needs to be reported to support. also, if it doesn’t match the documentation, then that needs reported as well.
@timshuwy
That’s the problem, I have reported it multiple times and they keep saying it’s working as designed and the Ship By Date is required. I have been reporting this issue to Support for years and I keep hoping it will be fixed, but we just get the old ‘working as designed’ shrug.
I will also do what was suggested by @Ernie.
The trouble is, due to CTP flakiness, I find most people don’t use CTP so there is a low chance of getting a lot of interest… but it’s a circular problem, most don’t use it because it doesn’t work well and they abandon it as buggy feature… the feature is then ignored and never gets any TLC.
Agree, have abandoned CTP many times because it just . . . does not work. And it really should. Support has no ability to solve this when development refuses to accept the problem.
Have you come up with an alternative?
People looking at time phase.
Any thoughts about What-If schedules? I can see time phase working for an end-items, but be difficult for uncovering machine load issues.
Yes I don’t have a solution - just agreeing CTP is not very functional the way it is. The need for it absolutely exists.
Check this thread… 2023.1.x upgrade issue for random users - "There is an unclosed literal string. Line xxx, position xx" - #2 by klincecum
I had that randomly with users on classic clients when upgrading to 2023.1. I had to ‘uncheck’ all tracing options in the user accounts. Having tracing off wasn’t enough, I had to clear any ‘grayed’ out boxes in the options.
