Error process and exception connector not invoked for UCM Batch Process when error occurs executing step Execute Propsets.
(Doc ID 1609731.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel Universal Customer Master - Version 220.127.116.11 SIA  and later
Information in this document applies to any platform.
The UCM Batch Process is being used to transfer records from the SDH tables to the base tables. The requirement is to capture and handle exceptions that occur at the step Execute Propsets, which calls the ExecutePropSets method on the UCM Batch Manager business service. An error process has been specified and an exception connector has been added to the step, but these are not invoked when an exception occurs. The question is, is this expected behavior?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|