Getting corrupted file generated at the target in pdf to pdf pass through scenario in PI 7.1

[somil_gulati]

Hi,

I am doing a pdf to pdf pass through scenario in SAP PI 7.1 . I have not created any ESR object as it is a pass through scenario (no mapping is involved), only configuration objects are created by me . I have read many forums in scn about this scenario (including the very much popular blog by william.li ).

The problem that I am facing is that my pdf file is picked from the source by SAP PI and it is also sent to the target system but at the target when I open the file it is corrupted and cannot be opened.

Same problem is in .zip to .zip pass through scenario .

[somil_gulati · Accepted solution]

The transport Protocol in the sender file adapter is NFS. I am uploading the file in PI  AL11 directory using the Tcode SXDA_TOOLS . Today I noticed that the pdf file that I upload to AL11 is getting corrupted , as when I again downloaded  the same file using Tcode SXDA_TOOLS I am getting the corupted file . So is there any way that I can upload the pdf to AL11 of PI without getting it corrupted .

[markangelo_dihiansan · Accepted solution]

Hello,

Can you do the following and get back to us?

1. Turn off the file sender CC in RWB CC Monitoring

2. Upload the file using sxda_tools, alternatively, you can also use the function module ARCHIVFILE_CLIENT_TO_SERVER

3. Once the upload is complete, turn on the file sender CC and see what happens

Hope this helps,

Mark

[somil_gulati · Accepted solution]

thanks for your reply.

I uploaded my pdf using the function module ARCHIVFILE_CLIENT_TO_SERVER .My files was properly uploaded without getting corrupted and my interface also worked fine.

[former_member184681]

Hi,

One more thing to check is if the file is completely written by the sender, before PI starts processing it. As a simple check, you could compare the sizes of the original and target file - are they identical? In case of problems, you can use the "Msecs to Wait Before Modification Check" option of the sender file adapter to make sure that PI only starts processing the file, when it is completely written. See more details here: http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm

Hope this helps,

Greg

[marcossola_bayarri]

I have the same scenario and works without problems.

if you are using the file adapter, are you reading and writing the file with "File type=Binary"?

[somil_gulati]

Yes I have set the file type as binary.

I have now found the problem with my scenario and it is as ---

The transport Protocol in the sender file adapter is NFS. I am uploading the file in PI  AL11 directory using the Tcode SXDA_TOOLS . Today I noticed that the pdf file that I upload to AL11 is getting corrupted , as when I again downloaded  the same file using Tcode SXDA_TOOLS I am getting the corupted file . So is there any way that I can upload the pdf to AL11 of PI without getting it corrupted .

Do you have any idea how can I upload pdf to PI AL11 directory without getting it corrupted ?

[baskar_gopalakrishnan2]

You can set the content type to application/pdf and see whether that helps.  There is a similar thread that talks about the issue. But scenario here is file to jms.

http://scn.sap.com/thread/1949938