Mapping Error: /ns0:Messages/ns0:Message1/ns1

Dear All,
I am using N:1 Mapping in BPM Collect pattern payload dependant.
System: SAP PI 7.0 SR2, SP 10.
Error is as follows:
"com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:Col_Receive_MT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start"
Input Payload:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
 <ns1:Col_Send_MT xmlns:ns1="http://RepeatCollectPattern">
 <KeyNo>1</KeyNo>
 <Name>ABC</Name>
 </ns1:Col_Send_MT>
 </ns0:Message1>
</ns0:Messages>
Can anybody will help me to solve this problem.?
-Gouri

I have followed Sample Collect pattern payload dependant pattern from SAPBASIS component.
In Interface Mapping,
Source Occourance: 0 to unbounded
Target occourance: 1
Mapping is 1: 1
Data Type:
Col_Send_MT      Complex Type
KeyNo                 Occourance 1
Name                  Occourance 1
In Message mapping,
Source is : 0 to unbounded
Target is: 1
-Gouri

Similar Messages

1: N multi mapping -----Message Mapping Error

Hi,
I am doing this scenario
Various multi-mappings and Optimizing their Implementation in Integration Processes (BPM) in XI.
In the design part of the mapping.
How can I perform the message mapping
Step 1. We are controlling occurrence of Output Piyush_msg_out_3 by mapping it with element2 with message context.
Step 2.
We are using u201CUseOneAsManyu201D under category node functions (SP14). It has three inputs ;
 1. Element which is going to be used for multiple times. In our case it is Element1 with message context.
 2. The element which is going to define how many times it will be replicated. Important thing, context should be same.
 3. Same as second input but with its own context in our case it is Element2.
For Step 1,
I have mapped piyush_msg_out_3 with Element2 (context is root)
For Step 2,
I have mapped
Element1(context root)----
|
Element2(context root)----
| useOneAsMany -
>Element1
Element2(context root)----
|
subelement------> subelement
I did not do root mapping.
when do the test I am getting the following error
Start of test
Compilation of MM_multimappingandoptimizing successful Cannot produce target element
/ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element
/ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
End of test
I thought error generated due to Parent Node condition fails, How do I map the Top node,
even though I mapped root------->root, I am getting the same error in the instance test
Please give me some suggestions
my message mapping is correct or do I need to change the context of the node or what should I have to do ?
thanks
manian

Hi Praveen,
I have checked the XSD tab of Source and Target message types. I can see the complete XSD.
Source Message Type XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
 <xsd:element name="piyush_msg_in_1" type="piyush_msg_in_1" />
 <xsd:complexType name="piyush_msg_in_1">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 f1fd03a0cddd11ddc1c4001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="root">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 99ffb9e0cd1a11ddc6b0001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Element1" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 99ffb9e1cd1a11dd8843001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Element2" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 99ffb9e2cd1a11dd8f7a001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="subelement" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 99ffb9e3cd1a11dd8ff2001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
Target Message Type XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
 <xsd:element name="piyush_msg_out_3" type="piyush_msg_out_3" />
 <xsd:complexType name="piyush_msg_out_3">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 058e2b60cdde11ddaffd001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="root">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7fb0d7d0cd1b11dd99ae001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="Element1" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7fb0d7d1cd1b11ddc07e001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Element2">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7fb0d7d2cd1b11dd9385001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="subelement" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7fb0d7d3cd1b11dda9d7001cc01cef0d
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
thanks
manian

BPM Collect Pattern: N:1 Mapping error in trnsformation step

Dear All,
I am using collect pattern Payload Dependant.
I have one source data type and one target data type. Mapping is one to one.
Data type contains 3 fields, Value Name and Surname.
In Loop I have used condition when Counter is equal to value stop the loop.
I have used Transformation step as I am using N:1 mapping.
I have used abastrct to abastract message mapping.
Source message is 0 to unbounded.
In interface mapping target message occourance is 1. But in mapping program target message occourance is 0 to unbounded.
When I am running my scenario, Third party to IP is working fine. But in IP i am getting error in transformation step.
"com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:Collect_Receiver_MT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start"
Can anybody will help me to solve this problem?
Warm Regards,
Gouri

Have a look
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Thanks

Mapping Error during BPM

Hi Gurus,
Im configuring a scenario to perform idoc collections using BPM.
When im testing the scenario, the SXMB_MONI transaction is telling me that there is a mapping error. I went thru the messages in SXMB_MONI but im unable to find out where the is the mapping error. In addition, I tried to test the scenario by sending 2 idocs and but its seems that the BPM is not triggered. It seems like somehow the erroneous BPM is stuck and im unable to trigger it anymore. I created a new BPM and tested it, it got triggered but is still giving me the mapping error.
Any advice?
Thanks in advance.

