How to Get Over Limit Issues While Enable Business Logic on Import for Integration Between OEC and SOA
(Doc ID 2603594.1)
Last updated on JUNE 28, 2022
Applies to:Oracle Fusion B2B Service Cloud Service - Version 11.13.19.07.0 and later
Information in this document applies to any platform.
On : 11.13.19.07.0 version, Activity Management
Facing 2 main issues on a specific setup for Import, integration between OEC and SOA.
1- The import is almost successfully closed while all records are not send to the SOA-queue. It means that the records haven't been processed into the groovyscript AfterTransactionPosted: aftertransactionpost.txt
Problem: For the same import shot 1/3 of contacts are not fully processed.
2- A modification from the groovy has been made in order to send the record to SOA even if reaching the API throttling limit.
Giving per record the possibility to be send to SOA if it didn't succeed (trying it 100 times). It is written in AfterTransactionPosted enclosed from def b = true.
Problem: So for 10100 contacts imported, consistently 3 contacts are set as rejected. When these contacts are once again imported, it works properly.
How to understand the reasons why this is happening and rapidly solve the issue.
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