SeeBurger Implementation

Hi All,
Can any body provide me with the details on how to configure Seeburger adapters? There is a requirement which I need to work on. I have the PI server but I dont have access to SeeBurger as of now.
I am new to SeeBurger but well versed with the concepts.
Can anyone provide me the step by step implementation of the EDI SeeBurger Adapter to process I/B and O/B EDI files.
Thanks
Tushar

Hi ,
BIC Mapping designer comes with the bundle of Seeburger Package, so with the package instally separately the BIC mapping designer tool and in that we have some standard set of converting i.e mapping programs. so if you go and search in help of that it provides the information of how to create a .SDA files and once you create that deploy that using basis people in to the PI server.
For the module configuration that to be used in the File adapters are as follows:
If it is to pick the sender EDI file then the following should be used in the Module Tab of the Sender File Adapter:
PROCESSING SEQUENCE
Number, ModuleName, Module Type, Module Key
1,localejbs/CallBicXIRaBean,Local Enterprise Bean,bic
2,CallSapAdapter,Local Enterprise Bean, 0
MODULE CONFIGURATION
Module Key, Parameter Name, Parameter Value
bic,desDelimeter,,~ (Here ~ is the separator)
bic,destSourceMsg,MainDocument
bic,destTargetMsg,MainDocument
bic,dynamicConfiguration,true
bic,mappingName,See_X2E_ANSIX12_810_V4010 (This is the 810 EDI mapping name which this should be deployed as .SDA in PI server)
bic,newLine,true
regards,
Kishore

Similar Messages

Any setting required in SLD for EDI,XI,Seeburger Implementation.

hi,
what we need to do in SLD to implement EDI using seeburger adapter,do we need to install SWCV and create TS and BS like we do in general?
or we create ,in Integration Directory,party and then Business service (or Business System) and CC?
thank yoiu,

Hi Babu,
Please see the below link,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e17fdb90-0201-0010-2cb6-fe937f3bfd97
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f70cc090-0201-0010-06bd-ff8d3754cfe4
Thanks,
Ram
Pls reward points if you find useful

Seeburger help required for Purchase Order,Dispatch Advice,Supplier Invoice

Dear All,
I wanted to do the Seeburger implementation.
I wanted to convert the EDIFACT to XML struture and XML struture to EDIFACT using the seeburger adpater for --
Purchase Order , Dispatch Advice and Supplier Invoice.
Points:
1. How will vendor will send and receive data to PI. (means how to use Seeburger spoke and how to give unique Ids in Seeburger AS2 adapter)
2. How to do Edifact to XML conversion and XML to Edifact conversion using Mapping Designer
3. How to configure modules in Seeburger AS2 adapter
Regards

HI,
For Seeburger implementation you should take licance for BIC MD and Adapters(AS2,SFTP).
1)You will receive the data from the vendor ,you need to configure the AS2 Sender Adapter and you need configure the Party with AS2ID(Global Indentfier).
2)For Conversion for the EDIFACT to XML you need to generate the the BIC mapping In BIC MD.once generate the map you can loaded the map into XI server.you need to configure the mapping detials in module(Classifer,BIC,Spliter......).
Steps to genrate the BIC MAP:
Steps :-
      1) Right click on Data type and Export structure (msg_....xml).
      2) Run u201CCreateXMLmessageu201D, (source file msg_....xml, target file XML_....xml).
      3) Import XMLu2026.xml to your Project XML Message.
      4) Run u201CCreateMappingXMLToEdiu201D source file (msg_...xml),target file      (X2E_....xml)
      if you are converting XML to Edi format.
      5) Run u201CCreateMappingEdiToXMLu201D source file (msg_....xml),target file      (E2X_....xml) if you are converting Edi to XML format.
      6) Import X2E/E2X_.....xml to your project mappings
