Seeburger adapter XML-EDI info

I would like know about Seeburger EDI adapter( XML-EDI) how it works, If any body have Seeburger adapter documentation pls. send some to [email protected] Thanks in advance.

Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.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

Similar Messages

Enveloping using Seeburger adapter

For the ones using Seeburger adapters...
How are you coding you envelope tempate (ISA/GS envelope template) using Seeburger adapter as EDI tool. Do you code each and every one of your transaction type / trading partner?
And how do you, for example, send or configure 1 transaction per envelop used for 820s or 100 transactions per envelop for 814s?
Can one you tell how are accomplishing these functions?
Thank you,
Pam

reposting....
Thanks, Pam

Without using Seeburger Adapter can we convert EDI 864 TC to XML

Hello Friends,
Can we convert 864 Transaction code (Text Message) to XML with out an External adapter like Seeburger Adapter? I mean can we write a code in JAVA for conversion? If so, what should i use in that Java code?

Hi
These blog can help u....
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Already discussed thread:
EDI Conversion
Re: Seeburger Splitter adapter!!
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

EDI SEEBurger Adapter

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 .....)

Hi,
Seeburger is a tool which will conver any type of standard EDI format into XML.
All standard EDi mappings are predefined in seburger,we have to install in XI Server and use that standard mappings.
Check this links
SEEBURGER
http://www.seeburger.com
Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.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
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards,
Phani
Reward Points if Helpful

EDI TRADACOM through Seeburger Adapter into PI

Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
Is there a useful tutorial to have a look at ?

>>Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
Yes
>>Is there a useful tutorial to have a look at ?
Well, there is nothing specific avauilable for TRADACOM. TRADACOM is just a type of format as we have EDIFACT OR X12. You can search for EDIFACT related articles/blogs on SCN (there are many). The only thing you then need is to use TRADACOM related mapping name in BIC module wherever you see EDIFACT mapping name.
One more thing, for using TRADACOM, there is a separate licence where Seeburger provides the TRADACOM related SWC with all the formats. So talk to Seeburger about this as well.
Regards,
Prateek Raj Srivastava

Sender / Receiver ID mapping for EDI interfaces and Type of seeburger adapt

We need to set up a interface using Seeburger adapter for Purchase order IDOC to 850 EDI mapping.. After reading from SDN,
1) We can use the standard mapping in BIC MD to do E2X and X2E mapping..
2) We can use any of the AS2, EDI generic adapter, Seeburger FTP adapter or Seeburger SFTP adapter...
How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security...
Also how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID
Also the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping.

Hi Kris,
I had worked in the somehow same scenario, It was IDOC to EDIFACT file.
I can give you few clues which might be helpful
In BIC MD you have to create your own mapping if the standard mapping is not available (First check all the standard mappings in BIC). For your reference you need X2E mapping, as your scenario is IDOC to 850 EDI.
"the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping."
In graphical mapping i created my own mapping, Seeburger has given some sample mappings you can check those for your reference (SEEBURGER_GENERIC_EDI software component). Mostly you have to create your own. You need a document from your functional consultant so that you are able to map correct fields and constants.
"how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID"
This has been generally hardcoded in message mapping (In my case i hardcoded). If any of ur IDOC field contains that data you can map that field. But better Idea is ask your functional expert.
"How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security... "
You can choose adapter according to your requirement. In my case i used File adapter as i have to create file in PI server only. My suggestion you can use SFTP for seeburger
Hope these points are helpfu for u
Regards,
Shradha

Seeburger Adapter Payload & XML Structure for AS2

Does anyone have a sample AS2 message with payload that I can use to test the Seeburger AS2 adapter for a customer in the UK?
Thanks in advance

Hi Frederic
we will be receiving Tradacoms over AS2. I understand that the Seeburger adatper uses the modules from BIC to convert to XI-SOAP ( XML ), but we need to have the schema created for us to construct the data types or to import external definitions into IR. I would like an actual AS2 message without header and signature if possible or a schema version of the tradacoms messsage format for EPOS data. Or if applicable the mapping program that the BIC module will call from the Seeburger adapter. I have the config guide for the BIC, so I know where to configure, but I need the mappping program which will create the XML prior to sending to XI.
Thanks.
I can send you a sample EDI message ( which will be the attachment ) if you give me your email address.
Cheers,
Mark

SEEBURGER AS2 and EDI adapters, PGP Avalanche adapter

Hi,
Kindly anybody can provide the information/links/documentation/PDFs on SEEBURGER AS2 and EDI adapters, PGP Avalanche adapter.
Thanks in advance,
Jogula Ramesh

When u install SeeburgerBIC mapper on ur machine, the below location will contain all the required manuals..
C:\Program Files\Seeburger\CPG EDI Adapter\manuals
You can seach SDN weblogs for Seeburger Adapter details if u don't have the software..
Below is the starting Seeburger Adapter Series weblogs..
/people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
-SM

Seeburger Adapter

