Archiving faulty source files in file sender adapter

Hi All,
I have configured file to file scenario in which files are read from FTP server & moved to archive directory after processing & new file is created in target directory.
Scenario is working fine with above mentioned case but I want to move faulty source files to different directory (not to archive directory). There is one option available to move it to different directory. But instead of moving faulty files to faulty directory, files are getting moved to archive directory & I am getting Mapping Exception error in SXMB_MONI (which is correct).
Does any body know how to move faulty files to fautly directory ..???
I am using PI 7.0

hi,
xi does not validate your message
(so it does not know if it's good or faulty)
so you can send anything, even jpg files...
only when you use MESSAGE MAPPING
will the error occure - indicating that
your message had wrong structure
if you want to validate youself you can
do it inside an adapter module and put it into another folder
this will requiure a little bit of programming but
you will have the files validate as you want
Regards,
michal

Similar Messages

Error with Archiving Faulty Source File in Sender FTP adapter

Hi All,
I have configured a Sender FTP adapter with Processing Mode as Archive.
I am able to read the files from FTP server and archive all the successfuly processed file in the PI aplication server directory XXX/success.
We need all the error files also to be archived on PI application server in directory XXXXX/Fail so I have checked the option Archive faulty Source Files and provided the application directory XXXXX/Fail .
I have unchecked the option Archive Files on FTP server.
But the problem is when FTP adapter is getting any error files it is not able to archive it to application directory XXXXX/Fail .
In RWB it is showing the error
Unable to archive faulty input file /data/abc.txt to /XXXX/fail/abc.txt
Cause: com.sap.aii.adapter.file.ftp.FTPEx: 550 rename: No such file or directory
This directory is existing and works fine when I give this directory name in Archive directory of processing mode.
Sender FTP adapter is trying to archive the file in FTP server which I dont want and giving us this error.
If I give any Directory which is present in FTP server my error files are getting archived on FTP server but not in the archived folder.
I have already unchecked the option Archive Files on FTP server.
Please help......
I am on PI 7.11
Regards
Henery H

Hi Henery,
Check the below thread, this should help you to fix the issue.
FTP adapter: exc. 550 : No such file or directory
Thanks,

Archiving faulty Source file not working in Sender Adapter FCC

Hi Experts,
I have enabled "Archiving Faulty Source File" in Sender Adapter FCC and pen down the directory path accordingly.
Likewise I also enable the processed mode as "archive" and give it the direcotory path.
However when there is a error flagged in sxmb_moni for this interface, I unable to see any file created in the error folder but I can see a file with timestamp being created in the archive folder.
I have checked the access right to the directory, so this is not an issue. I ran through the forum on this subject and come across the help.sap note on the following
" To archive source files where a permanent error occurred during processing, set the indicator.
A permanent error occurs either during the conversion of the file content, or in a module in the module processor.
More information: MessageTransformBean, Migrating Dispatcher Classes
○ Specify the Directory for Error Archiving.
○ To add a time stamp to the archived file, select Add Time Stamp. "
What is the definition as "permanent error". The error I got in sxmb_moni is a mapping conversion error, so it should be archive this to the error folder, right ?
Anyone have any such setting enabled and working ?
Regards
FNG

The error I got in sxmb_moni is a mapping conversion error, so it should be archive this to the error folder, right ?
No, it is not the case. As mentioned on the SAP Help site, for the faulty file to be archived, the error has to occur in content conversion, or in module processor.
If the error you are getting is in MONI, then it means syntactically the file is correct and hence adapter engine has picked up and sent to integration engine (SXMB_MONI).
-Supriya.

Processing Mode = 'Delete'; Archive Faulty Source Files; Add Timestamp ?

XI3.0 SPS 19
For FTP Sender adapter, if Processing Mode is Delete, and you want to Archive Faulty Source Files with an added timestamp, it does not work (meaning it does not archive the faulty source file at all).
Any suggestions?
If I change the processing mode to Archive, it works. But my requirement is to archive only faulty files after adding timestamp and the source files should be deleted if processed.
Thanks
JB

Hi james
If you are using FCC or Modules then only Faulty files will be archived.
The error that works with this should be a permanent error of file like field missing or compulsory field etc.
if i understand correct you are trying to use Archive faulty messages in delete mode and you have FCC right ?
I have also seen this behavior in delete mode it File adapter never archive. So it wont archive the faulty file as well.
Thanks
Gaurav

Archive Faulty Source files

Hi all,
What is the use of "Archive Faulty Source files" option in Sender File FTP adapter. When I can use it.
In general, we can expect error only at the mapping level in moni in that case file would have already been picked from the source directory and then deleted.
But I think when we enable this option, I feel like the file has to still remain in the source directory after having failed to process and this file has to be archived in a seperate directory for error messages. How do I achieve this and when can a file remain in the source directory itself without being deleted in case of error other than mapping error which is seen in Moni.
Regards,
Nithiyanandam

Hi Nithiyanandam,
I faced the same issue of faulty files not getting archived to the fault archive folder.
But finally I realized that the XML validation is happening at Integration engine and not at adapter level so it archives all the files which are getting read.
I checked the option of validation by adapter in ICO(this can be done only while creating ICO, otherwise it is greyed out) and this can also be checked in Sender agreement.
Finally the files were getting archived to fault archive folder in case of invalid xml files and valid ones to original archive folder.
There is no need to message transformation bean for achieving this.
Although late but I hope its was helpful!
Thank You,
Indu Khurana.

Archive Faulty Source File

We have an issue in moving the faulty source files to a particular directory.
We could move all successfully processed files to an archive directory, but not able to move the error files (having some data issue) to another archive directory, so that we can continue with processing of other files.
Module used:
AF_Modules/MessageTransformBean --> 1
Parameter:
Transform.PermanentErrors --> true
But this is not working.
I see a similar thread which is not answered:
Re: Archive Faulty Source File
Your inputs are appreciated.

I actually have two scenarios:
1. Asynchronous
2. Synchronous
In Asynchronous; best part is, all files are getting processed, in spite if there are any erroneous files in between, at least it continues with next file. My problem here is, it archives all successful and error files to the same Archive directory; though I have mentioned different directory for u2018Faulty Source Fileu2019. And there are no errors when I see in the CC monitoring. But there is error in sxmb_moni (actually I have failed it intentionally)
Runtime exception occurred during application mapping com/sap/xi/tf/_CreateProductMaster_to_CreateProdu~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The element type "Products" must be terminated bythe matching end-tag "</Products>".
In Synchronous: If there are any error files in between: it never go to the next file, it is stuck in the same file and retries the same. And error in CC monitoring is:
Error: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:EXCEPTION_DURING_EXECUTE:
In sxmb_moni
Runtime exception occurred during application mapping com/sap/xi/tf/_CreateProductMaster_to_CreateProdu~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The element type "Products" must be terminated bythe matching end-tag "</Products>".

How to enable the Archive faulty source file in File adapter

Dear XI expert,
I want to enable the Archive Faultly source file, when the exchange step detects any error then move the source file to the ERROR folder.
I've already applied patch XI ADAPTER FRAMEWORK CORE 7.00 SP10 but haven't seen anythings about this function.
Best regards,
Kobsak

Hi,
Check out this link for info on how to archive the file.
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards,
Vikram

File sender adapter (FTP) - processing mode "Archive"

Hello all
We're polling files from an external FTP server. For this I created a scenario on XI according to this thread:
When setting processing mode to "Archive" in the file sender adapter (ftp) it polls the file, stores it to the archive directory I specified and then tries to delete the file on the FTP server side. This returns me an error because we're not allowed to delete the retrieved files on the FTP server!
Because of this error the file adapter stops further processing and does not poll all the other files.
How can I disable this deletion mechanism while keeping processing mode to "Archive"?!?!?
We do not want to use processing mode "Delete" or "Test" and we don't see other options to influence this behaviour.
Thanks for any guideance on this one in advance!
Kind regards,
Renaud

Hi Bhavesh
Sorry for the late answer. Unfortunately I can't ask the application system to provide file names containing a timestamp within. The files are provided by an external partner and are retrieved by several others as well.
In the meantime I managed to achieve this:
In repository I created dummy data types, message types and message interfaces. No mapping programs and interface mappings!
In configuration I created the necessary communication channels (1 ftp sender, 1 file receiver) and the required receiver and interface determinations as well as the sender and receiver agreements.
The result of this is:
I'm able to poll some specific files via ftp from remote host. The file names are file1.arj, file2.arj, file3.arj and file4.arj. All 4 files have the same SourceFileTimestamp (e.g. "20060727T053900Z").
I'm able to store those 4 files 1:1 in a target directory with the same file names. Until here I did NOT need to follow this blog: <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>.
As of this blog it is possible to access adapter specific attributes and make them available in message mapping using user defined functions. This way I'm able to get the SourceFileTimestamp from the polled files and use it in a message mapping. This way I'm also able to use it in variable substitution on file receiver adapter (syntax = "payload:root,1,fileTS,1") in order to dynamically create a directory with this syntax: YYYYMMDD.
So far so good... but the only remaining BIG problem now is, that as soon as the mapping is activated and assigned in the interface determination, the created files contain the XML payload instead of the original binary content. Where has it gone? How should the target message type look like so that it can carry over the original binary file content?
BTW: isn't it possible to post screenshots? Would be much more easier to explain things... so sorry to anyone if I wasn't clear enough!
TIA and best regards,
Renaud

File Sender Adapter in XI

Hi,
I am not able to view some parameters in my File Sender Adapter like
1. Adapter Specific Message Attributes
2. Archive Faulty Source Files
3. Adavanced Selection for Source File
I feel some problem the deployment of adapter specific files. How can I view the component information for the adapters?
Regards,
Venkatesh. R

Hi Raj,
I am working on service pack 19. I can actually see those additional parameters in one instance of XI with the same service pack. But in the other installation I am not able to view these parameters.
I can see the meta data but those properties are missing in the adapter meta data. Where can I check the adapter version and additional information about the same?
Regards,
Venkatesh

File Sender Adapter - File overwritting in the Archiving folder

Hello Experts,
I am doing File sender to proxy Receiver Async Scenario.
In File Sender adapter, i am using the Archiving option by spacifying the
Archiving path.
Files are picked up and archiving happen successfully.
Problem is: - once the File is picked up and archivied into the Archiving location
If end user again rectifies some data in the same file and place it in the source directory
then i am getting the following error in RWB Commu. channel monitoring.
Failed to archive file 'File1.TXT' as '/Input File location/File1.TXT' after processing. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 File not renamed. File already exists. You may delete the existing file and then rename.u2019 For details, contact your FTP server vendor.
I know this is because of File sender adapter is trying to archive the file with the same name(File1.txt) in the archiving location.
My Question: - Is there any option to allow the File sender Adapter for overwritting the
File in the archiving location.
Thanks & Regards
Jagesh

check if there is proper rights to over write files in the archive folder.
The problem seems to be that the rights/authorization is not there. Else the adapter usually overwrites files in the archive folder unless you use the timestamp option.
Archive
Files that have been successfully processed are moved to an archive directory.
u25A0       To add a time stamp to a file name, select the Add Time Stamp indicator.
The time stamp has the format yyyMMdd-hhMMss-SSS. The time stamp ensures that the archived files are not overwritten and it enables you to sort them according to the time that they were received.
u25A0       Under Archive Directory, enter the name of the archive directory.
u25A0       If you want to archive the files on the FTP server, set the Archive Files on FTP Server indicator. If you do not set the indicator, the files are archived in the Adapter Engine file system.

File sender adapter: archiving not possible with transp.prot "filesystem,

Hi XI gurus,
in my FILE sender adapter I want to archive the processed files to a separate sub-directory of the "in" directory.
It works if I use transport protocoll "FTP" with a specific user
but it don't works when I use transport protocoll "file system (NFS)".
the xi user has all permission on the directories.
file system is on a UNIX machine.
Has anybody an idea why archiving only works with transf.protocoll FTP ?
Thanx very much in advance
regards
Hans

Hi,
Check this thread for same problem Re: NFS Sender File Adapter Source Directory
Thanks!

File Sender adapter - source file name - weird

Hi all,
We have a sender file adapter polling an ftp location. The Dynamic config has been enabled to get the source file name.
The actual file name is - "hrmd.xml", but in the dynamic configuration node, in sxmb_moni, the fileName is shown as ./hrmd.xml.
This does not occur with any other file sender adapter comm channels polling ftp locations.
I guess this has something to do with the ftp server. Did anyone face this issue?

the fileName is shown as ./hrmd.xml
The file name surely cant have a / in it....such characters are not allowed.
is there any way we can change the fileName message attribute once the file is picked up
Create a UDF for Dynamic Configuration and change the name as per your requirement (in XI)....the source file may be having proper format for name and i assume that you have to change it for receiver file name

File Sender Adapter - Multiple Source Directory

Hi all,
I have the following file to IDoc Scenaraio:
The source file might be in any of 3 directories in source system and so created file sender adapter as follows:
File access parameters:
Source Directory : Directory1
File Name         : Filename*.XML
Addiontal Directory:
Directory2    Filename*.XML
Directory3    Filename*.XML
The porblem we are facing is the file adapter is picking the file from Directory1& 2 and not from Directory3.
If the change Directory Order in adapter as follows:
File access parameters:
Source Directory : Directory3
File Name         : Filename*.XML
Addiontal Directory:
Directory2    Filename*.XML
Directory1    Filename*.XML
... then file from Directory 2 & 3 is getting processed and not from Directory1.
Any thoughts on this will be greatly appreciated.
Thanks
Sarat.

Why use BPM for this?
Instead write an abap program to pick from any of 3 directories in source directory and place it in the shared XI folder and configure your file adapter pointing to XI shared folder...shecdule the abap report for every 5 min..
Wanna know more /people/sravya.talanki2/blog/2005/08/23/sender-xi-ftp-adapter-with-regular-path-expression-150-abap
Or write OS level scripts for doing same.

Error Archiving File in File Sender Adapter using AF_Modules/PayloadZipBean

Hi everybody.
I have to pick a zip file up from ftp server, unzip an convert the file in xml.
Im using this modules in file sender adapter:
AF_Modules/PayloadZipBean --> To unzip de file
AF_Modules/MessageTransformBean --> file to xml
The problem is when I try to archive de file. Im getting this error and I dont know why (This path exists /out/ProcesadosSinError/)
Could not archive file 'test.zip' as '/out/ProcesadosSinError/20100518-091029-155_test.zip' after processing: java.io.FileNotFoundException: /out/ProcesadosSinError/20100518-091029-155_test.zip (A file or directory in the path name does not exist.)
Could it be that is not possible to archive with AF_Modules/PayloadZipBean?
Thank u so much

Hi Stefan.
Absolutely. This path exists. It's an absolute path from root. I can´t understand the error!!!!
Thanks!!!
Edited by: Christian Abad Chico on May 18, 2010 9:35 AM

File Sender Adapter - Dinamic Source Directory and Filename

Hi Experts,
I have to receive in XI a file and depeding of some info, put it in diferent directories with diferent fieldnames.
In receiver File Adapter we can set the directory and fieldname dinamically by ABAP-CLASS mapping, but not in Sender.
I've read Michal's blog
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
and sap help
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
But, I can't find Adapter-Specific Message Attributes in my File Adapter...:-) I've checked SP version is SP16, where are my Adapter-Specific Message Attributes?
How can I set Directory and Fieldname at runtime for Sender File Adapter?
Please help...
Thanks all in advance,
Regards.
Urtzi.

Hi Nilesh,
Your threath is not about my issue...
Answering to other friends, what I want is not to write p.e.: '/server/dir/' in each File Sender Adapter Channel, and put it with any other way looking some 'customizing' or checking a condition.
The problem is that frecuently in the Company changes servers and we have to enter to the Directory and change every Channel one by one...We would like to reduce the maintain of the Channels with a mapping, variable, customizing table...or something similar. Do I explain?
I don't know if its possible but I had the hope...:-)
Thanks all.
Urtzi.

Archiving faulty source files in file sender adapter

Similar Messages

Maybe you are looking for