Receiver File adapter not able to handle the special Char

We have asynchronous interface from MDM file to CRM (Seibel) file. XI picks up the file from MDM and process them with transformation. It is observed that if the file contains the special character such as ®, it is not writing the output file. The trace is checked and it goes to the adapter framework to do the FCC but do not write the file.It marks the process as successful in SXMB_MONI. Any pointer will be helpful.
Thanks,
Samir

Hi,
Try with ISO-8859-2
http://en.wikipedia.org/wiki/Windows-1250
see the last row in the above link.
Secondly to make sure if you are getting the correct char or not, just open the file in Internet Explorer and choose the correct codepage, then you see the characters correctly.
Regards,
Sarvesh

Similar Messages

Setting dynamic file name in Receiver file adapter - not from payload

Guys I just remember reading a weblog but can't find it now that I need it, on how to set the file name in message mapping dynamically but not using any payload field.
Please let me know if you remember this.
Thanks a lot,
Viktor Varga

also u can check in
<a href="/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II</a>
<a href="/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14: The same filename from a sender to a receiver file adapter - SP14</a>

Receiver File Adapter Not Executing OS Command

Hello All!
We are currently running PI 7.1 and wish to use a Receiver File Adapter to FTP a file to a mainframe and override the FTP system defaults.
Tried using the 'quote site recfm=fb lrecl=80' OS command but discovered that this would not work as the Adapter Engine is NOT on the mainframe.
Regrouped a bit and made a second attempt which involved writing a Unix script to ftp a file and override rthe system defaults. The idea was to use the File Adapter to FTP the data to the server, invoke the script and get the file to the mainframe with the proper attributes. The script when executed on the server works perfectly.
However, when the IDoc comes thru PI, the File Adapter ftp's the file ok but the script is never executed.
Any ideas why this is so or any suggestions?
Thank you.

Hi Ken,
Script only executes at Network File sharing (NFS) only. It dont work at FTP level.
So you can better write the file on NFS and then within the script to connect to ftp and do your processing.
Regards,
---Satish

Receiver file adapter not functioning

Hi guys,
We have developed some interfaces that are exporting some .txt files in ftp locations and therefore they make use of receiver file adapter. Although the receiver file adapter used to function properly some days ago, for some strange reason, it stopped receiving any files. This happens only in XI development system but not in XI production system. In XI development, in Runtime Workbench --> Communication Channel monitoring, I can see this communication channel's status as correctly configured and started, with a green sign on the right, but it is not responding when some files are sent to it, and therefore there are no output files in target directory.
Any ideas?? It is urgent.
Best Regards
Evaggelos

Udo,
Hi Amit,
I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
When I go into Details -->Audit Log for a single message:
2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-13 11:49:33 Success Message successfully put into the queue.
And in Message Data there is the following information:
Status To Be Delivered
Repeatable Yes
Cancelable Yes
Error Category
Error Code
Start 13.06.2007 11:49:33
End
Sender Party
Sender Service TPBS_GR
Receiver Party
Receiver Service TPBS_GR
Interface http://famar.gr:LoyaltyDataMNSToSRS
MI_LoyaltyDataMNSToGR_IB
Quality of Service Exactly Once
Message b2685674-7626-5141-bfa1-13155ad0d25a
Reference
Conversation ID
Serialization Context
Direction INBOUND
Message Type Recv
Profile XI
Connection File_http://sap.com/xi/XI/System
Transport HTTP
End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
Authorization
Sequential Number 0
Number of Retries 3
Failed 0
Retries 300000
Valid to
Persist Until 13.07.2007 11:49:33
Schedule Time 13.06.2007 11:49:33

Sender File Adapter not able to get file via FTP from an external system

Hi,
I have a Sender File Adapter using FTP which polls a server every 10 seconds looking for a file ".xml". The adapter will connect and pick up the waiting file, but sometimes the adapter not able to get file via FTP from an external system. The file is on the server, but despite the polling, the adapter does not pick up it. There is no return error.
The connect mode is Permanently and the transfer mode is Binary.
Can you help me?
Thanks.
T.

