Seeburger

Hi,
I have the following questions on EDI Seeburger.
1.BIC Mapping Designer:As per my understanding,the BIC Mapping Designer is used if any existing Generator mapping provided by Seeburger is not as per the requirement.If we need to edit the existing Generator Mapping then we use BIC Mapping Desinger,right?But if we need edit the existing Generator Mapping,do we see both source and target structure,right?But if we are suppoded to create the mapping from scratch then where to get both the structures from?
2.I searched a lot about the configuration details of the Seeburger adapters like AS2 and SFTP but could not find anything good,can you please provide me the same?Also,where and how to use AS2 and SFTP?What is VAN?Is it an alternative to AS2 or SFTP?
3.What are certificates in Seeburger?Which adapters are they relevant to?
Thanks,
Gayatri

Hi,
>>I searched a lot about the configuration details of the Seeburger adapters like AS2 and SFTP but could not find anything good,can you please provide me the same
When you purchase the third party adapter from seeburger you'll get configuration guide which will giv you the clear idea of cofiguring.
>>where and how to use AS2 and SFTP?What is VAN?Is it an alternative to AS2 or SFTP
The AS2 protocol is internally based on HTTP.AS2 uses two different message types: the actual payload message and the Message Disposition Notification (MDN). The payload message encapsulates an EDI file so that it can be transmitted via HTTP. The purpose of the MDN is to acknowledge the receipt of a payload message.
http://www.edibasics.co.uk/
>>What are certificates in Seeburger
certificate information required for encryption and signing
Refer these links it may help you
Re: Seeburger BIC Mapping Designer: Special Character (German Umlaut) Problem
SEEBURGER integration using PI: BIS, BIC, AS2 Adapter, FTP ?
Handling EDI interfaces using Seeburger BIC modules
http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
Regards,
Priyanka
Edited by: priyanka.anagani on Dec 26, 2011 7:22 PM

Similar Messages

Need Seeburger Attribute Mapper module details

Hi Experts,
We need to post a file(XML) on Receiver AS2 adapter with dynamic filename. We have followed the link :
Re: Dynamic Receiver file name in AS2 adapter to create the UDF in GUI mapping and have selected the fileName property under Dynamic Attributes in the Receiver AS2 adapter. However, even though in the message monitor, the filename property is shown to be corrrectly populated, the file is posted in receiver with a different name.
The above link mentions using an Attribute Mapper module for dynamic filename. Can anyone please provide the details of this module, the module name, parameter names etc. that need to be populated in the receiver adapter.
The same is not available on the net and we don't have the seeburger documents with us.
Regards
Shiladitya

The module parameter will have
Source - @Namespace/PropertyName
Target - Namespace/PropertyName
This way you may copy source FileName to target FileName.
Regards,
Prateek

As2 receiver channel, SEEBURGER AS2: 500 Internal Server Error

Hi,
There is one scenario in our landscape, its running in production, Proxy to As2. The interface working fine for last 2 weeks, today its showing error in As2 receiver channel saying
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: 500 Internal Server Error # , SEEBURGER AS2: 500 Internal Server Error #
I have searched in forum, but couldnt get much idea on why this error encounters and how can we resolve it.
Kindly provide your inputs to help me resolve this.
Thanks,
Ruchi

Hi Ruchi,
500 means the requested server does not understand the request (the requested service is unknown). The reason is obvisiously outside of PI. You have to contact the 3rd party owner and ask why the system is refusing the request instead of responsing like before.
Regards,
Udo

How can I use Seeburger java functions on SAP XI's user defined functions?

Hi All,
As my title implies; how can I use Seeburger java functions on SAP XI's user defined functions? I've tried searching over the net in tutorials regarding this topic but I failed to find one; can someone provide me information regarding my question? thanks very much.
best regards,
Mike

Hi Mike !
You should check your documentation about which java classes you need to reference in the "import" section of your UDF. And also deploy the java classes into the java stack or include them as a imported archive in integration repository...it should be stated in the seeburger documentation.
What kind of functions are you trying to use?
Regards,
Matias.

Multiple Partners for the same customer in Message tracking of SEEBURGER

