Target element missing in application mapping

Dear Experts,
                                           (Request)
I am working on SOAP <> SAP-XI <> SAP ECC ( Proxy).
                                           (Response)
Since the Request and Response message types are same , I have created 2 Message Type i.e. 1 for Request and 1 for
Response.
Part1:
So for Service Interface , I am using the same message types for SOAP and SAP.
Note: I have used all the data types,message types, message mapping and operation mapping under 1 namespace.
2 Message Mapping are working fine.Is this design fine?
Part2:
When tested with SOAP Test tool, I am getting error in Tx sxmb_moni with the text:
Error Text:" Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ProxyResponseTo_SoapRespo~;
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_SOAPResponse/Message_Type.
Values missing in queue co~".
The point to be noted is that target element /ns0:MT_SOAPResponse/Message_Type is not there and I have activated the deleted objects. I am not using this element in any  MM and OM.
Part3
For 1 request message, I am receiving, 2 response  from SAP ECC . What is the issue here.
Can anyone help me on both the querries and where I can improve my design aspects?
Regards
Alice~
Edited by: Alice@xi on Jan 23, 2012 7:15 PM

Part1: Your design is fine.
Part2: Looks like you are doing synchronous scenario. Just make sure in the service interface you referenced request and response correctly. This is for both outbound and inbound service interface. Also you have two mapping object one for the request and the second one for the response. You have to reference the first request mapping object for request in the operation mapping and the second response mapping object for response in the operation mappng. Make sure you do right. Also if you delete all the unwanted objects  and reference only live objects in the mapping and service interfaces you will not have delete issue.
Part 3: You might have to regenerate sproxy once again after deleting the unwanted objects in ESR/IR. Check how many message types you get after this. You should one each for request and response. Not two for response. Hope you sproxy for the target structure inbound service interface.
Hope that helps.

