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
Similar Messages
-
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> -
EXCEPTION_DURING_EXECUTE and Cannot create target element ?
hi experts
i got error in jdbc to idoc scenario (PI 7.1 sp7)
<?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="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_mm_avabtis_to_ps_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ZENTITY. Values</SAP:P3>
<SAP:P4>missing in queue context. Target XSD requires a v~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_mm_avabtis_to_ps_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ZENTITY. Valuesmissing in queue context. Target XSD requires a v~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
jdbc struc
jdbcdt->
row -->
comp
plant
dept
entype
entity
endesc
glcode
Idoc struc
zentity root--> (mapped to jdbcdt)
idoc
begin -
>( constant value 1)
edi_dc40---->(Disabled Total segment)
z1entity -
>(Mapped to Row)
segment -
>(Constant value 1)
comp
plant
dept
entype
entity
endesc
glcode
please help me out.Hi
-->In your IDOC do you have any other segments which are mandatory?Please do recheck your IDOC structure and check for the mandatory segments and assgin them with the constant value 1.
-->The error seems to be the mandatory segment value is not mapped.
Thanks -
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 PII 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
RKNHi
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(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.
-
How did i solve "Cannot create target element" but still having problems.
Hi Experts,
I solved my problem of "Cannot create target element" by removing of the data type structure the following fields :
DT_AS400_1 -> Complex Type
Payroll 1..1 (Should i put 0..0?)
-> Row 0..Unbounded And then Fields to be passed.
I can't figure how pi can't detect the fields, i use them pretty often.
Any Suggestions,
Thanks for your help,
Regards,
Steve.Hi Steve,
Check if input message, has the field that is producing the output.
Therefore, if you don't have any input to fill the structure root, you can fill it with an empty constant.
Best regards,
Pedro M. D. Pereira
Edited by: Pedro Pereira on Jun 10, 2010 1:26 AM -
Mapping Mapwthdefault at tiem level -Values Missing in Queue context
Here is the logic
If (E1EDP19-IDTNR_EXTR is not empty and (E1EDP19-QULF)=001
map IDT_EXTR to target Buyerpart
else
if E1EDP19-IDTNR is empty and E1EDP19-QULF=002
if E1EDP01-MENEE IS NOT EQAUL TO AU
map const (SEE_DESCRIPTION) to target
All context set to EDP01
Target is mandatroy field
1) data : If the 1st item level has the value IDTNR_EXTR and 2nd item level is not .
In the else condition also QUALF is not matching to 002 so not getting the value for else condition in second item level .
So getting the error ItemDetail[2]/ns0:BuyerPartNumber. Values missing in queue context
How can we add mapwithdefault to not to fail for mandatory field
2 data I added mapwithdefault befoe else it worked for this data but failed for other test with 3 line items IDTNR_EXTR values. 2nd line item was getting in target which is not
Thanks for your helpHere is udf i tried but not working as expected
String output = new String();
for (int i=0; i< qualf.length;i++)
if(qualf[i].equals("001")&&(idntex[i]!=("")))
output = idntex[i];
else
if((qualf[i].equals("002"))&&(idtnr[i]==(""))&&(manee[i]!=("AU")))
output = ("Notes") ;
result.addValue(output);
if item has only one value of idtnext and 2nd line item also it is displaying same value it should be blank
Thanks for your help -
ERROR Cannot create target (optional) element - SUPPRESS value
HI, XI/PI experts!
I am new in PI 7.1 (Ehp1 SP 7), previously work with PI 7.0.
I faced with problem of mapping optional target element, when queue has just SUPPRESS element. I expected to suppressing mapping of the target element, but mapping program raise exception:
Cannot create target element
/ns0:Messages/ns0:Message1/MT_DiadocMethods/ConnectInfo/TraceInfo/Folder.
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
XSD Folder declaration:
<xsd:element name="Folder" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
u043Au0430u0442u0430u043Bu043Eu0433 u0434u043Bu044F u0442u0440u0430u0441u0438u0440u043Eu0432u043Au0438 u0447u0435u0440u0435u0437 u0444u0430u0439u043Bu044B
</xsd:documentation>
</xsd:annotation>
</xsd:element>
[http://imagepost.ru/?v=queue_for_optional_element_fol.PNG|http://imagepost.ru/?v=queue_for_optional_element_fol.PNG]
If put mapWithDeffault with value "hello" between ifWithoutElse and target element Folder, then exceptions not raised, but target element also not created
15:53:03 Start of test
Compilation of MM_Diadoc_DownloadNewEvents__DiadocMethods_q successful
Document start
Start tag [ns0:Messages]
Add raw attribute [ xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"]
Start tag [ns0:Message1]
Start tag [MT_DiadocMethods]
Start tag [ConnectInfo]
Start tag [trace_level]
Put value [4]
Close tag [trace_level]
Start tag [TraceInfo]
Start tag [TraceViaMail]
Close tag [TraceViaMail]
Close tag [TraceInfo]
Close tag [ConnectInfo]
Close tag [MT_DiadocMethods]
Close tag [ns0:Message1]
Close tag [ns0:Messages]
Document end
Execution of mapping on server took 1160 milliseconds Executed successfully
15:53:05 End of test
<Display Queue> show that queue after mapWithDeffault has <null> value:
[http://imagepost.ru/?v=mapwithdeffault.PNG|http://imagepost.ru/?v=mapwithdeffault.PNG]
Inserting mapWithDeffault is workaround for this situation, but I am interesting to understand principle of SUPPRESS in 7.1
Thanks in advance and sorry for my English !Hi,
To understand the Suppress you can refer the below blog
/people/stefan.grube/blog/2006/01/09/the-use-of-suppress-in-the-xi-30-graphical-mapping-tool -
Unable to create Target Element error
Hi Experts,
I have Source and taget messages as below:
Target Structure
MT_Table----
1:1
Row--
0..unbound
-Field1--
1.1
-Field2--
1.1
-Field3--
1.1
-Field4--
1.1
Source is IDOC
ZMaterial----
1.1
IDOC--
1.1
-Begin--
Req
---EDIDC40
Segement---1.1
Table----
1.1
-E1MARAM-1.999
-SEGMENNT--0..999
Field1-------0..1
Field2-------0..1
I will have multiple IDOCs where I need to generate Multiple rows in a file:
I am getting an error as below:
Start of test
Cannot create target element /ns0:MT_Table/Row[2]/Field1. 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
I have a condition if SEGMENT-Field1 equals A then substring of SEGMENT-Field2 (first 16 characters).
Many Thanks
RajeevI see the Source Message is as below:
<?xml version="1.0" encoding="UTF-8" ?>
<ZMaterial>
+<IDOC BEGIN = "1">
+<IDOC BEGIN = "1">
+<IDOC BEGIN = "1">
</ZMaterial>
Dont know how to get multiple rows in a file with multiple IDOCs.
Any Light please?
Thanks
Rajeev -
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,
CThanks,
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! -
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,
RuchiHi 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 -
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 & RegardsHi 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. -
ERROR IDoc2File "Cannot produce target element"
Hi,
well i am sending an IDoc as i did some times before via XI to the client.
Funny thing is that now it's the first time the MM is not able to handle empty fields from sender.
I configured the target DT and the field 'co' from IDoc for occurrence with 0..1 but when i test the MM with the given XML-Structure from SXMB_MONI i am getting following ERROR:
<b>Cannot produce target element /ns0:MT_Certificate/recordType2A/co. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</b>
This field is the first one which is empty in the sent IDoc - but i have no clue why the is a problem because i did this some times before and it all works and i havn't done anything wrong - i hope.
So do u have an idea?!
br, JensJese,
I explained it above, but let me try to put it better.
MAPWITHDEFAULT is used to check if a the source field exists. if it exists then it maps the source with the field else it maps the default value to the target field.
When a field is not populated by an idoc, the field is not a part of your XML strucuture itself. In your mapping, the field for which you have used MAPWITHDEFAULT I guess has a occurence of 1..1 and so, as the source field does not come in the Idoc, the mapping fails and this is now handled with mapwithdefault.
Hope this helps,
Regards
Bhavesh
Maybe you are looking for
-
List View in the event browser stopped working.
Recently I was using Final Cut pro X when it crashed, when I re-opened the application I found that List View in my event browser no longer displayed any content, filmstrip view appears to work but I had gotten quite fond of list view. Is there a wa
-
My macbook works well while connected to the charger, but using the battery it gets really slow
My macbook pro 2011 yosemite 10.10.1, (2,3 GHz Intel Core i5 / 4 GB 1333 MHz DDR3 / Intel HD Graphics 3000 384 MB) recently started to present a problem that when using only the battery, it gets really slow, but connected to the charger, it operates
-
Synchronize folder not working in Lightroom 5.7
When I synchronize a folder in Lightroom 5.7 it shows 'Task completed', but nothing happens and Lightroom does not respond anymore. Any advice? Running on Windows 8.1..
-
Hi, When I do JOptionPane.showOptionDialog(...); Can anyone tell me how to make the ok and cancel buttons appear at the bottom right of the dialog instead of the bottom center. Thanks, Jim
-
Hi, I believe there is a limit on the number of rows a pivot table will support. Does anyone know what that limit is? Thanks Minesh