Sender File adapter error.

[Former Member]

Hi all,

I am getting the following error in Sender File adapter:

Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found

My configuration for FileContent Conversion is as below:

Document Name: MT_Invoice

Document Namespace:http://sols.com/mytestmessage

Recordset Name: Rootnode

Recordset Structure: Inv_HDR,1,Inv_dtl,*,

Recordset Sequence: Ascending

Rootnode.ignoreRecordsetName: 'true'

Inv_HDR.fieldNames:BUKRS,BLART,BLDAT,BUDAT,.................

Inv_HDR.fieldSeparator:,

Inv_HDR.endSeparator:#

Inv_HDR.processFieldNames:fromConfiguration

Inv_dtl.fieldNames:BSCHL,MWSKZ,WRBTR,ZUONR,SGTXT,KOSTL,..........

Inv_dtl.fieldSeparator:,

Inv_dtl.endSeparator:#

Inv_dtl.processFieldNames:fromConfiguration

Can anyone provide me the solution for this error in SENDER FILE ADAPTER?

Thank you,

Ann.

[Former Member · Accepted solution]

Hi Ann,

Please see this..

cheers,

Prashanth

P.S Please mark helpful answers

[Former Member · Accepted solution]

Hi Prashanth,

My input file is a flat file with variable length ans looks like this:

8932,GS,20070223,20070223,713196,INVOICENo567123,USD

27,0,287786.88,123456,800-000132-21000-000-123,13221010000

72,0,30682.80,123456,800-000132-21000-000-123,13221010000

56,0,35714.40,123456,800-000132-21000-000-123,13221010000

89,0,31824.00,123456,800-000132-21000-000-123,13221010000

34,0,33818.40,123456,800-000132-21000-000-123,13221010000

My Invoice_mt is like this:

Invoice_dt

Inv_HDR

bukrs,blart,bldat,budat,xblnr,bktxt,waers

Inv_dtl

bschl,mwskz,wrbtr,zuonr,stxt,kostl

In the File Content Conversion

Key Field name: bukrs or zuonr

ignoreRecordsetName:true.

Inv_HDR.fieldNames: bukrs,blart,bldat,budat,xblnr,bktxt,waers

Inv_HDR.fieldSeparator:,

Inv_HDR.endSeparator:'nl'

Inv_HDR.keyFieldValue:8932

Inv_dtl.fieldNames: bschl,mwskz,wrbtr,zuonr,stxt,kostl

Inv_dtl.fieldSeparator:,

Inv_dtl.endSeparator:'nl'

Inv_dtl.keyFieldValue:123456

I am getting the same error:<u><b>Inv_HDR.keyFieldValue:no Value found.</b></u>

Will anyone let me know what I am doing wrong....

Thank you,

Ann.

[Former Member · Accepted solution]

Hi Prashanth,

Thank you for your input and it solved the problem.

Ann.

[Former Member]

Ann,

Rootnode.ignoreRecordsetName: 'true'

please remove "Rootnode"

it should be ignoreRecordsetName: 'true'.

Regards

Sreeram.G.Reddy

[Former Member]

Hi Ann,

in Sender adapter:

Key field Name: Key

Key field Type: string(case sensitive)

Then in pair value:

Inv_HDR.keyFieldValue :'<>'

Inv_dtl.keyFieldValue :'()'

where <> you replace by your character which starts the header and () you replace by your character which starts the detail

Remove this line : Rootnode.ignoreRecordsetName: 'true' - this line is not needed.

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

Message was edited by:

RAJEEV GUPTA

[Former Member]

hi Rajeev,

Inv_HDR and Inv_dtl are header and detail nodes for the Source message type.

My Inv_dtl is 1-----unbounded.

I didn't get why it should be replaced by '<>' and '()' these characters.

Thank you,

Ann

[Former Member]

Hi Ann,

see the key field means the data which recognises the start of your header or detail - i.e. the key value of header or detail.

by <> and () i mean suppose your header data always start with HEADER written in your source file, then write the below in pair value:

Inv_HDR.keyFieldValue :'HEADER'

Similarly suppose your Item data always starts with IT written in source file, then write:

Inv_dtl.keyFieldValue :'IT'

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

please replace those by Key field values you use to identify the Header and Line item .

[Former Member]

hi Rajeev,

Thank you for your explanation.

Can we avoid the KeyField name and keyField Value in the Content Conversion of Sender File adapter.

Thank you,

Ann.

[prabhu_s2]

ann

just try out these links:

[url=https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1092] [original link is broken] [original link is broken] [original link is broken] [original link is broken];https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1092[ [original link is broken] [original link is broken] [original link is broken] [original link is broken];/url]