Receiver File Adapter Issue

Hi,
I have a scenario like R3(IDOC)->XI(Mapping)->FTP(Content Conversion)
I am trying to FTP a file across to a vendor's FTP server using the reciver file . adapter. The target filename is of the form %ABC%IJK%%b.However on posting the file i get a message like.
An error occurred while connecting to the FTP server '<hostname>:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 200 Command Okay. ID: <userid>, Current TR - Recv: <userid>, APRF: *BINARY, Dir: S. Get option: single. '. For details, contact your FTP server vendor.
It seems although the connection is established, the ftp put does not work
Can anyone help on what is the cause of the error and possible solutions.
Regards,
Alex.

There can be following things:
- Target Dir is not present or you dont have an authorization to create it.
- Check the Access to put the file in that directory.
Check the same for other interface also. If other interfaces are running fine then try to put the file in that DIRECTORY for test purpose.
Thanks
Farooq.

Similar Messages

Receiving file adapter content conversion issue

Guys,
Could someone please help me with a Receiving file adapter issue?
My output structure is something like this:
Vendor_file_MT (occurence 1)
--Recordset (occurence 0..unbounded)
Vendor (occurence 1)
Field1
Field2
Field3
Field73
Field74
My content conversion is very simple:
Recordset Structure: Vendor
Parameters:
Vendor.fieldFixedLengths   30,30,30, (...) ,1,27
Vendor.fixedLengthTooShortHandling   Cut
Vendor.endSeparator   'nl'
If I don't do the content conversion, it works fine, I get all the fields in the XML format.
When I do the content conversion however, I get multiple lines but only the very first field of each line.
What could be the problem? What am I missing here? Any idea?
Your help would be much appreciated.
Thanks,
Viktor

Varga:
Its little strange that its not working even after adding that. Did you check the receiver channel in your RWB for any logs. Add the statement in my previous post and Also try to clear the Cache and activate the channel again..See if it works
Glad it worked
Edited by: Guru on Apr 21, 2008 3:15 PM

Encoding issue in receiver file adapter

Hi experts,
I am having a file to file scenario using integrated configuration where i am using file encoding 'US-ASCII' for converting the target file to ASCII and its not working.
Is there any other settings need to be done in the receiver file adapter to convert to 'ASCII' encoding format?
Do we have any other method to convert to 'ASCII' format for the receiver file?
.txt file is used for this interface.
Thanks!

Hi Mahakrishnan,
What is the format of file mentioned in sender file adapter? If SAP-PI is receiving File format in US-ASCII. Then mention US-ASCII in sender communication channel in file encoding field,file type will be text. In case the file format received by SAP-PI is normal text file then by default sender adapter will convert it to UTF-8. Maintain the file type=text and encoding=US-ASCII for receiver file adapter also.
ASCII is an alias for US-ASCII file encoding, hence both mean the same encoding. Thus this format should work. If its still not working please refer to SAP note 821267.
Regards
Anupam
Edited by: anupamsap on Mar 9, 2012 5:47 AM

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 - Adapter Engine

I am able to read files using Sender File Adapter. But when I try to write a file using Receiver File Adapter I get the following erro:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="<http://sap.com/xi/XI/Message/30>" xmlns:SOAP="
<http://schemas.xmlsoap.org/soap/envelope/>" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.exi.usxid</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: No service user name found for Integration
Server is.00.usxid</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password)
for the Adapter Engine af.exi.uswalexi</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried executing the function module SAI_AE_DETAILS_GET but I am not getting the error URL Not found. This was working in the past. We upgraded to SP15 this showed up again.
Any help appreciated.

I'm working on integration of SAP with 3rd party application. While sending data from SAP to XI, i'm getting the following error which i've found in sxmb_moni (XML Message->Call Adapter).
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- -
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.xp1.sapxi</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: No service user name found for Integration Server is.00.sapxi</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.xp1.sapxi</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me to solve this issue. If possible mail me the solution to my personal email-id [email protected]
Note:
1. We are using CIM 1.3
2. In XI Server Message Monitoring, i'm getting the System Error message in Integration Engine.
3. In Payloads, i'm getting the required information in XML format as desired.
Thanks in advance.
Regards,
Navaneeth.S

Receiver File Adapter - FTPEx: 550 Access denied

