BatchValidate Method Does Not Work As Expected After Upgrading To 22.214.171.124
Last updated on MARCH 02, 2017
Applies to:Siebel eConfigurator - Version 126.96.36.199  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 188.8.131.52 (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