E1: ORCH: Error Handling with Abort Option and Exception Orchestration Results in NullPointerException When Not All Input Values are Passed In, Orchestration is Not Aborted (Doc ID 2909851.1)

Last updated on NOVEMBER 22, 2022

Applies to:

Symptoms

In an Orchestration, Error Handling is defined with Abort option selected and Error Handling Process to call a secondary Orchestration on a Form Request (In this example, MB_SREQ_AddItemWithPreference).

When the Orchestration is run with an invalid address book number passed in, it is not detecting the error on the Form Request and the Orchestration is not aborted correctly.

It is found that if not all input values are passed into the secondary Orchestration from the parent Orchestration, it causes a NullPointerException error on the previous step (in this example, MB_RULE_IsNumberGreaterThanZero) and the Error Handling Orchestration is not called and thus the Orchestration does not abort.

Previous step MB_RULE_IsNumberGreaterThanZero throws Java.lang.NullPointerException error

{
"status"" "ERROR",
"message": "MB_RULE_IsNumberGreaterThanZero: Java.lang.NullPointerException",
"exception":"Exception",
"timeStamp": "2021-11-09T07:50:49.760-0600",
"userDefinedErrortext": " "
}
 

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.