Hi Experts,
In my receiver file adapter scenario I'm getting 550 Access denied in RWB.
I am a little confused here because I could access the FTP client from my desktop using the same User and Password informed in the Receiver CC. I also could drag and drop a file there.
Here you have Detail Display in RWB, it seems that at least the user is working fine for PI also:
Success: Connecting to FTP server "<FTP IP>"
Success: Write to FTP server "192.168.10.85", directory "\Transportadoras\10326750000101\", file "Nfe_teste.xml"
Success: Transfer: "TXT" mode, size 8881 bytes, character encoding UTF-8
Error: Attempt to process file failed with An error occurred while connecting to the FTP server '192.168.10.85:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied.'. For details, contact your FTP server vendor.
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: An error occurred while connecting to the FTP server '192.168.10.85:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied.'. For details, contact your FTP server vendor.
Regards,
Daniela
Edited by: Daniela Machado on Aug 11, 2010 10:18 PM

Hi Daneial,
This is an issue due to any firewall or proxy between your Xi system and the FTP.In this case the direct logon
works with same user but when XI tries to create file at runtime you get this error due to network issues.
To resolve this contact your Basis/Network guys and
1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
Regards,
$rinivas

Receiver File Adapter error

Hi all,
I am trying to convert the XML to Plain file in receiver file adapter. I am using module - StrictXml2PlainBean
My target structure is -
<MT_Name>
    <records>
        <Header>
        </Header>
        <Item>
        </Item>
    </records>
</MT_Name>
<Header> and <Item> are at same level.
When I use --
1. Header.fieldSeparator = ,
2. Item.fieldSeparator = ,
3. recordTypes = Header,Item
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: records at XML element MT_Name,records
When I use --
1. records.fieldSeparator = ,
2. singleRecordType = records
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure MT_Name is too deep (reference: 3 levels, found: 4 levels) at XML element MT_Name,records,Header,Item
To add more details to the scenario, multiple records can be generated but one record will have only one Header, with multiple Items.
Any help in this regard will be highly appreciated.
Thanks,
Abhi

Hi Abhi,
Here you go....
For your target structure as:
<MT_Name>
<records>
<Header>
</Header>
<Item>
</Item>
</records>
</MT_Name>
Where I have assumed that <Header> and <Item> are at same level.
DO NOT use any Module just simply configure the receiver channel as below:
In the file Receiver Channel
Recordset Structure = Header,Item
Name                                                                    Value
Header.fieldSeparator                                             ,
Item.fieldSeparator                                                  ,
I have tried this and it works.
Let me know if you are facing any issues.
Cheers
Dhwani

Receiver file adapter creates an innecesarry extra line

Hi,
I have an issue with an extra line that add the receiver file adapter with the content conversion.
The file XML that the file adapter has to convert, is the next;
<root>
<cofig>
<FileName>NameOfTheFile.txt</FileName>
</cofig>
<lines>
<line>
<data>BBBBBBBBBBBBBBBBBBBBBB</data>
<data>Aaaaaaaaaaaaaaaaaaaaaa</data>
</lines>
</root>
Because FileName is not necessary, I remove it with:
cofig.fieldFixedLengths 0
cofig.fixedLengthTooShortHandling CUT
but it leaves an empty line that i don't want. that is, the text in the file start in the second line.
Any help?
Thank you in advance.

Can you do a small change in your mesg. structure ?
change it to....
<root>
<lines>
<line>
<data>BBBBBBBBBBBBBBBBBBBBBB</data>
<data>Aaaaaaaaaaaaaaaaaaaaaa</data>
</lines>
<i><b><cofig>
<FileName>NameOfTheFile.txt</FileName>
</cofig></b></i>
</root>
and then use
cofig.fieldFixedLengths 0
cofig.fixedLengthTooShortHandling CUT
followed by
endSeparator 0
Ref: Suppressing Field In Receiver File Adapter for more details.

REG: File content conversion in Receiver file adapter

HI Gurus,
I have the scenario like proxy to file with content conversion
my message type for the source like this
MT_SOURCE
-----||
       |---ROW
------------||
                |---LINE
target strucuture also same
MT_TARGET
-----||
       |---ROW
------------||
                |---LINE
i am using the following FCC parameters in receiver file adapter
LINE.fieldSeparator = '                       '
LINE.fixedLineWidth = 90
LINE.lineSeparator = 'nl'
LINE.fieldFixedLengths = 200
LINE.endSeparator        = 'nl'
the output file show the data differently in note pad when compare to word
word output
dgepvs                       023456987
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
notepad out put
dgepvs           023456987   kgdd0016155710                SS Smw Ne 01       kgdd0016155710                SS Smw Ne 01          kgdd0016155710                SS Smw Ne 01            kgdd0016155710                SS Smw Ne 01    kgdd0016155710                SS Smw Ne 01
word output is the correct output wat i am expect but same out put i want in note pad can any help me out for this how can i resolve this
Thanks in advance

There is nothing wrong in your content conversion parameters. This is pure editors interpretation for the next line character.
I would do in java program to fix this issue using '\r\n'   You might want to try and see how that helps for notepad editor.

