SWIFT Adapter ?

Hi All,
Please give me a clear description about how to implement the SWIFT adapter in SAP-XI and how it will work ?
Note: I have already seen the pdf file of iWay SWIFT adapter.
Thanks in advance

Hi
Have a look into these Documents.
http://help.sap.com/saphelp_nw04/helpdata/en/44/b7fcdc352056a2e10000000a1553f6/CMLibraries.pdf
/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
/people/bla.suranyi/blog/2006/09/29/conversion-agent--handling-edi-termination-characters
Regards
Aashish Sinha

Similar Messages

Using SWIFT adapter in XI

Can any one please tell me how to install and use iway SWIFT adapter in XI.
Thanks
Abinash

U ll have to deploy the adapter on the XI adapter engine. The information abt the adapter can be obtained here.
http://www.iwaysoftware.com/products/adapters/pdf/iwayswifttech.pdf
But i think the installation guide should be provided by iWay with the adapter
Regards,
Prateek

Swift Adapter for bea8.1 Error in parsing swift format to xml

hi All,
I need your help, how to parse swift format to xml format. Suppose I took one example of swift Message Type, that was MT103
To convert this message I have tried all of these methods:
wlai.swiftMT103EventMT103Event.SWIFTMT103Document.Factory.parse(File)
wlai.swiftMT103EventMT103Event.SWIFTMT103Document.Factory.parse(String)
wlai.swiftMT103ServiceMT103Request.SWIFTMT103Document.Factory.parse(File)
wlai.swiftMT103ServiceMT103Request.SWIFTMT103Document.Factory.parse(String)
But I still found the error
com.bea.xml.XmlException : Unexpected element :CDATA
while these methods were executed.
so anyone can help me how to transform swift format to xml format..?..
The final purpose of my transformation is transforming swift format to mainframe format..
so anyone has the clue how to do that..?
Thanks,
Juned

Hello
I've solved the problem.
In the stack.xml file are multiples software-components with the same name, here "SERVERCORE".
I had 3 entries, two with patch-level 0 and one with patch-level 1.
I've deleted the two entries with patch-level 0 and then it works.
Regards Christian

SWIFT Receiver channel error

Hi,
I have configured my Fileact sender channel as described in the "SAP Integration Package for SWIFT".
But i get this error in the channel monitor.
1)
Adapter Framework caught exception: java.lang.NullPointerException
2)
Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.xi.swift.ParserException: java.lang.NullPointerException.
It seems that I have some kind propblem with the swift adapter module. But can I clarify this ?

Did you solve the problem?
How do you transform form flat file to SWIFT_FAT xml format?

File to swift

Hi All,
I m trying to implement File to Swift Scenario but i m nt getting any link based on it.
can anyone plz provide me the link for the above scenario.
thanks

Hi,
please did you make it? I'm facing the same problem with lack of info for iWAY SWIFT adapter implementation.
Can you please help me with this ?
I've been looking on net for weeks and no good result at all.
I've implemented iWAY adapter but it looks that this adapter is not working (in runtime monitoring) and I dont know how to tel him which message I want to use and which rules it has to use.
Just for now I have BPM with receiver where I 'm reading file directly from server but only with XML structure. Now I need to bring up the adapter to read MT messages.
And in oposite way to save MT messages onto server
Thanks a lot
Petr

Problem with iWay Servlet Application Explorer

Hello Everyone,
I have installed the iWay SWIFT adapter. Now I am trying to configure the iWay Servlet Application Explorer. I have deployed the iwae.ear after making necessary changes as suggested. But the problem is when I am trying to open the Servlet Application Explorer at http://<XI host:port>/iwae/index.html, the page opens but it is not showing the available adapters and in the right pane it is giving following error:
Unable to Retrieve Information
The underlying connection was closed: Unable to connect to the remote server. Check your configuration or try to connect later
Has anyone faced any similar problem earlier, if so how to solve this issue.
I have used the following values for service line in the web.xml inside the iwae.war.
<service displayName="localhost" url="http://localhost:50100/"/>
<service displayName="jca" provider="com.ibi.adapter.jspae.CustomJCAIWAEConnection" url="c:\program files\iway55#base" />
(Where 50100 is the j2EE port on our XI server.)
Any tip regarding this is highly appreciated.
Thanks
Abinash

