Has any one ever met this kind of ABAP-mapping problem ??

Question

Dear all,
our scenario is:     
(remote)MQ(ssl connection)->(local)MQ-(jms)>XI---(proxy)>ECC
I met a very strange question during mapping which we use  abap mapping inside xi.
the message come out from the abap mapping step.after the abap-mapping, the generated target message still has the source message concatenated with. it occurs only when all servers integrated together, but not occurs when we mannully put the source msg at local MQ (means this way, it works all right).
even during error case, it still can go through all the remaining steps of IE, and the out bound jms adapter then goes into the
target SAP ECC system, but of cause at the final step, it will reach u2018CX_ST_GROUP_MISSING_CASEu2019 error (this is because the message is not a valid xml file, and abap proxy can not consume it...
sample file after abap mapping:
<?xml version="1.0" encoding="utf-8"?>
<ns:MT_MQIVMessage xmlns:ns="urn:ianes:mqiv">
     <MQIVMessage>
     <MQIVPayload> ..data..</MQIVPayload>
     </MQIVMessage>
</ns:MT_MQIVMessage>
<?xml version="1.0"?>
<ns:MT_K2 xmlns:ns="urn:ianes:prp:ipsc">
     <header> .header.</header>
     <data>..data...</data>
</ns:MT_K2>

Answer 1

Dear expert,
after detail analysis, i found the 1st place that the soap header was wrongly set...
in call adater setp...
<SAP:Sender>
  <SAP:Service>BS_PRP</SAP:Service>
  <SAP:Interface namespace="urn:ianes:ext:ips">MI_MQIV_outb</SAP:Interface>
  </SAP:Sender>
  <SAP:Receiver>
  <SAP:Party agency="" scheme="" />
  <SAP:Service>BS_SAP</SAP:Service>
  <SAP:Interface namespace="urn:ianes:prp:ipsc">MI_K3</SAP:Interface>
  </SAP:Receiver>
  <SAP:Interface namespace="urn:ianes:prp:ipsc">MI_K5</SAP:Interface>
  </SAP:Main>
you can see the k5  was wrong set to k3
correct soap header should be this
<SAP:Sender>
  <SAP:Service>BS_PRP</SAP:Service>
  <SAP:Interface namespace="urn:ianes:ext:ips">MI_MQIV_outb</SAP:Interface>
  </SAP:Sender>
- <SAP:Receiver>
  <SAP:Party agency="" scheme="" />
  <SAP:Service>BS_SAP</SAP:Service>
  <SAP:Interface namespace="urn:ianes:prp:ipsc">MI_K5</SAP:Interface>
- <SAP:Mapping notRequired="M">
  <SAP:ObjectId>RXmJZiHCMPynqzPehi20YQ==</SAP:ObjectId>
  <SAP:SWCV>z+4XcK+qEduCcMP2oNwEVQ==</SAP:SWCV>
  <SAP:SP>-1</SAP:SP>
  </SAP:Mapping>
  </SAP:Receiver>
  <SAP:Interface namespace="urn:ianes:prp:ipsc">MI_K5</SAP:Interface>
  </SAP:Main>
i guess this is the root of error, does any one give some hints on this ?
Thanks
Wu