Hi Teresa,
does this case appears with a file size higher the others?
Personally, I do not recommend to have a polling under 1min.
10s could be too just, if the file is not small and/or if the file server is far (several kilometers) to where the Adapter Engine is, and/or this file server is beside a firewall. Do not forget also that, with previous points, you could have like a conflict, betwen the 1st polling and the 2nd polling, if in less 10s PI adapter has not enough time: to connect to the FTP server (several Km), find the file (perhaps among 100 other files in the directory), go back to the file to Adapter Engine server (several Km again), convert your file to XML message (with a complex Content Conversion), then check the XML structure, and when all that is done, return back to FTP server (several Km), to archive the source file... Well It's my understanding of a FTP exchange with FILE adapter...
If you really need a 10s polling, that's mean your have a pseudo real time interface. In that case, in my mind file should not be used! but we should use a Web service, JDBC JMS (any exchange without a physical object like a file). For me, it's a non-sens to have a file in that case.
regards.
mickael

Receiver file adapter not responding

Hi guys,
I have 2 interfaces in XI development system that make use of receiver file adapter in order to receive some .txt files. Although these communication channels used to work until yesterday, for some strange reason they stopped functioning, but only in development system. However, I cannot see any error in Runtime Workbench (Communication channel monitoring), it's status is "correctly configured and started" and has a green sign. But, when I sent a file from sender adapter, it is sent correctly, but it never gets received from receiver communication channel.
There is no error in SXMB_MONI either.
In XI production system, the same interfaces are functioning well.
Any ideas?
Best Regards
--Evaggelos

Hi Amit,
I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
When I go into Details -->Audit Log for a single message:
2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-13 11:49:33 Success Message successfully put into the queue.
And in Message Data there is the following information:
Status To Be Delivered
Repeatable Yes
Cancelable Yes
Error Category
Error Code
Start 13.06.2007 11:49:33
End
Sender Party
Sender Service TPBS_GR
Receiver Party
Receiver Service TPBS_GR
Interface http://famar.gr:LoyaltyDataMNSToSRS
MI_LoyaltyDataMNSToGR_IB
Quality of Service Exactly Once
Message b2685674-7626-5141-bfa1-13155ad0d25a
Reference
Conversation ID
Serialization Context
Direction INBOUND
Message Type Recv
Profile XI
Connection File_http://sap.com/xi/XI/System
Transport HTTP
End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
Authorization
Sequential Number 0
Number of Retries 3
Failed 0
Retries 300000
Valid to
Persist Until 13.07.2007 11:49:33
Schedule Time 13.06.2007 11:49:33

File Adapter not able to read quotes after pipe

I have flat file delimited by pipe |, and optionally enclosed by " quot, below is the xsd definition
"<xsd:element name="vtext" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy="""/>"
<Field Before>|"TRANS" IN TRANS FAT SHOULD APPEAR IN ITALICS MH|<FieldAfter>
the file adapter fails to read |", but if I put a space between them, all works well. But, if it is continuous it fails to read resulting in an error.
any help in reading such a string in nxsd would be of great help..
thanks,
Shailesh

Can you please give us a before and after?
I am guessing you want to read the text with the pipes?
If thats the case try this:
"<xsd:element name='element1' type='xsd:string'
nxsd:style='surrounded' nxsd:surroundedBy='|' /> "
Replace the single ticks with double ticks. For some reason it does not display well in the forum.
Edited by: soa_adf on Apr 13, 2012 11:29 AM
Edited by: soa_adf on Apr 13, 2012 11:29 AM

Receiver FTP adapter not intialized

Hello all,
I have set up a receiver File adapter but when I check the adapter monitor it shows me "Adapter not initialized"...The authorizations are prefect since I have set admin id's in the FTP server username and pwd. I would like to check the adapter engine to see if this adpater has been turned on..What is the URL to check the adapter engine in the J2EE stack ?? Also I set up a mail adapter which never shows up in the adapter monitor ..What could be missing??
-Ken

Hi,
go to the path:
<server>\<sapSID>\DVEBMGS10\j2ee\cluster\server0\log\services\com.sap.aii.adapter.file.svc
inside you should be able to find all of you adapters
config_[adaptername] files.
inside you can see their configuration and sometimes
an error message at the end
maybe there will be something over there
Regards,
michal

RECEIVER FILE ADAPTER FCC ERROR