Hi all,
I have installed a generic seeburger FTP adapter, but I dont have any VAN connectivity at present. Can I convert the EDI ANSI X12 format to xml with this installation or it requires VAN connectivity to do this.
In this case do we require the BIC mapper? if so how to work with BIC mapper?
In the communication channel, I am able to see the installed Seeburger FTP adapter but it does not show the transport and message protocol. Is this related to the Installation/setup of VAN connection.
Regards,
Nithiyanandam

Hello..
SeeBurger is a leading provider of global business integration solutions.
Market launch of the most successful EDI solution for the automotive industry in 1986.
the company today serves more than 7,000 customers in 42 countries and more than 15 industries through its flagship B2B Gateway and related products and services.
First company worldwide to receive certification for SAP R/3
Building a closer partnership with SAP.
Extended any-to-any-conversion.
The SEEBURGER Business Integration Converter (BIC) is an Any-To-Any Format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex,high performance XML-to-XML mappings or to interface to existing JDBC Data Sources.
Supported EDI formats include: ANSI, EDIFACT, INHOUSE, IDOC, XML Schema, XML DTD, CSV,Delimited Data, positional data, SWIFT, EANCOM and many more.
Mapping Designer, a graphical tool, easily defines data format conversions via drag and drop functionality, enabling easy integration between source and destination files. A central mapping reposiu00ADtory enables comprehensive support of versioning and deployment support, such as self-testing and auditing.
The SAP Exchange Infrastructure message format is based on XML, but it also can work with non-XML data using attachments. In some cases it may be necessary to convert the main XML document in a message, into a non-XML document. The use of BIC is very common in Business-to-Business scenarios where EDI standards are in use.
The Business Integration Converter (BIC) of Seeburger is based on Java JIT Technology and can be used for small real-time messages, as well as very large master data (i.e.Catalogs) batches.
BIC can convert outbound invoices from XML format (used in SAP XI) to an EDIFACT invoice. The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, which is the format SAP XI supports.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. BIC will allow you to do the following
Once you install BIC, you need to do Import the Generator Mappings into the Project Explorer of BIC MappingDesigner.
You can find Generator Mappings as a ZIP file in the following location <BICMappingDesignerInstallationDirectory>\user\bicmd\Exchange and select the file prj_GeneratorMappings.zip.bicmd.
In MappingDesigner select File Import Generator Mappings Zip File prj_GeneratorMappings.zip.bicmd Clik on Add and OK.
Once Import is done you can see Generator Mappings in BIC Mapping Designer.
The SEEBURGER Adapter runs on the SAP WEB AS (J2EE Engine)
The SEEBURGER Adapter is integrated into the SAP Exchange Infrastructure over JCA (Java Connector Architecture)
Consequence :
Supply of the complete SEEBURGER EDI/B-to-B-Technology-Suite within SAP NetWeaver
Central File of Business Content (mappings, integration processes) in the Integration Repository of SAP XI
Central configuration and design by using the Tools of XI in the configuration
Central monitoring and alerting over SAP XI
Seeburger Solutions Overview
BIC Mapping Module
Functional Acknowledgement Solution
Operational Dashboard / Archiving
Invoice Solutions
Communication
The Business Integration Converter (BIC) from SEEBURGER is a converter for the implementation of data formats.
Following formats are available:
ANSI X.12 (American National Standards Institute)
CSV (Comma Separated Variable formats)
EDIFACT (all subsets)
INHOUSE (VDA, flatfiles, e. g. SAP IDoc)
SWIFT (banks)
TRADACOM (Trading Data Communications Standard)
XML (DTDs and SCHEMATA)
Able to classify messages into the following message types:
XML
EDIFACT
Ansi X 12
Tradacom
VDA
IDOC
Swift
Inhouse
XML Ansi X 12
XML EDIFACT
XML Tradacom
XML VDA
XML IDOC
Go through this links..
Some more..
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Reward Points if it is really useful to you.....
Thanks,
Satya Kumar..

Regarding seeburger adapter??

Hello guys
My client is going to implement EDI messages to SAP XI to SAP ERP .It would be great if you let me know the step by step proceedure ??
wht is the use seeburger BIC mapping tool here ??
wht is the configuration should be done at sender side(seeburger as2) adapter??

So this means your customer has purchased a Seeburger adapterlicense which will come with documentation for PI. Use that as first entry point. Such a general question you can not handle well in forum answer.
General first hints:
Seeburger delivers an EDI-adapter which will be deployed into PI. This adapter contains functionality to map between XML and EDIfact format. It also contains (normally) some standard mappings (e.g. for invoice). But be VERY careful with these standard mappings. Not all of them can be used without change. Make detailed tests and do not rely on them.
The BIC mapping designer is not used in PI, but you can see it as a kind of external development or debugging tool in case of problems. You will surely use it, because there are many pitfalls regarding EDIFact and XML/PI. The topic is quite complex.
CSY