Hi,
Check out for the parameter to be set in config tool.
Check these link.
http://egeneration.bea.com/iwaydocs/iway55/5.5.001/iw55_cics.pdf
SWIFT
file to swift
file to swift file scenario
http://download.sap.com/download.epd?context=876CA1622A3C697FF1D756D2FE10D2727D9FE0E9740911DBA785883225B46DF4F27EA184832BFBF3FDABDAAECF26794BC249BB326209F958
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/34a1e590-0201-0010-2c82-9b6229cf4a41
http://martin.hinner.info/bankconvert/swift_mt940_942.pdf - MT 940
http://www.bph.pl/res/docs/korp/DBE/MC/Aktualnosci_instrukcje/file_format_description_rft_mt101_v20050411.pdf - MT 101
iway's SWIFT adapter http://www.iwaysoftware.com/products/adapters/swift.html
SWIFT adapter available from iWay..
check... you can get documentation about conversion agent from service marketplace..
/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
/people/bla.suranyi/blog/2006/09/29/conversion-agent--handling-edi-termination-characters
/people/bla.suranyi/blog/2006/09/29/conversion-agent--handling-edi-termination-characters
Regards
Aashish Sinha
PS : reward points if helpful

SAP SWIFT as replacement for IWAY adapter

We are planning to replace the current IWAY adapter with the SAP SWIFT, however, it is found out that its usage is very different from the IWAY. Currently, we have several interfaces that use the IWAY adapter, basically, it is maintained in the DESIGN and has a metadata adapter which enables it to be used by the interfaces in the CONFIG. However, for the SAP SWIFT, there is no metadata adapter in it, it looks like just an ordinary stand alone interface having objects in both design and config. I am just wondering on how would the interfaces be able to use this SAP SWIFT? are there major changes in the interfaces (mapping, config, etc.) to be done in order to utilize the SAP SWIFT?
Thanks!

Hi,
I dont think SAP SWIFT will replace IWAY adapter ,IF you refered my first replay you will find below info,which explined clearly
(SAP NetWeaver XI) component lets you manage the pay-to-reconcile business scenario, processes, and mappings. The epository also contains the integration directory, where you can manage the technical characteristics of partners, such as party identification and collaboration agreements.When using FIN, you have the following file-adapter-specific functionality:
u2022 Creation of SWIFTNet-specific files formatted as protocol data units (PDUs) in the automated file transfer (AFT) format
u2022 Local user authentication management between SAP NetWeaver XI and the SWIFTAlliance Access messaging
interface, which eliminates the need to authenticate users to many different systems.
u2022 File transfer between SAP Net Weaver XI and SWIFTNet via FTP or through a shared folder.
u2022 Direct processing of SWIFTNetspecific files, formatted as PDUs of the AFT format by SAP ERP Financials
The following capabilities are enabled when using the FileAct messaging service:
u2022 Transmission of batch messages via the file transfer agent and processed by the SWIFTAlliance Gateway, which
manages access to SWIFTNet u2022 Local authentication between SAP NetWeaver XI and SWIFTAlliance Gateway
u2022 File transfer between SAP NetWeaver XI and SWIFTAlliance Gateway via FTP or through a shared folder.
Regards,
Raj

ISSUE IN SWIFT MT 101 ACK FILE

Hi Guys,
BANK->SWIFTNETGATEWAY(ACK/NACK Files)->SAP PI---->SAP ECC
The issue is regarding the ACKNOWLEDGEMENT/NACK files sent from back with respect to MT 101 files.
I am using FILE-PROXY scenario for this ( FILE SENDER ADAPTER---RECEIVER XI ADAPTER)
To read the sample ACK file i have used the module localejbs/swift/FINConversionFromSWIFTModule in sender file adapter. The sample file has multiple fields structure which is similar to SWIFT_FIN structure. But if you read the file using this module it will populate the data only for the 6 fields based on datatype SwiftMessage whose structure is different from SWIFT_FIN .Due to this data will not be populated in the mapping, so blank data is going to SAP ECC and its throwing error.
I have tried out all possible ways to use the modules provided in the configuration file but the file is read only with SwiftMessage structure and the standard mapping for ACK/NACK is provided with SWIFT_FIN structure as source and collectivePaymentOrderNotification as receiver structure.
I have explored and tried all the possible ways and got struck at this point of picking the file based on SWIFT_FIN structure, I request to let me know if there is any additional module available in the SWIFT integration package which will read the file based on SWIFT_FIN structure. Kindly suggest me with the valuable inputs.
Thanks,
Goutham

