SEEBURGER Blog - Your Engine driving the Digital Transformation

SEEBURGER

The Engine Driving Your Digital Transformation

ERP system

EDI Connection of SAP S/4HANA with APIs Instead of IDocs – Protect Your Investment

The IDoc structures used for SAP R/3 or ERP ECC continue to be available for connecting SAP S/4HANA. External business partners can be integrated if these IDoc structures are used in conjunction with an EDI solution. SAP also offers API-based interfaces and the SAP API Business Hub eases conversion of the connections from SAP S/4HANA environments to API interfaces – including IDoc-based connections between SAP ERP and the EDI solution. […]

|
Italy via the NSO

E-Ordering Mandate in Italy via the NSO Platform – Postponed to 1st of February 2020

Italy mandates e-ordering for suppliers of the national healthcare system, referred to as SSN (Servizio Sanitario Nazionale). For e-ordering the NSO platform “Nodo di Smistamento degli Ordini di acquisto delle amministrazioni pubbliche (NSO)”, known from the Emilia-Romagna region, is mandatory to be used by 1st of February 2020 (initial deadline was 1st of October 2019). […]

|
BIS 6.7

BIS 6.7 – Next Generation Mapping Technology for the Digital Shift. Taking Data Integration to the next Level

Two new powerful components expand the SEEBURGER portfolio for integration of different types of data formats: The BIS Mapping Engine and the BIS Mapping Designer. Both components benefit from our extensive expertise in designing scalable and robust data integration components as well as conversion design tools fostering user’s productivity. […]

|
Comparison of EDI and API

Comparison of EDI and APIs – Handling of Content Errors

When data is exchanged between business partners, errors also occur with regards to content. It is sufficient that a target system simply does not interpret plausible data correctly. With EDI as batch-driven file exchange, error handling typically takes place on the target system, whereas with coupling using APIs, the calling system only receives an error message back and is responsible for error handling itself. […]

|