Common errors in SAP CPI

This article will cover a list of common errors in SAP CPI. The document will have an error handling list and their solutions.

Here are a few of the common errors in SAP CPI which was encountered while working on different SAP CPI interfaces.

If you use * as a value for Allowed Headers, all the HTTP headers from the sender are passed to the receiver. This way you will not have any control over what was sent and sometimes it may even confuse the receiver.

Do not access or set a datastore (local variable, global variable, or aggregator) from within a parallel multicast. The parallel multicast spawns multiple threads, but a database transaction cannot be shared over multiple threads. Check if a sequential multicast can be used instead.

Global variables make use of headers to perform DB persist. Memory to these headers remains allocated even after the flow ends. In case the header is holding a large amount of data, it may fail the iflow processing. It is important to release the memory allocated to the header (having the same name as the global variable) before the iflow exits. This, however, cannot be performed from a content modifier – it will need to be done via a script.

Local variables are alive even after the iflow execution is over. Even though the local variable is visible only to the iflow, it is important to note that the memory allocated to the variable is not released when the iflow execution is over. It is important to reset the local variable at the beginning of the flow to avoid any values getting used from the previous flow. It is specifically relevant when the previous flow ended abruptly and the variable may be holding invalid data. For better memory management, it also makes sense to reset the local variables before exiting the iflow.

Never use an Aggregator step in a sub-process. The moment the sub-process exits the handle to the Aggregator is lost but the Aggregator stays allocated. It appears in Message Monitoring. Undeploying the corresponding integration flow does not release the Aggregator. Since Aggregator stores its data in the database, it poses stability and performance threats to the usage of the database.

One thought to “Common errors in SAP CPI”