Hi Goutham,
Answers of your questions:
>>> 1) whether the source xsd which u have imported should be provided by the client??? (the ack file provided by the bank has same structure as SWIFT_FIN structure)
I have created the XSD of Acknowledgement files i am receiving from bank (Means yes you can say that i am receiving files from client). I opened the XML file received by us and then using stylus studio i generated the XSD of that xml. I saved that XSD to local drive and the imported it to PI as External Structure.
>>>(the ack file provided by the bank has same structure as SWIFT_FIN structure)
No it has different structure and it is iso:20022 structure. what happens in swift fin is that the XML get converted to SWIFT_FIN message using beans and it was not happening in our case, so we were getting error in that scenario.
>>>2) And what are the modules u r using in sender file adapter????
No modules in File adapter. It is like simple file to proxy scenario.
Steps :
Import XSD
create SI for that External definition
create MM using XSD as source - Target as CollectivePaymentOrder
Create OM
and configure it in ID.
Regards
Aashish Sinha

Issue on file sender adapter communication channel

Hi All,
I have an issue on some of the file sender adapter communication channels .The channels are failing with the error :
(u201CAttempt to process file failed with com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.xi.swift.ParserException: com.sap.xi.swift.ParserException: Message does not start with character '0x1f'u201D).
Please let me know the procedure to get this message processed.
Thanks & Rgards
Vishnu

Hi Vishu,
Find out in what encoding the file is in. for that download Notepad++ and open the file with in.
In Encoding tab you will see the encoding format.
1. If its not UTF-8 or ANSI then you should set the correct encoding in Sender File channel.
2. Check for BOM characters which will not be visible directoly.
3. Use Notepad++ to convert the content to HEX and check for hidden values. i bet there will be some Encoding BOM in the file which is creating problem while picking the file.
Since you are using SWIFT module: try to validate the XML file using Altova XML and check weather is correct.
also ref to this thread:http://scn.sap.com/thread/2134946
Regards,
Senthilprakash

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

Need instructions for Enhanced Cable Tech "Liberty" VGA adapter....

Hi!
I'm trying to get my old PowerMac 8500 up and running. The only display I have that is (well, should be...) compatible is an old Apple Studio Display 15" Flat Panel (Rev B.). This is the second iteration of that display, with the VGA connection, not the earlier Mac 15 pin D-sub connection, which is what the 8500 has (http://support.apple.com/kb/SP135).
I have two adapters that I'd think should do the trick of getting me something on the display. An NEC MultiScan unit that has several resolutions printed on it, but no adjustments, and an Enhance Cable Technologies Liberty adapter.
The NEC one gets me noplace, and so far, neither does the Liberty.
The Liberty has a knob with several letter stops (A-M or N), and a set of 9 (I think) DIP switches. Instructions on the back list many resolutions, but only give instructions for the last 3 DIP switches, which are for sync. It mentions to consult the instructions (which I can't find or don't have) for using the other DIP switches to get "expanded" ID codes.
I've tried all of the knob stops, and a couple DIP switch settings, but nothing seems to get me an image on the display. The display does work, it just isn't detecting a signal, and it will tell me so.
I think the 8500 may be going into "headless" server mode (no video) when it can't detect a monitor attached, so once it boots (and it IS booting), I can't get anything until I re-boot again. I'll have to dig up an OS9 install CD, to see if that helps me any. When I stored it some years ago, it was running Mac OS X 10.2 via a boot loader (it has a Sonnet PPC G3 processor upgrade card), so that may be an issue, too.
But, I was hoping that maybe someone has the instructions for the Liberty adapter kicking around in their junk drawer. All I need is the instructions for the DIP switch settings.
Regards,
Larry W.

