JDBC TO RFC SYNC SCENARIO---- MONI ERROR

[former_member194741]

Hi All,

   I am doing jdbc to rfc sync scenario, while testing i am getting the below error.

As per my knowledge , this bapi is an test bapi, so there is some error in this value.I n audit log i am getting the same error.Can anybody suggest a soln to this.

Received XI System Error. ErrorCode: EXCEPTION_DURING_EXECUTE ErrorText: null ErrorStack: Runtime exception occurred during application mapping com/sap/xi/tf/_SMS_JDBC2RFC_MM_REQ_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:ZOFFIFM_BANK_TEST/TEL_NUMBER. Values missing in queue context~ 

  Regards,

Dhansuh

[smavachee · Accepted solution]

Hello Karthick,

1. Take payload from SXMB_MONI, test it in MM test tab.

2. "TEL_NUMBER" expecting some value.

3. Use node function "MapWithDefault".

It will help.!

Regards,

Sunil

[former_member194741 · Accepted solution]

Hi All,

  I tried to execute the payload, but i am getting the following error

18:51:48 Start of test 

Compilation of SMS_JDBC2RFC_MM_REQ successful
The processing instruction target matching "[xX][mM][lL]" is not allowed.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sap.aii.mappingtool.tf7.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:255)
at com.sap.aii.mappingtool.tf7.rt.xparser.XParser.run(XParser.java:89)
Caused by: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1441)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPIData(XMLScanner.java:689)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanPIData(XMLDocumentFragmentScannerImpl.java:750)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPI(XMLScanner.java:664)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:845)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.aii.mappingtool.tf7.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:252)
... 1 more
Root Cause:
org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1441)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPIData(XMLScanner.java:689)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanPIData(XMLDocumentFragmentScannerImpl.java:750)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPI(XMLScanner.java:664)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:845)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.aii.mappingtool.tf7.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:252)
at com.sap.aii.mappingtool.tf7.rt.xparser.XParser.run(XParser.java:89)
The processing instruction target matching "[xX][mM][lL]" is not allowed. 18:51:51 End of test

[former_member194741]

hI Sunil,

All my fields are asking for values, so i mapped all fields to mapby default, but i want to pass the value from database, so its again confusing.

   Regards,

  Karthick

[former_member194741]

Hi Sunil,

u r correct, I tried with Map by default, it worked.

But i got another error, Also i checked in Rec.Agrement and deleted and did it again, but iam using another receiver channel to get the response.

Received XI System Error. ErrorCode: CO_TXT_OUTBINDING_ERROR ErrorText: No standard agreement found in channel ,Problem occurred in receiver agreement for sender.

regards,

dhanush

[smavachee]

Test your configuration again with Test tool and complete the required ID Part.

Regards,

Sunil

[nabendu_sen]

Hi Dhanush,

There should be one Sender JDBC and One Receiver RFC communication channel, thats all. Both are able to handle Synchronous communication and no need to create any extra channel. Your error has occurred because the extra Communication Channel does not have suitable Agreement.

[Former Member]

Hi Karthick dhanush,,

First, download your payload from moni, and test in message mapping. sender structure and target structure different right, make sure that what you are passing  sender values to target values didn't match. Some time sender side sending null values which is expecting values from receiver side. I think this is most common problem.

Thanks,

Seshu.

[baskar_gopalakrishnan2]

Make sure you pass values from the sender structure to target structure where it requires values for the mandatory fields as well mandatory node occurence elements.  This is mostly a common issue.

[former_member312864]

HI,

Check your message mapping ,mandatory field of target structure not getting any value.

check your source data weather its passing any value to the target field TEL_NUMBER or not.

Regards,

Sarojkanta