Hi,
This is for third party customers which use EDI messages. We have for one customer multiple partner numbers configured in Partner profile. I would like to know while configuring the trading partners in SEEBURGER Message Tracking, can we have multiple keys for the same customer for multiple partners for an INVOIC02. Like the following keys:
12345_INVOIC02
34567_INVOIC02
45678_INVOIC02

Hi Satya,
you can define for a vendor/customer several partner functions with different
adresses. You can create certain partner roles several times.
If you create a purchase order, than you can choose the wanted
address and partnerrole on the header level. In the standard system you
can use the patner role 'OA' ordering address and for the finance
the 'IP' Invoice presented by.
I hope I was able to help you.
Kind regards,
Zsuzsanna

Error in Seeburger Message Monitoring

Hi ,
I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file.
I m getting error in seeburger message monitoring with status as "Could not send ansynchrone MDN to partner - url not set!". can anybody tell me whats the reason behind it,where it went wrong.

Really didn't understand your scenario. That sentence makes no sense:
"I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file."
But what I understand from the error message you have provided...................
if you are using Seeburger AS2 adapter as Receiver Comm Channel..........then there is definitely some cofig error is settings for MDN acknowledgement.
Under Parameters Tab:
You must have set the following parameter
MDN Mode = "ASYNC"
And has not provided the following parameter just below it :
Receipt Delivery Address
This parameter should have value: the URL of your own AS2
server where the asynchronous MDNs are
to be delivered.
Hope this solves your problem.
Regards,
Suddha

Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
Benoit

HI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup

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.

SFTP to AS2(non-seeburger): How to get sender Filename to be used in AS2 Receiver Channel

Hi Experts,
I have this scenario,
SFTP > Process Orchestration > AS2(non-seeburger)
My interface is not using Message Mapping and I want to use the source Filename as my Receiver Filename.
Sender
orders_1234 - source filename
Receiver
orders_1234 - target filename
How to do it in Process Orchestration without Seeburger.
Thanks and Best Regards,
Orlan

Hi Orlan - So are you using SAP AS2 adapter?
If you so i think you can make use of dynamic configuration bean.
Unknown use case of DynamicConfigurationBean: Store file name to JMS header without mapping
Enable adapter specific attributes in sender SFTP channel and in the receiver AS2 channel use the above module to swap the dynamic attributes.
Dynamic attributes
http://sap.com/xi/XI/System/SFTP ,FileName
http://sap.com/xi/XI/AS2/AS2: AS2Filename

Variable substitution error while using Seeburger module parameter

Hi Freinds,
I would like to use the variable substitution in a receiver file adapter to add the invoice no.
(which is contained in the XML file) to the target filename.
In addition I have to convert the XML file to an X12 EDI format using the seeburger module "localejbs/CallBicXIRaBean".
As soon as this entry is made in the modules the following error message occurs:
"com.sap.aii.adapter.file.configuration.DynamicConfigurationException:
Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException:
Caught SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
XMLParser: No data allowed here: (hex) 53, 4f, 48(:main:, row:1, col:3)"
My problem is that the conversion from XML to X12 EDI is done before the variable substitution is started.
That`s why the reference for the variable is no longer valid as the file is already converted to a X12 EDI (=flatfile) format.
If I disable one of the two steps (either 1:1-mapping or variable substitution) the other step runs properly.
Has anybody an idea how to solve this topic?
Is it possible to specify the variable substitution as module?
If this is possible I could solve it by just reordering the two steps in the module chain.
Regards
Venkatesh

Use Dynamic Configuration Bean to set this value. You have to use this well before "localejbs/CallBicXIRaBean".
Check SAP note : 974481 for more information.
Blog: [/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean|/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean]
Second Approach if the above approach doesnt work.
Use Dynamic Configuration concept in UDF to set the filename under message Mapping.
Thanks,
- Gujjeti.
Edited by: Praveen Gujjeti on Feb 25, 2009 11:25 AM

Variable substitution & Seeburger conversion module

Hi everybody!
I would like to use the variable substitution in a receiver file adapter to add the order no. (which is contained in the XML file) to the filename.
In addition I have to convert the XML file to an edifact format using the seeburger module "localejbs/CallBicXIRaBean".
As soon as this entry is made in the modules the following error message occurs:
"com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Caught SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 53, 4f, 48(:main:, row:1, col:3)"
My problem is that the conversion from XML to edifact is done before the variable substitution is started. That`s why the reference for the variable is no longer valid as the file is already converted to a edifact (=flatfile) format.
If I disable one of the two steps (either 1:1-mapping or variable substitution) the other step runs properly.
Has anybody an idea how to solve this topic? Is it possible to specify the variable substitution as module? If this is possible I could solve it by just reordering the two steps in the module chain.
Kind regards
Chris

