cancel
Showing results for 
Search instead for 
Did you mean: 

Special characters in File

Former Member
0 Kudos

Hi All

when we push an IDOc from ECC using file port we generate a file(Flat file) with .dat extension in SAP PI share folder. when we open the file in wordpad the '-' is converting into some junk character like â€" & space is replacing with some other character like  . In XI we have interface which will pick the file & places it in target for thirdparty to process... Due to this special characters thirdparty is not able to process the files.

Any one came across this kind of issues before, please share your inputs to fix ths issue.?

Regards,

Vasanth.

Accepted Solutions (0)

Answers (4)

Answers (4)

prasanthi_chavala
Active Contributor
0 Kudos

Hi Vasanth,

Are you just by passing the file from ECC system to target system without doing any transformations? Just wanted to understand if the file generated at ECC end has junk characters or after processing file to target system has junk characters?

If it is at inbound side of PI (PI to target system) then check the file encoding type in receiver channel. If it is at outbound side then check if ECC is generating the file with proper encoding. (it should ideally UTF-8 encoding).

Thanks,

Prasanthi.

Former Member
0 Kudos

Prasanthi,

We don't use any transformation in XI but still in receiver communication channel using the encoding type as UTF-8.

When ECC push the IDOC & it displays the data correctly but when it writes the file in the PI Server it has junk characters.

When we try to Open the Source file which ECC generates in Hex Edidtor we could see special chartacters  in it...

Thanks,

Vasanth.

prasanthi_chavala
Active Contributor
0 Kudos

Vasanth,

Try option with file type as text and encoding type in sender communication channel and see if it works.

Thanks,

Prasanthi

Former Member
0 Kudos

Prasanthi,

tried the option but still the issue persist...

Thanks,

vasanth.

prasanthi_chavala
Active Contributor
0 Kudos

Vasanth,

Just try to view the file at unix level in vi mode once the file is dropped by ECC system. Also verify if they have enabled unicode format in system setting in WE21.

Thanks,

Prasanthi

Former Member
0 Kudos

Prasanthi,

OS is windows 2003 not unix...

Unicode option is checked...still the problem persist

Thanks,

vasanth.

Former Member
0 Kudos

Hi Vasanth,

Is the issue resolved? I got similiar kind of issue. If it is resolved, can you please tell me?

Former Member
0 Kudos

Hi Srinivas

Now it is almost three years but still I could remember that is master data issue, when we requested the business to update the description...

Issue got resolved...

Thanks,

Vasanth.

prateek
Active Contributor
0 Kudos

You must not try wordpad to check the file. Try editors like Notepad++.

Are you transferring the file as text or binary? If you are using text, you may provide the respective encoding for the file.

Regards,

Prateek Raj Srivastava

Former Member
0 Kudos

Hi Prateek,

In Notepad it displays correct output but Thirdparty has unique encoding format(They are expecting the file with UTF-8 format,  we are tranferring the file as text with encoding UTF-8...

When ECC generates the file we could see the special characters when it is writing the file...

When we try to open the file in Hex Editor we could see special characters in the source file?

Thanks,

Vasanth.

Message was edited by: Vasanth Kumar S

deepak_shah
Contributor
0 Kudos

Hi,

use appropriate encoding in your receiver file channel.

For available encoding types refer link below:

help.sap.com/saphelp_nwpi71/helpdata/en/44/6830e67f2a6d12e10000000a1553f6/content.htm

-Deepak

Former Member
0 Kudos

HI Deepak,

Both Sender & reciever has encoding format as UTF-8...still the issue persist..

Thanks,

Vasanth.

Former Member
0 Kudos

Hi Vasanth

please select appropriate encoding type in receiver file channel.

Supported encoding types can be found at http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm

Regards

Raj

Former Member
0 Kudos

HI Raj,

In XI the scenario is kind of bi-pass so XI just picks it up & places it in Target folder...

Both Sender & reciever has encoding format as UTF-8...still the issue persist.

Thanks,

vasanth.

Former Member
0 Kudos

Select the File Type of the document as Text

Former Member
0 Kudos

Hi Raj,

Yes i have set the file type as text only but still the issue persist

vasanth