Common Transaction Errors

Process

This job aid describes the different types of Transaction Errors a CORE User may see when selecting Save, Validate, or Submit. Along with steps on how to view transaction errors, types of severity errors, and override errors.

 Selecting Save, Validate, or Submit will perform a series of edit checks on your transaction. These checks are to ensure there are no errors that will prevent the transaction from being accepted in the next phase. If errors are found, the user will see an error message along with the total number of errors (i.e. “1 of 7”).

Viewing Transaction Errors

Transaction Feedback

When you select the Save, Validate, or Submit actions, CORE  performs a series of edit checks on your transaction. If it encounters any issues or if the Validate or Save action is successful, details will appear in the System Feedback ribbon. It will be beneath the Page Title Bar. On the far left is a box for each message severity proceeded by an ‘ALL’ box that gives the total count:

• Successful (green check): Successful messages are issued. They then disappear as a way to show your action succeeded. 

• Informational (blue box with an “i”): These messages are for information only. It does not affect whether a transaction will be accepted to the next phase. The system accumulates all informational messages that occur during transaction processing. The user can see all the informational messages for that transaction version at one time. 

• Warning (red triangle with exclamation point): When a warning message is seen, it's checked against the previous validation or submission warning. If a new message matches a previous one, a red triangle with an exclamation point appears. If there are new warnings since the last time, the user can review them before accepting the transaction to the next phase. The next time the transaction is submitted, the transaction is accepted to the next phase if there are no new warnings. All warning messages that occur during transaction processing are accumulated. This allows the user to see all the warning messages for that transaction version at one time. 

• Severe (red diamond with a lightning bolt): the process stops immediately. It returns control to the user. All updates or changes made to the transaction and made outside of the transaction are not committed. The user sees only the messages that occurred before the severe message. They also see the severe message itself for review. 

All errors are shown in a horizontal bar. This bar displays one line of the short message. The successive boxes filter the horizontal bar by severity. On the far right are a pair of icons (Previous and Next) for navigating within a group of short error messages. The last icon is the Show All Messages. The Details icon opens a panel from the right. You can review all the message details and search across messages. 

Overriding an Error Message 

Error messages defined as an Override Error have an associated override level. This level requires a user to apply an override of that level or higher to proceed with the transaction. System configuration for each transaction code can have three settings for applying overrides on transactions with workflow established:

• Allowed only after reaching – You can only apply the override action after the transaction reaches Pending.

• Required before reaching – You must apply the override action before the transaction reaches Pending.

• Allowed before or after reaching – You can apply the override action before or after the transaction reaches Pending.