Attempting to complete worktask, get error indicating object can only be approved by active work task

While attempting to complete a work task I am recieving an error stating the following:

"This Class of Object may only be approved via an Active WorkTask. Please ensure that the related WorkOrder is started and that the WorkTask Accepted.
(From DbEventHandler: 'ebh_approve_package')"

The user has quite clearly accepted the work task as they are now attempting to complete it and it is in their inbox.  I am stumped as to an explanation for this and I do not have access to review exactly what ebh_approve_package is doing so there is very little I can do to investigate.

Any ideas would be much appreciated.

  • This will not likely help but here is the detailed stack recieved when completing from director:

    System.Exception: <Cast from Oracle.DataAccess.Client.OracleException>

    Oracle.DataAccess.Client.OracleException ORA-20512: This Class of Object may only be approved via an Active WorkTask. Please ensure that the related WorkOrder is started and that the WorkTask Accepted.\n\n(From DbEventHandler: '{0}').params[{ebh_approve_package}]

    ORA-06512: at "EBFCMS.EBP_RAISE_DB_EVENT", line 296

    ORA-06512: at "EBFCMS.EBP_WORK_COMPLETE", line 75

    ORA-06512: at line 1    at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck)

      at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)

      at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()

      at eB.Service.Index.Database.Command.Execute()

      at eB.Service.Index.IndexWriter.WorkComplete(String session, Int32 wsId)

  • I believe is looking into this per SR 7000148992.



    Answer Verified By: Roberto Garcia 

  • For anyone looking back for an answer:

    Our user had manually removed the relationship between the ECP document that housed the work order and the change request.  Once that relationship was restored the user was able to continue the workflow normally.

    Answer Verified By: Ryan Mooney