In IFS10, shortly after upgrading from IFS8:When we go to an active Task Schedule with a single task, Create Order Proposal, and attempt to add a day, change the time it executes, or alter the schedule in any way we receive the error message, “The Batch Schedule Par already exists.” The SQL trace comes back clean in the debugger having successfully run the validation method on the database task.Deleting the task schedule and database task in an attempt to recreate the job results in the same error message when attempting to reconstitute the task schedule.
Some background:We have a custom event action running as a validation on the LotBatchMaster LU intended to ensure 1 part number per Lot Batch #. This is done with ‘pragma autonomous_transaction’ in order for the event to run on a mutating table. In IFS8 performing a “receive by-product” on a shop order with multiple by-products received simultaneously would perform one database transaction per line and our after create action would correctly error if a lot batch number was repeated on that submission.IFS8 has the COMMIT shown after the first line is submitted here, and the next line errors with the event action:In IFS10 it appears that a transaction is opened for the entire submission as a batch, and since the event action is validating outside the scope of the transaction which is in process it is not able to find that any record exists with the Lot Batch #.My questions are:Is there a way to force IFS10 to revert to one line per transaction? (I’m guessing not without meddling with the
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
