BatchValidate Method Does Not Work As Expected After Upgrading To

(Doc ID 1642563.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel eConfigurator - Version [23021] and later
Information in this document applies to any platform.


BatchValidate has been called in order to create the default instance of a customizable product.

However, BatchValidate doesn't save the instance when status is Invalid
Happens after upgrade to (Incremental Repository Merge applied)


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms