EDI SEEBurger Adapter

Former Member · ‎10-16-2007

We are evaluating XI for ANSI X12 EDI , Have some EDI Quesitions using SEEBurger Adapter.

1) Does SEEBurger Adpater has ANSI X12 Enveloping and De-Enveloping capabilities ??? If Yes,how this is configured /Developed.

2) Does SEEBurger Adapter has capability of generating sequential ISA control numbers by Trading Partner ??? If Yes,how this is configured /Developed.

3) Can It perform EDI Structure validation based on the EDI standard rules (For eg: Looping structures, Element qualifier restriction list .....)

Former Member · ‎10-17-2007

Sushil,

This is Basic EDI requirement that any company does EDI implementation. If you have worked in EDI this is like any other EDI messages requirement talking to outside world . I think i have explained in my previous reply what is the requirement for EDI Messages . Anyways , Here it is When I send say EDI 855 Msg to a TP , i envelope 855 message using ANSI X12 EDI standard ISA and IEA and GS and GE segments . One of the element in above mentioned segements has control number which is incremented every time a new ISA msg is sent to TP using previous Control number for Eg , If i send first 855 Say Control # is 001 and next time When I send another 855 this time control # as 002 . Hope i explained your quesition. Thanks for taking interest with these EDI quesitions.

Former Member · ‎10-17-2007

Thanks Sushil, Still i couldn't get the generation of Sequential ISA Control # by partner for each EDI Transaction we communicate , Here is what I am talking about , See Highlighted elements below . In the EDI world Each time when we send ISA msg our current EDI tools increment the control numbers so that TP keeps track of any missing ISA messages (This is EDI Standards). if there is a skip in the control number TP will alert the sending partner.

ISA00 00 ZZTESTPARTNER ZZTESTING 0709181208U004010000032800P>

GSSWTESTPARTNER9999999992007092512083285X004010

ST

-

Actual Transaction elements

-

SE

GE13285

IEA1000003280

Former Member · ‎10-17-2007

Thanks for your quick response , I appreciate your input . I had read all the blogs regarding SEEBurger with XI before posting my Que's. I didn;t get a concrete information or answer that, How SEEBurger Adapter can Envelope or De-envelope (I mean ISA-IEA and GS-GE ) EDI Transaction sets, Generate ISA Control numbers by trading partner, or Validate EDI transaction set structures by applying EDI std rules , or Generate FA's to TP. Can it do out of the box ?? If NOT how this is done , If anyone can explain in brief , I would really appreciate it. We do heavy EDI (80% of business)and that I need to evaluate the development effort and cost if we add another layer of XI on top of existing EDI infrastructure (TLE,Cyclone,Mercator), due to which I need to clearly understand the Tech details of it in brief.(My background working in SAP/EDI for the past 9 yrs) .

Former Member · ‎10-17-2007

Hi Girish !!

SeeBurger adapter doesnot come with XI and it is not free. They have different adapters like AS2, FTP etc. So depending upon your requirements you will purchase. For pricing you should check in seeburger.com.

Once you purchase this you have deploy the adapter in J2EE and you will import the SWC into IR. They have some predefined mappings. You can directly use them also.

Seeburger adapter is the B2B EDI Adapter.Seeburger adapter is also many types adapters:

1)BIC Adapter

2)Split997 adapter

3)AS2 adapter.

Based on your usage you have to configure thes adapter.for example

AS2 sender adapter:

1)AS2

2)Asynchor MDN Setting:

a)SSL Certificates and Clint certifactes.

b)SSL host name:HTTP Timeout,MDN Retry interval and MDN Retry count

c)use proxy

AS2 Receiver adapter:

a)HTTP:server ,port ,url and http time out

b)proxy:

c)AS2:Compress,Sign.Encrypt,Sign MDN use proxy and Xi Message

Seeburger Adapter have more funcations:it is very good to Moniter Message.

1)Archiving

2)Message monitor

3)message Spliter

4)Mapping Variable

5)Resource manger

If you nedd any more information regarding the Seeburger ,send your maild then i will send the some more docs to you.

Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.

These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.

Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.

The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:

1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)

2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.

3. create a one to one mapping between input en output.

4. export the metadata in xsd or sda format for import in XI

5. generate an SDA which can be deployed in XI and used as a module.

Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.

The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:

1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)

2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.

3. create a one to one mapping between input en output.

4. export the metadata in xsd or sda format for import in XI

5. generate an SDA which can be deployed in XI and used as a module.

Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:

http://www.seeburger.com

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf

http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt