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

Similar Messages

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.

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,

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>".

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

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

Processing mode - DELETE not working in Synchronous mode (File - RFC - File

Hi ,
I need to the delete the files from source folder once the processing is done, so i am giving the Processing mode as Delete in the Sender C.C.
But after execution it doesnt get deleted. what could be the reason?
We are using a file - RFc - file scenario.
also could anyone let me know what is the command to move a file from one folder to another in UNIX.
i tried
mv /home/out but it doesnt work
pls help.

Hi,
you can use AL11: navigate to the folder, where the file is inside, mark it and press button "Attributes". Then look to value "Mode": 777 means owner, group and everybody else has right for write (in your case delete), read and execute. UNIX command to change is may be ch mod (i m not good in UNIX).
My suspect is that the file adapter user has not the right for write, but ur direct user has.
Regards,
Udo

Archivelog Mode Deleting archive files

Hey,
I have been reading about archivelog mode for a while and understand the concept and how it works. The one thing that is still alluding me is the removal/deleting of old archivelog files and how long I need to keep the files.
I hear people saying "backup your archive files", how long do I need to keep the backed up archive files?
What this sounds like to me is "you better keep every archive file ever created by your database in order to restore". This sounds silly to me but thats how I am interpreting this. Can someone please help me understand this a bit better?
Thank

Archive logs are normally backed up when a database backup is done. Some shops might backup archive logs more or less frequently. You need to keep the backuped archive logs for as long a necessary to meet the recovery policies set forth by the business.
For example, for some database that I manage the business decision is to retain backups for an entire year. Other database have a smaller time frame of 2 to 6 months and some are only a week. So you can see that I do not keep every archive log ever created, I just keep the ones necessary to fulfil the recovery policies set by the business.

JDeveloper v10.1.3.0 - Debugging Mode - Unable to fiind source file

I just upgraded to a newer (10.1.3.0) version of JDeveloper.
When I'm stepping through Java code in the debugger and I need to step into code that is in another project, I get a dialog box telling me "Unable to find source file".
The dialog box has four radio buttons and in the past, I chose the "Look for the file in project: " which had a drop down box where I could select the project that the Java file was in.
With the new vesion, this does not work. I have to select the second option, which is "Let me find the file myself with the open file dialog".
This latter method works, but it is much more time consuming than the former. Has anyone else noticed this problem before and found out a way to fix it?
Thanks in advance for any help on this matter.
Greg

Just some more information from me, the original poster...........
When I try to do the remote debugging....
Under the project's Run Configuration, Launch Settings, I check the "Remote Debugging and Profiling"
Under Debugger, Remote, I select the "Listen for JPDA
Then I select the project and chose "Start Remote Debugger"
Then I set a breakpoint in the PL/SQL
Then at the SQLPLUS command line, I enter "exec DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', 4000 );"
Response from SQLPLUS is:
BEGIN DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', 4000 ); END;
ERROR at line 1:
ORA-12571: TNS:packet writer failure
===========================================================
When I try debugging locally............
I uncheck "Remote Debugging and Profiling"
In Run Config, Debug, Remote, I select Attach to OJVM as the protocol
I then select the PL/SQL function that I would like to debug and select "Debug"
Here are the results from JDev....
Connecting to the database QF.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '3263' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database QF.
=========================================================
Any help would sure be appreciated.
Thanks,
Greg

Need Target File Name Timestamp is same as Source File name Timestamp

Hi ,
I want to genereate Target file name (Target_09062008082030.xml) but this time stamp is exactly Sorce FileTime stamp..(Source_09062008082030.xml)..
so, i want to create a target file with the same source file time stamp..
for this.. i sed Message Specific attributes... in both sender and receiver side.. but that was creating with the complete name.of source file name.. but i want only Timestamp of the source filename... and remaing is the constant.. for this how can i proceed ..
Thanks
Jain

See in Sender CC when you set the Adapter Specific Message Attr for file name it will send the filename in the header of the XI Message.
To acces this file name inside mapping you need to create a UDF . The type can be any thing as you desire.
You dont need to pass any variable .if suppose you want the file name (constant) e.g ABC_<timestamp>.xml
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String fileName= conf.get(key);
//see above your key is FileName which will be sent by the sender CC automatically... You are simply accessing it here using get() method.
//now ur filename will contain name of the source file... you need to perform a substring operation to get the timestamp and create a new file name as you desire.
fileName = "New_<timestmp>.xml"; //for e.g
//set this file name again in header message using put()
conf.put(key, fileName);
//when you check on the adapter specific message attr for fileName in the receiver CC ,it will automatically take this new file name value.
return fileName;
// if you want to use this new fileName inside your mapping payload (for other fields) you can assign this to any target field,else just assign it to the root tag which will make no difference if this file name is not used anywhere.

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

Archive Source Files with Errors

Hi All,
I need to archive my sending file in repective directory, if it has errors..
It is mentioned in library that A permanent error occurs either during the conversion of the file content, or in a module in the module processor.
What is permanent error?
For example if my input file name is abc.txt which containg 3 fields id,name,address.
i have configured sending file adapter with FCC .
now i have given some faulty entries in abc.txt like for example 4 fields separated by comma,
but this is a error.Asper FCC i have given only 3 fields..
so this error file has to archive in so and so folder.
If i check Archive Source Files with Errors parameter in sending file adapter.
and specified the specified directory.
but its not working for me. file is not picking but its not coming in the archive folder.
In library it is mentioned to see message transfer bean link.
there i found Transform.PermanentErrors: True/False.
If we have not used message transfer bean then, in that case will this parameter archive source files with errors will work for FCC?
Please suggest me .
I would really appreciate if anyone could send a complete blog for this how to archive source files with errors in FCC?
Thanks in Advance..
Regards,
Reehan

Reehan,
I am not sure if you are still stuck with your issue of archiving faulty source files but I came across the same issue. Please check your mode of processing. The faulty source files archiving feature will work good in ARCHIVE mode but not in test or delete mode. I haven't check for set for read-only mode.
Good luck!

Archive Source Files with Errors, Option Does not work

Any one tried "Archive Source Files with Errors" on the
sender adapter. It shows no effect.
1.We are on SP19.
2.Adapter type : FTP adapter.
Steps for the Reconstruction
1. Configure a sender FTP adapter.
2. choose the option "Archive Faulty source files"
3. Specify a directory for "Directory for archiving Files with Erroors"
4. Send a file which can cause File Content conversion errors.
Regards,
Raj

Hi,
FYI
I am in PI 7.0 SP 10. It works fine for me. Whenever you have any content conversion problem or module problem, it has created the same input file in specified directory.
In your case are u getting content conversion error in the Communication Channel ..just cross check it. If not try to get error over there and then test this feature
Rgds,
Moorthy

Archiving Processedor Errored Files on FTP folder-Receiver File Adapter

Hello,
A quick question, we have a scenario where we are picking a file from FTP folder and we need to archive it on the
1) Processed file on the same FTP server different folder
2) errored file on different FTP folder.
How could we achieve this using the FILE Adapter?
As what i could see the file adapter does not gives you the option to select the FTP site for this...
Help is appreciated.
Regards

To archive source files where a permanent error occurred during processing, select Archive Faulty Source Files.
A permanent error occurs either during the conversion of the file content, or in a module in the module processor.
More information: Adding MessageTransformBean in the Module Processor
u25CB Specify Error Archive Directory.
u25CB To add a time stamp to the archived file, select Add Time Stamp.
ref: http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/655453b48a4ddfe10000000a1553f7/content.htm

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

Similar Messages

Maybe you are looking for