Multiple Header line in Receiver File adapter

Hi,
I have an issue in Receiver File adapter with multiple header lines. I am able to get only 1 header lines in the receiver file but not multiple header lines with 'nl' since it is static in file mode
[CommunityTag:Header]
empNo,EmpName,Age
[CommunityTag]
I tried with the below in content conversion one as below with no luck
Root.addHeaderLine=1
Root.headerLine=[CommunityTag:Header] 'nl' empNo,EmpName,Age 'nl' [CommunityTag]
Root.fiedSeparator=,
Root.endSeparator='nl'
I am getting the Header line as same row as static text.
Can you advise this.

Hi Gabriel, I suggest to produce the header lines from additional nodes in the message payload. That means you need to modify the data type of the target message in order to generate an extra structure in the payload. Use constants in message mapping to generate the header column names, e.g.
<Header>
<H1>CommunityTag:Header</H1>
<H2>empNo,EmpName,Age</H2>
<H3>CommunityTag</H3>
</Header>
In content conversion you have to convert the Header row with
Header.endSeparator='nl'
You won't need parameter addHeaderLine anymore then.
Regards, Martin

XI Receiver file adapter : Dyanmic File PATH

Hi,
Appreciate if someone could help me on the issue below:
I have a receiver File adapter with a dynamic target directory as per below:
Target directory: /test/YYYY/MM/DD
the value for YYYY (Year) , MM (Month) and DD (Date) will be the date when the file being transfered from the sender.
Appreciate if someone could help me to achieve this. I know we can use the variable substitution however it doesn't allow us to set a systems field such as sy-datum.
Cheers,
ZAB

Hi,
Populate this value in your payload , and then use Dynamic File Name concept of File Adapter.
The dynamic filename generation concept is as follows.
In your filename field. just give a variable with % symbols. (eg: %file% ).
Now, under the option Variable Name Substitution, you can give how the value has to be created.
It can be your interface name, sender service name, etc or it can be some value dynamically from your payload.
For the former, your give
message:interface_name ,etc
and for the payload part you give,
Payload: "your element root which u wanna acecss"
Just check this link out,
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
And read the contents under variable substitution and it will help you understand the concepts better.
If you have any clarifications, do get back,
Regards,
bhavesh

PI 7.1 Receiver file adapter - Spaces are truncated at end of each line

In Receiver file adapter, I specified file content conversion parameters. My file structure is as below:
Header
Field1 10
Field2 20
Field3 8
Filler   20
Detail
Field1 10
Field2 8
Filler    8
In both Header and Details structures I have to fill 20 and 8 spaces at end of each line. In XML (Payload) I can view the spaces. But when the text file is created all the spaces are truncated.
Could you please solve this issue.
Regards

Recordset Structure: ns1:MT_SAP,REC,Header,Detail
ns1:MT_SAP.fieldSeparator          '0'
ns1:MT_SAP_PNC_PPAY.fieldContentFormatting     nothing
REC.fieldContentFormatting          nothing
REC.fieldSeparator               '0'
REC.processConfiguration               FromConfiguration
Header.fieldFixedLengths               10,20,8,20
Header.endSeparator               'nl'
Header.fixedLengthTooShortHandling          Ignore
Header.fieldNames               Field1,Field2,Field3,Filler
Header.fieldContentFormatting          nothing
Detail.fieldFixedLengths               10,8,8
Detail.endSeparator               'nl'
Detail.fieldNames               Field1,Field2,Filler
Detail.fieldContentFormatting          nothing
Detail.fixedLengthTooShortHandling          Ignore

Creating .RTF output files - PI7.0 Receiver file adapter

Hi Experts,
I am currently facing an issue with the Receiver File adapter where in the output files are required to be of the format of .RTF (Rich Text Format).
The scenarios is an outbound proxy from SAP ABAP - > PI 7.0 -> .RTF File
All the data required to be present in the file will be coming in the source structure
Can the File Receiver Adapter handle this ?
Is there a way to generate Files with extension .rtf ??
It is a requriement since the output files will be used as Reports , and so the desired format.
I am unsure if I will have to use XSLT mapping , in this because i am new to that , Kindly let me know how to go about it ,. any links or pointers on how to achieve the same will be welcome.
thanks
Dev
Edited by: sd on Feb 17, 2010 8:23 AM

Thanks for your reponse Praveen
Can you please let me know how can i put the extension as .rtf for the output files i am generating ??
as far as the formatting is concerned ... it is like ... the header needs to be of a particular Font , a particular font size , bold etc and so is the case for line items
I am unsure if it is possible using an Adapter module as well
thanks
Dev

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

Receiver File Adapter Issue

Similar Messages

Maybe you are looking for