Average Balance Computation Error Codes Dashboard

7.3.6.1.3 Average Balance Computation Error Codes Dashboard

The Average Balance Computation engine displays various messages and status indicators as it processes the data. This section covers how input data is validated, what each error code means and how to fix it, how the system notifies when a computation succeeds or fails, and how results and error details appear on the Process Dashboard.

Status	What It Means	What You Should Do	Where to Look
Running	The process is currently executing.	Wait for the process to complete. Do not re-submit.	Process Monitor – watch status refresh
Completed	The process finished successfully.	No action required. Results are available.	–
Failed	The process encountered an error and did not complete successfully.	Open the process in the Process Dashboard. Check Event Error Code and Event Error Description. Review Logviewer Service logs.	Process Dashboard → Event Error Code & Description, Logviewer, Launch Execution Canvas
Cancelled	The process was manually cancelled before completion.	Re-run the process if needed.	–

Error Codes

Event Error Codes appear in the Process Dashboard when you expand a failed process run and look at the Activity Details table. Each code identifies a specific type of failure at the component level.

Error Code	ABC_ERR_003
ABC_ERR_001	Average Balance Computation Execution failed
ABC_ERR_002	Average Balance Computation Execution is not started
ABC_ERR_003	Invalid input for Average Balance Computation

System Notification Messages

These are pop-up messages that appear on screen during process submission. They are not the same as Event Error Codes.

Notification Message	Type	What It Means	What You Should Do
Object Id already exists Process execution attempt failed	Error	You used an Object ID that is already linked to an active or recent run. The system rejected the submission.	Use a different, unique Object ID and submit again. Check the Process Monitor to see what run is using the same ID.
Process execution started successfully	Success	Your process has been accepted and is now queued or running.	No action needed. Go to Process Monitor or Process Dashboard to track the run.

Logviewer Message

When a process fails, open the Logviewer Service by clicking the log icon on the process run in the Process Dashboard. The table below explains the key log messages you will see for a failed Average Balance Computation run.

Severity	Log Message	What It Means	Action Required
Info	Input Valid Data Sources part of the System > [ OTH ]	The system has validated that the specified Data Source (OTH) is recognized and accepted.	No action required.
Info	Input Valid Product Processors > [ BORROWINGS ]	The system has validated that the BORROWINGS product processor is recognized and accepted.	No action required.
Error	InValid Avg Bal Computation Input Field: {BORROWINGS=[{ Source Business term = End Of Period Interest Amount, Target Business Term = Avg End Of Period Interest Amount Month Till Date }]}	The Average Balance Computation found invalid input field. The Target Business term 'Avg End Of Period Interest Amount Month Till Date' is not valid.	Fix the Target Business term as 'Average End Of Period Interest Amount Month Till Date'. Ensure Source and Target Business term are accurate. This error triggers ABC_ERR_003.
Error	Average Balance Computation Engine Input Parameters Validation Failed.	The overall input parameter validation for the Average Balance Computation engine has failed due to one or more invalid fields (see error above).	Refer to the specific invalid field error above. Correct the configuration and retry.
Error	Execution Unsuccessful	The process run has failed and could not complete successfully.	Review all Error-level log messages in the Logviewer for this run. Fix identified issues and re-execute the process.
Info	Avg_Balance_Computation Execution Completed with status FAILED	A final status notification confirming that the Avg_Balance_Computation component finished execution, but the final result is FAILED.	No action needed for this specific message. The actual cause is in the Error-level messages above.

How to Investigate a Failed Run

Follow these steps when you see a process with the status Failed:

Step 1 – Find the failed run: Open the Process Dashboard. Filter by process name or Object ID. Look for runs with status Failed.

Step 2 – Open the Activity Details: Click on the failed run row to expand it. You will see the Activity Details panel with columns including Event Message, Category, Component Name, Event Error Code, and Event Error Description.

Step 3 – Note the Error Code: Find the Event Error Code column (ABC_ERR_003).

Step 4 – Open the Logviewer: Click the Launch Execution Canvas icon next to the failed run. The Logviewer Service shows all log entries for that batch run, including Info, Error, and Fatal messages.

Step 5 – Read the Error messages: Click on the Error tab in the Logviewer to filter only error entries. Read each Error-level message carefully. The message will name the specific input field or validation rule that failed.

Step 6 – Fix and Re-run: Based on the error message, fix the root cause (e.g., correct the product processor field mapping or update the Application Parameters JSON). Then go back to the Process Modeller, open the process, click Execute, enter a new unique Object ID, and submit again.