About SEEBURGER-SPLIT 997 adapter

Hi
Can anybody please brief about me SEEBURGER-SPLIT adapter.
In which cases Split adapter comes to picture.?
In our project i will have to implement this adapter, for incoming Purchase order 850 I need to use this split adapter before posting it into R/3.
As i'm new to this seeburger, i'm completely in confuse...
can anyboby give me sugguestions on this ?
pls dont point out me to links....
Regards,
Sandeep

Hi,
Check with this basics..
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/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
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Thoughts on EDI in an SAP XI Environment
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
regards,
Kishore

Similar Messages

997 adapter type not present in Seeburger for PI 7.1

Hello Experts,
We recently installed Seeburger on our PI 7.1 system. We deployed all the relevant modules successfully and also imported the meta-data to ESR after whcih we were able to see the FTP adapter from Seeburger. But we were not able to see 997 adapter.
As mentioned in one of the blog, it is necessary to post funcitonal acknowledgements and configuration of 997 adapter is required for the same.
We checked the installation guide from Seeburger but nothing has been mentioned in the same. any idea how to get the same in ID?
Also one more doubt. Suppose I am getting 850 orders from 2 customers do i need to configure Identifiers in the Sender Seeburger adapter representing different customers?
Thanks in advance.
Regards
Rajeev

Rajiv,
Identifiers are required only when the receiver channel is IDOC.
To summarise, you create one party per customer and the same would be done in partner profile as customer rather than logical system,.
Then you specifiy the identifiers in parties and the same is represented in idoc communication channel . By this the idoc comms channel will know which customer in ERP it needs to post the idoc.
This will be used only when the receiver is idoc. Moreover in seeburger, you need to maintain an entry in the message splitter which will enable to use split 997 adapter.
If you create party in XI, make sure to represent that party in ERP as either vendor or customer rather than logical system. This will give you more clarity.
Regards
Krish

SEEBURGER's VAN Adapter

Hi all,
Im wrking on an IDOC to EDIFACT format scenario. The reciever adapter is a SEEBURGER's VAN adapter.Can anyone pls help me with some documents on this?
Thanks in Advance.

HI,
The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine as shown in the diagram below.
The FTP/VAN Adapter supports the following protocols:
IBMIE VAN, all report options.
GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
Sterling Commerce and Sterling IIB.
MCI EDI*Net.
The following FTP options are supported:
SSL, both IMPLICIT and AUTH_TLS support, server authentication.
All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
Active and Passive connection modes.
"KeepAlive" feature.
Binary, ASCII and custom transfer types.
Refer the below thresd which taks about the AS2 adapter configuration inroder to convert the EDI to XML message the similar configuration needs to be done in case of VAN/FTP adapter.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Seeburger adapters like FTP,OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
Seeburger provides the std mapping program which has to be deploy on to XI and we need to give it to module tab in adapter which does the conversion.
Here are the some of the std mapping program which is provided by seeburger.
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
We need to take the license from seeburger and we need to deploye the seeburger adapters then only we can see in adapter list on XI.
Thanks and Regards,
Chirag Gohil

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

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 AS2: AS2 Adapter failure -- CryptoApiException: Access Denied.

Hi,
I am trying to send AS2 message to my partner by using Certificates and I am getting the following error at AS2 receiver adapter.Looks like it doesn't have User Credentials to access the certificates.But we provided all the details.We are not sure where it is going wrong.
2008-08-30 14:49:42 Error Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed:com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Access Denied.
Can anyone please suggest us what is missing and where it is going wrong?
Regards
Stephano

Hi,
1) First of all create the Seeburger Certificates.
2) You have to deploy those certiates in your Visual Administrator.
After that in Interration Builder -
> Receiver Agreement -
> In Security Settings -
>
                   AS2 Sender Configuration -
> Signing Key -
>give the certificate name over there.
                   AS2 Sender Configuration -
> Encription Certificate & Authenitication Certificate is there
                   u have to give u r certificate names over there.
Thanks,
Satya Kumar

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

SEEBURGER AS2: AS2 Adapter failure - Cannot authenticate the user

Hello,
All was working fine but now I got these errors in an AS2 scenario. Sending a message via AS2. Also we don't receive any messages via AS2 anymore. This is the error when sending a message:
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure.
Please advice, many thanks!
Erik

Are you using the "Use Authentication" option in the communication channel? If yes, then ensure that the user provided is correct and is not locked. Also recheck the authentication certificate settings.
Regards,
Prateek

Seeburger X.400 adapter

Hi Experts,
I want material/links on seeburger X.400 adapter, I searched on SDN, but could not find any material for X.400 channel configuration.
In our landscape, client is thinking to install the X.400 adapter & so, I want to understand its configuration
Also, please let me know what is the Transport protocol supported by X.400 adapter?
-Supriya.

Hi Supriya,
Seeburger X.400 is actually a mailbox solution.actually X.400 /p7 is a protocol which the adapters uses for communication.
Any business partner sends or receives data through a mailbox and that has to be connected to PI thru X400 adapter. when trying to create a channel of type X400, the details of the VAN mailbox to poll or post the data need to be given.
x.400 is one of the communication mechanism/protocol used by SEEBURGER BIS.
regards,
Rohit

