cancel
Showing results for 
Search instead for 
Did you mean: 

Few clarification on SeeBurger adatpers.

Former Member
0 Kudos

Hi All,

Presently we have EDI middleware tool which converts the IDOC into EDI and EDI into IDOC. On the outbound scenerio, the converted EDI flat file is sent to VAN and on the inbound scenerio the converted IDOC file is sent to SAP system.

We have PI system to send XML files to our non EDI partners. We decided to eliminate the existing EDI middleware tool and install SeeBurger in XI/PI.

Based on the bussiness environment and current requirement we evaluated the list ( [http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f0c0d023-a296-2b10-1ea0-bb15d4498035|http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f0c0d023-a296-2b10-1ea0-bb15d4498035] ) of SeeBurge adapters and we decided to purchase the below SeeBurger adapters.

Retail Industry Adapter

Cross Industry Payment Adapter.

FYI : I'm aware that for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program(BIC) at the adapter module which does the conversion. For this module I need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.

I believe that , to achieve this(IDOC->PI/SeeBurger->VAN) design, I don't need any additional technical adapters. Please correct me if i'm not right here.

Thanks,

Accepted Solutions (1)

Accepted Solutions (1)

former_member854360
Active Contributor
0 Kudos

Hi,

For connecting to VAN system you need to Buy Seeburger VAN adapter.

I am not not sure is it comes under the below packages you mentioned.

Retail Industry Adapter

Cross Industry Payment Adapter.

VAN Client Adapter (included in SEEBURGER EDI Adapters)

http://www.seeburger.com/9464/

former_member854360
Active Contributor
0 Kudos

Hi ,

Retail industry adapter contains VAN also.

Retail industry standard mappings and communication protocols include:



EDI Conversion for EDIFACT EANCOM subset and ANSI X.12. Mapping templates for retail business documents such as: 
Orders  (inbound/outbound) 
Order response  (inbound/outbound) 
Dispatch advice (inbound/outbound) 
Invoice (inbound/outbound) according to EDI Standards (EDIFACT EANCOM Subset, ANSI X.12)
Basic acknowledgment message handling supporting ANSI 997 and EDIFACT CONTRL message
Communication:
VAN-based communication (incl. X.400 VAN support)

http://www.seeburger.com/9451/

Answers (3)

Answers (3)

Former Member
0 Kudos

Thank you all for your replies.

Shabarish_Nair
Active Contributor
0 Kudos

usually the seeburger adapters are purchased as a bundle. So for the transfer technology to be supported, you will need to have the AS2 or the VAN adapter etc along with it.

Former Member
0 Kudos

Hi,

VAN(Value Added Networks)

VANs also provide an advantage with certificate replacement in AS2 transmissions. Because each node in a traditionally business-related AS2 transmission usually involves a security certificate, routing a large number of partners through a VAN can make certificate replacement much easier.

The FTP/VAN Adapter supports the following protocols:

• IBMIE VAN, all report options.

• GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.

• EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.

• Sterling Commerce and Sterling IIB.

• MCI EDI*Net.

The following FTP options are supported:

• SSL, both IMPLICIT and AUTH_TLS support, server authentication.

• All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.

• Active and Passive connection modes.

• "KeepAlive" feature.

• Binary, ASCII and custom transfer types

Regards,

Raju.