Use Dynamic Configuration Bean to set this value. You have to use this well before "localejbs/CallBicXIRaBean".
Check SAP note : 974481 for more information.
Blog: [/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean|/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean]
Second Approach if the above approach doesnt work.
Use Dynamic Configuration concept in UDF to set the filename under message Mapping.
Thanks,
- Gujjeti.
Edited by: Praveen Gujjeti on Feb 25, 2009 11:25 AM

PI 7.1 and seeburger error

Need some help on this error.
SQLException while getting MessageId entries! Caused by: com.sap.sql.log.OpenSQLException: The SQL statement "SELECT "CID","CSECONDARYID","CSTATE","CINCOMING","CCREATIONDATE","CLASTMODIFIEDDATE","CTIMEOUTDATE","CCUSTOMDATA","CINSTANCEID","CENV" FROM "SEE_MSGIDSTOREP7" WHERE "CENV" = ? AND "CCREATIONDATE" >= ? AND "CCREATIONDATE" <= ? ORDER BY "CCREATIONDATE" DESC" contains the semantics error[s]: - 1:121 - the table or view >>SEE_MSGIDSTOREP7<< does not exist
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:37)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:115)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:91)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:476)
at com.sap.sql.jdbc.common.CommonPooledStatement.<init>(CommonPooledStatement.java:236)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnectionImpl.java:1522)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:258)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:79)
at com.seeburger.dt.messageidstore.spi.db.SimpleAccessHandler.buildQueryStatement(SimpleAccessHandler.java:1104)
at com.seeburger.dt.messageidstore.spi.db.SimpleAccessHandler.getByQueryCriteria(SimpleAccessHandler.java:580)
at com.seeburger.xi.workbench.systemstatus.db.MessageIDQueryManager.getResult(MessageIDQueryManager.java:80)
at com.seeburger.xi.workbench.systemstatus.db.MessageIDQueryManager.getSpecificCount(MessageIDQueryManager.java:49)
at com.seeburger.xi.workbench.systemstatus.infoprovider.MessageIDStoreInfoProvider.getMessageIDStoreInfo(MessageIDStoreInfoProvider.java:26)
at com.seeburger.xi.workbench.systemstatus.infoprovider.MessageIDStoreInfoProvider.getInfo(MessageIDStoreInfoProvider.java:41)
at com.seeburger.xi.workbench.systemstatus.infoprovider.OverviewInfoProvider.fillAllInfo(OverviewInfoProvider.java:36)
at com.seeburger.xi.workbench.systemstatus.infoprovider.OverviewInfoProvider.getInfo(OverviewInfoProvider.java:18)
at com.seeburger.xi.workbench.systemstatus.actions.OverviewInfoAction.getSpecificInfo(OverviewInfoAction.java:35)
at com.seeburger.xi.workbench.systemstatus.actions.OverviewInfoAction.run(OverviewInfoAction.java:22)
at com.seeburger.xi.workbench.systemstatus.Controller.service(Controller.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:173)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

Check the table?
"1:121 - the table or view >>SEE_MSGIDSTOREP7<< does not exist"
Could also be insufficient access rights.

Problems with Seeburger FTP Receiver adapter

Hello,
I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
Hostname <Hostname of our FTP server>
Port <Port # of our FTP server>
Host Path/VAN partner id <some local directory of FTP server>
Payload mode: Maindocument.
At runtime i received following exception
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
Few questions related to this
1] can we use Seeburger adapter to generate EDI files on local FTP server
2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
Any idea how to generate EDI files with Seeburger FTP on test server?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
> 1] can we use Seeburger adapter to generate EDI files on local FTP server
Yes we can use.
> Any idea how to generate EDI files with Seeburger FTP on test server?
It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
BIC
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Regards
Ramesh

