How SEEBURGER Business Integration Suite connects to SAP S/4HANA (also SAP ECC)
SAP-certified S/4HANA connector
SEEBURGER states the connector is SAP-certified. It exchanges business documents with S/4HANA using IDocs or SAP APIs, depending on the process, and handles protocol conversion (AS2, SFTP, OFTP2 and others) to trading partners.
ECC to S/4HANA EDI migration
Existing ECC IDoc-based partner flows can be re-pointed to the S/4HANA system, with maps kept where the document structures still apply. Plan for message type changes and field differences in the new release.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Trading partner | SAP | Orders, forecasts (EDI or API) | Partner transmits |
| SAP | Trading partner | Order confirmations, ship notices, invoices | Order, delivery and billing events |
| SAP | Tax authority or buyer portal | E-invoice | Billing document posted |
| SAP | Bank or partner | Files via managed file transfer | Scheduled job |
Setting it up
- 1Inventory existing EDIList partners, document types, maps and transports currently running on ECC.
- 2Choose connector and transportDecide IDoc vs API per process and confirm the certified connector version for your release.
- 3Set up SAP partner profiles and portsReconfigure WE20 and WE21 for the S/4HANA system and test connectivity.
- 4Migrate or rebuild mapsReuse maps where structures match, revalidate where S/4HANA changed fields.
- 5Re-certify with key partnersSome partners require re-testing when your sender system changes.
- 6Cut over in wavesMove low-risk partners first, run parallel where partners allow.
What usually breaks
- !Assuming ECC IDoc structures are unchanged in S/4HANA. Business Partner and material number changes affect segments.
- !Partner endpoints pinned to old IP addresses, certificates or AS2 IDs break at cutover.
- !E-invoicing rules differ by country and change often, so keep the country schedule with the project.
- !Duplicate processing if the old and new systems both consume the same inbound feed during parallel run.
- !Missing monitoring ownership: errors sit in IDoc queues for days with no one assigned.
A private AI layer across both systems
Partner onboarding checklist
From a partner's spec and your SAP configuration, draft a gap list of missing master data or partner profile settings for review.
Failed message triage
Read failed messages in the suite and IDoc status in SAP together and explain the likely cause.
Migration regression comparison
Compare ECC and S/4HANA outputs for the same sample orders and flag differences.
Try it here, free
IDoc to EDI X12 Mapping Worksheet (INVOIC to 810)
An editable mapping sheet that pairs IDoc segments and fields with X12 segments and elements, with rules and open questions, exported as an Excel spec.
When something else fits better
- SAP Integration Suite is the native option if you want to stay inside SAP BTP.
- OpenText Trading Grid is a similar managed network, which may suit you if your partners already use it.
- A managed retail-focused service such as SPS Commerce may be simpler for retailers only.
Frequently asked questions
Is the SEEBURGER connector SAP-certified?
SEEBURGER describes its S/4HANA connector as SAP-certified. Ask for the certification scope and the release matrix, since certification applies to specific versions and interfaces.
Can I keep my ECC EDI maps?
Often partly. The aim is to move ECC EDI over during migration without rebuilding every partner, but S/4HANA data model changes mean maps must be validated, not assumed.
Does it handle more than EDI?
Yes, SEEBURGER positions the suite for B2B and EDI, e-invoicing, managed file transfer and API integration.
Pairing documented at www.seeburger.com/integration-marketplace/connectors/sap-s4hana . SEEBURGER Business Integration Suite is a product of SEEBURGER; Netray is independent and not affiliated with either vendor.