OSC Bulk Process Webservice PROCESS Operation Is Not Successful Even If Few Transactions Failed.
(Doc ID 2216472.1)
Last updated on SEPTEMBER 20, 2018
Applies to:Oracle Fusion Sales Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Customer is using bulk process webservice and PROCESS operation is not successful even if few transactions failed.
Below is the current feature of partialFailureAllowed functionality:
1. ignore the rows with row level errors, commit the rows without errors
2. rollback everything where there is transaction level error.
In the current CREATE case the validations occurs at transaction level hence the whole transaction is rolled back.
Customer wants that even when a record is errored out rest of the transaction (records) should be committed and return the response.
Consider an example - Using processContact operation, Customer is trying to create 3 contacts.
Contact with first names Ann and Prince have correct request data and account party id.
Contact with first name Susane does not have the correct account party id.
I have set the processControl element partialFailureAllowed to true as below true
With this setting the 2 contacts of Ann and Prince should get created for the account party id 999999999999 even if the contact Susane contains incorrect Account party id.
The result that comes out is that none of the contacts are getting created.
The expected result is that even contact when one contact fails due to invalid account party id the one's which are correct should be created.
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