Siebel Insurance Guide > Business Services for Siebel Financial Services > Handling Business Rules Processor Errors >

Recovering from Errors Within a Business Rules Process


For every BRP process, a procedure can be nominated as the error procedure at the process level. If defined, when an error condition occurs, this procedure is automatically invoked to handle the error.

On completion of the error procedure, System_ErrorCode property is rechecked. If it is empty, the execution continues from the point where the error was originally thrown. If the error code is still populated, the process does not necessarily end, but rather follows an error bubbling process.

For example, if an error encounters in Statement 10 Step 5 Procedure Main, the error procedure is first executed with System_ErrorSource to be 'Statement 10 Step 5 Procedure Main'. If the error is not handled, the error bubbles one level higher, to Step 5 Procedure Main. The error procedure is then re-executed with System_ErrorSouce to be 'Step 5 Procedure Main'. If error is handled there, the next step following Step 5 is executed. Otherwise, the error bubbles to Procedure Main.

The whole bubbling process continues until it reaches the process level, with System_ErrorSource to be Process myProcessName. If the error is not handled at the process level, the process ends with an error.

It is important that the error procedure be thoroughly tested. If an execution error occurs within the error procedure, the error procedure will not be recursively invoked; the error procedure will end with an error.

TIP:  Use a Switch block within the error procedure to check for known error codes.
Siebel Insurance Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.