We had a similar issue w/ Quick Entry after upgrading to 9.05.702. This is the result:
This has been considered as a bug, and I have just received the SCR from the Development Team.
Unable to create Jobs in Quick Job Entry, when the revision's BOM of the part has no Operations, and the Material of that revision is a subassembly. The system returns an error message (4GL STOP condition: The Server application has returned an error. (7243) (7241) when attempting to save.
Jobs should be created with no issue, even when the main part has no operations in its BOM.
Create jobs using regular Job Entry,
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of Jose Gomez
Sent: Monday, October 14, 2013 9:05 AM
Subject: Re: [Vantage] Job Entry screen not working
BPM? Data Directives In Place? Customization? DB Triggers? DB Locks?
next time it happens run sp_who2
Jose C Gomez
T: 904.469.1524 mobile
Quis custodiet ipsos custodes?
On Mon, Oct 14, 2013 at 9:02 AM, <gracefulthreads@...> wrote:
Epicor has punted on this one, saying they can't replicate the issue even on my database.
My Job Entry screen RANDOMLY doesn't work any more. Some mornings our production supervisor is unable to firm up jobs, change production quantities, engineer, or release ANY jobs through the Job Entry program. The screen updates with the changes, but the SAVE function does not save them. We can use Job Status Maintenance and other programs to make the changes as a workaround, but that is rather clunky (especially when changing production quantities). There are no customizations and no personalizations on Job Entry, and this situation seems to come and go randomly (this morning she couldn't firm up a job, but after I firmed it, changed quantity, re-engineered, and released the job, she was then able to perform all functions on an different one).
Anyone ever seen something like this before?
We're on 9.05.702A SQL.