Hi team
My scenario is a text file has to be picked up by PI, has to processe it and the receiver is Proxy and it has to get updated and sent back to FTP location.
i am using Sender File Adapter with FCC and Also receiver File Adapter with FCC.
Both the sender and receiver structures are same; i am using the same FCC parameters for both the sides.
in Receiver File Adapter i am getting the following errors
1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
please help me out
thank you
Edited by: vemugantivn on Aug 16, 2010 12:19 PM

Hi,
> 1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
> 2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
It is saying that you are not using the fieldSeparator parqameter.
have you provided the field separator parameter? if not then give like below
order_row.fieldSeparator : , (give what ever the separater you are using)
or
order_row.fieldSeparator : 10,5,... (if you are using fixed length)
Regards
Ramesh

Receiver file adapter error for special char.

I am using MTB in my receiver file adapter. I am getting a special character from source system at end of the string. How to resolve this type of error u2013 please advice.
This error is not coming for every message.
Error message:
Column value xxxx Â too long - must stop, probably configuration error in file adapter
Thanks
Vick

Hi,
Itu2019s basically IDOC to file scenario.
This error is coming for name field.
What I am thinking at this stage to do changes in MTB by define parameters like (NameA.enclosureConversion)

Not able to run the Jdeveloper Pages in Local Machine

Dear All,
I am developing Custom OAF Pages in R12. while am not able to run the page in Local Machine Currently i am using Remote VPN. same page i import into server am able to run in Application.
The error says:
1, Increae the time limit bye setting the JRAD.RUNREG.TIMEOUT Parameter in ide.parameters file loacted in System directory.
I found the file . am not able to find the JRAD.RUNREG.TIMEOUT Parameter option
2, Check the Host Name in the Preferances, Under Embeded OC4J.
I Verified same and using the Default Local IP Address.
I am using Jdeveloper Version : p8431482_R12_GENERIC.zip
Please help me. I approciate before
Thanks
Venkat Reddy Pulichintha
00971502644919
[email protected]

Dear Gaurav,
Thanks for you quick replay
For this Patch number (p8431482_R12_GENERIC.zip), there is no (JAVA Options: remove this statement: -DFND_JDBC_STMT_CACHE_SIZE=200 -DCACHENODBINIT=true)
Please guide me furthe steps. any other settings requird.
Thanks
Venkat Reddy Pulichintha
00971502644919
[email protected]

I received a pdf from someone with an updated reader. I am not able to open the file or download the update. ERROR 1932 ????

I received a pdf from someone with an updated reader. I am not able to open the file or download the update. ERROR 1932 ????

ERROR 1935 SORRY PLEASE HELP I CANNOT OPEN ANY PDF'S ON MY COMPUTER NOW????????????????

The same filename from a sender to a receiver file adapter

Michal has provided us with a brilliant <a href="/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14. I guess a lot of people have been waiting to do this. However, I have a slightly different scenario. In this case, XI is used as a medium to transfer a PDF file from one directory to another directory. There is not transformation or mapping involved.
The message is send by File Sender Adapter and received by File Receiver Adapter. Message type is created as a simply type hexBinary. The file is supposed to be picked up as a PDF and received as a PDF, retaining the same file name. As such, the file name is neither stored in the source structure nor the target structure.
Once the PDF file is transfered into target directory, it should be able to be open by using Acrobat directly without further conversion.
We might add a file name file into the target structure but would that rendered the PDF non-readable upon being received by the File Receiver Adapter?
Any feedback is highly appreciated.

Hi
>>We might add a file name file into the target structure but would that rendered the PDF non-readable upon being received by the File Receiver Adapter?
No, adding file name would not hamper the properties. You can name *.pdf or something else.
For that matter any file pdf, word, .msg format etc can be transferred by this approach. We have tried it.
Earlier to SP14 you cannot give the same name to outgoing file without writing a Adapter module. But things are easy with SP14.
Cheers,
satish

Receiver file adapter creates empty files, Empty-Message Handling SP19

Hello,
We have just upgraded the system to SP19.
One of the new features is that it should be possible to determine how XI messages with an empty main payload are to be handled in the receiver file adapter.
If the parameter Empty-Message Handling is set to 'Ignore' no file should be created if the main payload is empty. In our case an empty file (size 0 kb) is still created even though the main payload is empty and the flag is set to 'Ignore'.
Has anybody experienced the same problem?
// Best regards Hans