Similar Messages

  • Cannot create target element /Invoice. Values missing in queue context.

    Hi Experts,
    I am working on Idoc to File scenario using SAP PI 7.1. In this scenario I am mapping Invoic02 Idoc with Invoice xsd. I am able to test the mapping in ESR with status as success.
    In ID Tools --> Test Configuration I used the same payload and tried testing the configuration step by step. while executing I am getting an error at Operation Mapping saying "Runtime exception occurred during application mapping com/sap/xi/tf/_MM_SRM_Hubwoo_Invoice_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /Invoice. Valuesmissing in queue context. Target XSD requires a v~"
    Even though the mapping is getting executed successfully in ESR, I am not able to fix this issue. Need your inputs in resolving the same.
    Regards,
    Saurabh
    Edited by: saurabh mathure on Oct 16, 2010 8:14 AM

    Hi ,
    issue"Can not create the target element   value missing the queue context'.
    reason for this issue:
    Target field expecting some value from sender field. so in testing your not getting  any data from source field  for this reason your getting that issue.
    Solution:
    In mapping use node function:Mapwith deafault between source and taget fileds.
    Then activate mapping . now excute the scenario it  will properly without that issue.
    Cheers,
    Meera

  • Cannot create target element(Runtime exception occurred during application

    Hi ,
    this is IDOC TO HTTP Scenario. in error description it is shoein g below error.
    Runtime exception occurred during application
    Cannot create target element (inbound)
    please advice
    thank you.

    Copy the payload from sxmb_moni and test it in the mapping tool using debug mode. I suspect some mandatory elements in target structure requires value but it is missing during mapping. Sometime sender data structure due to values are not getting at runtime does not create target structure element. Check all the individual fields in the mapping tool.

  • 1:N mapping for ZALEAUD01: Cannot produce target element /ns:0Messages

    Hi,
    I am working on a scenario where my sender MT is ZALEAUD01 (idoc occurance 1..1) and receiver MT is a xml file (Root Node occurance 1..1). I want to generate the number of files based on the occurance of a particular node (E1STATE). I am using a multi-mapping here by changing the occurance of the root node of Receiver xml file  to 0..unbounded in Messages tab of MM and mapping it with E1STATE
    During runtime, I am getting the Mapping error and in Trace I am getting the message: Cannot produce target element /ns0:Messages.Check xml instance is valid for source xsd and target field mapping fullfills requirement of target xsd
    Please tell me some solution
    Thanks & Regards

    Hi All,
    Thanks for your quick responses
    But I have already checked all that..
    My mapping is E1STATE----> MT_Root with the context of E1STATE as Idoc,
    I have tested the mapping in test and everything is successful.
    I know we can not test the mapping with the Idoc structure generated in sxi_monitor as its missing the /ns0: Messages and /ns0: Message1 nodes. So I have added these nodes in my xml structure while testing in IR and the mapping test is successful.
    But @ runtime as these Messages node should be generated by Xi so I feel this is where the problem is.

  • Cannot create target element/ns1:MT_CONTRACT.Value missing in queue context

    Hi Friends,
    AgrmntID,Company_Code,Vendor_No,PurDoc_Type,ValidPeriod_Start,ValidPeriod_End,Pur_Group,Currency,Incoterms,Item_Cat,Tax_Code,Part_No,Document_Desc,Net_Price,Tgt_Qty,Price_Unit,Plant,Price_Revision
    002,UBUK,1568956,LP,16.02.2011,16.02.2012,3P,GBP,FOB ,D,V1,5100000102515,CARD-Twiglets Original 45g x 12,0,1,10,AM04,N
    002,UBUK,1568956,LP,16.02.2011,16.02.2012,3P,GBP,FOB ,D,V1,5100000102515,CARD-Twiglets Original 45g x 12,0,1,10,AM04,N
    002,UBUK,1568956,LP,16.02.2011,16.02.2012,3P,GBP,FOB ,D,V1,6000005,CARD-Twiglets Original 45g x 12,0,125.00,145,AN03,N
    002,UBUK,1568956,LP,16.02.2011,16.02.2012,3P,GBP,FOB ,D,V1,5100000102515,CARD-Twiglets Original 45g x 12,0,1,10,AM04,N
    002,UBUK,1568956,LP,16.02.2011,16.02.2012,3P,GBP,FOB ,D,V1,6000005,CARD-Twiglets Original 45g x 12,0,125.00,145,AN03,N
    that is csv file am trying to convert to xml. but am getting error "Cannot create target element /ns1:MT_CONTRACT. Value missing in queue context."
    my data types is:    MT_CONTRACT_SNDR                                                            MT_CONTRACT
    SUB_ELEMENT:              Recordset                                                                            Recordset
    SUB_ELEMENT:                   Item                                                                                Item
      SUB_ELEMENTS:                    AgrmntID                                                                              AgrmntID
                                                     Company_Code                                                                    Company_Code
                                                     Vendor_No                                                                            Vendor_No
    like this all the 18 elements under Item node. I kept Recordset occurance 0-1 and Item 0-Unbound and all 18subelements as 0-1 in both sender and receiver. And in content conversion:
    Document Name: MT_CONTRACT_SNDR
    Document Offset: 1
    Recordset Structure: Item,*
    Record Sequence: Asending
    Recordsets per Massage: 1
    Key Field Type: String (Case-Sensitive)
    Item.fieldSeperator : ,
    Item.endSeperator: 'nl'
    Item.fieldNames: AgrmntID,Company_Code,Vendor_No,PurDoc_Type,ValidPeriod_Start,ValidPeriod_End,Pur_Group,Currency,Incoterms,Item_Cat,Tax_Code,Part_No,Document_Desc,Net_Price,Tgt_Qty,Price_Unit,Plant,Price_Revision
    KINDLY SUGGEST ME WHAT MISTAKE AM DOING. AM NEW TO SAP PI

    I have this error in audit log. On searching I read that the error is connectivity problem between abap stack and java stack. but I made restart the server but error not cleared. can anyone of you suggest me to solve?
    Audit Log for Message: 7c06ee0d-d70b-406f-07bc-f56228cc1d6a
    Time Stamp Type Description
    10.08.2011 18:05:07 Information RfcAdapter received a asynchronous message. Trying to send tRFC for ZFM_SRM_CONTRACT_CREATE with TID XIV0Rk3TSBG6y7lFLYACmTQW.
    10.08.2011 18:05:07 Information RfcAdapter received a asynchronous message. Trying to send tRFC for J2EE_GUEST with TID XIV0Rk3TSBG6y7lFLYACmTQW.
    10.08.2011 18:05:07 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZFM_SRM_CONTRACT_CREATE in remote system (RfcClient[CC_Contrct_Recivr]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.
    10.08.2011 18:05:07 Error Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZFM_SRM_CONTRACT_CREATE in remote system (RfcClient[CC_Contrct_Recivr]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught..
    10.08.2011 18:05:07 Information The message status was set to WAIT.
    10.08.2011 18:05:07 Information The asynchronous message was successfully scheduled to be delivered at Wed Aug 10 18:10:07 IST 2011.
    10.08.2011 18:10:07 Information The message status was set to TBDL.
    10.08.2011 18:10:07 Information Retrying to deliver message to the application. Retry: 1
    10.08.2011 18:10:07 Information The message was successfully retrieved from the receive queue.
    10.08.2011 18:10:07 Information The message status was set to DLNG.
    Time Stamp Type Description
    10.08.2011 18:10:07 Information Delivering to channel: CC_Contrct_Recivr
    10.08.2011 18:10:07 Information RfcAdapter received a asynchronous message. Trying to send tRFC for ZFM_SRM_CONTRACT_CREATE with TID XIV0Rk3TSBG6y7lFLYACmTQW.
    10.08.2011 18:10:07 Information RfcAdapter received a asynchronous message. Trying to send tRFC for J2EE_GUEST with TID XIV0Rk3TSBG6y7lFLYACmTQW.
    10.08.2011 18:10:08 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZFM_SRM_CONTRACT_CREATE in remote system (RfcClient[CC_Contrct_Recivr]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.
    10.08.2011 18:10:08 Error Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZFM_SRM_CONTRACT_CREATE in remote system (RfcClient[CC_Contrct_Recivr]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught..
    10.08.2011 18:10:08 Information The message status was set to WAIT.
    10.08.2011 18:10:08 Information The asynchronous message was successfully scheduled to be delivered at Wed Aug 10 18:15:08 IST 2011.

  • UDF required !! Cannot create target element Values missing in queue context

    Dear Experts,
    I am getting the cannot create target element error with acknowledgement payload in response message mapping  in synchronous interface. I have shared the response payload2. Please suggest do I need write any UDF.
    Message mapping successful with below payload1:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:updateOppResponse xmlns:ns0="http://soap.sforce.com/schemas/class/clientUpdateInqWebService">
       <ns0:result>
          <ns0:Description>Record Updated</ns0:Description>
          <ns0:SFDCId>006M0000007xjTrIAI</ns0:SFDCId>
          <ns0:Status>true</ns0:Status>
       </ns0:result>
    </ns0:updateOppResponse>
    With the below target system response message, Mapping failing with Cannot create target element /ns1:MT_InquiryUpdate_ECC_Ack. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD com.sap.aii.mappingtool.tf7.IllegalInstanceException:
    Actual acknowledgement reply from target system payload2:
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns="http://soap.sforce.com/schemas/class/clientUpdateInqWebService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
       <soapenv:Body>
          <updateOppResponse>
             <result>
                <Description>Record Updated</Description>
                <SFDCId>006M0000007xjTrIAI</SFDCId>
                <Status>true</Status>
             </result>
          </updateOppResponse>
       </soapenv:Body>
    </soapenv:Envelope>
    Regards
    RKN

    Hi
    The easiest solution will be , write an simple java map for your response mapping.
    Please provide your target structure , if you need any help on the java mapping.
    Sample code:
    Response message from web service
    target msg:
    java code:
    package com.sap;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.transform.Result;
    import javax.xml.transform.Source;
    import javax.xml.transform.Transformer;
    import javax.xml.transform.TransformerFactory;
    import javax.xml.transform.dom.DOMSource;
    import javax.xml.transform.stream.StreamResult;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    import com.sap.aii.mapping.api.AbstractTransformation;
    import com.sap.aii.mapping.api.StreamTransformationException;
    import com.sap.aii.mapping.api.TransformationInput;
    import com.sap.aii.mapping.api.TransformationOutput;
    public class populateResponseMessage extends AbstractTransformation {
          public void transform(TransformationInput arg0, TransformationOutput arg1)
                      throws StreamTransformationException {
                try {
                      DocumentBuilderFactory tfactory = DocumentBuilderFactory
                                  .newInstance();
                      DocumentBuilder tbuilder = tfactory.newDocumentBuilder();
                      Document doc = tbuilder.parse(arg0.getInputPayload()
                                  .getInputStream());
                      Document newdoc = tbuilder.newDocument();
                      Element root = (Element) newdoc.createElementNS(
                                  "urn:sap-com:document:sap:rfc:functions",
                                  "ns1:ZTEST_FAULT_MESSAGE_DATA.Response");
                      newdoc.appendChild(root);
                      NodeList nlList = doc.getElementsByTagName("ConversionRateResult");
                      if (nlList.getLength() != 0 && nlList != null) {
                            Node data = nlList.item(0);
                            String sourceval = data.getTextContent();
                            Element rate = (Element) newdoc.createElement("RATE");
                            rate.setTextContent(sourceval);
                            root.appendChild(rate);
                      Transformer transformer = TransformerFactory.newInstance()
                                  .newTransformer();
                      Source source = new DOMSource(newdoc);
                      Result output = new StreamResult(arg1.getOutputPayload().getOutputStream());
                      transformer.transform(source, output);
                } catch (Exception e) {
                      e.printStackTrace();
          }// end of transform

  • Cannot create target element /ns0 Values missing in queue context

    Hi Sdn,
    When I am testing the Message mapping in PI i am getting the below error message .
    Cannot create target element /ns0:TechObjChange. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD See error logs for details
    Could you please tel me what would be the wrong.
    below is the XML file data .
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:TechObjChange xmlns:ns0="http://schemas.xxxxx.com/iiiii/xxxxxx">
       <TechObjChangeFLEQ>
          <FormType/>
          <FunctionalLocation/>
          <Descoffunctionalloc/>
          <Equipment/>
          <DescofEquipment/>
          <StartupDateofTechObj/>
          <Manufacturer/>
          <Manufacturermodelnumber/>
          <Manufacturerpartnumber/>
          <Manufacturerserialnumbe/>
          <Countryofmanufacture/>
          <Yearofconstruction/>
          <Monthofconstruction/>
          <TypeofTechObject/>
          <PlannerGroup/>
          <MainWorkCenter/>
          <CatalogProfile/>
          <NameofUserchangingtheobject/>
          <Characteristic>
             <CharacteristicName/>
             <Characteristicvalue/>
          </Characteristic>
          <MeasuringPoint>
             <MeasurementPosition/>
             <Characteristic/>
             <MeasurementPoint/>
             <MeasuringPointAsIs/>
             <MeasuringPointAsLeft/>
             <PCTCodeGroupMP/>
             <PCTCodeMP/>
          </MeasuringPoint>
       </TechObjChangeFLEQ>
    </ns0:TechObjChange>

    WSDL structure
    WSDL structure
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://schemas.xxxxxxxx">
       <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:p0="http://schemas.xxxxxxxxx" targetNamespace="http://schemas.xxxxxxxxxx">
             <xsd:element name="TechObjChange">
                <xsd:complexType>
                   <xsd:sequence>
                      <xsd:element name="TechObjChangeFLEQ">
                         <xsd:complexType>
                            <xsd:sequence>
                               <xsd:element name="FormType" type="xsd:string" minOccurs="0" />
                               <xsd:element name="FunctionalLocation" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Descoffunctionalloc" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Equipment" type="xsd:string" minOccurs="0" />
                               <xsd:element name="DescofEquipment" type="xsd:string" minOccurs="0" />
                               <xsd:element name="StartupDateofTechObj" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Manufacturer" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Manufacturermodelnumber" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Manufacturerpartnumber" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Manufacturerserialnumbe" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Countryofmanufacture" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Yearofconstruction" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Monthofconstruction" type="xsd:string" minOccurs="0" />
                               <xsd:element name="TypeofTechObject" type="xsd:string" minOccurs="0" />
                               <xsd:element name="PlannerGroup" type="xsd:string" minOccurs="0" />
                               <xsd:element name="MainWorkCenter" type="xsd:string" minOccurs="0" />
                               <xsd:element name="CatalogProfile" type="xsd:string" minOccurs="0" />
                               <xsd:element name="NameofUserchangingtheobject" type="xsd:string" minOccurs="0" />
                               <xsd:element name="Characteristic" minOccurs="0" maxOccurs="unbounded">
                                  <xsd:complexType>
                                     <xsd:sequence>
                                        <xsd:element name="CharacteristicName" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="Characteristicvalue" type="xsd:string" minOccurs="0" />
                                     </xsd:sequence>
                                  </xsd:complexType>
                               </xsd:element>
                               <xsd:element name="MeasuringPoint" minOccurs="0" maxOccurs="unbounded">
                                  <xsd:complexType>
                                     <xsd:sequence>
                                        <xsd:element name="MeasurementPosition" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="Characteristic" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="MeasurementPoint" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="MeasuringPointAsIs" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="MeasuringPointAsLeft" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="PCTCodeGroupMP" type="xsd:string" minOccurs="0" />
                                        <xsd:element name="PCTCodeMP" type="xsd:string" minOccurs="0" />
                                     </xsd:sequence>
                                  </xsd:complexType>
                               </xsd:element>
                            </xsd:sequence>
                         </xsd:complexType>
                      </xsd:element>
                   </xsd:sequence>
                </xsd:complexType>
             </xsd:element>
          </xsd:schema>
       </wsdl:types>
       <wsdl:message name="TechObjChange">
          <wsdl:part xmlns:p4="http://schemas.xxxxxxx" name="TechObjChange" element="p4:TechObjChange" />
       </wsdl:message>
    </wsdl:definitions>

  • Error in message mapping - Cannot produce target element

    As one step in my integration process, I am builing a very simple file to BPM integration (inbound MI async, outbound MI abstract).
    The source type and the target type are completely equal - I am only doing some modifications to some of the content.
    The type for both messages - source & target message - is an imported external definition (DTD), and hence no DT or MT are created.
    As a first step I am trying to fill the target message with the content from the source message (without any modifications to the content). However, when testing this in the message mapping area, I get an error message already when filling the first element, the 'root node'.
    The error message is as follows:
    Start of test
    Compilation of <MM name> successful
    Cannot produce target element <elementname>. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element <elementname>. . Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    End of test
    Any suggestions?
    Thanks,
    C

    Thanks,
    when creating the source message manually in the MM it worked - so nothing wrong with the mapping.
    I saved this file and compared with the "original file" - containing the content which I wanted to upload, and on which the xsd (external definition) was based - and there where some inconsistancies.
    I changed some values in the source XML which made it work, also when uploading the file from a drive.
    So, I will go back to the source system and try to get a better XML.
    Thanks for now!

  • Changing datatype, afterwards Message-Mapping cannot produce target element

    Hi,
    we use PI/700.
    I changed a working system by changing a datatype of an existing message (adding a new element). My interface mapping contains two mappings: an XSL-Mapping and afterwards a Message-Mapping.
    My interface mapping looks like this:
    Message-Type A ->
          XSL-Mapping ->
    Message-Type B ->
          Message-Mapping ->
    Message-Type B
    When I test each mapping alone everything works fine (with the new element I added).
    But if I test my interface mapping in IBD with both mappings together, I'll get an error:
    "Cannot produce target element /MT_EDM_OUTBOUND_LASTGANG_TO_SAP/LASTGANG/MASSEINHEIT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd".
    Is it possible that XI has problems in refreshing the XSDs?
    I tried this:
    (1) I changed my Message-Mapping and now all elements are mapped 1:1 -> no success!
    (2) Later I changed my Message-Mapping and build in "exists" with "if" to check whether the element "MASSEINHEIT" is generated by the XSL-Mapping -> It doesn't exists (??? - WHY? - when I test it, everything works fine)
    (2) Afterwards I changed my interface mapping and take only the XSL-Mapping (without the following Message-Mapping) -> the element "MASSEINHEIT" exists now!
    I'm totally confused!
    Any ideas?
    Regards
    Wolfgang Hummel

    Hi,
    If you have made structural changes to the data type..such as number of fields have decreased/increased..or some new fld altogether, then you have to activate the datatype..goto message mapping and then re-do the mapping...but if you have made "typo" changes like names have been changed, etc..then i think it should be alrite..i have sometimes made changes to my datatype, but after activating it, i had to redo the mapping..that was it!...the rest would fall into place:) No changes had to be made in the interface mapping..
    Regards,
    Sushumna

  • BPM Message Mapping: "Cannot produce target element /ns1:BAPI...."

    Hi,
    A scenario File - BPM - BAPI call was developed, as described in blog 'RFC scenario using BPM' cfr. link
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    The Mapping is as follows:
    MT_EDB_MATERIAL_REQ (1:1) --> BAPI_MATERIAL_EXISTENCE_CHECK (1:1)
    MATNR (1:1) -
    > MATERIAL (1:1)
    When executing the scenario, an error appears in the trace of SXMB_MONI, step 'Request Message Mapping'
    Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....
    I tried the following:
    1) import the XML-file into the testmapping: executed successfully
    File:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_EDB_MATERIAL_REQ xmlns:ns0="http://agfa.com/SD_EDB">
    <MATNR>15P6X</MATNR>
    </ns0:MT_EDB_MATERIAL_REQ>
    2) Removed the mapping on node level and left mapping only on element level (material): same error
    3) Activated the message mapping, interface mapping, determinations, etc again...:same error
    4) Removed the Interface Mapping and created it again: same error
    5) Compared the version ID of the Interface Mapping/message mapping in the Monitor trace with the version ID of the IR and saw that there was a difference.
    After the CPA full cache, SXI_CACHE full refresh and object refresh in the IB Administration, the differences remain, and also the error....
    Anybody an idea ?

    Hi
    >>>Cannot produce target element /ns1:BAPI_MATERIAL_EXISTENCECHECK. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd....
    The error clearly says that one of the occurrence value  for the target node mentioned is not coming from the source during mapping. The easiest way to solve the problem is as follows
    <b>
    First Execute the mapping as pointed out by "Raj" and the following steps.
    </b>
    1. Goto the Mapping Editor
    2. Double click on the target node that is causing the problem here BAPI_MATERIAL_EXISTENCECHECK.
    3.  Right click on the same node and select "DisplayQueue".
    4. View the Queue.
    5. YOu will find "Suppress" entries, which means a value is expected but no value is coming in.
    6.Go from right to left and check each node in the mapping and you will be able to trace where the suppress node comes from and take appropriate action
    regards
    krishna

  • Mapping exception in XI :Cannot produce target element

    Hi All,
    This is for RFC-to-JDBC Scenario.
    I import an RFC from SAP for Vendor Master ( BTE Event : 00001421). In that there are tables and structures.
    When i create a Vendor in transaction XK01, if i dont fill any of the values in structure WYT3, it gives an exception in mapping in XI when i test it in Message Mapping ( Cannot produce target element /ns1:MT_MDM_RECEIVER/STATEMENT1/NC_SUPPLIERMASTER/ACCESS/PARTNERTYPE. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd ).
    In the XML format in XI at sender side it doesn`t show the fields in the structure at all if it doesnt have any data.
    Thanks & Regards,
    Ruchi

    Hi Suraj,
    The sender xml is a structure(FWYT3) which might have data and might not , -
    - <xsd:complexType name="FWYT3">
    - <xsd:sequence>
    - <xsd:element name="PARVW" minOccurs="0">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    If this structure doesnt have data it`ll only show like this in sender xml,ni.e it doesnt show the fields in this structure (T_YWYT3).So this field parvw is mapped to partnertype in target.But when parvw doesnt have any data this field is not at all displayed in this structure WYT3.
    - </T_YWYT3>
    The target xml structure is whose occurence is '1'-
    - <xsd:element name="PARTNERTYPE" default="Supplier">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d27dbd80e40b11da8293ece80a9821f4</xsd:appinfo>
      </xsd:annotation>
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="40" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    Thanks & Regards,
    Ruchi

  • Mapping error: cannot produce target element

    Hello all,
    I am trying to test a mapping. i have 3 messages in my source and one Msg in my target. when i test execute it
    i get this msg:
    1) compilation of mapping successful
    2) cannot produce target elements/Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd.
    I am not sure what the error might be, can somebody please advice..
    Thanks in advance

    Hi Harika,
    how many Elements do u have In your Source Message Type(for example you have 3 elements and how u want to see these elements in your Target Message Type, define that much elements in your Target Message Type and Mappe those)
    1. usually people will go with one to one element mappaing, in such case define your souce and Target Message type Elements equal
    other wise you can do one Source having 3 elements and you want to see only one output from them then use Standard Function like "Contacte" that will add the 3 elements in one.
    if you are satisfied with this please provide points to me.
    Ashok

  • Reg: Runtime exception occurred during application mapping

    Dear SAP Gurus,
    This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
    I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
    While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
    *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Request Message Mapping*
      -->
    - <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/_HRS_LISTReferral_Response_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
      <SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    These are the steps I did while implementing..
    1. Importing the XSD's successfully
    2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
        RESPONSE Mappings.
    3. I already checked the link of WSDL once again...
    4. Even I found REsponse Interface once again...
    Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
    Regards:
    Amar Srinivas Eli
    Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AM

    Hello,
    I already checked all those queues and context fields////
    Based on my Observation I found
    1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
    2) ANother most Important that I found later doing these settings are....
        I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
        REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
        in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
        elements are  coming I mean passing from source or not...
    OBSERVATION::
    I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
    see for example ::
    CENTRE <----
    > DISCHARGE DATE..
    For going to CENTRE..here I found that in DEfiniition TAB...
    Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
    But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
    But I found that...
    Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
    This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
    In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
    Am I Correct ?
    If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
    Regards:
    Amar Srinivas Eli
    Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM

  • Runtime exception occurred during application mapping

    Hi All,
    Please find the error message which we are getting:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Request Message Mapping
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> 
      <SAP:Category>Application</SAP:Category> 
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
      <SAP:P1>com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~</SAP:P1> 
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2> 
      <SAP:P3>on: Cannot create target element /ns0:ProductCateg</SAP:P3> 
      <SAP:P4>oryHierarchyMassReplicationRequest/ProductCategor~</SAP:P4> 
      <SAP:AdditionalText /> 
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor~</SAP:Stack> 
      <SAP:Retry>M</SAP:Retry> 
      </SAP:Error>
    Please give your expert Advice on the same.
    Regards
    RK

    Dear Rableen,
    As Muniyappan and peter told about the mandatory field value is missing for the target element
    "/ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor", I am able to see other fields are also not getting input data.
    as below
    "Cannot create target element /ns0:ProductCateg"
    Request you to test with the payload in message mapping and activate the message mapping first and then edit your operation mapping and call the same message mapping in your operation mapping and activate all your objects.
    Thank you!
    Regards
    Hanumantha Rao

  • RuntimeException when executing application mapping program

    Dear Friends
    I am trying to send an Idoc from R3 system to an SCMTM system.
    I have imported the idoc, message mapping is preconfigured from SAP and requisite  configurations in ID have been completed.
    I am getting this error in test of Interface mapping (operation mapping).
    RuntimeException when executing application mapping program com/sap/xi/tf/_DESADVDELVRY03_to_ShipmentRequestRequest_; Details: com.sap.aii.mappingtool.tf7.IllegalInstanceException; Cannot create target element /ns0:ShipmentRequestRequest. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD.
    Please help.
    Thank You
    Warm Regards
    Arjun Ghose

    Hi,
    it seems that per your XSD the element "/ns0:ShipmentRequestRequest" needs to be created and filled with a value (occurance min 1). But appearently within your mapping you do not create or fill this element. So the validation of the XML against the XSD fails.
    Please check your mapping regarding the element "/ns0:ShipmentRequestRequest".
    Reagrds,
    Kai

Maybe you are looking for