on 08-05-2009 12:52 PM
Hi,
I am using the following source structure:
<Goods> 0..unbounded(Data Type)
<HeaderData>(1..1)
<1>
<2>
<3>
<ItemData>(1..unbounded)
<10>
<11>
<12>
<13>
.
.
.
<n>
1:What will be the FCC details for the above structure?
2:Solution for the following error:
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: 'xml.documentName' is a mandatory parameter if more than one recordset per message is specifiedMandatory parameter 'xml.keyfieldName': no value found"
Regards,
Vishal.
>
> 1:What will be the FCC details for the above structure?
Document Name: your msg type
Document Offset:
Recordset Name:
Recordset Namespace:
Recordset Structure: HeaderData,1,ItemData,*
Recordset Sequence: Ascending\Descending
Recordset per Message: *
KeyField Name: give one value which u want to use as a key
KeyField Type: String(Case Sensitive)
header.fieldFixedLengths fix length according to your requirement eg: 2,2,2
header.keyFieldValue value of field which fixed as key field in header
header.fieldNames 1,2,3
body.fieldFixedLengths fix length according to your requiremen eg: 2,2,2,2
body.keyFieldValue 02 value of field which fixed as key field in item
body.fieldNames 10,11,12,13
> 2:Solution for the following error:
> "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: 'xml.documentName' is a mandatory parameter if more than one recordset per message is specifiedMandatory parameter 'xml.keyfieldName': no value found"
It is because you would have missed the values for the mandatory fields like documentName and keyfieldName
Thanks,
Arivarasu
Edited by: Arivarasu S on Aug 5, 2009 9:32 PM
Edited by: Arivarasu S on Aug 5, 2009 9:33 PM
Edited by: Arivarasu S on Aug 5, 2009 9:35 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi vishal,
your have configure this things
header.fieldNames,header.fieldSeparator,header.endSeparator,
keyFieldValue=TEST,keyFieldInStructure=add. some as follow another structure.it should be work.
I
Regards,
Veera
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi vishal,
1. please uuse following para merters
Document name = your Mesage type
Document name space = your namespace.
Document offset = 1
Recorset name = GOods
Recordset structure = HeaderData,1,itemdata,*
key field name = enter the field name which will be used as key from header
2. In the table section
Header.fieldnames = make sure ur field which is used as key field is mentioned.
header.keyFieldValue = enter value which will come in file
Edited by: Deepak Shah on Aug 5, 2009 4:04 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Vishal,
Specify the following in Content Conversion Paramerters.
Document Name : <Message Type Name>
Document Namespace : <Message Type Namespace>
If multiple recordsets available then specify those in Recordset Strucure and add the mandatory parameters.
For parameter help go through the following link.
[http://help.sap.com/saphelp_nw04s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm]
Regards,
JP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please go through this link:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
It has a structure template and the File Content Conversion parameters required.
The error you are getting is because you have left few of the mandatory Content Conversion parameters empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.