3) you need to open firwall from the vendor and your system..
AS2 Sender Adapter:
Transpoert protocl:HTTP
Message Protocol:AS2
Authincation Requered(Check box)
Message subject:
Asynchorns MDM Settings:
Server Certifacte:
Private key:
HTTP TimeOut:
MDM retry interval:
MDM retry Count:
Proxy Server:
Proxy prot:
Proxy User and Password.
For more information end to end :above menation rajesh weblog.
regards,
Ramesh

Seeburger AS2 Adapter implementation in PI 7.1

HI Experts,
We have seen lot of implemetation of seeburger adapters in PI 7.0 but didnt got any chance to look ahead for any documents related to seeburger AS2 adapter implementation in PI 7.1 .
Request if you can please guide or provide some hands on documents which can give the clear overview of how to configure AS2 adapter in PI 7.1 and its parameters.
Thanks & Regards,
Abhishek

Hi,
refer the blog by prateek:-
http://wiki.sdn.sap.com/wiki/display/XI/ParametersUsedinModuleProcessingforSeeburgerAS2AdapterforSAP-PI
u can also refer other blogs for details search on SDN
http://www.sdn.sap.com/irj/scn/advancedsearch?query=seeburger
I think everything remains same.
chirag

SAP XI Seeburger and X.400 Adpater

Hello,
We are trying to implement Seeburger X.400 Adapter in our XI 3.0 landscape for the first time.
I went through Seeburgers config documentation and did all the setup and still getting errors. Not sure what I missed.
At the log it seems to be complaining about "Resource". I did create a logical resource and assigned it to the channels.
Following error is what I see in Comm.Channel Monitoring for both Sender and Receiver Channels:
2009/04/21 - 14:45:34:368 Retryable fault in 'Channel:CC_NL_Receiver_Test'. Description: P7 error occured! Details: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:44 PM]
Error type: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. >> Error date: 4/21/09 2:45 PM >> Description: : trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:45 PM]
Following is the error log I see in the log files (seeburger-x400p7-readable.2.trc):
Apr 21, 2009 3:21:47 PM    com.seeburger.p7.statemachine.TransportLayer.disconnect()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Error while disconnecting! The transport layer is not connected.
Apr 21, 2009 3:21:47 PM    com.seeburger.p7.MessageStore.bind()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Failed to establish a connection. Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
     at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
     at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
     at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
     at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
     at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
     at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
     at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
     at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
     at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
     at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
     at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
     at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Apr 21, 2009 3:21:47 PM    com.seeburger.p7.P7Processor.handleP7Exception()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isnt connected yet. Caused by: com.seeburger.p7.exceptions.P7Exception: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
     at com.seeburger.p7.MessageStore.bind(MessageStore.java:379)
     at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
     at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
     at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
     at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
     at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
     at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
     at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
     at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
     at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
     at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
     at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
     at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
     at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
     ... 11 more
Apr 21, 2009 3:21:47 PM    com.seeburger.xi.connector.fw.XICommunicator.reservationReleased(String)                                                                               [SAPEngine_Application_Thread[impl:3]_27] # Error # Error while releasing resource in resource-management:Cannot create reservation, reason: Cannot find reservation with id X400-Seeburger49; affected object : null
Thanks in advance for your help,
Sumant.

Hi Prateek,
Thanks for your quick response.
As you said, there was a reservation entry and I deleted it. But still having the same issue.
Do you know what this error means. I see this in the comm.channel monitor:
Alert: Polling failed, caused by: Task final state is RETRY or ERROR [4/21/09 3:45 PM]
2009/04/21 - 15:45:16:341 Retryable fault in 'Channel:CC_PollingX400'.
Description: P7 error occured! Details:
trying to open a connection -->
connecting to remote session service -->
com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
The transport layer isn't connected yet. [4/21/09 3:44 PM]
Error type:
trying to open a connection -->
connecting to remote session service -->
com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
The transport layer isn't connected yet.
>> Error date: 4/21/09 3:45 PM
>> Description: : trying to open a connection -->
connecting to remote session service -->
com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
The transport layer isn't connected yet. [4/21/09 3:45 PM]
Regards,
Sumant.

