XI File Content Conversion Issue

[Former Member]

Peace to All,

I am having this funny problem in File Content Conversion:

com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:ZIN_MT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

What did I do:

DATA TYPE1.

Structure1: TESTOUT_DT Complex Type

REC Element 1-1

Name11 Element xsd:string 1-1

Name12 Element xsd:string 1-1

Structure2: TESTIN_DT Complex Type

Name21 Element xsd:string 1-1

Name22 Element xsd:string 1-1

Mapping:

name11-name21

name12-name22

Configuration of Sender File :

DocumentName : TESTOUT_DT

Document NameSpace : http:/myspace.com/test1

RecordSetName : Recordset

Recordset Structure : Rec,1

Rec.fieldNames :name11,name12

Rec.fieldSeparator :,

Rec.endSeparator :'nl'

-

---

So when I test it it picks up the file but is unable to map it to destination.

Can anyone help me to find out why?.

One more hint is that I am using Third party Business System and I use the same for both file CC sender channel and Filereceiver channel.

I will appreciate your help.

Thanks

[Former Member · Accepted solution]

Hi Shilpa,

To me, it seems that you have a problem in your Message mapping.

Grab the input data from SXMB_MONI and test your mapping with that data; you should be getting the error while executing the MM.

Thanks,

Pooja Pandey

[Former Member]

Answered elsewhere

[Former Member]

Many thanks to your guidance...SDN is the best...It worked

Moving forward I encountered another issue, when I extend it a Trail to it and end up with this mapping:

ZOUT_MT 11 -

---

ZIN_MT 11

Recordset 1--1

Rec 1unbounded

---

Test01 1-----unbounded

key(string) 1...1----

---

key 1..1(string)

name11(string) 1..1----

---

name21 1..1(string)

name12(string) 1..1----

---

name22 1..1(string)

Trail 1...1 -

---

Trail 1---1

key(string) 1..1 -

---

key 1..1(string)

test(string) 1...1 -

---

test1..1 (string)

In Config: Sender File CC

Doc Name :ZOUT_MT

Doc namspace : http://mytest.com/test1

RecordsetName : Recordset

Recordset Structure : Rec,*,Trail,1

Key Field Name : key

Recordset per message : 1

Rec.fieldNames : key,name11,name12

Rec.fieldSeparator : ,

Rec.endSeparator : 'nl'

Rec.processConfiguration: FromConfiguration

Rec.keyFieldValue : 1

Trail.fieldNames: key,test

Trail.endSeparator: 'nl'

Trail.processConfiguration : FromConfiguration

Trail.keyFieldValue : 1

Trail.fieldSeparator : ,

From all this work above , when I put the file having:

1,111,112

1,222,223

1,333,334

1,99

The output file in empty (null)...

Does anyone out there understand why the output file is becoming null..

here is the log I get in workbecnh (commuunication channel)

Audit Log for Message: c1a434f5-ad9f-4a26-08c1-e7d579a5927a

Time Stamp Status Description

21.01.2009 11:48:22 Success Channel ztest_sender_cc: Entire file content converted to XML format

21.01.2009 11:48:22 Warning Channel ztest_sender_cc: Empty document found. Proceed without sending message

21.01.2009 11:48:22 Success File "/mylocation/interface/SCM/somefolder/in/shilpagirlsinput.txt" deleted after processing

[Former Member]

Hi Shilpa,

you have to maintain structure like below then u will get data on target side... you need to maintain root node..

MT_Source

. . Recordset

. . . REC

. . . . . Name11

. . . . . Name12

Regards,

Yadav

[Former Member]

The problem was solved but the output file in empty

[VijayKonam]

You have to create a Recordeset(since you mentioned your recordset as Recordset in the FCC parameters) element on top of REC to process it coreclty. Mind that everything is case sensitive.

VJ

[Former Member]

Specify the ignoreRecordsetName to true in case you dont need that record set in target structure.

Rajesh

[Former Member]

Hi Shilpa,

I can see the problem is in your File content conversion (FCC). As you know FCC is case sensitive so you have to be very careful while doing FCC.

For example, Recordset Structure : REC,1 (you have used Rec)

Check other things in FCC and then run your scenario, I am sure it will work.

Regards,

Sarvesh

[Former Member]

It worked, thanks for the help

[Former Member]

Great !!!

[Former Member]

Have you mapped something to your root element ZIN_MT? if yes, Does the source field have value in your actual message?

Like Pooja said, copy the message from MONI and test it in the test tab of the MM.

[Former Member]

When I test the mapping in Desin, it works well. I get its payload and put in workbench, it goes well.

But when I get the the payload from SXMB_MONI, it fails and gives me the same error.

I am just disgusted, tried all the combinations possible and it is not working still...

Need your help guys or/and girls

[Former Member]

HI Shilpa,

Do you have any condition/UDF in your mapping to generate the target node /ns0:ZIN_MT ?

As per the error, your mapping couldnt generate the ZIM_MT node, so, you have to see what factors play role in generation of the node.

Thanks,

Pooja