Page tree
Skip to end of metadata
Go to start of metadata

Applies to:

SAP Process Integration (XI 3.0, PI 7.0, PI 7.1, PI 7.3)

 Table of Contents

  1. Introduction
  2. Possible options for EDI communication with SAP PI.
  3. Seeburger Versions and Availability
  4. References
  5. Related Contents


This wiki would talk about the usage of Seeburger set of products to strengthen the B2B capabilities of SAP PI. Seeburger in partnership with SAP provides rich set of adapters and tools to overcome the EDI communication related limitation of SAP PI in a standard and organized way.

Seeburger is a much talked about topic these days or let's say since quite a few days. But there is very little information available on SDN when it comes to various aspects of Seeburger. Therefore this wiki is a compilation of related information at a single point. It is considered that the readers are comfortable with basic PI terminologies and EDI (Electronic Data Interchange) to some extent. Let us start with what Seeburger means to a PI consultant.

EDI format are widely accepted across the globe for both inter and intra organizational business information exchange. SAP PI being the long term strategic integration solution promoted by SAP should incorporate the capabilities to communicate this EDI format through them. However, there is no EDI communication specific adapter which is delivered as part of standard PI license.

Possible options for EDI communication with SAP PI

  • Create an adapter module that incorporates all the EDI parsers capabilities to convert specific EDI format into EDI-xml or vice-versa. 

The Dark Side: The problem with this approach is that even if you are able to convert the EDI-xml to EDI or vice-versa, you are still missing the protocol that will be used for communication e.g. AS2, X400. Another problem is that you need to create the adapter module for various kind of EDI format like EDIFACT, X12, TRADACOMS etc

  • Use Conversion Agent for converting EDI into EDI-xml and vice-versa.

The Dark Side: The issue with this approach is same as that of first case.

  • Create your own adapter.

The Dark Side: Only issue with this approach is if your organization uses multiple protocols with their customers, then it would mean that multiple custom adapters need to be created for each protocol. This would delay the overall project timeline certainly by months.

  •  Purchase a third-party adapter.

Seeburger, being a market leader in providing EDI related solutions, has exposed a rich set of EDI adapters which gets integrated to SAP PI adapter engine seamlessly. Seeburger adapters are SAP certified and are now widely used by Customers enhancing their PI capabilities.

Seeburger Vesions & Availability

Seeburger have middleware of their own called as Seeburger BIS (Business Integration Server) which could work independent of SAP PI. However, my discussions will be concentrated on only those parts of Seeburger (adapters) which are applicable to SAP PI based EDI communication using Seeburger adapter suite. The versions of Seeburger adapters that are widely used these days with XI 3.0 and PI 7.0 are of 1.X series 1.8 being the latest. With PI 7.1, 2.X version of Seeburger has evolved which incorporated the adapter engine specific changes that are required with PI 7.1, 7.11 and 7.3. Detailed release information can be found in note 890721, 890722.

We will now have a look at the few resources provided by SAP with regards to Seeburger adapters:

       Note: Before downloading make sure that you have purchased Seeburger license. Otherwise you won't be able to find required links.


Seeburger's Website

B2B Communication Strategy

Adapter and Module Development

Related Content