Sender File Adapter : File Content Conversion Issue

[Former Member]

Hi All,

I am getting a CSV file (UTF-8 encoding) with multiple record types ,which needs to be processed. I am doing content conversion . FCC is not working for the first row in the file. This is working fine from second row onwards..

Sample CSV file :

"RH",2011/06/27 22:55:38 +0100,"R","9SLQ9ZVU8ZNLL",006,

"FH",01

"SH",2011/06/26 00:00:00 +0100,2011/06/26 23:59:59 +0100,"9SLQ9ZVU8ZNLL",""

"CH","Transaction ID","Invoice ID","PayPal Reference ID","PayPal Reference

FCC is not working for RH record type(generated XML file do not have the first row tag). But if I place the same record in second row ..it is working fine. Can you please guide me to fix this ?  (If I leave the first row blank , this is working fine from second row onwards)

File Encoding that I am using is : UTF-8

Thanks ,

Prem

[DankoRupcic]

Hello,

I'm exepriencing the same thing after patching PI 7.11 system to SPS10 from SPS6.

Did you solve the problem?

Br,

Danko

[Former Member]

Hi All,

I am able to know the issue cause.

The file is UTF-8 , BOM encoded . This will add a special character to the first column of the first row. Thats why I am unable to do the content convesion correctly for the first row. (since it did not recognize the KeyField value) .

I went throught he following thread http://scn.sap.com/message/9788103 but unable to solve the issue . Can you please help me with this..

How to make the KeyField recognizable ?

I have used encoding type as both UTF-8 and UTF-16 in Communication Channel.

I have used the key field with BOM character as well (like "RH") but no result.

Regards,

Prem

[Former Member]

Hi , help me out if you have any clues please..

Thanks,

Prem

[zameerf]

Hi Prem,

I guess the input file you are using is manually generated, hence you get the BOM.

This would just consume your time and will not help.

I too have faced this scenario previously.

Always use the file generated by the source application and you should not face any issues.

Request the sender application team to provide a valid CSV file generated by the application.

This should solve your issue.

-Zameer

[Former Member]

Hi Zameer,

The file used is from source server directly.. Source is supplying the file in this format.

Source is using a mechanism to place the file on the source server ..as this is common for all of their partners , they don't want to change their file generation process. They want to continue CSV files with UTF-8 BOM .

Is there a way to process this kind of files in File FCC ?

Thanks

Prem.

[Former Member]

Hi , Below are my FCC Parameters

Document Offset : blank

Recordset Name : Header

Recordset structure: RHHeader,*,FHHeader,*,SHHeader,*, etc...

keyFiledName: TypeColumn

RHHeader.fieldNames : TypeColumn,ReportGenerationDate,ReportingWindow, etc..

RHHeader.keyFieldValue : "RH"

RHHeader.fieldSeparator : ,

RHHeader.enclosureSignEsc :""

RHHeader.enclosureSign : "

The incoming file is of UTF-8 encoding. Will this adding anything in the first line that may not recognize the KeyField? . When I open th file in notepad++ , I do not see any extra on the first line.

Thanks

Prem

[Former Member]

Hi Prem,

Please set addHeaderLine to 0 and keep document offset parameter as blank , I think it will solve your issue.

Best Regards,

Sagarika

[gagandeep_batra]

Hi Prem,

Can you check following parameters and document Specifications  :

Document Offset,

ignoreRecordsetName

Regards

Gagandeep

[iaki_vila]

Hi Prem,

Could you paste your FCC parameters?

Regards.

[Former Member]

Hi,

I hope u are not using Document offset parameter in Sender FCC??

Thanks

Amit Srivastava

[Former Member]

No Amit. I am not using.