In Hera, if the system has a problem with something, it generates what is called a 'HERROR' message with a unique code and description.  If you cannot see what went wrong with the provided description, you can look up the code here to see even more information about the problem that occurred.


Here is an example of a 'HERROR' message


If you break it down, you can see it is broken into three parts.  The action, the problem, and the 'HERROR' code.  In this example, the action was that the user tried to update the Work Order and the problem was that the NTE was too high after markup and tax to be allowed without an approval.  The 'HERROR' code if #03-064-008G.  You can than take that 'HERROR' code and quickly see how critical of an issue it is.


A 'HERROR' code can end in the four different letters listed below.

  • U
    • This is the most common type of ending.  This means it was a 'User' error and that there is nothing wrong with the system.  This could be anything from entering an invalid Store Code to a blank value.
  • G
    • This is the second most common type of ending.  This means it is a general error that could be either the system of the end user.  For example, the user could of entered too high of an NTE, or the system had the incorrect max value set.
  • M
    • Seeing this type of ending is uncommon, but might happen from time to time.  If you see this ending, a ticket needs to be created with the 'HERROR' code and what you were doing during the time of the issue.  This is a system issue that will be fixed normally within 1 business day.  It is a real system issue, but nothing that will stop what you are doing.
  • C
    • If you get this error, someone needs to be contacted immediately.  This means a critical error has happen with the system and it will be fixed immediately by the development team.  Create a ticket and enter the 'HERROR' code along with what you were doing.