Where do we configure Seeburger adapter in case of outbound?

<b>Hello Freinds,
Can you please help me out where do we configure the Seeburger adapter if the sender is EDI ANSIX12...I mean at what point of time we use this Seeburger adapter to convert to XI Specific XML format?</b>

Hi
seeburger adapter is used when you want to convert an EDI format into the EDI XML format so that it can be uunderstand by the XI, bcoz XI can understand only the XI.
seeburger have povioded following adapters
1.AS2
2.OFTP
3.FTP/VAN
4.X400P7
the selection of the adapter depends on the requirement.
Thanks
Rinku

How to configure Seeburger adapter

Hi All,
Can you pls guide me on how to configure adapter? and also why do we need mercerator and converstion agent tools along with see burger adapter?
Can't find any doc on how to configure seeburger adapter!!!
Can someone pls put light on the messageflow when seeburger and these converstion agents are used?
Regards,
Ashish

Hi Ashish,
It is similar like other adapters once it is supplied. But take care about security/firewalls settings.
and also why do we need mercerator and converstion agent tools along with see burger adapter?
>>>Not a mandatory to use along with seeburger.
Can someone pls put light on the messageflow when seeburger and these converstion agents are used?Can't find any doc on how to configure seeburger adapter!!!
>>>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.
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.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Thanks
Sreeram

Seeburger Adapter details

Hi All
What are the things that are to be kept in mind for choosing the Seeburger adapters.
For a logistics based EDIs we are planning to go for Seeburger adapters in XI, i need to know the following things that will help me to contact the seeburger guys for pricing.
1. what are the seeburger components we need to develop the interfaces,(The softwares comes with what all adapters)
2. Does any trial version is available for download?
3. What are the things that will differ from a normal interface development when we use the Seeburger adapters(any1)
steps in IR and ID.
is there any Document from SAP which gives overall picutres the things to be taken care when taking seebuger in XI?
regards
Nisar Khan

Hi Nisar,
1. what are the seeburger components we need
to develop the interfaces,(The softwares comes
with what all adapters)
2. Does any trial version is available for
download?
No trial version available.
3. What are the things that will differ from a
normal interface development when we use the
Seeburger adapters(any1)
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
4) from the followingt types of adapters:
1)BIC Adapter:
There is no BIC adapter it is the client based tool provided by seeburger which has the standard mapping program which does the conversion of EDI-XML and XML-EDI it supports many data types like INHOUSE,CSV, TRADACOM etc. So the std mappinf provided by seeburger has to be deploye first on XI and then used in adapter module tab for conversion.
Using BIC we can create our own data strucutre like we do in IR,we can create our own data type mapping program.
There are three mapping program which is provided by seeburger which is used for creating our own mapping program.
1) Create XML message
2) CreateMappingXML to EDI
3) CreateMappingEDI to XML.
You need to use this mapping program and create your own mapping program for your own structure once it is created import it in BIC.
2)Split997 adapter
The SEEBURGER message splitter module initiates new XI messages as children of a main (or parent) XI Message. A new child (or split) message will be created for each main messages attachment in the split list.
Example of when to use splitter:
1) mail adapter initiates a XI message which contains several attachments, you can use the message splitter to create a new XI Message for each attachment in the original email.
2) U have many UNH messages in one EDI file and u want to create different IDOC for every UNH message for that file that time splitter can be sued.
3)AS2 adapter.
I have provided u the details.
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
I hope I have given u better picture.
Thnx
Chirag

Seeburger Adapter Scenario

Hi Frnds,
I want See Burger ,CIDX Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
Regards,
Raj

Hi Rajshekar,
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
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.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you 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.
AS2 vs OFTPS:
AS2 & OFTPS
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
Please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.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
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration
https://www.sdn.sap.com/irj/sdn/forums
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
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
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.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
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Regards,
Vinod.

SEEBURGER adapter - How much does it help?

We have a PI box just installed and we'll be implementing a few EDI transactions with some business partners.
I was told that SEEBURGER is the preferred EDI adapter for EDI transmissions from PI (XI).
1 - How much does SEEBURGER help the development of PI EDI interfaces? Is there a way to estimate on how much work is saved using it instead of relying on standard? (lets say 10, 20 or 30%)?
2 - I am considering here 2 options (Use SEEBURGER or not). Is there a better alternative?
Thanks
Leonardo

Hi,
For EDI implementation there are ways by which u can implement with XI
1) Using third party seeburger adapter.
2) Conversion agent
3) Writing module.
Preferred one is seeburger.
1) It has std XSD available which we just need to import into External definition
2) It has std mappings for all the message type which converts EDI to XML and XML to EDI format.
3) Provides different adaters
4) BIC tool
5) Many adapter modules.
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you 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.
It provides std mapping program which does the conversion of EDI to XML and XML to EDI which need to used in XI comm channel module tab.
Thnx
Chirag

Seeburger adapter XML-EDI info

Similar Messages

Maybe you are looking for