Hi,
I referred to the below blog but i do not have the option for Create New Transformation under the Transformation step.
Transactional Behavior in BPM.
But i managed to get some information on the mapping error
Cannot produce target element /ns0:Messages/ns0:Message1/PEXR2001/IDOC.
Im trying to collect all the PEXR2001 idocs, i.e. im going a N to 1 mapping. I've mapped the PERX2001 element of the source to element IDOC of the target. Is this correct? I've change the source from 0 to Unbounded.
In addition, now in SXMB_MONI, after i click on PE, im getting the following message
Message DD8878FE218C60F1948400170853600D held at process 000000002001 but not yet processed.
Is there any tcode i can goto to trigger this process?
Thanks!!!

XI-XML Error: Cannot Produce Target Element /ns0:Messages?

Experts,
Anybody ever seen this error?
Looks like XI is expecting a line of XML that says:
<ns0:messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
I making this assumption based on a valid test case for this mapping in XI. However, the real SAP outbound file incoming to XI is missing these lines.
Any direction is appreciated.
Thank-You
Are we having fun yet?

These are the missing lines of code I think?
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>

Mapping error when trying to test SOAP message from RWB

Hi all,
I am very new to XI and I will like to get some advise for testing an asynchronous interface:
SOAP -> XI -> File
To test the interface:
I logged into RWB - Component Monitoring - Adapter Engine - Test Message:
URL: http://ootspdbs02:50100/XISOAPAdapter/MessageServlet?channel=:BS_RON_TEST:SOAP_Sender_Test
Service: BS_RON_TEST
Interface: MI_TestWebServiceServer_UpdatePatAdmissInfo
Interface Namespace: urn:test:ron:fapl:TestWebServiceServer
QOS: EO
Payload (I generated this from XMLSpy with the WSDL generated in Integration Directory):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns0="urn:OOTSUpdatePatientAdmissionInfoWsd">
 <SOAP-ENV:Body>
 <m:MI_TestWebServiceServer_UpdatePatAdmissInfo xmlns:m="urn:test:ron:fapl:TestWebServiceServer">
 <ns0:Header>
 <ns0:encoding>String</ns0:encoding>
 <ns0:sendingApp>String</ns0:sendingApp>
 <ns0:sendingFac>String</ns0:sendingFac>
 <ns0:receivingApp>String</ns0:receivingApp>
 <ns0:receivingFac>String</ns0:receivingFac>
 <ns0:timeStamp>2001-12-17T09:30:47.0Z</ns0:timeStamp>
 <ns0:messageType>String</ns0:messageType>
 <ns0:messageId>String</ns0:messageId> <ns0:messageDesc>String</ns0:messageDesc>
 </ns0:Header>
 <ns0:patientID>String</ns0:patientID>
 <ns0:institutionID>String</ns0:institutionID>
 <ns0:caseNumber>String</ns0:caseNumber>
 <ns0:admissionDateTime>2001-12-17T09:30:47.0Z</ns0:admissionDateTime>
 <ns0:ward>String</ns0:ward>
 <ns0:bed>String</ns0:bed>
 <ns0:room>String</ns0:room>
 <ns0:movementCategory>String</ns0:movementCategory>
 <ns0:movementType>String</ns0:movementType>
 </m:MI_TestWebServiceServer_UpdatePatAdmissInfo>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The error I got in SXMB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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_TestWebServerService_UpdatePatA~</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_TestWebServerService_UpdatePatA: RuntimeException in Message-Mapping transformatio</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:MT_TestMsg/CaseNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:303) at .....
The message mapping consists of direct maps from each field in the source to the target (MT_TestMsg).
CaseNumber is the first field to be mapped.
In IR, I tested the interface and it works fine - no error in mapping.
I assume I cannot use the message generated in IR, because the SOAP envelope is required. (I tried anyway, and encountered the same error.)
Please advise how I can resolve this error.
Many thanks in advance.
Ron

Hi all,
I notice the tag and namespaces are changed when I generate the XML from the WSDL.
I am expecting something this format in IR:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:updatePatientAdmissionInfo xmlns:ns0="urn:OOTSUpdatePatientAdmissionInfoWsd">
 <ns0:Header>
 <ns0:encoding/>
 <ns0:sendingApp/>
 <ns0:sendingFac/>
 <ns0:receivingApp/>
 <ns0:receivingFac/>
 <ns0:timeStamp/>
 <ns0:messageType/>
 <ns0:messageId/>
 <ns0:messageDesc/>
 </ns0:Header>
 <ns0:patientID/>
 <ns0:institutionID/>
 <ns0:caseNumber/>
 <ns0:admissionDateTime/>
 <ns0:ward/>
 <ns0:bed/>
 <ns0:room/>
 <ns0:movementCategory/>
 <ns0:movementType/>