Seeburger FTP Adapter And SAP PI 7.1

Hi Everyone,
Just a few questions about Seeburger FTP adapter please. Bit of background for clarity, we are doing an implementation using Seeburger FTP and sap PI 7.1 picking up EDIFACT (Orders) and returning (DESADV, ORDERSP, INVOICES). However we are not using any BIC, using another tool for EDIFACT -> EDIFACT-XML conversion (conversion agent) and in-house mapping development using graphical mapping.
So couple of things which I haven't been able to figure out from the standard documentation for Seeburger FTP adapter:
1) First is the functional ACK which we are meant to send back to the VAN is that a STANDARD FUNCTIONALITY with Seeburger FTP adapter?
2) Because we are receiving a mix bag EDIFACT interchange on the way IN, I need to split messages accordingly and pass them on to the relevant channels and mappings. By using the standard module Splitter can I achieve that?
3) Lastly some of the standard validations which are applicable to EDIFACT are they supported within the FTP adapter automatically? e.g. Counting number of messages in one interchange etc.
Any help in this regard will be really great.
regards

Now a Good news.
If you are using Seeburger version 2.1 (which you should be as you want it for PI 7.1), then there is an Internal Classifier and Split option for FTP adapter. You just need to tick checkbox "Use built-in splitting" and you are done. Then I believe there won't be any need for considering all these problems. The earlier version of Seeburger with PI 7.0 doesn't have such option and that could be the reason you haven't received any appropriate response yet.
Still I will reply all your questions considering that "your case is of PI 7.0". -> remember PI 7.0
>>even with just splitter we should be able to break it up?????? or am I wrong in thinking this?
No. You even need BIC or an equivalent custom module for achieving this.
>>I can't visualize where to handle the overall message count in one Interchange any suggestions?
You need to write an adapter module for this. Not sure about the code but this module has to be added before the split happens.
>> seeburger ftp adapter it does talk about a lot of reports which are available on sender/reciever actions. e.g. delivered, despatched etc. Are these reports not essentially ACKs?
These reports are the ones used at the receiver side for getting the ACKs from the receiver. Your requirement is at present for sender scenario.
Regards,
Prateek

Seeburger bic module mapping parameter

Hi all,
I'm implementing a Invoice02 to 810 scenario, my mapping name in repository is MM_xyz..
But I'm using the standard content of Seeburger...there are lot of mapping transformation..
So do I need to create 1:1 mapping in BIC mapper or can I use See_X2E_ANSIX12_810_V4010 as my mappingName in bic module config...
Thanks,
Srini

>
Srinivas Davuluri wrote:
> Hi all,
>
> I'm implementing a Invoice02 to 810 scenario, my mapping name in repository is MM_xyz..
> But I'm using the standard content of Seeburger...there are lot of mapping transformation..
> So do I need to create 1:1 mapping in BIC mapper or can I use See_X2E_ANSIX12_810_V4010 as my mappingName in bic module config...
>
> Thanks,
>
> Srini
Dont confuse yourself with the data mapping and the BIC mapping.
Note that the data mapping transforms your IDoc XML to 810 EDI XML. Here you have a transformation logic via the business rules. The BIC mapping is nothing but a structure conversion something you can say like FCC in file adapter which will convert the EDI XML to the EDI flat file
The BIC is at an adapter level conversion as it is part of a module. You actual IDOC to EDI XML transformation is done by your message mapping.

Seeburger AS2: MD5WithRSAEncryption NoSuchAlgorithmException

Hello,
we use a AS2 receiver communication channel with SSL encryption. However when sending out a message we get the following error.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption), SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: MD5WithRSAEncryption, provider: BC, class: org.bouncycastle.jce.provider.JDKDigestSignature$MD5WithRSAEncryption)
We already checked that all Java Policy Files have been deployed. We have also tested the adapter successfully.
Any ideas on this?
Thank you!

