'Conversion configuration error: Unknown structure 'ns0:Message1'

[Former Member]

All,

I'm using multimapping.

I'm getting error, when doing end to end testing.. below is the error log from RWB.  Unit testing works just fine.
The configuration was working fine when it was one-one mapping(before converting this to multimapping 1-n)

it is FCC(file Content conversion)

Apr 4, 2012 11:26:14 AM Information Write to file "/interfac/JPMC_PaymentData_20120404-112614-271.txt" as text (encoding ISO646-US) size 244 bytes.  

Apr 4, 2012 11:26:14 AM Error File processing failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Message1' found in document', probably configuration error in file adapter (XML parser error)'

Apr 4, 2012 11:26:14 AM Information Start converting XML document content to plain text

Thanks for your help in advance.

Prema

[Former Member · Accepted solution]

closing this thread as i have another thread opened for related query.

[Former Member]

all,

I'm still awaiting answers;  anybody came accross such problem? expecting some solution to this..

[Former Member]

I noticed you have an extra Message1 tag as parent node in the source mapping.

Should that be the structure you want /ns0:Message1/Message1/...  FCC could be throwing an error because of the extra Message1 tag. Recheck your MT structure and test again.

Hope it helps.

[Former Member]

albert,

it is actually Messages and Messages1 tag.  this added when i say occurence 1 to 0:n occurence

[baskar_gopalakrishnan2]

When you do end to end testing , you should not see ns0:Message1 tags. Please check your target structure as well fcc conversion parameters thoroughly. Since  you don't have these tag reference in content conversion parameter section, you get this message.

[Former Member]

Thanks Baskar;
could you let me know, what should i check in target structure and fcc parameters?

yes i should NOT see this message1 tag at adapter level.

what could probably be wrong?

[baskar_gopalakrishnan2]

Please provide your target structure and fcc conversion parameters here.  Only during testing at mapping section, you will find message 1 tags.  Are you providing 0 to unbounded occurences for your target structure parent node?

[Former Member]

yes I'm providing  o:unbound to my target structure.

FCC is

BankHeader,BuildingGroup,LeaseDetail,BuildingTotal,BankTotal

BankHeader.fieldFixedLengths	1,35,8,2,18
BuildingGroup.fieldFixedLengths	0,0
LeaseDetail.fieldFixedLengths	1,2,1,5,10,1,6,1,6,3,6,14
BuildingTotal.fieldFixedLengths	1,18,6,11,5,18
BankTotal.fieldFixedLengths	1,12,12,11,5,1,18
BankHeader.endSeparator	'nl'
LeaseDetail.endSeparator	'nl'
BuildingTotal.endSeparator	'nl'
BankTotal.endSeparator	'nl'
BankHeader.fixedLengthTooShortHandling	Cut
BuildingGroup.fixedLengthTooShortHandling	Cut
BuildingTotal.fixedLengthTooShortHandling	Cut
BankTotal.fixedLengthTooShortHandling	Cut

[baskar_gopalakrishnan2]

Target Structure and fcc parameters looks good. Hope you specified message type as document type?

[Former Member]

baskar; what do yo meant by saying:   "you specified message type as document type?"

[Former Member]

DocumentName = MRI_PaymentData.

DocumentName is a field in the file adapter receiver.

Also make sure you changed the occurrence in the interface mapping .  Also copy the payload from SXMB_MONI and test it locally on the message mapping or interface mapping to make sure that its creating the right structure .

[Former Member]

thank you Rahul;

I see DocumentType only in sender adapter not in recvr though..

[Former Member]

my bad.. you are right . its only on the sender .

Did u run the mapping locally .

Can you try entering the configuration parameters for only the BankingHeader , BuildingGroup and BuildTotal .

[Former Member]

Rahul,

I'm using "integrated Configuration"  so how do i make changes to occurrence in the interface mapping ?  yes i did test locally using the payload from SXMB_MONI on the message mapping. but cant test it on interface(operation) mapping as it has those Messages tags..

[iaki_vila]

Hi Prema,

Have you checked the seven point in this wiki http://wiki.sdn.sap.com/wiki/display/XI/Troubleshooting+the+File+Adapter ?

Check the target payload after mapping and make sure all the fields are generated. In case any field is not created the FCC for fixed length files will fail.

Regards

[Former Member]

thanks Inaki. but the wiki did not help me with my error.