This should work:
Use your own adapter module that parses incoming message and checks if it has any record sets in the document. If it does not have any record sets, then set the message to empty and then give this modified message to File receiver.
For example, see the example code below:
Module imports..
Audit log import..
DOM imports/SAX imports..
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData) throws ModuleException {
          try {
               // get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
               Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"RemoveRootTag: Module called");
               XMLPayload payLoad = msg.getDocument();
               Document doc = parseXmlFile(payLoad.getInputStream());
               if(doc != null){
                    if(!doc.getDocumentElement().hasChildNodes()){
                         Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS, "Document is empty!!");
                         payLoad.setContent("".getBytes());
                         msg.setDocument(payLoad);
               // provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
               } catch (Exception e) {
               // raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
               // return XI message
          return inputModuleData;
     private Document parseXmlFile(InputStream xmlpayload) {
          try {
               DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
               factory.setValidating(false);
               //        Create the builder and parse the file
               Document doc = factory.newDocumentBuilder().parse(xmlpayload);
               return doc;
          } catch (SAXException e) {
          } catch (ParserConfigurationException e) {
          } catch(IOException e){
          return null;

PI is not able to pick the file from the FTP folder

This is the FILE TO IDOC scenario. We have configured the file adapter. But its not able to pick the file from the specified directory. We have tried changing the transfer mode from Binary to Txt & also we have tried to put advance selection for source file but it didn't work. Its throwing the below error:
PI Adapter Log:
An error occurred while connecting to the FTP server '10.130.150.21:8529'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 451 Unexpected reply coderequested action aborted: local error in processing'. For details, contact your FTP server vendor.
Also we have contacted the FTP team & they told that PI is sending an unsupported command. So instead of taking the file TLOG.txt, its treating this file name a s a directory. Please find the logs from FTP end below:
FTP Log:
(207197)2/5/2013 14:48:25 PM - sysisappi (63.130.82.16)> 230 Logged on
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> FEAT
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 211-Features:
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> MDTM
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> REST STREAM
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> SIZE
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> MLST type*;size*;modify*;
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> MLSD
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> AUTH SSL
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> AUTH TLS
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> PROT
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> PBSZ
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> UTF8
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> CLNT
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> MFMT
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 211 End
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> PBSZ 0
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 200 PBSZ=0
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> PROT P
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 200 Protection level set to P
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> CWD /Qas
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 250 CWD successful. "/Qas" is current directory.
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> CWD SAP_ORION
(207197)2/5/2013 14:48:26 PM - sysisappi (63.130.82.16)> 250 CWD successful. "/Qas/SAP_ORION" is current directory.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> CWD Inbound
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> 250 CWD successful. "/Qas/SAP_ORION/Inbound" is current directory.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> CWD IRIIN04
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> 250 CWD successful. "/Qas/SAP_ORION/Inbound/IRIIN04" is current directory.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> CWD TLOG.txt
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> 550 CWD failed. "/Qas/SAP_ORION/Inbound/IRIIN04/TLOG.txt": directory not found.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> QUIT
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> 221 Goodbye
It should list *TLOG.txt* but instead it is trying to get into a directory named *TLOG.txt*. same for other interface.
So me & my team is struggling for last couple of days to fix this issue.Please share your suggestion

Hi Sisir
The screen shot of your config doesn't seem to correspond to the FTP log. I say this because the * is dropped from file name pattern "*TLOG.txt" (comparing your config and the FTP log). Can you share an updated FTP log?
Sisir Das wrote:
"/Qas/SAP_ORION/Inbound/IRIIN04" is current directory.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> CWD TLOG.txt
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> 550 CWD failed. "/Qas/SAP_ORION/Inbound/IRIIN04/TLOG.txt": directory not found.
(207197)2/5/2013 14:48:27 PM - sysisappi (63.130.82.16)> QUIT
Also, like Rajesh suggested, have you tried to manually check permissions by logging in, traversing the directory, and getting the file?
By the way, we always use backslash \ instead of forward slash in our configs. Not sure this would make any difference for you though. Also, I don't normally use a trailing \ at the end of the source directory path.

Receiver File adapter not able to handle the special Char

Similar Messages

Maybe you are looking for