Well, bought some new PRAM batteries from OWC. Installed one on the 8500/150 (also bought spares for my G4 & SE/30), zapped the PRAM several times, and still nothing. Then dug out my DVI-VGA adapter for my MBP, just to verify that nothing had gone sour with the display since I last put it in the box. All good there.
But, it turns out that I had a solution all along in the "Accessories Kit" in the box the Studio Display came with. There was, still sealed in 16-year-old plastic, an adapter that came bundled with the display! Cut open the plastic, installed it, hooked on the display, and presto-chango, I'm watching Jaguar boot up!
Though, Jaguar isn't so swift on this machine, even with a 250Mhz G3 processor... Might have to do with only 240MB of RAM... Once I got it back running Mac OS 9.1, though, it's a pretty snappy machine. It even reports a processor speed of 279Mhz!
Now I can get what I need from the machine, and move it on to a new home. Also check out all the rest of my SCSI devices for data I think I need, as this is my last SCSI machine that'll take more than one internal device!
And I may even see if I can make the Liberty adapter work like the Apple-supplied one.

Creating data and .par files using SWIFT Integration Package

Hi,
I have a requirement to generate a data and .par file using SAP PI Integration package for SWIFT.
I am following the SAP Note: 1303428.
I have created 1 sender and 2 receiver comm channels(one for payload and other for par). Used operation mapping SWIFT_payload_parFile_split in the Interface determination.
I am using the adapter module : localejbs/swift/FileActConversionToSWIFTModule and setting the parameter DetachParameters to true. This adapter module is being used in all the three channels(1 sender and 2 receivers).
I have used ASMA ans has set the FileName checkbox.
Now after placing the file in the input directory, the file with the same name gets created in the output directory but the file is exactly same and also no .par file is getting created. I have set the Empty file handling to Ignore, so it shows that there is no data to create a .par file and only payload file is getting created but the payload file is exactly same.
Also if I use the adapter module : localejbs/swift/FileActConversionToSWIFTModule in only the sender communication channel, a payload file gets created like below.
<?xml version="1.0" encoding="UTF-8"?>
-<ns1:SWIFT_payload xmlns:ns1="http://sap.com/xi/SWIFT"><payload>PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPEZpbGU+CiA8UGFyYW1ldGVycyB4bWxucz0idXJuOnN3aWZ0OnNhZzp4c2Q6ZnRhLnBhcmFtLjEuMCIgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSI+CiAgPE92ZXJyaWRlcz4KICAgPFJlc3BvbmRlcj5jbj1jZngsb3U9bmEsbz1jaXRpZ2IybCxvPXN3aWZ0PC9SZXNwb25kZXI+CiAgIDxTZXJ2aWNlPnN3aWZ0LmNvcnAuZmEhcDwvU2VydmljZT4KICAgPFJlcXVlc3RUeXBlPnBhaW4uMDAxLjAwMS4wMzwvUmVxdWVzdFR5cGU+CiAgIDxUcmFuc2ZlckRlc2NyaXB0aW9uPkIwNDExMC1CYXRjaDE3ODc8L1RyYW5zZmVyRGVzY3JpcHRpb24+CiAgIDxUcmFuc2ZlckluZm8+QjA0MTEwLUJhdGNoMTc4NzwvVHJhbnNmZXJJbmZvPgogICA8RmlsZURlc2NyaXB0aW9uPjIwNzY4PC9GaWxlRGVzY3JpcHRpb24+CiAgIDxGaWxlSW5mbz5Td0NvbXByZXNzaW9uPW5vbmU8L0ZpbGVJbmZvPgogICA8Tm9uUmVwdWRpYXRpb24+VFJVRTwvTm9uUmVwdWRpYXRpb24+CiAgIDxTaWduPlRSVUU8L1NpZ24+CiAgIDxQcmlvcml0eT5Ob3JtYWw8L1ByaW9yaXR5PgogIDwvT3ZlcnJpZGVzPgogPC9QYXJhbWV0ZXJzPgogPERvY3VtZW50IHhtbG5zPSJ1cm46aXNvOnN0ZDppc286MjAwMjI6dGVjaDp4c2Q6cGFpbi4wMDEuMDAxLjAzIiB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWluc3RhbmNlIj4KICA8Q3N0bXJDZHRUcmZJbml0bj4KICAgPEdycEhkcj4KICAgIDxNc2dJZD4xMDAwMzI4MTE1PC9Nc2dJZD4KICAgIDxDcmVEdFRtPjIwMTQtMDMtMjhUMTk6MjY6Mzc8L0NyZUR0VG0+CiAgICA8TmJPZlR4cz4xPC9OYk9mVHhzPgogICAgPEN0cmxTdW0+NTkwLjAwPC9DdHJsU3VtPgogICAgPEluaXRnUHR5PgogICAgIDxObT5BTEVYSU9OIElOVC4gU0FSTDwvTm0+CiAgICAgPElkPgogICAgICA8T3JnSWQ+CiAgICAgICA8QklDT3JCRUk+QUxYTlVTMjBYWFg8L0JJQ09yQkVJPgogICAgICA8L09yZ0lkPgogICAgIDwvSWQ+CiAgICA8L0luaXRnUHR5PgogICA8L0dycEhkcj4KICAgPFBtdEluZj4KICAgIDxQbXRJbmZJZD4xMDAwMzI4MTE1PC9QbXRJbmZJZD4KICAgIDxQbXRNdGQ+VFJGPC9QbXRNdGQ+CiAgICA8QnRjaEJvb2tnPmZhbHNlPC9CdGNoQm9va2c+CiAgICA8TmJPZlR4cz4xPC9OYk9mVHhzPgogICAgPEN0cmxTdW0+NTkwLjAwPC9DdHJsU3VtPgogICAgPFBtdFRwSW5mPgogICAgIDxJbnN0clBydHk+Tk9STTwvSW5zdHJQcnR5PgogICAgIDxTdmNMdmw+CiAgICAgIDxDZD5TRVBBPC9DZD4KICAgICA8L1N2Y0x2bD4KICAgIDwvUG10VHBJbmY+CiAgICA8UmVxZEV4Y3RuRHQ+MjAxNC0wMy0yOTwvUmVxZEV4Y3RuRHQ+CiAgICA8RGJ0cj4KICAgICA8Tm0+QUxYTiBCRU5FTFVYIEJWIE5MIEJSQU5DSDwvTm0+CiAgICAgPFBzdGxBZHI+CiAgICAgIDxTdHJ0Tm0+U3RyYWF0PC9TdHJ0Tm0+CiAgICAgIDxUd25ObT5OZXRoZXJsYW5kczwvVHduTm0+CiAgICAgIDxDdHJ5Pk5MPC9DdHJ5PgogICAgIDwvUHN0bEFkcj4KICAgICA8Q3RyeU9mUmVzPk5MPC9DdHJ5T2ZSZXM+CiAgICA8L0RidHI+CiAgICA8RGJ0ckFjY3Q+CiAgICAgPElkPgogICAgICA8SUJBTj5OTFhYQU5CQTEyMzAwNDU2NzY3ODkwPC9JQkFOPgogICAgIDwvSWQ+CiAgICAgPENjeT5FVVI8L0NjeT4KICAgIDwvRGJ0ckFjY3Q+CiAgICA8RGJ0ckFndD4KICAgICA8RmluSW5zdG5JZD4KICAgICAgPEJJQz5BQk5BTkwyWFhYWDwvQklDPgogICAgICA8UHN0bEFkcj4KICAgICAgIDxDdHJ5Pk5MPC9DdHJ5PgogICAgICA8L1BzdGxBZHI+CiAgICAgPC9GaW5JbnN0bklkPgogICAgPC9EYnRyQWd0PgogICAgPENocmdCcj5TTEVWPC9DaHJnQnI+CiAgICA8Q2R0VHJmVHhJbmY+CiAgICAgPFBtdElkPgogICAgICA8RW5kVG9FbmRJZD5OTDEyMzAwNDAwMDAwMDwvRW5kVG9FbmRJZD4KICAgICA8L1BtdElkPgogICAgIDxBbXQ+CiAgICAgIDxJbnN0ZEFtdCBDY3k9IkVVUiI+NTkwLjAwPC9JbnN0ZEFtdD4KICAgICA8L0FtdD4KICAgICA8Q2R0ckFndD4KICAgICAgPEZpbkluc3RuSWQ+CiAgICAgICA8QklDPkFCTkFOTFhYWFhYPC9CSUM+CiAgICAgICA8Q2xyU3lzTW1iSWQ+CiAgICAgICAgPE1tYklkPjAwMzwvTW1iSWQ+CiAgICAgICA8L0NsclN5c01tYklkPgogICAgICAgPE5tPkFCTiBBbXJvPC9ObT4KICAgICAgIDxQc3RsQWRyPgogICAgICAgIDxDdHJ5Pk5MPC9DdHJ5PgogICAgICAgPC9Qc3RsQWRyPgogICAgICA8L0Zpbkluc3RuSWQ+CiAgICAgPC9DZHRyQWd0PgogICAgIDxDZHRyPgogICAgICA8Tm0+QUxYTiBOTCBEb21lc3RpYyBWZW5kb3I8L05tPgogICAgICA8UHN0bEFkcj4KICAgICAgIDxDdHJ5Pk5MPC9DdHJ5PgogICAgICA8L1BzdGxBZHI+CiAgICAgIDxJZD4KICAgICAgIDxPcmdJZD4KICAgICAgICA8T3Rocj4KICAgICAgICAgPElkPjAwMTUwMDAxOTc8L0lkPgogICAgICAgIDwvT3Rocj4KICAgICAgIDwvT3JnSWQ+CiAgICAgIDwvSWQ+CiAgICAgPC9DZHRyPgogICAgIDxDZHRyQWNjdD4KICAgICAgPElkPgogICAgICAgPElCQU4+TkwxMjAwMzA0NTY3ODkxMjAwMDA8L0lCQU4+CiAgICAgIDwvSWQ+CiAgICAgIDxDY3k+RVVSPC9DY3k+CiAgICAgIDxObT5BTFhOIE5MIERvbWVzdGljIFZlbmRvcjwvTm0+CiAgICAgPC9DZHRyQWNjdD4KICAgICA8Um10SW5mPgogICAgICA8VXN0cmQ+L1BNREQvVEVTVDY4MSw1OTAuMDAsRVVSLDIwMTQwMzI8L1VzdHJkPgogICAgIDwvUm10SW5mPgogICAgPC9DZHRUcmZUeEluZj4KICAgPC9QbXRJbmY+CiAgPC9Dc3RtckNkdFRyZkluaXRuPgogPC9Eb2N1bWVudD4KPC9GaWxlPgo=</payload></ns1:SWIFT_payload>
But while creating the par file, it shows that the file could not be overwritten and so the .par file is not getting created.
I need to understand that:
1) How do I configure both of my receiver channels i.e. what should be the difference. Currently, I am just setting the
same Output directory in both and file name schema * and has used ASMA with FileName parameter. So same name files are getting created and so one file gets discarded. How to create a .par file.
2) Also Is the file above is the correct file required by SWIFT.
3) Also when I check in SXMB_MONI, I can see that after running the adapter module same payload as given above is going in both payload and par files i.e. also if I am using different names in my receiver communication channels two files are getting created payload and par both are having the same payload. So what exactly should get created.
Kindly guide on this implementation.