</ns0:updatePatientAdmissionInfo>
However, the message generated is :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns0="urn:OOTSUpdatePatientAdmissionInfoWsd">
<SOAP-ENV:Body>
<m:MI_TestWebServiceServer_UpdatePatAdmissInfo xmlns:m="urn:test:ron:fapl:TestWebServiceServer" >
<ns0:Header>
<ns0:encoding>String</ns0:encoding>
<ns0:sendingApp>String</ns0:sendingApp>
<ns0:sendingFac>String</ns0:sendingFac>
<ns0:receivingApp>String</ns0:receivingApp>
<ns0:receivingFac>String</ns0:receivingFac>
<ns0:timeStamp>2001-12-17T09:30:47.0Z</ns0:timeStamp>
<ns0:messageType>String</ns0:messageType>
<ns0:messageId>String</ns0:messageId> <ns0:messageDesc>String</ns0:messageDesc>
</ns0:Header>
<ns0:patientID>String</ns0:patientID>
<ns0:institutionID>String</ns0:institutionID>
<ns0:caseNumber>String</ns0:caseNumber>
<ns0:admissionDateTime>2001-12-17T09:30:47.0Z</ns0:admissionDateTime>
<ns0:ward>String</ns0:ward>
<ns0:bed>String</ns0:bed>
<ns0:room>String</ns0:room>
<ns0:movementCategory>String</ns0:movementCategory>
<ns0:movementType>String</ns0:movementType>
</m:MI_TestWebServiceServer_UpdatePatAdmissInfo>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The namespace and the root tag is changed!
I think this might be causing the problem.
But how do I resolve it?

Please help me to solve error: Split mapping created no messages

Hi Experts,
I am facing Split mapping created no messages when i run my scenario.
My Scenario is : Proxy to FILE.
I am triggering Proxy and based on one condition i am generating different Flat Files.
Now when i do this i am getting error :Split mapping created no messages in SXI_MONITOR.
When i check this in Message Mapping by taking data from SXI_MONI its working fine...
but when i trigger the data from RUNTIME WORKBENCH its throughing the error.
When i remove the NameSpaces <ns0:message>
and <ns0:messages1> its working fine.
How can i solve this issue.
Even though i removed Namespace in Message Type, i am getting the error.
I changed occurance of Target message to O..unbounded both in Message Mapping and Interface Mapping.
Its working fine in Message Mapping, problem occurs only when i run end-to-end scenario.
So please help me to solve this issue.

I think there might be mismatch between your name spaces.
may be this link might help you
Split mapping created no messages -Mluti Mapping
are you getting the same structure from your proxies whatever structure you have in your XI structure(sender) and NS should match.
but I dont have exp with proxies.
Sri

XSLT Mapping: Namespace for prefix 'ns0' has not been declared