Adapter Modules & split 997 channel reqd for splitting Edi and Acknowledgement

Hi,
I am using PI 7.11 with B2B add-on installed.We will be using AS2 adapters ,as of now
configured file adapters in place of it.
This B2B scenario does not consists of Party because 1 sender and 1 receiver system is involved as of now.
May be client provides identifiers details and include party.
In my previous B2B scenario(PI 7.3) involving Seeburger , AS2 channel was configured with(image shown below)
SeeClassifier,BIC, message splitter modules and Split997 channel for splitting EDI PO and Functional Acknowledgement.
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it requires
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
Regards,
Mayank Yadav

Hey Mayank,
Inbound Scenario configuration: (3 step)
1) Sender AS2 (EDI messages) -----> EDI separator receiver (no mapping required here; EDI separator is used to split bulk EDI messages and configure acknowledgements (997) if required)
2) EDI separator sender (with message type(eg.850),version and sender ID/receiver ID configuration; here X12convertor module is used to change raw edi into XML) ----> Idoc or any receiver channel (inbound)(here you have your actual mapping)
(if 997 is configured as requested in the first step; then you need to handle the 997 generated by EDI separator)
3) EDI separator sender (997 message type,version,reverse combination of sender ID,receiver ID) to Receiver AS2 ( no modules required pass through)
Outbound Scenario configuration
1) sender channel (say Idoc) to AS2 receiver (requires mapping)
997 file can be sent back by partners (EDI 997 as acknowledgement)
this will be taken care like any other inbound message) which can be then converted to SYSTAT IDOC or so to track the status of outbound message.
B2B status tab in PI monitoring helps you track acknowledgements
Hope this answers your question:
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it require
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
For detailed information on this; please refer Functional Acknowledgement (Inbound and Outbound FA 997)- for Beginners
Regards,
Pooja

Configuration details about Seeburger adapter

Hi,
How to configure the Seeburger Adapter on the outbound and inbound side to intigrate with XI?
Thanks
Koteswara Rao

Rao,
You have to install the seeburger adapter and import the metadata into IR and use it. You check the document for some help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
SEEBURGER
---Satish

About seeburger adapter

Does SFTP Seeburger Adapter has the option for:
1) Archieving
2) File Content Conversion
3) Running Shell Commands
4) Sending Orignal file name.
5) EO, EOIO, Best Effort
6) Add MessageID to the file name.
7) Transfer Mode: Text or Binary
XIer

Hi
Dont mind but please see the below blogs
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
Vaibhav

Message subject in seeburger sender AS2 adapter

Hi Experts,
I read few fourms regarding message subject in seeburger and in those below forum is related to my problem
AS2 Sender adapter.. How we can receive 2 messages from same partner??
like how we can identify different message types when we receive from partner
A) using AS2 ID and message subject
If we give message subject as * it will receive all the message but how to identify them as our partner is not providing message
subject.
I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter

Hi,
> Can anyone please me how to identify different messagetype (like order response,ASN and invoice) without using message subject in AS2 sender adapter
When message comes to PI, initially it goes to seeburger workbench, here based on the EDI type (ANSI X12 or EDIFACT or...), EDI Version (4010 or 4020 or...) and Signal (850 or 810 or ....) it determines the respective mapping (E2X or X2E) program, this is done by Classifier.
When we are sending outbound scenarios and using MDN option then message subject plays an important role. Once we send the outbound signal we can get the ack(997) signal, based on AS2ID and message subject it identifies the respective 997 inbouns scenario.
> I cant use splitter because my sender is sending XCBL data and splitter we can use when we go for EDI.
Seeburger is used if you are handling the EDI data but here you are using XCBL so you no need to use the seeburger adapters.
Regards,
Venkata Ramesh

Seeburger OFTP/ ISDN adapter

Hello,
Does anyone have an experience with configuring OFTP_ISDN adapter from Seeburger? I have a problem to configure an inbound channel (Sender) when the same dataset name can come from four different ISDN numbers (One MAIN ISDN MSN and three SUB ISDN MSN ). I can't use four channels because of conflict with the same dataset name and I don't know how to configure using one channel. Any help appreciated. Points rewarded. Pls urgent.
Regards,
Pavol Suba

Hi Pavol!
I don't have experience with this one, but only idea:
What about different dataset names? You will use the same structure, jsut with other names.
Or, what about creating 4 virtual sender services using the same structure?
You can also try to contact Seeburger company for a technical help. They're very friendly and helpful.
Peter
p.s. Ze zdravim v ceskom Nesse ak s tym fakt nemozes pohnut a chce sa ti, posli mi screenshoty CC do mailu (opytaj sa J dikana na moj mail). Robil som od Seeburgra AS2, tak mozno sa to bude podobat, mozno nie.. skusit mozme

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

About SEEBURGER-SPLIT 997 adapter

Similar Messages

Maybe you are looking for