In this lesson, you learned that EIC has a defined but expanding functional scope - it supports Integration Flows, API proxies, and a broad adapter set, but is not a full replacement for the Cloud Integration Runtime, and gaps must always be validated against SAP Note 3391207, the single authoritative reference that travels with every EIC release. Three adapters - RFC Sender, NFS, and OFTP2 - are exclusive to EIC and cover private-network communication protocols that are architecturally impossible in the cloud runtime. EIC is the right choice when local execution is genuinely required: data residency, ground-to-ground scenarios, EIC-exclusive adapter needs, and SAP PI/PO migration of on-premise scenarios are the strongest justifications; for everything else, the Cloud Integration Runtime is simpler, fully managed, and feature-complete. SAP is actively investing in EIC - adapter coverage and platform support are expanding - but the roadmap is not a planning substitute: always check the current version of SAP Note 3391207 before committing to a deployment.
The Unit 4 Closing ties together all four units and returns to Global Manufacturing AG one final time - showing how everything covered in this course applies to a real deployment decision.
| What you learned | Why it matters |
| EIC is an additional runtime option within SAP Integration Suite - not a standalone product. | All design, monitoring, and lifecycle management always go through the SAP Integration Suite Cockpit, regardless of runtime. |
| EIC does not have complete feature parity with the Cloud Integration Runtime. | Deployment decisions must be based on verified scope. Gaps can block migrations or cause rework. |
| SAP Note 3391207 is the authoritative, continuously updated scope reference. | It is the only reliable source - always check the current version before planning, not a summary from a previous project. |
| RFC Sender, NFS, and OFTP2 are EIC-exclusive adapters. | These adapters identify scenarios where EIC is technically required - they are the strongest technical justification for an EIC deployment. |
| Use EIC only when local execution is genuinely required. | For cloud-to-cloud or cloud-to-on-premise without data residency constraints, the Cloud Integration Runtime is simpler, fully managed, and feature-complete. |
| Migration from SAP PI/PO to EIC requires compatibility assessment first. | Not all PI/PO scenarios migrate without modification. Consult migration tooling before planning. |
| The EIC product roadmap shows continued SAP investment. | The gaps are narrowing - but roadmap information is not a delivery guarantee. Verify against SAP Note 3391207. |