SAP CPI Max connection limit

[ADIDAS]

One of our processes is generating about a 1000 IDocs through RSEOUT and calling CPI to send the information to a 3PL application. What we are seeing is about 600 of those IDocs reach CPI and get processed successfully and the remaining 400 IDocs end up in Status 02 status indicating it couldn't connect to CPI. We don't even see them in CPI. 

Does anyone know if there is a max CONCURRENT connecting limit in a CPI tenant and how to have it updated?

Thanks in Advance

[chris_75]

That's not only a question of the connection limit of the CI and SAP ECC but also of the receiver system. Therefor a good and well definiend integration design is crucial. One very important thing is the decoupling via JMS queues. Otherwise SAP always can stuck in Status 02 when the receiver system of the iFlow is not available or under overload etc.

Good luck

Christian

[Ryan-Crosby]

You can always try something like this which I have made available on Github and supports bundling. The first blog gives background and some initial steps for inbound but part II focuses on outbound, and everything is available for download to try.

https://community.sap.com/t5/technology-blogs-by-members/sap-edi-idoc-communication-in-cpi-using-bun...

Regards,

Ryan Crosby

[MAVR]

Hi @ADIDAS 

Please get in touch with the operation team (open an SAP case LOD-HCI-PI-OPS) and provide the detailed volume you are having and your tenant information. They will validate and increase the resources accordingly. 

I had a similar issue with SOAP services S/4HANA, which was unable to reach BTP Cloud Integration, but after the changes, the issue was solved.

I hope this helps you. 
Best regards 🖖🏻

[ONavas]

Hi ADIDAS,

For outbound processes with many IDOCs, the best practice is to activate the option Collect IDocs and to use a Pack Size according to your requirement.

For 1000 IDOCs, 50 or 100 value for Pack Size should be a good option.