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

Similar Messages

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: 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

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 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 Vs Seeburger BIC adapter

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

Hi,
<i>Seeburger EDI adapter Vs Seeburger BIC adapter.</i>
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

SAP PI 7.1 custom adapter deployment error

Hi Experts,
I have developed one custom SFTP adapter and i am trying to deploy it in PI server via JSPM.
But in JSPM i am getting some error messages. what may be the cause of this error.
ERROR log:
sample_ra.sda<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.7.1006]/>
<!NAME[D:\usr\sap\P71\DVEBMGS88\j2ee\JSPM\log\log_2011_06_15_11_00_05\deploy_2011-06-15_11-55-05.log]/>
<!PATTERN[deploy_2011-06-15_11-55-05.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 15, 2011 11:55:05 AM [Info ]:DC API is trying to connect to 'p71:58804'
Jun 15, 2011 11:55:06 AM [Info ]:DC API has Connected to 'p71:58804'
Jun 15, 2011 11:55:06 AM [Path ]:+++++ Starting V A L I D A T E action +++++[ deployerId=10 ]. timerId=51
Jun 15, 2011 11:55:06 AM [Path ]:Selected archives for validation. [ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
Jun 15, 2011 11:55:06 AM [Debug ]:Got full sdu path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Jun 15, 2011 11:55:06 AM [Path ]:component version handling rule is UpdateAllVersions.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:deployment workflow strategy is normal deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Error strategies[ deployerId=10 ]:
Jun 15, 2011 11:55:06 AM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorSkipDepending'
Jun 15, 2011 11:55:06 AM [Debug ]:deployer initialized successfully:[id:#52, elapsed: 125 ms.].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Debug ]:Total time:[#52: 0.125 sec].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Info ]:Start validating.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Validating completed. Preparing the validation result.
Jun 15, 2011 11:55:06 AM [Path ]:
Sorted Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Admitted'
Deployment Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Admitted'
Jun 15, 2011 11:55:06 AM [Info ]:+++ Validation finished with status 'Success' +++[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:+++++ End V A L I D A T E action +++++[ deployerId=10 ]. Total time:[#51: 0.25 sec]
Jun 15, 2011 11:55:06 AM [Path ]:+++++ Starting D E P L O Y action +++++ [ deployerId=10 ] [ timerId=53]
Jun 15, 2011 11:55:06 AM [Path ]:Selected archives for deployment. [ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
Jun 15, 2011 11:55:06 AM [Debug ]:Got full sdu path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Jun 15, 2011 11:55:06 AM [Path ]:component version handling rule is UpdateAllVersions.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:deployment workflow strategy is normal deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Error strategies[ deployerId=10 ]:
Jun 15, 2011 11:55:06 AM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Debug ]:deployer initialized successfully:[id:#55, elapsed: 125 ms.].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Debug ]:Total time:[#55: 0.125 sec].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Starting deployment.[ deployerId=10 ]
Jun 15, 2011 11:55:07 AM [Debug ]:deployment triggered : DeployItem[file=
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
,deployItemStatus=Admitted
,versionStatus=NEW
,description=
sdu=name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', softwareType ''J2EE', sub type '''
clusterDescriptor=null
Jun 15, 2011 11:55:09 AM [Debug ]:deployment performed : DeployItem[file=
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
,deployItemStatus=Aborted
,versionStatus=NEW
,description=
1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.
sdu=name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', softwareType ''J2EE', sub type '''
clusterDescriptor=null
Jun 15, 2011 11:55:17 AM [Error ]:Deployment Exception during deployment phase 'DeploymentException',cause=An error occurred while deploying the deployment item 'sap.pi.adapter.sftp_SFTPAdapter_raEAR'.; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.pi.adapter.sftp_SFTPAdapter_raEAR. Cannot deploy it.
Jun 15, 2011 11:55:17 AM [Error ]:Deployment Items status: '
Sorted Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Aborted'
Description:'1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.'.
Deployment Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Aborted'
Time statistics( ms ):
   1.validate : -1
    1.1.deployment : 2156
     1.1.1.Notify:Event triggered : 16
     1.1.2.Disable LCM deployment : 2140
      1.1.2.1.Perform delivery : 2140
       1.1.2.1.1.Application Deployer : 2140
Description:'1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.'.
Jun 15, 2011 11:55:17 AM [Path ]:+++++ End D E P L O Y action +++++[ deployerId=10 ]. Total time:[#53: 10.779 sec]

Hi Debashish,
I have a similar requirement to develop a Custom module for SFTP adapter for SAP PI 7.1 version..
Can you please advise how you build the adapter and please share the document if you have any...
thanks

Conversion Agent V/s Seeburger EDI adapter

Hello Experts,
I'm doing a comparative study on Conversion Agent and Seeburger's EDI adapter. Till now I could find details relevant to both the adapters vaguely. I would like to know as far as conversion from any format to EDI and vice versa is concerend which would be better?
Thanks and regards,
Merrilly

U ll find the list of supported formats for both Seeburger and iway here
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40faf9ae-1ce5-2910-f89c-f187628ea6a0
The decision should be made according to ur requirements
Regards,
Prateek

EDI 810 transaction error: Cannot uniquely identify a trading partner

Hi,
I am facing following error on B2B 11g version 11.1.1.6.0. Please provide the solution if you are aware of the issue.
Error Description: Cannot uniquely identify a trading partner. The trading partners PARTNER-A, PARTNER-B have the same set of identifications.
Partner Identification parameter for PARTNER-A and PARTNER-B
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-A
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-B
Thank you
Ram

Two TPs can not have same identification.
There are two ways to come out of this problem.
1. Change the identification criteria for the TP.
2. Use exchange level Identification for one TP.

Resource Adapter Deployment Error (Resolved)

This Problem Has Been Resolved.
I'm trying to develop an application using Inbound resource adapters on Weblogic 9.2.1 .
I have the resource adapter and the MDB packaged separately. The MDB appears to deploy successfully, but the resource adapter does not.
I get the following exception
javax.naming.NamingException [Root exception is java.rmi.RemoteException: javax.naming.InitialContext; nested exception is:
     java.io.NotSerializableException: javax.naming.InitialContext]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:97)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:421)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:297)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:389)
     at weblogic.connector.deploy.JNDIHandler.bindRA(JNDIHandler.java:575)
     at weblogic.connector.common.RAInstanceManager.putRAintoJNDITree(RAInstanceManager.java:1361)
     at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:432)
     A similar issues was referenced in this message :
     http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4330872
     It appears that the exception means the InitialContext is not serializable.
     This is my start(BootstrapContext) method in my resource adapter. If I DO NOT call new InitialContext(), or setMDBOnMessageMethod(), the exception does not occur.
public void start(BootstrapContext ctx)
     this.ctx = ctx;
     System.out.println("entering AddScanResourceAdapterImpl start");
     logger.info("entering AddScanResourceAdapterImpl start");
     try
     this.JNDIContext = new InitialContext(); // This causes the exception.
     this.wm = this.ctx.getWorkManager(); // Calling this does not cause and exception.
     setMDBOnMessageMethod(); // This also appears to cause the same exception.
     catch (Exception e)
          System.out.println("AddScanRA start : Exception thrown: " + e);
     // TODO: Log problem.
     logger.info("exiting AddScanResourceAdapterImpl start");
private void setMDBOnMessageMethod()
try
Class socketListenerClass = com.fedex.ground.tms.mtms.server.addscan.connector.ra.AddScanSocketHandler.class;
Class[] paramTypes      = { java.net.Socket.class };
this.onMessageMethod      = socketListenerClass.getMethod("onMessage", paramTypes);
catch (NoSuchMethodException ex)
ex.printStackTrace();
Thanks for your any help,
John
Edited by johnbrod20 at 04/17/2007 6:48 AM

Hi John,
One of my customer is facing the same error .
Can you please share the resolution of this problem

X.12 EDI Relational Condition Check in Seeburger EDI Adapter

Hello,
We're in middle of implementing ANSI X.12 EDI message integration with
Seeburger BIC Module with SAP PI 7.0. In X.12 protocol, there are so called
Relational Condition constraints on particular fields of a EDI segment. For
example, for EDI 850, the segment REF is bound by a constraint R0203;
segment FOB is bound by C0302, C0405, C0706, C0809.
Can anyone clarify that the standard EDI-To-XML 1:1 mapping generated by
Seeburger BIC Mapping Designer include these check rules or not ?
Are these check rules mandatory for all inbound EDI message processing
according to industry common practise ?
Thank you for any idea you may provide !
Ying-Jie Chen

Hi Chirag,
For EDI 850, the segment REF has the following elements :
128
127
352
C040
The relational condition R0203 is bound to REF. This implies that elements 02 (ie 127) and 03 (ie 352) are Required, meaning at least one of both fields must exist.
The incoming EDI 850 data is validated by this rule.
Segment REF has several occurrances in the 850 schema and for all those occurances, the check rule applies.
For constraint C0302 on Segment FOB, it specifies that a "Conditional" condition
is bound on this segment, dictating that if element 03 exists, then element 02 must
also exist.
These constraints (aka Relational Condition) are expressed as "Syntax Notes"
on segments for a particular X.12 EDI message type.
FYI,
Ying-Jie Chen

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

Seeburger EDI conversion Vs XI Conversion Agent EDI conversion?

We have implemented Seeburger's EDI solution at a client, and our another client wants to an EDI solution for them.
I cam across this weblog, and it is very interesting. I have some questions.
1. Does Converstion Agent support the converstion of all versions of native EDI X12 and EDIFACT to the corresponding XML verions, and vice versa.
2. What are the differences between Seeburger's and XI Conversion Agent's EDI soultions?
Your feedback would be greatly appreciated.
Thanks a lot.
Karma

Hi Karma,
SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
Have a look at these links:
/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
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.
For more i would suggest you to go through these links:
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
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/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
There are also a few ways to use EDI with the ALE system of R3.
inbound EDI to R3
1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
outbound ALE message from R3 to EDI system
1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
have a look at this example:
http://www.ean.se/EANCOM%202000/iftmin/example.htm
Details on how to configure can be found on SDN
I hope this helps....
Regards,
Abhy

Seeburger EDI Adapter Deployment Error: Cannot register EarLoader

Similar Messages

Maybe you are looking for