Hello everyone,
We are implementing Concur cloud solutions implementation, which involves integrating SAP ECC on premise. In our landscape, we're also utilizing the CI/CPI middleware. I'd like to address a question we're currently facing regarding our chosen integration method within ICS.
ICS offers two integration options: one through middleware and the other is a direct approach. During our assessment, we've identified that while some interfaces can seamlessly utilize ICS, others such as Employee Data, Payroll, Exchange rates, etc., might require either a flat file or a Concur API approach outside ICS. I have two specific questions that I'd like to address: What would be the most suitable approach, given that not all interfaces are compatible with the ICS method? Should we consider employing CPI (Cloud Platform Integration) for all interfaces, even if it acts as a pass-through for ICS interfaces? This approach could potentially provide encryption and SFTP capabilities for certain interfaces. Please provide insights into the factors or reasons and any references for best practices that support this choice. For those interfaces that won't utilize the ICS add-on, would it be advisable to opt for the Concur API approach by using custom integration flows or standard iFlows wherever they are available? It's important to note that we are not inclined towards the flat file approach. Your input on these matters would be greatly appreciated.