Hi,
I am able to generate the .par file by setting the localsecurity to true and the KeyId from the key manager.
Now two files are getting created .xml and .par. .xml file which is the payload file is the same as the input file with no difference and contains both the overrides and the data parameters. The .par file contains the Algorithm and the Value.
Is this correct?
Also suppose the input file name is SEPA.xml, then the payload file is created with the name as
SEPA.xml and the par file is created with the name SEPA.xml.par. I need only SEPA.par. How to achieve this.

Can you share a USB to Serial Adapter that is connected to a MAC

Can you share a USB to Serial Adapter that is connected to a MAC, across the network (LAN).
Essentially it would be comparable to a simple Terminal Server.
Is it possible?

Thanks for the swift reply.
Continuing my investigation I started to come to the conclusion you just mentioned. I am surprised none of the staff at my store realized this. However, at least I know now.
The basis for me looking to this is... With leopard on the eve of its release, I wanted to get a large network accessible storage solution that would allow my wife's and I's Macbook pros to use time machine on the network drive when we were at home. Since we rarely use our laptops while sitting at a desk connected to an external drive, I figured this would be a great idea and started to look into various NAS solutions.
Surprisingly, most generic (netgear, western digital) network drives require you use proprietary software to connect to them, and are only compatible with windows xp. After seeing the options the airport extreme opens up in terms of network storage I figured it would be the best bet.
Do you have any other suggestions besides getting an airport extreme? I would rather not have to buy a full blown mac that I have to leave on 24/7 to share the drives. Or do you see any possible pitfalls to this idea? Such as, would time machine forget to use the network drive after a while since it wouldn't always be available to it when away from home?

