cancel
Showing results for 
Search instead for 
Did you mean: 

SFTP to SFTP interface

0 Kudos

Hi Folks,

I am working on SFTP(File) to SFTP(File) interface in sandbox system. File(Txt) is sending data in ~ format to target system .we are using a new approach ~ here.

i tested with following files in sandbox

1.xml to txt----successfull

2.txt to xml----successfull

3.txt to txt---unsucessfull

PI able to pick file and placing the file in target server but data is not populating .In target file the data is displaying only ~~~~~~ like this.

I checked in moni i can see the payload overthere.but in target system data is not coming.

Sender FCC

Receiver FCC

In output directory i am only getting this

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Muni,

Everyone here is correct in saying you could do this without any mapping steps.

However, you should also be able to make this work with mapping. You are obviously very close to making this work because in your output file you are getting 4 delimiters but just the content is missing.

If you look at your source payload in moni, right click, view source, copy this payload and paste it into your design mapping, test tab (source view).

Then switch back to tree view which will parse your test input and verify your input message structure versus what your map expects.

Now is your root node red or green? Sometimes you could run into a root level message name difference that keeps your payload from being recognized in the map.

If you run this test and get output, you know the problem is something trivial in the output FCC parameters. However, if you run this test and get empty results, you may have a message type mismatch on your input FCC parameters and your sending message type.

Regards,

Aaron

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Are you not seeing error in any of the pipeline steps? Also I want you to see in the receiver communication channel to find more details on this error.  The error could be due to mapping area or invalid conversion parameters specified on the receiver channel.  Provide more details on the target structure side.

0 Kudos

Hi Baskar,

Thanks for the reply...

I am not getting any error in pipeline steps...the above screen shots mentioned both sender & receiver fcc.

Mapping is fine..Source and Target structure is same.

SOBID,FEEDERCODE,TRANSACTIONCODE,CONVERSIONTYPE,CURRENCYCODE

In receiver Fcc i mentioned like this

Recordset structure  : Row

Row.fieldSeparator:~

Row.fieldNames:SOBID,FEEDERCODE,TRANSACTIONCODE,CONVERSIONTYPE,CURRENCYCODE

Row.endSeparator:'nl'

any other things need to add in receiver fcc.Correct me if i am wrong

Former Member
0 Kudos

Hello!

Is this structure hierarchical or plain row? Anyway, try checking the wiki page below for some reference on the receiver FCC configuration:

http://wiki.sdn.sap.com/wiki/display/XI/FCC+For+Hierarchical+Structure+in+Receiver+Channel

Hope it helps.

BR,

Lucas Santos

0 Kudos

My Source and Target structure is same.

Hi

baskar_gopalakrishnan2
Active Contributor
0 Kudos

If your source and target structure is same and no mapping involved then why do you use file content conversion. Is that right? You dont need ESR objects at all. Just configure ID objects and do simple pass through scenario itself.

refer:  http://scn.sap.com/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-wit...

0 Kudos

Hi Baskar,

Thanks for the reply..

I agree with your answer but pi undesrtands only xml files in that case no FCC...

But here .txt(~) to .txt(~format) so for this we need FCC..correct me if i am wrong..

In this case in fcc what are the things i need to do..

Recordset structure  : Row

Row.fieldSeparator:~

Row.fieldNames:SOBID,FEEDERCODE,TRANSACTIONCODE,CONVERSIONTYPE,CURRENCYCODE

Row.endSeparator:'nl'

Former Member
0 Kudos

Hello Muni!

If you are not performing any changes on the data itself (the same input TXT file will be sent as output), then you don't need to convert it to XML.

BR,

Lucas

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>I agree with your answer but pi undesrtands only xml files in that case no FCC...

That is not true. Here you dont need any conversion. You DONT need ESR objects. Just do ID objects and follow the blog I have shown in the above reply. PI can also be used to handle other file types like binary, zip, gif etc.

0 Kudos

Hi Baskar,

I removed FCC  both sender & Reciver CC,now file is not getting placed getting below error.

<SAP:Category>Application</SAP:Category> 

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>com/sap/xi/tf/_mm_file2file_</SAP:P1>

<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>

<SAP:P3>Content is not allowed in prolog.</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_mm_file2file_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.</SAP:Stack>

<SAP:Retry>M</SAP:Retry>
gagandeep_batra
Active Contributor
0 Kudos

Hi Muni ,

The following link might help you.

http://www.saptechnical.com/Tutorials/XI/File2File/Demo1.htm

Regards

Gagan

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Use File adapter for sender and receiver SFTP purpose. Don' use ESR/IR objects. I hope you have done per william's blog.  There is no mapping involved. This is basically pass through scenario. It should work. Don't do mapping.

zameerf
Contributor
0 Kudos

Just remove your mapping mm_file2file_ in Interface Determination.

Your interface determination should have only outbound and inbound interfaces, interface mapping should be kept blank. Test end to end, it should work. Then remove all your ESR objects.