Seeburger EDI adapter Vs Seeburger BIC adapter

hi,
what is the difference between Seeburger EDI adapter Vs Seeburger BIC adapter.any docs please.
thank you,
babu

Hi,
Seeburger EDI adapter Vs Seeburger BIC adapter.
If your edi file converts with BIC mappers then you would have to use BIC adapter or BIC modules, i hope BIC modules, next EDI Adapters see the below links to get more details..
/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.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards
Chilla

Similar Messages

Seeburger EDI Adapter: skill preperation

Hi everybody,
we will soon install the seeburger EDI Adapter for some EDI scenarios.
Could anybody suggest who we can prepare ourselfs for this?
Which documents should we read. Whcih additional knoledge do we need to have (e.g. BIC Mapping Designer)
Thank you for any useful hints
Regards Mario

The seeburger adapter comes with documentation from Seeburger on how to use it. That is the best document you can read to implement.
Others -
About EDI - EDI Overview
BIC - /people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Of course search SDN itself for more info

EDI Integration---Using Seeburger Adapter

Hi All,
I have a below requirement.
EDI----->XI--
>SAP and vice versa.
I am new to EDI integration,i would like to know the procedure steps to do the above scenario.
Thanks in advance,
AVR

Hi,
How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005
http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
Handling EDI interfaces using Seeburger BIC modules
Regards,
Priyanka

SEEBURGER integration using PI: BIS, BIC, AS2 Adapter, FTP ?

Hi All,
we are exploring on EDI project, where sap ecc is integrated with an seeburger edi partner via PI.
the integration involves: EDI ANSI X12 documents like 850, 855, and UN/EDIFACT documents like DESADV
for this while searching, i came across:
1. the wiki content created by Prateek Raj Srivastava, http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
2. a presentation by sam raju http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf?QuickLink=events&overridelayout=true
I was trying to find out, what all we need in PI..
in PI, what type of communication channel can be used,
can we use FTP adapter, that is comes by default in PI.
or is it necessary to buy something (adapter or content) from SEEBURGER.
after searching little more on seeburger front, got to know that there are:
BIS (Business Integration Server)
BIC (Business integration Converter)
AS2 adapter.
is BIC is an adapter, that we can select as adapter type, while creating the communication channel.
the presentation by sam raju, describes "Configuring BIC as Module", if BIS is configured as a module, what is the type of communication channel in ID.
is AS2 adapter is part of BIS or BIC.
for integration using PI, out of BIS, BIC, AS2, what all is minumum required?
what are the roles of BIS, BIC and AS2 in the context of integration using PI.
thanks in advance.
Madhu_1980

