Receiver file adapter archiving

Is there any mechanisam to archive the files at receiver file adapter?

Hi Praveen,
Use file adapter to put the file into the archive directory and use the above mentioned OS commands in "Execute OS commands after message processing" section of Receiver file adapter.. so your file will be placed in archive folder and then copied to actual folder.
This process is followed so as to make sure that you have the receiver file archived.. suppose you have a receiver process which will read the output of PI and delete the file .. then just to make sure we have a copy in the archive location we are first putting the file in archive directory and then copying it to the correct location
Regards
Suraj

Similar Messages

Archiving files in the Receiver File Adapter

Hi All,
I am trying to archive the file created in the Receiver File adapter. Reading from the link below,
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
I gave the command cp %F <target dir> in the Command Line of "Run Operating System Command After Message Processing". As well as I tried cmd.exe copy %f <target file>
But it does not work. Can anyone please help me out?
Thanks
Shivanjali

Hi Aamir,
For my case its not feasible to make a bat file...
I want to write a direct OS command in adapter only.
Do you know what is the basic difference for running OS command before processing and after processing.
In my opinion if i use a OS command after file processing then it ll take a file name with timestamp so there may be a problem...
thanks
Shivanjali

Archive processed files at receiver file adapter

Hi Experts,
I need to archive(copy) processed messages from the target folder to another folder.
I tried using the Run OS Command after processing and not sure with the exact command.
Can anyone please provide the exact command (syntax) for copying file from the target file folder to another folder.
Do we need any authorization from BASIS team to perform this command in run OS Commandline please.
Note: the original file should not be deleted.
Thanks in advance!
Regards,
Mahakrishnan T.

hi Mahakrishnan Thangam,
I used the OS command feature where FTP is not used and it worked in the way I already posted. When it comes to FTP in receiver file adapter you need a batch file and a script both on PI server. The script will function as follows
1. Login to FTP server.
2. change to target folder you specified in target directory in cc.
command: cd foldername
3.Read the file created by receiver file adapter in remote FTP location. File will be copied to local directory of PI server.
command: get filename
4. Now again change remote directory to archive directory.
5. Copy the file back to FTP server again from local directory to archive directory you want to copy to.
Now from batch file call this script.
Would suggest to read these links carefully
http://wiki.sdn.sap.com/wiki/display/XI/SAPXIFileAdapterOSCommandLine+Feature
http://www.cs.colostate.edu/helpdocs/ftp.html
Alter algorithms to meet your requirement.
Hope this solves your problem.
Regards
Anupam

How to create an Excel file from XML in the Receiver File Adapter Comm Ch

How do I create an Excel file from XML in the Receiver File Adapter Communication Channel? I have my mapping done and I am outputting the file as a comma delimited csv file. However, the target can only process an Excel file (.xls). How can I generate an Excel in XI?
I saw this blog, but I don't know how to create a XSLT transformation.
/people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible
Any help would be appreciated. Thanks.

Here are the steps I took to create an XSLT transformation in XI 3.0:
1. I created my source and target XSDs using XMLSpy.
2. I created the XSLT mapping from source to target in XMLSpy (referencing the souce XSD schema).
3. I created another XSLT mapping to format the target into Excel XML.
4. Import the source and target XSDs in the IR's External Definitions
5. Zip each XSLT mapping (.xls) and import it into the IR's Imported Archives
6. Reference the XSL mappings in the Interface Mapping

Receiver file adapter posts multiples for singel source files

Hi,
I am using wild character in my input source ftp adapter but my receiver file adapter is creating multiple duplicate files. I am not sure why this happens as QOS is set to "Exactly Once" with archive processing mode. I tried with delete mode and the same error occurs. We had no problems testing it in our Dev environment but in QA its acting so strangely...Any advise is appreciated..
-Teresa

Hi,
2. Homany files you posted at oubound directory?
1. You said duplicate files at receiver side, is the files having time stamp? if so those are not duplicate files.
Thanks,
Satish.

Append in Receiver File Adapter

Hi All,
i want to append data into the same file in the receiver file Adapter.
<b>for Example ..</b>I have given XYX a file name in the target directory ..for the first execration it puts the data in to the file..
for the Next execution its not appending data to that file..
<b>the Requirement is</b>
for the first time XYX has data 1234
for the next time XYZ need to add
1234 and below this the next data must come
2345 like this
how can i archive this in receiver file adapter,?
thanks
shakif

hello,
if you put that question into the correct forum (i.e. XI) you'll probably get an answer within minutes.
kind regards, anton

Change file extension in receiver file adapter

File to File Scenario
Posted: Sep 11, 2006 3:47 PM Reply E-mail this post
I am working on a File to File scenario.
Source System gives out a file: abc ( with no extension)
We need to archive it as: abc.done
And we need to send it to a FTP server ( receiver File adapter) as abc.txt.
How can I append a file extension when I archive and
how can I change the file extension in the receiver File adapter?
FYI, we are using XI as FTP server so I have created dummy message interface with no mapping.

Hi,
If I understood correctly once XI picks up the file it should be archieved as filename.doc and then it should be FTP'ed to a different location with a change in extension filename.txt.
1. To Archive in the sender communication channel you can use OS Commands after prosessing (>=SP14) to rename the file and archive it. Suggested write a batch file which will rename the file and call the batch file from the OS Command of the sender file adapter. You can either use Archive functionaliy of the Sender adapter or you can write one more command in batch file to move the file to different folder. Make sure you are using fullpath while writing batch file.
2. As said use dynamic configuration in a dummy mapping and then get the source file name and change the extension.
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
Thanks,
Prakash

Keep attachments in receiver file adapter

