Topic
  • 1 reply
  • Latest Post - ‏2012-10-25T23:57:47Z by Keshav1980
Keshav1980
Keshav1980
5 Posts

Pinned topic From MQInput to SAPRequest

‏2012-10-25T19:22:12Z |
Hi All,
WS Message Broker toolkit: V7
Successfully connecting to SAP. Message flow is MQInput to SAPRequest to MQOutput.
But when I am sending below XMl to MQ byt typing the XML in en editor. Request goes to SAP and I am getting this error pasted below. Please provide your input.
Some questions and information:
1) MQInput message domain is set to XMLNSC : For XML messages (namespace aware, validation, low memory use). Is this ok?
2) MQInput connects out to in of SAPRequest without any tranformation in between. Above XML is as per mxsd for SAP BAPI call. is it fine?

Message sent to MQ:
<?xml version="1.0" encoding="UTF-8"?><sapbapisalesordergetstatus:SapBapiSalesorderGetstatus xmlns:sapbapisalesordergetstatus="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapbapisalesordergetstatus" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapbapisalesordergetstatus Sample.xsd"><SalesAndDistributionDocumentNumber>769</SalesAndDistributionDocumentNumber></sapbapisalesordergetstatus:SapBapiSalesorderGetstatus>
*********************************
Error from SAP:
2012-10-25 09:42:11.862779 116 UserTrace BIP3484E: ''Error while calling checkBapiRc.execute(BAPI_SALESORDER_GETSTATUS)Error Msg:Error thrown by SAP: Message=Data was not found for the document, error code: V4211
com.ibm.j2ca.sap.exception.SAPBAPIFaultException: Error thrown by SAP: Message=Data was not found for the document, error code: V4211
at com.ibm.j2ca.sap.bapi.SAPRfcErrorHandler.readBapiRc(SAPRfcErrorHandler.java:430)
at com.ibm.j2ca.sap.bapi.SAPRfcErrorHandler.checkBapiRc(SAPRfcErrorHandler.java:365)
at com.ibm.j2ca.sap.bapi.SapBAPIInvoker.invokeSimpleBAPI(SapBAPIInvoker.java:441)
at com.ibm.j2ca.sap.bapi.SapBAPIInvoker.invokeBAPI(SapBAPIInvoker.java:166)
at com.ibm.j2ca.sap.bapi.SapBAPIInvoker.execute(SapBAPIInvoker.java:565)
at com.ibm.j2ca.sap.SAPInteraction.invokeBAPI(SAPInteraction.java:915)
at com.ibm.j2ca.sap.SAPInteraction.doExecute(SAPInteraction.java:350)
at com.ibm.j2ca.base.WBIInteraction.execute(WBIInteraction.java:336)
at com.ibm.broker.adapter.deploy.MbAdapterAccess.execute(MbAdapterAccess.java:172)
at com.ibm.broker.adapter.nodes.MbAdapterRequestNode.requestData(MbAdapterRequestNode.java:534)
at com.ibm.broker.plugin.MbRequestTemplateNode.requestData(MbRequestTemplateNode.java:51)
''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-10-25 09:42:11.868960 116 UserTrace BIP3484E: ''CWYAP2044E:The BAPI, BAPI_SALESORDER_GETSTATUS, (without transaction) failed. Error: Error thrown by SAP: Message=Data was not found for the document, error code: V4211 Explanation=In the input BAPI business object, either the data, metadata, or both, are incorrect. UserAction=Refer to the exception message for more details.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-10-25 09:42:11.869084 116 UserTrace BIP3484E: ''invoking BAPI_TRANSACTION_ROLLBACK method ''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-10-25 09:42:12.127698 116 UserTrace BIP2231E: Error detected whilst processing a message in node 'SAPSyncTestFlow.SAP Request'.
The message broker detected an error whilst processing a message in node 'SAPSyncTestFlow.SAP Request'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2012-10-25 09:42:12.127705 116 RecoverableException BIP3442E: An exception occurred in adapter node ''SAP Request'', which is using adapter component ''TestSyncFlow.outadapter''..
This message broker node ''SAP Request'' attempted to process a message and communicate with an EIS using an adapter component ''TestSyncFlow.outadapter''. An error occurred during this processing.
See the following messages for details of the error.
2012-10-25 09:42:12.127707 116 RecoverableException BIP3514E: An invalid request was sent to the adapter. Primary keys: ''''.
The adapter received an invalid request. Details: Error type = ''InvalidRequestFault''; Error code = ''V4211''; Primary keys: = ''''; Error message = ''BAPI Interface failed to process the request.Error thrown by SAP: Message=Data was not found for the document, error code: V4211''.
Check that the request is valid.
2012-10-25 09:42:12.128567 116 UserTrace BIP2638I: The MQ output node 'SAPSyncTestFlow.Fail3' attempted to write a message to queue ''Fail3'' connected to queue manager ''DevBrokerComm''. The MQCC was '0' and the MQRC was '0'.
2012-10-25 09:42:12.128572 116 UserTrace BIP2622I: Message successfully output by output node 'SAPSyncTestFlow.Fail3' to queue ''Fail3'' on queue manager ''DevBrokerComm''.
2012-10-25 09:42:12.220584 116 UserTrace BIP3484E: ''isTransactionSupported - true''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-10-25 09:42:12.220619 116 UserTrace BIP3484E: ''isTxnSupported - true''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-10-25 09:42:18.254624 4 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2012-10-25 09:42:18.254782 4 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-10-25 09:42:18.254844 4 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-10-25 09:42:18.254926 4 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '212' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2012-10-25 09:42:18.255208 4 Information BIP2152I: Configuration message received from broker.
An execution group received a command from the Broker.
No user action required.
2012-10-25 09:42:18.255264 4 Information BIP2153I: About to ''change'' an execution group.
An execution group is about to perform an action.
No user action required.
Updated on 2012-10-25T23:57:47Z at 2012-10-25T23:57:47Z by Keshav1980
  • Keshav1980
    Keshav1980
    5 Posts

    Re: From MQInput to SAPRequest

    ‏2012-10-25T23:57:47Z  
    Hi All,

    The issue has been resolved. I had to pad the request value (SalesAndDistributionDocumentNumber) with leading 0 to maintain field lenght.
    I sent the XML to MQ as required by the SAP Adapter based on XSD.
    Thanks.