>>in PI, what type of communication channel can be used,
Any. Using Seeburger Adapter for EDI communication is not mandatory.
>>can we use FTP adapter, that is comes by default in PI.
Yes, you can use it to send even EDI files.
>>or is it necessary to buy something (adapter or content) from SEEBURGER
To convert EDI-xml file to EDI, you have to use Seeburger BIC module which has to be purchased.
>>is BIC is an adapter, that we can select as adapter type, while creating the communication channel.
No, it is an adapter module.
>> BIS is configured as a module, what is the type of communication channel in ID.
Don't get confused between BIC and BIS. BIC is a module and BIS is a separate middleware provided by Seeburger just like PI. You can use BIC module in any channel which supports use of adapter module.
>>is AS2 adapter is part of BIS or BIC.
AS2 can come with BIS middleware. It is type of adapter while BIC is module.
>>for integration using PI, out of BIS, BIC, AS2, what all is minumum required?
For EDI communication, BIC is required (if you don't want to create your own modules). AS2 is required only when some partner demands the use of AS2 protocol for communication.
>>what are the roles of BIS, BIC and AS2 in the context of integration using PI.
Already explained. Forget BIS when you already have PI.
Regards,
Prateek Raj Srivastava

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

Details on XI EDI adapter from seeburger

Hi,
We currently have our B2B integration going through Gentran & Webmethods.
We are having a evaluation process on the different tools available.
Can anyone give information on the licensing details of the XI EDI adapter from seeburger? Also do they have evaluation period? Has anyone gone through this process?
We have written to seeburger on this, but i thought of posting on SDN as the responses would be faster
Thanks & Regards,
Renjith

Hi Renjith,
There is no downloadable trial version available.
You need to contact your local or regional Seeburger sales office.
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
Regards,
Abhy
Message was edited by: Abhy Thomas

Error in communication channel AS2 Seeburger EDI Adapter

Hi,
I am facing one issue in communication channel at receiver side. Adapter type is AS2 Seeburger EDI adapter.
Brief overview of scenario: Sender is R/3 sending an IDOC and Reciever is Party (Vastra_Gotaland).
The error in reciever communication channel is : Error type: REPORT_ERROR >> Error date: 8/26/10 10:18 AM >> Description: MIC not verified # integrity-check-failed [8/26/10 10:18 AM].
Please give your important feedbacks.

Hi Vikrant,
I have already checked channel configurations and there is no problem with signing certificate. I have checked that also.
Edited by: Sadhna Achhra on Aug 26, 2010 1:10 PM

Seeburger EDI Adapter Vs AEDAPTIVe EDI Adapter

Hello all,
A client, who already works with SEEBURGER wants to test the AEDAPTIVe EDI Adapter.
I would like to know if someone has already worked with this 2 EDI Adapter and if there is a big difference between then.
I have already worked on Seeburger EDI Adapter but not Aedaptive...
I know it's a very specific question, hope i find someone who did it..
Regards,
JP

Hi,
Did you already test AEDAPTIVe's EDI?
Gordon

Seeburger EDI Adapter

hi experts
provide ma details on SEEBURGER EDI Adapter.
Thanks in advance

Hi
have a look
/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
Thanks

SEEBURGER EDI &AS/2 adapter installation and configuration guides

hi ,
can any one provide me SEEBURGER EDI &AS/2 adapter installation and configuration guides or links please?
thank you,
babu

Hi,
You can get the original manuals from Seeburger if you are installing the Seeburger on server.
Please see the below links
/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.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards
Chilla

Seeburger EDI Adapter Installiation

Hi,
Just now we installed Seeburger EDI Adapter, I want to make sure we installed correctly. what are the components I can verify in IR/ID. Is there any post installation steps.
Mallik

Hi Malik,
during installation you have to follow Seeburger installation manuals like SAPXI_SeeMasterInstallationGuide_en.pdf, SAPXI_BICAdapter_en.pdf etc.
You also can check installed components in SDM or take installed component information from http://10.10.27.80:50000/sap/monitoring/SystemInfo.
Regards
Naycho

Seeburger EDI Adapter with terrible performance problems

Hi,
we installed seeburger edi adapter on PI 7.1 and we have terrible performance problems:
We have a mail sender adapter polling a mail account.
Till the message is visible inside integration engine it takes sometimes 1-2 minutes or longer.
We already tuned the j2ee-engine and checked the DB-indexes (there are some OSS Notes) - no success.
We think that the problem is inside the DB-tables of Seeburger an that some indexes are missing (Oracle DB).
Any ideas?
Thanx
regards
Wolfgang Hummel

Hi,
I think in PI 7.1 SAP installed their own Java-VM (compatible with Sun 1.5) - is it true?
Do you have the same performance problems inside the adapter?
The adapter is like a black hole and it take sometimes one hour till you can see a message inside the integration engine (sxmb_moni).
Regards
Wolfgang

Seeburger EDI Adapter Deployment Error: Cannot register EarLoader

Hello,
we currently have updated our SAP Netweaver Development Environment 2004s to SP20. This installation runs on IBM iSeries.
We also have to deploy a Seeburger EDI Adapter (Version 1.8) but we faced following error in the deployment:
---snipped
PM Error: Aborted: development component
'SeeFunctionsEar'/'seeburger.com'/'SEEBURGER
AG'/'20090701183537.1.8.1'/'1', grouped by software component
'SeeXIExtendedTools'/'seeburger.com'/'LOCAL'/'20090701183537.1.8.1''/'1':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application
seeburger.com/SeeFunctionsEar..
Reason: null; nested exception is:
java.lang.NullPointerException
(message ID:
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
---snipped
We've deployed not only with the JSPM but also with developer Studio. (The SDM-Tool has a big problem after upgrating to SP20 - SAP knows the error and with the next SP this will be fixed. So this tool cannot be used!)
First of all, I think it is very useful for us to know what is the EarLoader but unfortunately we can't find any information on the sap help, documentation or here in the SDN. Neither on the Web .....
Could someone explain the issue to me, please?
Thanks in advance.
Christian Sperlich

Hi,
1)Can you check your class path, whether it is configured correctly
2)Check whether you have included the latest class file while importing
3)Check whether you have activated the objects after you have made changes are imported
Regards
Agasthuri Doss

Problem Encountered in JMS adapter using SEEBURGER module