Hello, I am working on a synchronous SOAP call and having some trouble with the response message. The web service has its own namespace and I am trying to convert this to my custom data type in PI. PI wants the message to be in format of having ns0 prefix and namespace like we have defined (http://foo for example).
I have an XSLT mapping (see below) which works fine with my test response payload (pulled from SXMB_MONI source) on this online XSLT test site:
http://www.freeformatter.com/xsl-transformer.html
However when I import this archive to PI and test with operation mapping it always says "Namespace for prefix 'ns0' has not been declared."
This is very confusing because when I test it online, I see both prefix and namespace declaration perfectly. Is there a way to see the results in the PI test tool? After this XSLT java error it doesn't give me the output even in Trace Level All mode.
Please advise on this issue or if you know an easier way (such as altering my datatype/message type to match the inbound SOAP message). I tried working with the 3rd party WSDL but the response message types show a different root level node than what PI is receiving so I gave up to make my own matching datatype. I just have to solve this last inbound namespace issue and should be finished.
FYI I have refreshed all PI caches and activated all objects.
Thanks for your ideas!
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ns0="http://foo"
<xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
<xsl:template match="@* | node()">
 <xsl:copy>
 <xsl:apply-templates select="@* | node()"/>
 </xsl:copy>
</xsl:template>
<xsl:template match="/*">
 <xsl:element name="ns0:{local-name()}">
 <xsl:apply-templates select="@* | node()" />
 </xsl:element>
</xsl:template>
<xsl:template match="/">
 <xsl:element name="{local-name()}">
 <xsl:apply-templates select="@* | node()" />
 </xsl:element>
</xsl:template>
</xsl:stylesheet>

Some additional info, here is an example payload which goes through the XSLT mapping perfectly, but in PI I get the error about missing ns0 declaration.
XML input:
<bar xmlns='http://irrelevantnamespace'
xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<foo/>
</bar>
XSLT mapped output using test tool and XSL above:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:bar xmlns:ns0="http://foo">
 <foo />
</ns0:bar>

Message Mapping error: RuntimeException in Message-Mapping transformation

Hi,
Being new to XI, I am struglling to sort out a basic mapping error. Appreciate if you could help out.
Its an File->XI->R/3 scenario.
My FCC successfully reads the File and creates an XML. However this XML is not transferred to the target XML structure which is exactly same except the root element name is different at top.
I tried various forum tips but I still am getting the error.
( When I Test the Message mapping in test mode..it seems fine, however if I copy the XML from SXMB_MONI, it then throws the above error)
I looked at the MM in text mode: below is the extract
/ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER=
/ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/SOURCE=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/SOURCE=
/ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/DESTINATION=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/DESTINATION=
/ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=
As seen the name space in both starts with nS0 and end of each line has '=' sign. Is that ok.
I have run out of options and dont know , whats the problem. Please help.
The target and Source XML structures are exactly same as shown below
MT_REQUEST MT_REQUEST_TO_SAP
 |__MSG_HEADER |__MSG_HEADER
 |__SOURCE |__SOURCE
 |__DESTINATION |__DESTINATION
 |__MESSAGE_ID |__MESSAGE_ID
And the SXMB_MONI Trace shows the following error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation:
Cannot produce target element /ns0:MT_REQUEST_TO_SAP.
Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at ..
Thanks
Shirin
Edited by: Shirin K on May 29, 2008 10:29 AM

Hi Prakasu,
As structure are exactly same, I have done 1:1 mapping. So all the fields in target structure are mapped, so no field has beeen left.
In this structure, I do not have any 1:n relation. So 1:1 mapping should be fine.
Apart from this could teher be any other reason.
Regards
Rajiv

1:2 Message Mapping WithOut BPM - Split mapping created no messages Error

Hi,
I am a new-bie to SAP PI and am trying out the following scenario without BPM.
Make multiple files based on Age received from input file.Input File contains Name,DOB and Output File contains Name, Age.
I want to create 2 files, one containing details of people with Age <21 and the other output file containing details of people with Age >= 21.
To acheive this,
In IR, I created 2 DT and 3 MT,1 MM with 2 Target MT,both having occurences 0..unbounded, 1 IM with 2 Target MI,both having occurences 0..unbounded
And in ID, 1 Sender Agreement, 2 Receiver Agreement, 1 Receiver Determination, 1 Interface Determination using Enhanced Interface Determination.
When i run this scenario, I am getting the following error "Split mapping created no messages"
Please let me know how can I resolve it.

Oops, I did not know that.
Thanks for that information. uhuuuuuuuuuuu, atlast the message is processed and I am seeing output files created.
But, there is still one problem. My output files are created with just the following content
<?xml version="1.0" encoding="utf-8" ?>
<ns1:MT_2OP_File_Out xmlns:ns1="http://POC_Sec1_1IP2OP2" />
In MM, I see the output message as follows:
Message
 Message1
 MT_2OP_File_Out
 Employee
 Name
 Age
 Message2
 MT_2OP_File_Out1
 Employee1
 Name
 Age
The mapping done:
MT_2OP_File_Out and MT_2OP_File_Out with the Message Type element on source end.
Employee and Employee1 are mapped as
 Age -> removeContext -> SplitByValue[Each Value] < 21, Map Employee
 Age -> removeContext -> SplitByValue[Each Value] >= 21, Map Employee1 resp
The fields are straight maps.
Is there any basic mapping error that I am making. Please help.

Catch mapping error message in BPM Exception branch

Hi dudes,
Does anyone know how to catch the mapping runtime error message into a BPM exception branch? I know how to create an exception branch and how to trigger it, but I wonder whether it's possible to pass the mapping error message as shown in SXI_MONITOR (i.e. 'Cannot create target element XXXXX. Values missing in queue context').
Otherwise, everytime my BPM fails I will have to take the payload and run the mapping test in order to find out the reason of the error.
Many thanks in advance!
Paco

Thanks,
My problem is not about handling exception in BPM, but getting the mapping error description and then passing it to the exception branch.
I can see in the workflow log that this info is contained into the Exception container EXCEPTIONS[2] / T100MSG:
Message Class: SAI_MAPPING
Message Number: 217
Message Type: E
Message Variable: com/sap/xi/tf/_<MM name>
Message Variable: com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti
Message Variable: on: Cannot create target element /ns1:<path/field>.Message Variable: Values~
The text in bold is the one I am interested in to be get and mapped into the exception branch.

Error in Message-Mapping transformation

I'm getting an error while processing the data from JDBC to SAP through IDOC's.
During the application mapping com/sap/xi/tf/_MM_HRMD_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
while testing the mapping in IR (message mapping) it got succesfull.
while testing the mapping in ID (Test configaration) with inbound payload we are getting the below error.
interface Mapping
... (173 lines)
Please provide the solution for this...

Hello,
Check out the trace thorougly in MONI as at which node/field the error is occuring.
W.r.t ID testing,kindly check your interface determination(sender,receiver parameters and also the inbound interface etc)
Regards
Madhu

BPM Mapping error in SXI_MONITOR Message scheduled on outbound side.

When I try to process this message i get an error.
Message scheduled on outbound side.
I am using a BPM.
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Using EOIO in the send step Queue Name: cases
If I remove MI_TRANS2_BPM the message reaches the bpm, but with both transformation in the BPM the message gets an error in the queue where I get a green flag 'Message Scheduled on the outbound side"
This BPM was working on Friday but hasn't worked since. There have been no changes to the my development XI environment.
Some things that i have tried: Clearing the Queues (smq2), Redoing the entire scenario, clearing cpa cache.
Please help.
Thanks
Chirag

Hi,
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Any specific need to have the above design pattern....you can also try:
MI_Receive_BPM -> MI_TRANS_BPM -> MI_TARGET
You can use the message that you initially receive and apply all the necessary transformation on it and the map it to the target structure....
As you mentioned that if you remove MI_TRANS2_BPM your message is executed successfully...it means that the BPM transformation 2 is waiting for some event / Message....
If you need to go by the same design then you can follow the below steps to resolve the problem:
1) Check the return code of BPM in SXI_CACHE...it should be 0
2) Check for any errored instance of your BPM in SWWL (as mentioned in above posts)
3) Open the corresponding Queue and see for the messages stuck in the Queue....your Queue may be blocked....your BPM will be using a particular Queue and if any message is stuck in the Queue then all the messages that follow will get stuck in the Queue....
Now if it is only your BPM that is using this particular Queue then Delete the Queue (applicable to development environment....do not try in QA or Production environment)
4) In SXMB_MONI click on "PE" and open the Graphic Flow to see where actually your BPM has failed (possible only if the message has entered the BPM.
Regards,
Abhishek.

Error in Message Mapping and Workflow

Hi everyone.
I have a BPM that works fine. We've discovered that doesn't work because of big files. We've changed some parameters that SAP told us but still doesn't work.
I'm trying to send a 60mb file from XI to R3 via RFC. I haven't reach that step because in the step that make the mapping between the message and the RFC, i get this error :
Work item 000000133919: Impossible to execute object 'CL_SWF_XI_MSG_BROKER', method 'CALL_TRANSFORMATION'.
Any solution for that?
I'm implementing sap Note 718735.
Regards.

Hi Krishna.
I've read that note but when i go to the method to change what the note says, i realise that no change is needed because it's already done by SAP.
I don't know if i understood the note, but if i am right, i don't have to delete anything and i only had to add the line 'CLEAR: sendfault.' after CLEAR: messages_out[]', right?
If this is ok, i don't know how to solve this problem.
Regards

Error in Message Mapping "Target message IDOC: ORDRSP.ORDERS02 does not exi

Hi,
I have joined newly to the team.
When I tried to open one message mapping it throwinf follwing error...
"Target message IDOC: ORDRSP.ORDERS02 does not exist in software component version ID: 44423362454456485465..
Check whether the software component version ID: 44423362454456485465 is in Enterprise Service Repository. Import this version if necessary"
Is there any impact because of which in the message flow?
In my case some of the messages are failing with mapping error "runtime exception occured during application mapping com/sap/xi/tf/_SUS2MMOrderResponse_; java.lang.NullPointerException: while trying to invoke the method java.util.Map.get(java.lang.Object) of an object loaded from field com.sap.aii.map`"
And some of the messages are processed sucessfully and they also using the same mapping program 'SUS2MMOrderResponse'.
Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
Regards
Baskaran K

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

Mapping Error: /ns0:Messages/ns0:Message1/ns1

Similar Messages

Maybe you are looking for