Hi Florian,
have you checked the following:
-Installation of the Java Cryptography Extension?
-Did you deploy SeeCryptoSourceBridgeLibXI.sda? (Seeburger Certificate Service)
-The Exception "java.io.IOException: java.security.NoSuchAlgorithmException: Error constructing implementation" could also point to a problem in the Keystore:
--> Did you create an Adapter User to access the Keystore?
--> Check if you have set the view_creator role of the keystore you are using to EVERYONE.
--> Maybe your certificate is corrupt?
regards,
Daniel

Error will starting SEEXIAS2 in Seeburger

Hi,
I have deployed AS2 in the PI7.3 System using JSPM and also imported the metadata. After that while starting the SEEXIAS2 services it is giving this error. Can you please help me to solve the below error.
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.frame.core.thread.Task.run(Task.java:73) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.prl.ParallelApplicationThread.run(ParallelApplicationThread.java:64) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser.execute(ParallelApplicationStartTraverser.java:230) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:2666) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:322) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:571) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:256) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:283) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:319) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.startFactory(ResourceAdapterStarter.java:742) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:350) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:337) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:186) System.err
    error 2012-01-03 11:29:50:195 at com.sap.engine.services.connector.jca.AdapterCache.startMCF(AdapterCache.java:340) System.err
    error 2012-01-03 11:29:50:195 at com.seeburger.xi.connector.SPIManagedConnectionFactory.start(SPIManagedConnectionFactory.java:268) System.err
    error 2012-01-03 11:29:50:195 at com.seeburger.xi.connector.SPIManagedConnectionFactory.prepareStartup(SPIManagedConnectionFactory.java:694) System.err
    error 2012-01-03 11:29:50:195 at com.seeburger.xi.connector.queue.Queue.<init>(Queue.java:120) System.err
    error 2012-01-03 11:29:50:195 at com.seeburger.xi.resource.ResourceManager.cleanReservations(ResourceManager.java:519) System.err
    error 2012-01-03 11:29:50:195 at com.seeburger.xi.resource.impl.db.DbHandler.cleanReservations(DbHandler.java:1125) System.err
    error 2012-01-03 11:29:50:195 com.seeburger.xi.resource.ResourceException: Cannot clean reservations.; affected object : null System.err
    error 2012-01-03 11:29:50:132 !!!! UNLIMITED SECURITY POLICY FILES ARE NOT PRESENT. [LOC: !!!! UNLIMITED SECURITY POLICY FILES ARE NOT PRESENT..checkUnlimitedStrength] Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: 1.2.840.113549.3.7, provider: BC, class: org.bouncycastle.jce.provider.JCEKeyGenerator$DESede3)
at... com.seeburger.as2.AS2Plugin
    error 2012-01-02 11:39:46:604 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316) System.err
Thanks & Regards,
sreeram

Hi Prateek,
I have followed the installation guide and I have deployed using JSPM and in that Ihave selected New software component and deployed. After that I have done the same steps given in the installation guide for metatdata. When I Check the services in NWA->configuration-> infrastructure and SEEXIAS2 services are not running and I get the above mentioned errors. The version I am using is the PI 7.3 and in the directory of security there are all the files related to javapolicy. But still I get the above errors only.
Thanks & Regards,
Sreeram
Edited by: sreeram_basis on Jan 4, 2012 3:28 PM

EDI on XI without using SeeBurger Adapter

We're about to begin a project to do EDI on XI. We'd like to know about all options we have in addition to just using the recommended SeeBurger EDI adapter. We have a 3rd party middleware tool we could use as well. We'd like to leverage the knowledge we already have in this product. Let me know if this is a feasible architecture.
- XI handles all the SAP communication.
- 3rd party middleware vendor tool handles all EDI mappings, and also handles all communication with partners via AS2, FTP, etc.
- Communication between XI and 3rd party middleware is accomplished thru SOAP/web services or direct HTTP calls.
Under this architecture, i'm not exactly sure what XI buys us as we could communicate directly to SAP without XI but lets leave it as is for now.
Is this a feasible option?? Assume the extra development of the maps is not a major consideration since our business requirements would cause us to modify any out of the box mappings SeeBurger would provide anyway.
Has anyone else implemented EDI via an adapter outside of SeeBurger's??

