Understanding Batch Error Messaging

The Oracle's JD Edwards EnterpriseOne error message system provides a consistent interface to review batch application errors. You can set up batch applications to send messages to users when processing is complete. These messages include the success or failure of the batch job and notification when information is incorrectly entered into the system. To enhance the usability of the messages, the system uses a tree structure (or parent/child structure) to group related messages.

You can create two types of error messages for batch applications:

• Non-text substituted

• Text substituted

A non-text substituted error message provides a high-level indication that an error exists in the batch application. For example, Document number is invalid.

You can use text substitution messages to provide additional information regarding errors. For example, rather than the Document number is invalid error message, the message can instead state Document number 55.5555 is invalid.

You can also include a link to the associated interactive application in the message. This type of message is referred to as an active error message. The user can open the associated interactive application from the link that is attached to the message.

Error messages appear in the Oracle's JD Edwards EnterpriseOne Work Center (P012503) application after the batch job has completed. When you create custom batch error messages, determine what information Oracle's JD Edwards EnterpriseOne users require. For example, you might create a number of different messages that are generated when a journal entry report is run. You can create a message stating that the report completed successfully when the report data is in balance. Additionally, you can create multiple levels of messages that describe various errors if the report is out of balance. The first level might state that the report completed with errors while additional levels explain the specific details regarding the errors.