Hello,
We receive via Abap proxy a txt file by attachment, and we need to archive that file in other machine using a receiver file adapter but the receiver file adapter doesn´t have any keep attachment option. How can we achieve that?
Thanks!
Luis

Yes, I thoug that was possible but in fact the attachment is intended to be something that should be not accessed from the integration server and so not mapped.
http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/0b733cb7d61952e10000000a11405a/frameset.htm
I think that the adapter module will be the better choice.
Regards,
Sandro

Email attachment name in sender mail adapter to the receiver file adapter

HI ,
Ths is regarding email to file scenario. I am trying to create file (in rceiver file adapter) with the same name as the email attachment that i read from mail sender adapter. I want ro use adapter module for this. I could find from blogs that there is module - GetAttachmentName - available that i can use for this in sender mail adapter.
Can you please let me know what whetehr i neeed to mention any module key and parameters for this.
I assume , i need to do following steps :Please confirm.
1. i can use this module - after payload swap module and before standard mail adapter module in sender mail adapter
2. select ASMA option in advanced tab in sender mail adapter
3. In receiver file adapter select ASMA option in advanced tab in sender mail adapter
4. Also select file name option in ASMA in sender mail adapter
Thanks,
Vamsi

Hi Vamsi,
your scenario is also described here: Re: sender mail adapter - attachment name
If you use the Module getAttachmentName, which is described here,
http://wiki.sdn.sap.com/wiki/display/XI/AdapterModulePI7.0GetAttachmentName
your scenario should work as you described it.
You just need to make sure that the Attachment Name that you read in the first place, is mapped to the Filename Attribute of the
Fileadapter (http://sap.com/xi/XI/System/File/FileName).
regards,
Daniel

Receiver file adapter settings

Hi,
I have a scenario in which I need to generate a file in tab delimited format. But in the receiver file adapter configuration we have only text/binary file creation mode. By setting the File Type in TEXT mode will I be able to do a tab de-limited file?? Or is there any other configuration settings need to be done?
-Ken

Hi Amanda,
Thank you so much for the great info. I think I can find some stuff but still it would be helpful if you could forward the doc to [email protected] Also, yeah it looks like the receiving file format would be complex with header and footer. In the content conversion can we specify header and footer?? or is there any other way to define...FYI my source file also contains header and footer..I am just a little confused on how to set up the message types for mapping...
Many thanks..
-ken

Problem with file content conversion in receiver file adapter

Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
Chandra

Posted in Incorrect forum.
Posted again in Process Integration forum

Problem with fixedlenthgs in receiver file adapter

HI,
I am doing XML to flat file scenario and using mutli mapping concept without BPM.
in the receiver file adapter I am using FCC with fixedlengths,then it generated just 3 output files out of nearly 100 source files.the errored one are succcessful in the SXMB_MONI and failing in RWB-->Message moni with waiting status and MDT says that XI_J2EE_ADAPTER_FILE ,Error Code PROCESSING_ERROR .
i tried in SDN and then found something like enable the disablesecurity check box in variable substitution parameters ,then I got 4 files out.
these are my FCC params for all structures:
struc1.fieldFixedLengths
struc1.fixedLengthTooShortHandling
struc1.endSeparator
and I tried with fieldSeparator then it gives successfully all output files.
so,where is the problem?I didnt understand?
any suggestion.
thank you,
regards,
Babu Sri

Bhavesh,
I felt the same way,but assumed that ,in that way fixedlenghths wont work.
in my target structure most of the fields have 0-1 occurences ,and even in the source structure too.so,I think it might be the reason.Then I have to make all my about 60fields 1-1 madatory and using mapWithDefaultValue function, as my sources are optional.
you think it will work just using the "mapWithDefaultValue" function without changing my occurences to 1-1 in the target structure(mandatory)?infact I can try but ,cos of pain for changing like 60 fields....:) and even dont know which fields are causing the problem,so that we can apply "mapWithDefaultValue" function only on those fields.
thank you,
Babu Sri

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

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>

Sender_interface_name in Variable Substitution in Receiver File Adapter CC

Hi,
as per this page : http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
it says:
Variable Substitution (Target Directory/File Name Scheme)
If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
●      Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
The variables can refer to attributes of the message header or elements of the message payload.
○       If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace, message_id, message_id_hex
Can we not access sender_interface_name and sender_interface_namespace are not mentioned in above list of variables.
Is it not possible to access sender_interface_name or sender_interface_namespace as variable substitute parameters from within Receiver File Adapter Communication channel.
thanks.

>Shabarish Vijayakumar wrote:
>>the sender interface details will always remain a constant
>>so you can hard code the value, isnt it?
Yes, i can hardcode, thats not a bad idea, i need to create then 3 different Reciever File Communication Channel objects, as I am dealing with 3 scenarios for which sender system and sender interface is different.
>Shabarish Vijayakumar wrote:
>>if you look at the mapping runtime constants, those are also for the receiver since the sender interface will always remain constant for any particular CC.
>>http://help.sap.com/saphelp_nw04/helpdata/en/b3/9a2aeb24dc4ab6b1855c99157529e4/content.htm
yes in this link you provided i can see..
INTERFACE     Interface
INTERFACE_NAMESPACE     InterfaceNamespace
SENDER_SERVICE     SenderService
RECEIVER_SERVICE ReceiverService
RECEIVER_NAME     ReceiverName
RECEIVER_NAMESPACE     ReceiverNamespace
it seems both INTERFACE (,INTERFACE_NAMESPACE) and RECEIVER_NAME(,RECEIVER_NAMESPACE) are present, may be one is for sender, and another is for receiver.. may be if i use dynamic configuration, possibly my issue would be addressed.. correct me if i am wrong.
thanks.

Receiver file adapter archiving

Similar Messages

Maybe you are looking for