on 03-06-2007 8:33 AM
Hi all,
i am going through the msgsplit using BPM....
and it is throughing error in Transformation step....
I have tested the Mapping also,it is fine...
Any suggestions...
thanx
krish..
HI,
Can you please explain how you are testing , what is is input msg, and xml is it valid,and UTF-8..
Regards
Chilla..
<i>Points rewarded if it is helpful..</i>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
this is my source XML message..
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:File_MT xmlns:ns1="urn:File_split">
<ecode>1</ecode>
<ename>11</ename>
<esal>111</esal>
</ns1:File_MT>
</ns0:Message1>
</ns0:Messages>
any suggestions....
thanx,
krish..
hi,
always message split you need to test as like below.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:File_MT xmlns:ns1="urn:File_split">
<ecode>1</ecode>
<ename>11</ename>
<esal>111</esal>
</ns0:File_MT>
Take the above payload and test directly..don't test above payload in message mapping test tab..
directly keep the above data in file then test the ur mapping..
Regards,
Venu.
Hi sree,
I am getting an error in Send step...(for msgsplit using BPM)..
I have gone through like this..in BPM
first i inserted the receive step to receive msg...
second i inserted the transformation step to split the msg.....
next fork with two branches ....
in each branch I inserted receiver determination and then send step......
but iam getting error in send step...
my Transformation step is working fine...
any suggestions..
Thanx,
krish..
HI,
See with SXMB_MONI by selecting the Process option and select the PE , see the each step by step , so that , you can have the correct error stage.
Also take the runtime code into mapping and test it , you can get the runtime error.
See the below pdf document , how to monitor the BPM..
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb4...
Regards
Chilla..
<i>Points rewarded if it is useful..</i>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
>>An empty container element was specified when sending.
This error means the send step you used contains no msg at runtime.
Do a F7 in your BPM in IR.
What is the result msg of your transformation step?
Use Michal's Blog for getting the result of transformation.
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Regards,
Jai Shankar
Hi,
The container element is empty means at that perticular container element which refers the Interface is not containing the message. Please check the before step ,whether that step is having the value or not, if yes and if it is transfermation the check the interface mapping and message mapping ..and also check the container elements are for source and target container elements ..
Please let me know the correct stage..
Regards
Chilla..
<i>Points rewarded if it is helpful..</i>
hi ,
my Transformation step is working fine...
problm comes in send step only...
what i did is in msgmapping i defined the msgtypes as (0..unbounded) for both the source and target messages... and then i mapped....
so, i think the prblm comes in (abstract interface-->msgtype) which is defined for Send step ....
what do u say?
thanx,
krish..
HI,
Why is there any need to do as 0..unbound..source and target..
Please first change the occurrences as 0..1/1.1 in the mapping , messages tab. same should be in IM.
Then try send the msg , test , the BPM..
Later plz let me know the error..
Regards
Chilla..
<i>Points rewarded if it is helpful..</i>
Hi chandra,
I have gone through the testing the mapping ...
but iam getting a warning message like...
19:23:41 Start of test
Compilation of Fspl_MM successful Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2074) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2722) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2074) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2722) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
any suggestions...still iam getting an error in Send step..
thanx..
krish..
Hi,
while testing msgsplit the message not like blow
(I assume that source has the two fileds one is BUKRS,LTEXT..in target will split these two fileds and it will store in two files..)
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:CompanyCode_MT xmlns:ns1="http://testt.com">
<BUKRS/>
<LTEXT/>
</ns1:CompanyCode_MT>
</ns0:Message1>
<ns0:Message2>
<ns2:input_MT xmlns:ns2="http://multimapping.com">
<Person>
<name/>
<age/>
</Person>
</ns2:input_MT>
</ns0:Message2>
</ns0:Messages>
while testing msgsplit the message shoule like blow
<ns0:CompanyCode_MT xmlns:ns0="http://testt.com">
<BUKRS/>
<LTEXT/>
</ns0:CompanyCode_MT>
when you test the msgsplit doesn't required..Messages as a header..please post your xml message..
Regards,
Venu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Krishna,
What is the error msg you are getting?
How do you chack the mapping in IR?
Use /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Regards,
JaiShankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.