02CONNECTED ENTERPRISE
Integration Consulting and Architecture
We build, review and monitor the traffic between your systems.
We design secure, observable end-to-end integration architectures across SAP Integration Suite, SAP PI/PO, SAP NWBPM, APIs and EDI.
OUTCOMES FIRST
Business outcomes
- 01
Uninterrupted data flow
Visible status, consistent error handling and fast intervention on critical interfaces.
- 02
Manageable architecture
Standard naming, versioning and ownership across APIs, integration flows and EDI assets.
- 03
Safe modernisation
A prioritised move to SAP Integration Suite that keeps what has been built in SAP PI/PO and SAP NWBPM.
OVERVIEW
Scope and approach
Processes that run from order to invoice, from production to logistics and from the bank to trading partners depend on integration to run on time, correctly and traceably.
We position SAP Integration Suite as the modern integration target without ignoring existing investments in SAP PI/PO and SAP NWBPM. Based on the interface inventory, usage volume, protocol, error model and business criticality, we build a roadmap for coexistence or migration.
From a simple file transfer to multi-step B2B scenarios, we design API, event, file and EDI flows with shared rules for security, observability and lifecycle. That way an integration no longer depends on the person who built it; every flow is managed by the same rules.
FOCUS
What do we solve?
Hidden dependencies
We bring interfaces, their owners, data contracts and critical business chains together in one inventory.
Recurring errors
We make retry, idempotency, alerting, logging and operational responsibilities part of the architecture.
Scattered B2B/EDI
We move partner, message, channel and certificate lifecycles into a model that can be managed end to end.
WHAT WE OFFER
Capabilities and scope
SAP Integration Suite
In SAP CPI (new name: SAP Integration Suite, Cloud Integration) we do more than build iFlows; we set up package structure, naming, the error pattern and transport discipline together with your team.
SAP CPI - Integration SuiteSAP PI/PO
Improvement, operation and migration analysis of existing interfaces.
SAP PI/POSAP NWBPM
Modelling and orchestration of processes that combine human and system steps.
API architecture
Security, versioning, quotas, observability and reuse principles.
End-to-end EDI
Management of ORDERS, DESADV and INVOIC messages and trading partner communication channels.
Operations
Central logging, alerting and regular performance reports. Monitoring and alerting run 24/7; support is provided in business hours.
MIGRATION
Moving from SAP PI/PO to SAP Integration Suite
Maintenance for SAP PI and SAP PO 7.5 follows SAP NetWeaver 7.5. Mainstream maintenance ends at the end of 2027; extended maintenance to the end of 2030 comes at the same price and terms as SAP Business Suite 7. In SAP's own case for migrating, the new capabilities sit in SAP Integration Suite: API management, event-driven integration and prebuilt integration content.
Each interface gets its own decision: what the tool can move is moved, the rest is rebuilt, and what is no longer used is switched off. We take the interface inventory and prepare a migration plan scenario by scenario. SAP's Migration Assessment classifies scenarios as Ready to migrate, Adjustment required or Evaluation required and estimates the effort.
SAP PI/PO maintenance timeline
- 7.4 and earlier: end of mainstream maintenanceNo extended maintenance option
- 7.5: end of mainstream maintenanceFollows SAP NetWeaver 7.5
- 7.5: end of extended maintenanceSAP support ends after this date
Four differences in the migration decision
Where it runs
SAP PI/POOn-premise, on SAP NetWeaver. The company manages infrastructure, backups and capacity.
SAP Integration SuiteA cloud service on SAP BTP managed by SAP. Flows whose data must stay inside the company network run on Edge Integration Cell, which the company operates on its own Kubernetes cluster.
APIs and events
SAP PI/POServices are exposed as SOAP or REST endpoints; it has no structure suited to an event-driven architecture, and the JMS adapter is used where needed.
SAP Integration SuiteAPI Management for policies, quotas and usage analytics; Advanced Event Mesh for publish and subscribe; Kafka and AMQP adapters.
Updates
SAP PI/POThe company applies and tests support packages with its own resources.
SAP Integration SuiteSAP updates the service monthly.
Lifecycle
SAP PI/POMainstream maintenance for 7.5 ends at the end of 2027, extended maintenance at the end of 2030.
SAP Integration SuiteA cloud service; SAP publishes its new integration capabilities on this side.
- The two layers run side by side for a while: a moved scenario is tested with the same test messages, and the old scenario in SAP PI/PO is switched off once the results match.
- Ready to migrate does not mean automatic migration; it shows that the features in use have a counterpart in SAP Integration Suite. Some adjustment may still be needed after the move.
QUALITY
Architecture and quality review
On SAP PI/PO and SAP Integration Suite projects, our expert consultants take a technical role to hold the project to its standards. They make sure the right architecture, performance and working standards are applied; we set up package structure, naming, the error pattern and transport discipline together with the project team.
A review is a recorded step, not a verbal sign-off. Every interface goes through the same checklist before go-live; findings are logged with an owner and a closing date, and nothing is transported while a finding is open. A shared pattern also makes it easier to estimate the effort for a new interface before work starts.
A small detail handled at the start becomes a big advantage years later.
Interface checklist
Every interface passes these nine checks before go-live; nothing is transported while a finding is open.
Design and naming
- Compliance with the naming standard
- Synchronous or asynchronous choice
- Message size and packaging
Error handling and security
- Error branch: notification and retry
- Credentials are not written into the flow; they are read from security material
- Idempotency: the same message is not processed twice
Performance and handover
- Performance criterion: target time and volume
- Load test result
- Operations handbook
ReviewA second consultant gives every check a status
- PassedThe check is closed
- Revision or on holdTracked with an owner and a closing date
- FindingNo transport to production until it is closed
- DEV
- QA
- PROD
Nothing moves from QA to production while a finding is open.
- Design standard and architecture fit: naming, error handling, retry and logging rules are written down at the start; the synchronous or asynchronous choice, message size and idempotency are reviewed before go-live.
- Performance acceptance criterion: each interface gets a target processing time and volume threshold, and the load test is run against that threshold.
- Code and mapping review: a second consultant reviews the mapping logic, the functions used and custom developments.
- Transport and release discipline: the transport path between development, test and production and the rollback scenario are fixed at the start; nothing is developed in production.
- Handover documents: the interface inventory, dependency map and operations handbook are delivered as project outputs.
LAYER
SAP and non-SAP systems in one layer
We build and run the data flow between SAP and non-SAP systems on SAP PI/PO or SAP Integration Suite. Every flow passes through the same layer, with shared monitoring and error handling.
EDI flows, bank and logistics integrations and e-document providers connect to this layer. We also implement the prebuilt integration scenarios for Salesforce and SAP SuccessFactors.
In SAP CPI (Cloud Integration), an adapter makes the connection. The SAP Integration Suite connectivity list has more than 80 standard adapters, some of which depend on the service plan. For non-SAP cloud applications without one there are the prebuilt Open Connectors connectors, and if needed custom adapters built with SAP's development kit.
The integration layer
Instead of point-to-point connections, every system connects to one manageable layer.
SAP systems
- SAP S/4HANAOn-premise or cloud
- SAP ECCOn-premise
- SAP SuccessFactorsSAP cloud
- SAP AribaSAP cloud
SAP PI/PO or SAP Integration SuiteRouting, mapping, monitoring
Non-SAP systems
- EDI trading partnersAS2, SFTP
- BanksPayments and statements
- Logistics and carriersShipping and tracking
- e-Document providere-Invoice, e-Dispatch Note
- Salesforce and other SaaSCloud applications
- Cloud Connector
- On-premise systems connect without being exposed to the internet.
- DEV QA PROD
- Nothing is developed in production; packages move between tenants.
SAP Integration Suite capabilities
Capabilities are activated one by one within the same subscription; which ones are available depends on the service plan.
Flows, APIs and events
- SAP CPIDesigning, running and monitoring iFlows
- API ManagementPolicies, quotas, Developer Hub, usage analytics
- Advanced Event MeshDistributes events across a broker network with publish and subscribe; subscribed separately
- Open ConnectorsPrebuilt connectors for non-SAP cloud applications without an adapter
- OData ProvisioningPublishes SAP Gateway services from SAP Business Suite as OData endpoints
SAP Integration SuiteSAP BTP
B2B and assessment
- Integration AdvisorB2B message and mapping guidelines (MIG, MAG)
- Trading Partner ManagementTrading partner profiles and agreements
- Integration AssessmentThe integration style and technology for each interface
- Migration AssessmentClassifies SAP PI/PO scenarios and estimates the effort
SAP CPI adapters
The SAP Integration Suite connectivity list has more than 80 standard adapters.
SAP applications
- IDoc
- RFC (receiver only)
- XIABAP proxy
- SuccessFactors
- Ariba
- SAP Master Data Integration (receiver only)
- AIGenerative AI Hub (receiver only)
Web services and files
- HTTP(S)
- SOAP
- OData
- SFTP
- FTP
- JDBC (receiver only)
- SMB
- NFS
B2B and EDI
- AS2
- AS4
- OFTPEdge Integration Cell
Messaging and events
- JMS
- Kafka
- AMQP
- Advanced Event Mesh
- RabbitMQ
- IBM MQ
- Azure Service Bus
- Google Pub/Sub
- Amazon EventBridge (receiver only)
Cloud storage and data
- Amazon Web ServicesS3, SQS, SNS
- Azure Storage
- Google Cloud Storage
- Microsoft SharePoint
- Microsoft OneDrive
- Dropbox
- Google BigQuery (receiver only)
- Snowflake (receiver only)
- MongoDB (receiver only)
Business applications
- Salesforce
- Microsoft Dynamics CRM (receiver only)
- ServiceNow (receiver only)
- Workday (receiver only)
- NetSuite (receiver only)
- HubSpot (receiver only)
- Coupa (receiver only)
- Jira (receiver only)
- Slack
- Microsoft Teams (receiver only)
- Google Workspace (receiver only)
- Twilio (receiver only)
- Zendesk (receiver only)
- Shopify (receiver only)
- Docusign (receiver only)
Receiver-only adapter: the tenant calls the system; messages from the system enter through an HTTPS, SOAP or OData sender.
- Open ConnectorsPrebuilt connectors for non-SAP cloud applications that have no adapter in the list.
- SAP Business Accelerator HubSome adapters come from here as packages; which ones you can use depends on your service plan.
- Adapter Development KitSAP's kit for building a custom adapter and deploying it on your tenant.
Adapter names follow SAP's SAP CPI (Cloud Integration) adapter list. OFTP and the RFC sender run only on Edge Integration Cell.
- SAP SuccessFactors and SAP Ariba run in the cloud and do not go through Cloud Connector; SAP provides prebuilt integration packages for connecting them to ERP.
- For flows whose data must not leave the company network there is Edge Integration Cell: the flow runs in your own landscape, while design and monitoring stay in the cloud.
- Every flow carries a correlation ID, the shared error pattern and alerts; a failed message is seen in monitoring, corrected and reprocessed.
- KnowledgeWhat is SAP Integration Suite?
REPORTING
SAP PI/PO performance reports and SAP CPI monitoring
We prepare daily, weekly and monthly performance reports with improvement suggestions for SAP PI/PO. The reports come from the raw data in message monitoring and, on request, include error details and the action needed to fix each error. The aim is to see a threshold coming and act before it is crossed.
On the SAP CPI (Cloud Integration) side, continuous monitoring takes the place of periodic reports: we watch failed messages and compare the number of processed messages with the message quota in the subscription.
To watch several systems from one place we use SAP Cloud ALM. Integration & Exception Monitoring covers both SAP CPI (Cloud Integration) and the Java side of SAP PI/PO: messages can be searched by business data such as an order number, rule-based alerts are set for failed messages and exceptions, and each alert is emailed to the right person. Health Monitoring warns before a certificate expires or JMS resources run out.
Monitoring and reporting flow
Three sources come together in one reading: alerts arrive at once, and the SAP PI/PO report is prepared weekly and monthly.
- SAP PI/POMessage Monitor and channel monitoring in PIMON
- SAP CPIFailed messages and licensed message consumption
- SAP Cloud ALMIntegration & Exception Monitoring, Health Monitoring
ReadingA one-off error or a pattern?
- At onceAlertFailed message and exception alerts are emailed to the right person
- DailyOperations checkFailed messages, stuck queues, scheduled jobs
- Weekly · monthlySAP PI/PO reportVolume and time trends, recurring errors, prioritised recommendations
Indicators tracked
- Message processing time
- Error rate
- Queue backlog
- Message volume
- Licensed message consumption
- Recurring errors
- Certificate expiry
- Interfaces nearing a threshold
- A one-off error or a pattern: a single error line means little on its own. If it repeats on the same interface during the day there is a structural issue underneath, and the report says so clearly.
- Slowing interfaces: in SAP PI/PO, interfaces whose processing time rises well above their weekly average are flagged. The cause is usually message size, mapping complexity or the target system's response time.
- Volume and thresholds: message count, error rate and queue backlog are compared with the previous period in every report; items nearing a threshold are flagged in advance.
- Message quota: the number of messages processed in SAP CPI (Cloud Integration) is tracked, and you hear from us before it nears the quota in your subscription.
- Monitoring and alerting run 24/7; intervention, support and interpretation of the reports happen in business hours.
METHOD
How we work
- 01
Take stock
We record interfaces, protocols, owners, data volumes, errors and criticality.
- 02
Set the target
We define integration patterns, platform placement and security principles.
- 03
Transform
We build and test in priority order and plan an uninterrupted cutover.
- 04
Operate
We set up SLAs, observability, support and continuous optimisation.
COMMON QUESTIONS
Frequently asked questions
Should companies on SAP PI/PO move to SAP Integration Suite right away?
The migration decision should be taken in waves, based on interface criticality, technical fit, licensing and the operating model. We first make the real effort visible with an inventory and Migration Assessment.
Does the EDI service cover only the technical connection?
No. Bringing trading partners on board, message mapping, communication channel, certificates, testing, monitoring, reprocessing and operational responsibility are handled end to end.
How is traceability of integrations ensured?
A correlation ID, central logging, alerts with business context, performance indicators and an ownership model are built into the design of every flow.
GET STARTED
Take stock of your integration landscape with us
We review your interfaces, message volumes and accumulated technical debt, and prepare a prioritised roadmap.
THE COMPLETE JOURNEY
Other areas of expertise
- 01ENTERPRISE CORESAP S/4HANA Consulting
- 02You are hereIntegration Consulting and Architecture
- 03CONTINUITYSAP AMS Support
- 04LOCALIZATIONRollout Project Consulting
- 05FULL CONTROLProject Management Services
- 06DIGITALIZATIONNegzel n-Solutions
- 07CLOUDRISE with SAP
- 08EXPERIENCEOur Expertise
- 09FUTURER&D and Artificial Intelligence
- 10SAP MODULESSAP Consulting