cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Mapping Issue

Former Member

on ‎07-28-2009 2:49 PM

0 Kudos

Hi Gurus,

I have a JDBC-XI-RFC scenario (EOIO), where in I had to use Enhanced receiver determination to split the calls to RFC's (Regular Vs Emergency). Emergency call was directed using the filter queue to change the priority. We have tested in many env (d,q, pre prod) & now when I moved to Prod I get a strange error. When it first come to the integration engine & if it requires a split it fails showing a mapping error. But if I re-trigger it flow succesfully. Please fing the log from "moni" below(1) & a sussesful log (2).

Please see the below bolded log which I am getting confused

In case of error I get

<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>

Else I get

<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface>

**(1)**
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
 <!--  Request Message Mapping 
  --> 
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">- <SOAP:Header>
 <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
  <SAP:MessageClass>ApplicationMessage</SAP:MessageClass> 
  <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode> 
  <SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId> 
  <SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent> 
 <SAP:Sender>
  <SAP:Service>CIS_PROD_STORMS</SAP:Service> 
  •  <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface> *
  </SAP:Sender>
 <SAP:Receiver>
  <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" /> 
  <SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service> 
  <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface> 
 <SAP:Mapping notRequired="M">
  <SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId> 
  <SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV> 
  <SAP:SP>-1</SAP:SP> 
  </SAP:Mapping>
  </SAP:Receiver>
  <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface> 
  </SAP:Main>
 <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService> 
  <SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId> 
  </SAP:ReliableMessaging>
 <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>Application</SAP:Category> 
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
  <SAP:P1>com/sap/xi/tf/_MM_ENVISION_WO_TO_SAP_NOTIF_EMERG_</SAP:P1> 
  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2> 
  <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>

(2)

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
 <!--  Response 
  --> 
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SOAP:Header>
 <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
  <SAP:MessageClass>ApplicationMessage</SAP:MessageClass> 
  <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode> 
  <SAP:MessageId>4A6DDA42-B138-7443-E100-00000AAA0C0C</SAP:MessageId> 
  <SAP:TimeSent>2009-07-27T22:01:00Z</SAP:TimeSent> 
 <SAP:Sender>
  <SAP:Service>CIS_PROD_STORMS</SAP:Service> 
  <SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface> 
  </SAP:Sender>
 <SAP:Receiver>
  <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" /> 
  <SAP:Service>BS_ENVISION_SAP_REGULAR</SAP:Service> 
  <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface> 
 <SAP:Mapping notRequired="M">
  <SAP:ObjectId>oPLLbgxJOWimAK6rdZb/MA==</SAP:ObjectId> 
  <SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV> 
  <SAP:SP>-1</SAP:SP> 
  </SAP:Mapping>
  </SAP:Receiver>
  •  <SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION</SAP:Interface> *
  </SAP:Main>
 <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService> 
  <SAP:QueueId>XI_ENV_SERIALIZE</SAP:QueueId> 
  </SAP:ReliableMessaging>

Regards

UK

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
‎07-29-2009 7:15 AM
0 Kudos

Hi Unni,

Don't see any issue ..!!!

Please paste the error message at Moni Level..

Regards,

Show replies
Show replies
Former Member
‎07-28-2009 3:12 PM
0 Kudos

Unni,

Please make your post more elaborate. Use the text help and make it clear, so that it can easily understandable.

Edited by: Gangadhar G on Jul 28, 2009 4:12 PM

Show replies
Show replies
Former Member
‎07-28-2009 4:06 PM
0 Kudos

Hi,

Sorry, My text help was not working due to some IE setting & I can understand the message got cluttered.

Anyways let me repost the actual thread,

I have a JDBC-XI-RFC scenario which requires an Enhanced receiver determination and requires calling two different RFC programs(emergency, regular) based on that. I use a queue filter to direct to XBQA* for emergency. As I indicated, it seems working fine with d,q,preprod. When I move it to prod, it show me some maping issue. However when I retrigger the same from my moni, they execute succesfully. Please see the log below for a message that goes error & the log when it is succesful (retrigger). Let me know if you need more details.

When there is error Please see the last tag

MI_TBL_WMS_SOURCE_STAGING_SDW_EGD is the sender

<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

<SAP:MessageId>4A6DF427-B0EE-7444-E100-00000AAA0C0C</SAP:MessageId>

<SAP:TimeSent>2009-07-28T13:37:05Z</SAP:TimeSent>

<SAP:Sender>

<SAP:Service>CIS_PROD_STORMS</SAP:Service>

<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>

</SAP:Sender>

<SAP:Receiver>

<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />

<SAP:Service>BS_ENVISION_SAP_EMERG</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>

<SAP:Mapping notRequired="M">

<SAP:ObjectId>RNPgv18MOBmjhpr+oO1mNw==</SAP:ObjectId>

<SAP:SWCV>oZGAQNmpEdym2dnSCqoHjQ==</SAP:SWCV>

<SAP:SP>-1</SAP:SP>

</SAP:Mapping>

</SAP:Receiver>

*<SAP:Interface namespace="http://enbridge.com/envision/envision2/jdbc">MI_TBL_WMS_SOURCE_STAGING_SDW_EGD</SAP:Interface>

</SAP:Main>*

Blelow is when its succesful

<SAP:Interface namespace="urn:sap

-com:document:sap:rfc:functions">ZWM_INBOUND_NOTIFICATION_EMERG</SAP:Interface>.

Regards

Unni

Edited by: Unni Krishnan on Jul 28, 2009 5:06 PM

Former Member
‎07-29-2009 6:58 AM
0 Kudos 
When I move it to prod, it show me some mapping issue

So, are you getting an error in Moni ?If yes, can you paste it here.

Or some issue with the interface name ?

former_member200962
Active Contributor
‎07-28-2009 2:55 PM
0 Kudos 
_MM_ENVISION_WO_TO_SAP_NOTIF_EMERG_

Can you confirm that the MM mentioned above is working properly...everything (in terms of Cache is up-to-date)

Regards,

Abhishek.

Show replies
Show replies
Former Member
‎07-28-2009 3:05 PM
0 Kudos

Hi,

If I test from the IR, they all seems to work fine. What is the technique, I can paste the log in here. They are not showing correctly in my thread.

Regards,

Ask a Question