While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
1. The error encountered is :
Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3'; detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
SEEBURGER BICXIADAPTER --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: XML file should begin with white spaces or <. (Found char :U(Hex :85). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
2. The targer PAYMUL xml is as follows :
( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
PAYMUL XML
<?xml version="1.0" encoding="UTF-8" ?>
- <LIST>
- <S_UNA>
<D_DELIMITER>:+.? '</D_DELIMITER>
</S_UNA>
- <S_UNB>
- <C_S001>
<D_0001>UNOA</D_0001>
<D_0002>2</D_0002>
</C_S001>
- <C_S002>
<D_0004>SAPDM</D_0004>
<D_0007>ZZ</D_0007>
</C_S002>
- <C_S003>
<D_0010>000000000000</D_0010>
<D_0007>55</D_0007>
</C_S003>
- <C_S004>
<D_0017>070201</D_0017>
<D_0019>1150</D_0019>
</C_S004>
<D_0020>01945678912345</D_0020>
- <S_UNH>
<D_0062>1</D_0062>
- <C_S009>
<D_0065>PAYMUL</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
<D_0057>FUN01G</D_0057>
</C_S009>
- <S_BGM>
- <C_C002>
<D_1001>452</D_1001>
</C_C002>
<D_1004>01945678912345</D_1004>
<D_1225>9</D_1225>
</S_BGM>
- <S_DTM>
- <C_C507>
<D_2005>137</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <G_SSG4>
- <S_LIN>
<D_1082>1</D_1082>
- <S_DTM>
- <C_C507>
<D_2005>203</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>ACK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>AEK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_BUS>
<D_3279>IR</D_3279>
- <C_C551>
<D_4383>UGI</D_4383>
</C_C551>
</S_BUS>
- <G_SSG5>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
</G_SSG5>
- <G_SSG6>
- <S_FII>
<D_3035>OR</D_3035>
- <C_C078>
<D_3194>ES921998500000000012</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAES17000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG6>
- <G_SSG7>
- <S_NAD>
<D_3035>OY</D_3035>
- <C_C080>
<D_3036>XYZ CORPORATION LTD</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG7>
- <G_SSG11>
- <S_SEQ>
- <C_C286>
<D_1050>1</D_1050>
</C_C286>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
- <S_DTM>
- <C_C507>
<D_2005>227</D_2005>
<D_2380>2007-02-01</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>AIK</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>CR</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_FCA>
<D_4471>13</D_4471>
</S_FCA>
- <G_SSG12>
- <S_FII>
<D_3035>BF</D_3035>
- <C_C078>
<D_3194>AT921998500000000011</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAAT14000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG12>
- <G_SSG13>
- <S_NAD>
<D_3035>BE</D_3035>
- <C_C080>
<D_3036>ABC CORPORATION 1</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG13>
- <G_SSG16>
- <S_PRC>
- <C_C242>
<D_7187>11</D_7187>
</C_C242>
- <S_FTX>
<D_4451>PMD</D_4451>
- <C_C108>
<D_4440>SENDERPN1</D_4440>
</C_C108>
</S_FTX>
</S_PRC>
</G_SSG16>
</S_SEQ>
</G_SSG11>
</S_LIN>
</G_SSG4>
- <S_CNT>
- <C_C270>
<D_6069>2</D_6069>
<D_6066>1</D_6066>
</C_C270>
</S_CNT>
- <S_UNT>
<D_0074>1</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</S_UNH>
- <S_UNZ>
<D_0036>1</D_0036>
<D_0020>01945678912345</D_0020>
</S_UNZ>
</S_UNB>
</LIST>
3. The module parameters for Seeburger inputs :
( In receiver communication channel)
Processing Sequence
localejbs/CallBicXIRaBean Local Ent Bean x2e_bic_paymul
SAP XI JMS Adapter/ConvertMessageToBinary Local Ent Bean convert_XI2Bin
SAP XI JMS Adapter/SendBinarytoXIJMSService Local Ent Bean
 exit
Module Key
x2e_bic_paymul destSourceMsg MainDocument
x2e_bic_paymul destTargetMsg MainDocument
x2e_bic_paymul logAttID ConverterLog
x2e_bic_paymul mappingName See_X2E_PAYMUL_UN_D96A
x2e_bic_paymul newLine true
x2e_bic_paymul saveSourceMsg XMLEDI

Hi,
Check Below links,
/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
Regards,
Phani

FTP Adapter and Seeburger

Hi,
We are using the FTP adapter and the Seeburger BIC adapter (is configured as a module in the FTP communication channel)
When we receive EDIFACT files the first step that is performed is the conversion from EDIFACT to XML messages (done by Seeburger module). This process performs also a XML syntax check. When this syntax check fails the complete process stops. The FTP adapter wants to read the file (with the error) again and again.
When we have 10 files in the directory and the first one is in error, the adapter does'n process the other 9 anymore!!
Quality of service is: Exactly Once.
Thanx
Ron

Felix / Ron,
In the Seebuger FTP adapter, I have
Module Key - exit
Parameter Name - JNDIName
Paramter Valu - deployedAdapters/SeeXIFTP/shareable/SeeXIFTP
JNDIName, should I be replacing this with some other name. I'm trying to get Seeburger FTP to work and in the messaging monitor, I see the message as passed to Module Processor but it does go anywhere from there.
Can one you throw some light on this...what to expect from this definition.
Thank you,
Pam

Seeburger EDI adapter Vs Seeburger BIC adapter

Similar Messages

Maybe you are looking for