Configuring a Seeburger FTP Receiver Adapter

Hello,
I am trying to build a scenario where SAP ECC 6 sends an invoice to a customer via EDI.
We are using ECC 6.0 and PI 7.0 and the Generic Seeburger EDI Adapters. The VAN is a GEIS EDISWITCH VAN (Eircom in Ireland).
I am able to successfully send an IDoc from ECC 6 and into PI where a Seeburger map converts the message to EDI-XML format. I can use a file adapter to create a file in normal EDI format. But I can't get the Seeburger FTP adapter to work with the VAN.
I have configured the correct IP, port, username and password but I keep getting the following message when the communication channel tries to send the message:
<h6>Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 501-Syntax errors in parameter. usage: %[recipient id]%[APRF] where either [recipient] or [APRF] can be omitted. (to change your current default SEND relationship). %% (places you in your 'HOME' TR). &['s'|'single'] ('get' command gets single file). &['m'|'multiple'] ('get' command gets multiple files). >> </h6>
The FTP session is expecting a PUT command with the recipient id and APRF as parameters but these are not getting passed. I suspect this is because I am not passing the correct variables to the receiver adapter but I don't know what variables it expects and where they should be specified. And I can't find the answers in the documentation.
Can anyone shed some light on what I need to do?
Thanks,
Ben

Hi Prateek,
Thanks for your comments. The channel is set to GEIS(GeMarkIII). There is nowhere to specify a directory or filename. The settings I have used are as follows:
Adapter Type: FTP (http://seeburger.com/xi)
Receiver
Transport Protocol: FTP
Message Protocol: GEIS/GeMarkIII
Adapter Engine: Integration Server
Host name: <IP address of VAN server>
port: 21
User Id: <Our mailbox number>
Password: <Correct password>
Host path/VAN Partner ID: <blank>
Script file: <blank>
Transfer type: ASCII
Connection mode: Passive
Use keep alive: <Not checked>
Security Mode: None
Proxy Mode: none
Resource ID: <blank>
Deliver transmission report: <not checked>
Payload mode: Attachment
Attachment ID: SeeburgerMain
Channel status: Active
Use dynamic attributes: <Checked>
Use non-empty attributes: <Checked>
Request displayed report: <Not checked>
Request dispatched report: <Not checked>
Report timeout (minutes): 720
Handle received reports: Refer reports to XI system
There is nowhere in the communication channel configuration that allows me to specify the receiver ID or the APRF. The documentation say this is read from the EDI data and the relevant fields are populated.
Any ideas?
Thanks,
Ben

Dynamic filename creation with Seeburger's SFTP adapter

Hi Experts,
I read in one of the forum that Seeburger's SFTP adapter supports dynamic configuration.
My requirement is i need to dynamically create a file name and put it into a predefined folder(of a third party system) with SFTP adapter.
Can any one help me with some blogs/Materials on this?
Thanks,
Niranjan

HI,
Have you look into the blogs mentioned in below forum
How do we do File content conversion using SFTP SEEBURGER Adapter
Thanks
Swarup

Seeburger BIC Mapping deployment issue in PI 7.1

Hi experts
We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to a compatible version.(2.x).
Mappings_user.sda was used in 3.0 environment.
But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
Is there any way to convert .sda to .sca and deploy?
Or how can we generate a compatible deployment file for 7.1?
I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
Thanks in advanceDhanish Joseph

Hi
I have installed BICMD 632 version and imported .BICMD project file.
Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
Then installed this in PI system using JSPM.
I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
When i send data to PI data comes to channel and it shows conversion error. But detailed information not available.
In seeburger monitoring the message goes to recovery mode.
I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
I faced some issues>>>
1. while importing project file into BIC MD it asked for apply some autocorrection for one map.(different than this). I have clicked on cancel
2. When i assigned SDA number to my project i have selected 2.1.0 SDA version( 1.8.0 option was also there).
Your prompt reply is greatly appreciated .
Thanks

Seeburger

Similar Messages

Maybe you are looking for