Seeburger AS2 Adapter

Hi,
I need few information how to implement seeburger adapter(Using AS2 or FTP) with XI. I have a requirement to convert the EDI Ansi X12 messages from a EDI system and post it into a R/3 system using XI.
The client system(EDI system) is in US has VAN and we have the R/3 in India. So do we need to establish a VAN connectivity or it can directly access the client VAN to take the EDI messages.
Do clarify whether to go for AS2 or FTP, and what are the advantages of each.
I went thro few documents from Seeburger which comes up with the package of Generic FTP adapters or we have a Standalone AS/2, or BIS:HUB and spoke.
Regards,
Nithiyanandam

HI,
Brief about the FTP/VAN adapter:
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

Seeburger Adapter

Hi all,
I have installed a generic seeburger FTP adapter, but I dont have any VAN connectivity at present. Can I convert the EDI ANSI X12 format to xml with this installation or it requires VAN connectivity to do this.
In this case do we require the BIC mapper? if so how to work with BIC mapper?
In the communication channel, I am able to see the installed Seeburger FTP adapter but it does not show the transport and message protocol. Is this related to the Installation/setup of VAN connection.
Regards,
Nithiyanandam

Hello..
SeeBurger is a leading provider of global business integration solutions.
Market launch of the most successful EDI solution for the automotive industry in 1986.
the company today serves more than 7,000 customers in 42 countries and more than 15 industries through its flagship B2B Gateway and related products and services.
First company worldwide to receive certification for SAP R/3
Building a closer partnership with SAP.
Extended any-to-any-conversion.
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.
Mapping Designer, a graphical tool, easily defines data format conversions via drag and drop functionality, enabling easy integration between source and destination files. A central mapping reposiu00ADtory enables comprehensive support of versioning and deployment support, such as self-testing and auditing.
The SAP Exchange Infrastructure message format is based on XML, but it also can work with non-XML data using attachments. In some cases it may be necessary to convert the main XML document in a message, into a non-XML document. The use of BIC is very common in Business-to-Business scenarios where EDI standards are in use.
The Business Integration Converter (BIC) of Seeburger is based on Java JIT Technology and can be used for small real-time messages, as well as very large master data (i.e.Catalogs) batches.
BIC can convert outbound invoices from XML format (used in SAP XI) to an EDIFACT invoice. The conversion can be executed before the message is transmitted to the business partner. The other way around, once an EDIFACT message has been received from the business partner, it must first be converted to XML format, which is the format SAP XI supports.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. BIC will allow you to do the following
Once you install BIC, you need to do Import the Generator Mappings into the Project Explorer of BIC MappingDesigner.
You can find Generator Mappings as a ZIP file in the following location <BICMappingDesignerInstallationDirectory>\user\bicmd\Exchange and select the file prj_GeneratorMappings.zip.bicmd.
In MappingDesigner select File Import Generator Mappings Zip File prj_GeneratorMappings.zip.bicmd Clik on Add and OK.
Once Import is done you can see Generator Mappings in BIC Mapping Designer.
The SEEBURGER Adapter runs on the SAP WEB AS (J2EE Engine)
The SEEBURGER Adapter is integrated into the SAP Exchange Infrastructure over JCA (Java Connector Architecture)
Consequence :
Supply of the complete SEEBURGER EDI/B-to-B-Technology-Suite within SAP NetWeaver
Central File of Business Content (mappings, integration processes) in the Integration Repository of SAP XI
Central configuration and design by using the Tools of XI in the configuration
Central monitoring and alerting over SAP XI
Seeburger Solutions Overview
BIC Mapping Module
Functional Acknowledgement Solution
Operational Dashboard / Archiving
Invoice Solutions
Communication
The Business Integration Converter (BIC) from SEEBURGER is a converter for the implementation of data formats.
Following formats are available:
ANSI X.12 (American National Standards Institute)
CSV (Comma Separated Variable formats)
EDIFACT (all subsets)
INHOUSE (VDA, flatfiles, e. g. SAP IDoc)
SWIFT (banks)
TRADACOM (Trading Data Communications Standard)
XML (DTDs and SCHEMATA)
Able to classify messages into the following message types:
XML
EDIFACT
Ansi X 12
Tradacom
VDA
IDOC
Swift
Inhouse
XML Ansi X 12
XML EDIFACT
XML Tradacom
XML VDA
XML IDOC
Go through this links..
Some more..
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
Reward Points if it is really useful to you.....
Thanks,
Satya Kumar..

SWIFT Adapter ?

Similar Messages

Maybe you are looking for