Skip to Content
avatar image
Former Member

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

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>

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jul 01, 2009 at 07:34 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 02, 2009 at 01:34 AM

    does anybody who has abap mapping experience could help on this ??

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 02, 2009 at 08:50 AM

    > I met a very strange question during mapping which we use abap mapping inside xi.

    How should anyone know what is wrong with your mapping?

    Try to debug it.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 03, 2009 at 03:42 AM

    This is a eoio scenario, the abap mapping works fine when i debug it, as what i said previously, it only occurs when

    more than 1 msgs come, and after mapping, the source msg is concatenated with target msg...

    but one by one test , no problem occurs..

    thanks Stefan, you can just assume that the abap code is ok, could you please give me some advice on if the problem may be at system level btw, our xi is in 700, patch 15.

    Thanks !

    BR,

    Wu

    Add comment
    10|10000 characters needed characters exceeded