hello
ur architecture seems to be ok becuase as of now i have'nt heard of XI supporting AS2 features..i guess u can configure a partner in XI in configuration builder and then create a communication channel for the same with the transport protocol as HTTP or SOAP.u can apply security over here by configuring necessary certificates..
regarding XI usage goes what third party middleware ur using..check whether it offers flexible mapping capabilities like XI (with GUI maps, XSLT or Java maps etc) or BPM capabilities (which u may require in future) and message persistence capabilities etc..
also now XI is free with NetWeaver 2004s licence.
Regards
Rajeev

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 Interface configuration problem

I am facing some problems in configuring the interfaces in seeburger.
As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.

>
Rohit Kaushal wrote:
> I am facing some problems in configuring the interfaces in seeburger.
> As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
> Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.
Can you provide more details like what you are expecting..
If my understanding is correct you want to implement a mappings in seeburger bic mapping tool for your sceanrio which can take care of conversions right?
if yes provide more details about your scenario
Rajesh

EDI integration thru seeburger

Hi Folks,
Scenario: ECC sends PO (orders Idoc) 850 to PI and then PI sends to EDI subsystem using seeburger (AS2 protocol).
EDI system has to send PO order acknowledgment 855 to PI and then to ECC.
1) whether Seeburger adapter supports synchronous scenario ?
2) Please suggest some input reg. this.
3)
Is it good for ECC integration with EDI system using PI (ie seeburger),
Please give comments on Pros and Cons (any way Seeburger adapter licence cost associated)
a) in terms of time line with out PI , how it goes?
Thanks in advance
Regards,
Praba
Edited by: Prabaharan Rangasamy on Mar 16, 2010 2:23 AM

Hi,
If you have already PI System in your landscape you can definetly go for ECC ,EDI System integration with PI using seeburger.
Many customers implemented the same integrations.
Wiithout PI ,are you planning to use someother middleware???? if NO,then withput midleware its very difficult integrate SAP System with EDI System.
Regards,
Raj

EDI using seeburger

Hi Friends,
Recently I have worked on EDI scenarios using Seeburger adapter.
there are so many in and outs for EDI / Seeburger ,
out of that I need some inputs on finalization of error handling framework for EDI implementation using Seeburger.
Please give your thoughts on error handling in EDI /Seeburger.

Beside my two cents above, your question can't really be answered without defining some business rules around it. So for the sake of discussion i am going to make up a scenario. And the cycle upto Despatch advice.
So business rules are:
1) Over supply not do able. Which implicitly means no manual changes in the incoming ORDER.
2) Under supply allowed as in the real world this will always happen as at the time of ORDER, the supplier side could be out of stock on a particular item ordered.
Message Cycle:
1) Order (Inbound)
2) Order confirmation (Outbound)
3) Dispatch advice (outbound) - DESADV
So briefly speaking based on how the Order confirmation is setup (based on business guidelines) will determine what we are suppose to handle.
If order confirmation is allowed to change the Order i.e. If no stock available and hence line item rejected it would update the original Order in the sending partners system hence no issues at the time of desadv (this is situation one). However if due to some human error more stock shipped than agreed upon in the DESADV then 'excess stock' process can be invoked and based on business rule it can be returned e.g.. This wouldn't require any message amendment. However if short delivered then what was agreed in DESADV partner can always request amends and new DESADV (corrected) can be issued.
I will stop here; I am hoping that i am making sense above? Will continue if i am making sense and then we can talk about technical side for addressing different situations.
regards,

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 Implementation

Similar Messages

Maybe you are looking for