E9.2 E1 Error Code Lookup, 002V and Renaming Errors to be User Friendly

[KenMoe]

Is there a good place to go that has an extensive listing of JDE E1 error codes and what they mean? It is hit or miss with internet searches and going to varies JDE related sites. It just seems like I spend a lot of extra time trying to see what the error code represents.

For example, I'm working on one now. We have a time clock orchestration that has a field named "szErrorCode" and in our JSON errors I get ("id":9,"value":"002V","name":"szErrorCode"). For the life of me I cannot find what 002V represents for a error. I'm assuming it is something to do with the name.

Also, is there a way to, using the example above, change the error code from ("id":9,"value":"002V","name":"szErrorCode") to something like "Employee Name is Invalid" or something more simple like that?

Thanks for your support...... Ken

 

[BOster]

Unfortunately error handling in general in JDE can sometimes be all over the place.

The error code itself is going to be meaningless. Some errors will be very specific to a very specific error in a very specific application in a very specific context and may have extended information in the error glossary text that describes exactly why the error occurred and what is needed to fix it. When viewed in an APPL this extended information is easily viewed by the end user and if bound to a control or grid cell will also give additional context to what went wrong. Most errors will still have additional information in the glossary text but will really only have meaning within the context of the APPL or UBE that is throwing the error and even then may be very vague.

It sounds like you are working with an Orchestration that is returning this error code in a param instead of actually throwing it within the context of a form request or something like that. BSFNs will often do this so the client caller can choose what to do with the error.

Your best bet to research these errors is most likely going to start with having at least read only access to the Data Dictionary, specifically the DD Errors. You can then at least view the Glossary Text. In your specific case you would be able to see the following (this is from a fat client but there may be Web version or 3rd party tool I am not aware of that can give you the same info):



That may give you some clue, but w/o more context its probably still going to be hard to determine exactly what is wrong. If it is being thrown by an APPL you may be able to query to get additional information about exactly which object (including source line) threw the error which can help you determine what went wrong.

 

[KenMoe]

Thank you very much for taking the time to respond. Regards, Ken

 

[KenMoe]

Unfortunately error handling in general in JDE can sometimes be all over the place.

The error code itself is going to be meaningless. Some errors will be very specific to a very specific error in a very specific application in a very specific context and may have extended information in the error glossary text that describes exactly why the error occurred and what is needed to fix it. When viewed in an APPL this extended information is easily viewed by the end user and if bound to a control or grid cell will also give additional context to what went wrong. Most errors will still have additional information in the glossary text but will really only have meaning within the context of the APPL or UBE that is throwing the error and even then may be very vague.

It sounds like you are working with an Orchestration that is returning this error code in a param instead of actually throwing it within the context of a form request or something like that. BSFNs will often do this so the client caller can choose what to do with the error.

Your best bet to research these errors is most likely going to start with having at least read only access to the Data Dictionary, specifically the DD Errors. You can then at least view the Glossary Text. In your specific case you would be able to see the following (this is from a fat client but there may be Web version or 3rd party tool I am not aware of that can give you the same info):

View attachment 20440

That may give you some clue, but w/o more context its probably still going to be hard to determine exactly what is wrong. If it is being thrown by an APPL you may be able to query to get additional information about exactly which object (including source line) threw the error which can help you determine what went wrong.

Brian - I do have access to this and yes it will help put more pieces of the puzzle together. I'm able to export the date except for the Text information language "CAUSE....The Operation Sequence..." Would you have a recommendation as to how best pull this information out of E1? Thank you in advance for your time. Ken

 

[BOster]

If you mean the literal Glossary Text of the DD item, then I can't think of an easy way other than using the JDE Error DD Application I showed in my screen shot. Others I am sure could probably tell you a good way to easily pull all of this info and there may be a third party tool that I am not thinking of that can pull this info as well.

 

[KenMoe]

If you mean the literal Glossary Text of the DD item, then I can't think of an easy way other than using the JDE Error DD Application I showed in my screen shot. Others I am sure could probably tell you a good way to easily pull all of this info and there may be a third party tool that I am not thinking of that can pull this info as well.

Thank you... Ken