Junk character at end of file from sender adapter creating a blank record

[Former Member]

Hi All,

I am using the File to File scenario.

My input file has one junk character at end of file which is causing which is creating one blank record in the xml.

Can any one suggest please how to remove the extra blank record?

Input file is as follows (one junk character at end of file)

2 273770000110042008PMT EB331773 EB331773 1

2 273770000106662008PMT EB331775 EB331775 1

2 273770000107912008PMT EB331776 EB331776 1

The FCC parameters are as follows

Record.fieldNames ITEM,BUKRS,BELNR,GJAHR,SGTXT,ZUONR,BUZEI

Record.endSeparator 'nl'

Record.fieldFixedLengths 3,4,10,4,50,18,3

ignoreRecordsetName true

Record.lastFieldsOptional YES

If I do not use the lastFieldsOptional Parameter it is not being picked up by XI.

Early response is highly appreciated. points will be rewarded.

Many Thanks in Advance,

Jitender

[Former Member]

Hi Jitender.

Try to set one more parameter

Record.additionalLastFieds ignore

Let see if it works.

Thanks,

Akhil

[Former Member]

Tried now. No change in the xml. it is still creating one extra blank record.

[Former Member]

You can either you a OS command to run a shell script/batch or custom adapter module to remove it.

[Former Member]

... or maybe you can deal (ignore) with it in your mapping ? If I understand correctly, input file has this junk char so your output xml doc a blank record in it ?

Sorry if I misunderstood

Chris

[Former Member]

Is there any other way by adding some parameters in FCC?

[Former Member]

Hi Chris,

Here we are not using any mapping.

[Former Member]

Jitender,

I'm not used to FCC, but if no native settings exist, then you will have to either get rid of this char using a "before" script or either get rid of it using your own custom module ...

Chris

PS : btw, do you know why this char exists in your input file ? are you doing FTP or (network) file system access ?

Edited by: Christophe PFERTZEL on May 2, 2008 11:18 PM

[Former Member]

Hi Chris,

Thanks for your reply.

Actually we have the interface from EAZYBOOK to SAP.

The file is being generated with that character in EAZYBOOK and XI is pulling via FTP.

We have another interface with the same FTP service with the structure Header, Detail. In this case also they are sending the junk character but the blank record is not coming in XI.

FCC Parameters are as follows

Header.endSeparator 'nl'

Header.keyFieldValue 1

Header.fieldFixedLengths 1,4,2,8,8,8,10,20,25,5,4

Header.fieldNames Indicator,CompanyCode,DocumentType,DocumentDate,PostingDate,TranslationDate,UserName,Tcode,HeaderText,Currency,BizTransaction

Header.lastFieldsOptional YES

Detail.endSeparator 'nl'

Detail.keyFieldValue 2

Detail.fieldFixedLengths 1,3,2,1,18,1,13,50,10,13

Detail.fieldNames Indicator,Item,PostingKey,AccountType,AssignmentNumber,DCInd,Amount,ItemText,Account,LocalAmount

Detail.lastFieldsOptional YES

I have used the similar to parameters like above. I do not understand why the blank record is not coming here and why it is creating in another case. Only difference is there we have the flat structure.

Thanks and KindRegards,

Jitender

[former_member181985]

Hi,

It can be problem with file encoding.

Check the Communication channel for encoding used for the successful case.

now check encoding of unsuccessful case. If both are different modify it in the second case and execute your scenario.

Let me know once you have done.

Thanks,

Gujjeti

Edited by: Praveen Gujjeti on May 5, 2008 3:56 PM

[Former Member]

You're welcome ... One question : I do not understand what you mean by "the only diff is flat structure" ? I've set exactly the same settings for both adapters, but input file structure are not the same ?

Examples would be welcomed

Chris

[Former Member]

Hi Praveen,

I can't see any parameter with File enable etc. Can you please expain a bit more.

Hi Chris,

the difference b/w the two cases is - successful one, the structure is Header and Detail and failure one is Record (mentioned in my previous mail).

Thanks in Advance,

Jitender

[former_member181985]

Hi,

Please check these links

[http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm]

[http://help.sap.com/search/highlightContent.jsp]

In the first link find the page for encoding.

And check your two scenario cases(successful and Unsuccessful).

Thanks,

Gujjeti

[Former Member]

Hi ,

try these parameters in FCC.

In the content conversion of recr CC,pass below parameters.

<recdset>.fieldFixedLengths - 0

<recdset>.fixedLengthTooShortHandling - Cut

Regards,

Srini

[Former Member]

Thanks for the reply.

Praveen - File encoding is Binary in both the cases.

Srinivas - Tried the FCC parameters but no use.

Thanks in Advance,

Jitender