Root element added in existing mapping PI 7.1

Hi Experts,
I got existing mapping with around 500 fields, the source structure is external defination, they added the root element to existing xsd, when i try to import the external definition into the mapping it is giving following error.
Function model undefined (FUNCMODEL_UNDEF)
MESSAGE ID: com.sap.aii.mappingtool.mf.mapping.rb_Mapping.FUNCMODEL_UNDEF
Parameter AMappingTool has the invalid value null
Is anyone faced this problem before, i am working on PI 7.1, but when i create the new mapping then i can successfully imported the external definition into mapping, but how can i get my existing mapping into new mapping??
Thanks

> Is anyone faced this problem before, i am working on PI 7.1,
Yes, indeed. Report this to SAP.

Similar Messages

Hierarchy could not be included; root element does not exist ?

hi,
I try to change hierachie for the released WBS with function CN2W_WBS_HIERARCHI_CHANGE_STRU, but I got an error like : "Hierarchy could not be included; root element does not exist" But this does not happen when we change the WBS hierachie in CJ20N, Could you please help me how to change hierachie for the released WBS using the function ? And Which function I can use ?
Thanks in advance

you are using correct function module. Just check the values in Up and down columns .

Multiple Root elements in the XSD Schema

Hi Dear MDM gurus,
I have manually created an XSD Schema and I can import it in the Syndicator without any problem.
I have 3 different Root elements in the schema that I want to use and map to the corresponding table of this type.
In my Syndicator screen in the Rood dropdown box I can see all three of the Root elements that I have in the schema.
If I select the first Root element - everything goes fine and I can do my mapping, save the map, etc.
The problem is that if I select the second or third root element to do the mapping for them, the syndicator does not show the structure in the Item Mapping after that.
I tried moving the Second root element of the schema and make it first and it works with it, but then the other two are not appearing and I have the same issue.
Does MDM support only one Root element in the Schema? If that's the case, why does it show all three of them in the dropdown?
Here is an example:
1. If I have them in this order in my XSD
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
I can only see the structure when I select the "ManufacturerGroupNumber".
2. If I have them in the Schema in this order
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
I can only see the structure when I select the first one again "SupplierLocationNumber" and I can only do the mapping for it.
Any help would be appreciated.
Thanks in advance,
Boris

Hello Satish,
Thank you for your quick response.
I read some of the architectural approaches and XML specifications and depending on your design, you may have only one Root element or in rare cases Several Root elements. In my case, I was advised by our PI experts to use Multiple Root elements and this gives me the following:
Advantages:
u2022 The reusability of the schema definition is available for all types and all elements defined in the global namespace.
Disadvantages:
u2022 Since there are many global elements, there are many valid XML documents.
I initially had the schema as you suggested, but they didn't like it in PI and advised me to change it with having multiple roots.
What I'm trying to figure out is if there is a bug in MDM that does not allow to use the rest of the root elements, so I can open an OSS message.
Thanks,
Boris

Reg "Parsing an empty source. Root element expected!"

Hi techies,
This is in regard of error generated while testing my configuration in configuration window.
Till yesterday the senario is working for JDBC to JDBC.
It is giving this error.
"Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected! at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: java.io.IOException: Parsing an empty source. Root element expected!"
My mapping and interface mapping is working fine when I tested them in Design window.
Please suggest me how to go.
Thanks In advance.
Regards,
Kiran

Hi Hareen,
Thanks for your reply.
While Testing the scenario both at message mapping and interface mapping tests are working fine.
even XML conversion is also fine at design end.
only while testing in config window it is giving the error.
Sender Interface mapping Test
<?xml version="1.0" encoding="UTF-8"?>
<ns0:mt_sender xmlns:ns0="http://jdbc_2_jdbc">
   <row>
      <NAME>Kiran</NAME>
      <ID>123456</ID>
      <ADDRESS>address</ADDRESS>
      <FLAG/>
   </row>
</ns0:mt_sender>
Reciver Interface mapping after test
<?xml version="1.0" encoding="UTF-8"?>
<ns0:mt_receiver xmlns:ns0="http://jdbc_2_jdbc"><Statement><dbTableName action="INSERT"><table>LIBRARY</table><access><LIBID>123456</LIBID><LIBNAME>Kiran</LIBNAME><LIBADDRESS>address</LIBADDRESS></access></dbTableName></Statement></ns0:mt_receiver>
Upto this level it is working fine. Is there anything I have to refresh to carry out my editing to configuration window.
Thanks in advance.
Regards,
Kiran

Reg RFC to JDBC "Parsing an empty source. Root element expected!"

Hi techies,
This in regard of RFC to JDBC.
in integration test iam getting the error.
"com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_mm_mapping_: Parsing an empty source. Root element expected!"
My Mapping and interface mapping tests are working fine, while testing the configuration Iam getting this error.
My interface Mapping test result is as mentioned below
Sender Interface (RFC Sender)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ZTEST_PI_ZHRT002 xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
   <ZHRT002>
      <item>
         <MANDT/>
         <PERNR>1234</PERNR>
         <PERID>kiran</PERID>
         <SHOPN>test</SHOPN>
      </item>
   </ZHRT002>
</ns0:ZTEST_PI_ZHRT002>
Reciver Interface after test
<?xml version="1.0" encoding="UTF-8"?>
<ns1:mt_receiver xmlns:ns1="urn:sap-com:RFC2JDBC"><Statement><dbTableName action="INSERT"><table>ZHRT002</table><access><PERNR>1234</PERNR><PERID>kiran</PERID><SHOPN>test</SHOPN><access></dbTableName></Statement></ns1:mt_receiver>
My message Mapping is as mentioned below
ZTEST_PI_ZHRT002 is my BAPI which is mapped to mt_receiver.
ZHRT002 it my table which is mapped to Statement of reciver
item of sender is floating ( not mapped to any reciver node)
subsequently feilds are mapped.
Reciver action is atribute (required) calling INSERT
table is "ZHRT002" (constant) (1...1)
This is my scenario.
Thanks in advance,
Regards,
Kiran

This is RFC to JDBC. Is it Synchronous or Asynchronous?
Some tips:
Create JDBC target data structure something similar to this
<StatementName>
<dbTableName action=u201DINSERTu201D>
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2</col2>
</access>
</dbTableName>
</StatementName>
Map Table name and action using Constant.
>>item of sender is floating ( not mapped to any reciver node)
What is that? you have to map source item node fields to target access fields.
Please go through the below sap link . This might be very helpful.
http://help.sap.com/saphelp_nw70/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

Getting Error in java mapping: Parsing empty source. Root element expected!

Hi Experts,
   I am using java mapping for schema validation of input message. I have followed all the standard procedures and implemented the java class in the interface mapping.
My interface mapping is like this:
OrderData --->Java Class ---SchemaValidate
                     Mesg Map ---OrderData_to_BAP --->BAPI Msg
So first I want to validate the schema of the input message. If the input message is invalid then XI should throw an exception. Then I use the actual message mapping to map the input order data to the BAPI input parameters.
In the java code I am using xerces parser.
The java code works fine when I run it as a standalone application.
The interface mapping also works fine if I don't include the java mapping. Ofcourse schema validation does not happen.
But when I test the interface mapping by including the java mapping then I am getting the error:
Call method execute of the application Java mapping SchemaValidate
Java mapping SchemaValidate completed. (execute() of SchemaValidate
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected!
What am I doing wrong? Why it is not getting the root element?
My Java code is as follows:
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.*;
import java.util.Map;
import javax.xml.parsers.*;
import org.xml.sax.helpers.*;
import org.xml.sax.*;
import org.apache.xerces.jaxp.*;
Sample mapper for SAP-XI
@author Gopal
public class SchemaValidate implements StreamTransformation {
    //Constants when using XML Schema for SAX parsing.
     static final String JAXP_SCHEMA_LANGUAGE =
     "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
     static final String W3C_XML_SCHEMA =
     "http://www.w3.org/2001/XMLSchema";
     static final String JAXP_SCHEMA_SOURCE =
     "http://java.sun.com/xml/jaxp/properties/schemaSource";
Injection of mapping parameters
from integration engine
@param map Map with configuration data
    public void setParameter(Map map) {
Mapping implementation
@param inputStream Input data from integration engine
@param outputStream Output data to integration engine
    public void execute(InputStream inputStream,
                        OutputStream outputStream)
      throws StreamTransformationException {
        try {
              // obtain an object of class javax.xml.parsers.SAXParser,
              SAXParserFactory spf = SAXParserFactoryImpl.newInstance();
              spf.setNamespaceAware(true);
              spf.setValidating(true);
              SAXParser sp = spf.newSAXParser();
              // setup the schema file
              sp.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
              sp.setProperty(JAXP_SCHEMA_SOURCE, new File("IOReqMsgSchema.xsd"));
              //parse the input xml using the given schema
              sp.parse(inputStream, new ParseErrorHandler());
        catch(SAXException se) {
          se.printStackTrace();
        catch ( Exception e ) {
          throw new StreamTransformationException( e.getMessage() );
My input message is :
<?xml version="1.0" encoding="UTF-8"?>
<ns0:OrderCreate_request xmlns:ns0="mynamespace">
   <ORDER>HTEST1234567</ORDER>
   <ORDER_TYPE>z001</ORDER_TYPE>
   <ORDER_NAME>Test Order</ORDER_NAME>
   <CO_AREA>INTC</CO_AREA>
   <CCTR_POSTED>1234567890888888888</CCTR_POSTED>
   <CURRENCY>USD</CURRENCY>
   <PERSON_RESP>12345679</PERSON_RESP>
</ns0:OrderCreate_request>
Kindly help! please this is urgent!!!!!!
Thanks
Gopal
Edited by: gopalkrishna baliga on Feb 28, 2008 9:34 AM

Hi Stefan,
   I did the code changes to return output stream and the java code works perfectly in standalone mode in my PC.
   But when I use the same in the Java mapping with XI then It throws an error "Getting Error in java mapping: Parsing empty source. Root element expected!".
My XI J2EE server has JDK1.4.3.11.
Is there any limitation of using SAX parser in XI? If Yes, then which parser should be used for schema validation in XI?
I have included the XSD file for schema validation along with class files in the .jar file. This jar file is then imported in XI repository. Is the XI engine not able to read the XSD file?
Do I have to handle reading XSD file differently? Any suggession how?
Is this parser error due to some security access?
Kindly help me! I have been struggling with this problem since 2 weeks. I will be greatfull to you if you can help me.
Thanks
Gopal

Adding Root Element

Hi
I have an existing structure in XML
<article>
<text>
</text>
</article>
Here the element article is holding the content and is associated with the text frame.
I would like to modify the structure to
<Root>
<article>
<text>
</text>
</article>
</Root>
But still the article element should only be holding the content and shud be associated with text frame is it possible to do that either manually or through scripting in ID CS3
Thanks

Hi Priya,
assume you have an Xml File imported
<?xml version="1.0" encoding="UTF-8"?>
<article>
<text>myText</text>
</article>
and you have dragged <article> from the InDesign xml structure onto a textframe on the layout.
Now, run this script to apply the Root-Tag to your article.
myDoc = app.activeDocument;
myArticleXmlElement = myDoc.xmlElements.item(0);
myArticleXmlTag = myDoc.xmlTags.item("article");
myTextXmlElement = myArticleXmlElement.xmlElements.item("text");
try{
myRootXmlTag = myDoc.xmlTags.add("Root");
catch(e){
myRootXmlTag = myDoc.xmlTags.item("Root");
myArticleXmlElement.markupTag = myRootXmlTag;
myNewArticleXmlElement = myDoc.xmlElements.item(0).xmlElements.add(myArticleXmlTag);
myTextXmlElement.move(LocationOptions.AT_BEGINNING, myNewArticleXmlElement);
Hope this is what you were looking for. You can do all of this manuallly as well. In fact this is how I began before writing the script.
Just for curiosity, what is that for ? And can you not just import an Xml that already contains the root element ?
Stefan

Dynamic Programming: Adding Transparent Container to Root Element

Hi,
I simply am adding a Transparent Container to the Root Element dynamically and I am getting the error "The ASSERT condition was violated".
Does anyone have an idea what the problem is.
Below is my VERY MUCH simplified code:
method WDDOMODIFYVIEW .
DATA:
    LR_ROOT TYPE REF TO CL_WD_UIELEMENT_CONTAINER,
    LR_TCONTAINER TYPE REF TO CL_WD_TRANSPARENT_CONTAINER,
    LR_FLOW_DATA TYPE REF TO CL_WD_FLOW_DATA.
LR_ROOT ?= VIEW->GET_ROOT_ELEMENT( ).
LR_TCONTAINER = CL_WD_TRANSPARENT_CONTAINER=>NEW_TRANSPARENT_CONTAINER(
    id = 'TCONTAINER_01' ).
LR_FLOW_DATA = CL_WD_FLOW_DATA=>NEW_FLOW_DATA( LR_TCONTAINER ).
LR_TCONTAINER->SET_LAYOUT_DATA( LR_FLOW_DATA ).
LR_ROOT->ADD_CHILD( LR_TCONTAINER ).
endmethod.

Found the answer on this link:
Creating dynamic tranparent container

Adding namespace prefix to the XMLa root element

I am facing a problem in our application. I am assigning an XML content to a XSD variable. While assignment operation is performed the prefix of the XML root element alone is getting replaced with default namespace, though the source XML has the prefix. Please let me know if any patch or workaround is available to address this issue.
Thanks!

Hi All,
we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

Root element required error in syndication

Hi,
We have added few new fields into the main table. Now accordingly we need to update the Oubound map to include these new fields. I have created a new XSD file having these new fields. But when I try to use this in syndicator to update, it throws me an error back saying "Root element required". I checked in SDN but couldnt find enough clues.
Any pointers will be highly appreciated.
Regards,
Ponraj M

Hello,
There are few possible root causes to this error appearing in MDM Syndicator:
1. This error indicates that the XSD is not valid as there is no declaration of the root element.
If you try to validate this XSD in XMLspy you will receive a similar error.
2. The XSD declares the root element but it does not appear in the XML.
If you validate the XML against the XSD in XMLspy you will receive a similar error.
3. An illegal character in the XSD root element declaration makes it impossible for Syndicator to detect it.
Please check these possible causes.
Best regards,
Hedda Cohen.

Root element is missing - Response from a WCF service - WCF-Custom adapter

hi BizTalk experts,
In the production environment, as soon as the response is getting subscribed by the orchestration, the orchestration instance is getting suspended and the error that shows up in console is
"Root element is missing".
I have checked the actual response message in the console it is a well formed xml. This is happening only for a few responses from the WCF services. A majority of them are getting processed successfully. I have tried getting the parsing the response in a
pipeline (using custom pipeline component, the production one uses xml receive) and pass it to the orchestration, but it fails giving the same error.
Thanks in advance.

Do you have any mapping done on the response message from the WCF service . ?
If so Better to copy the suspended message coming from the WCF service and validate against the custom response Schema you have created.
Note : You can try running fiddler tool to check the response from from the web service incase of failure.
Also try logging the message in the event viewer or any debug tool.
Thanks
Abhishek

Several namespaces in root element

Hi,
I'm using JDOM and I would like to create an XML document that starts like this:
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"
xmlns:ccts="urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0"
xmlns:cur="urn:oasis:names:specification:ubl:schema:xsd:CurrencyCode-1.0"
xmlns:sdt="urn:oasis:names:specification:ubl:schema:xsd:SpecializedDatatypes-1.0"
xmlns:udt="urn:oasis:names:specification:ubl:schema:xsd:UnspecializedDatatypes-1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd">
</Invoice>
Is there a way to add several namespaces to the root element?? I have tried hard, but nothing works...
Thank you very much for your help,
Susana

OK, it's like dvohra09 said. I had an old copy of jdom.jar and the method addNamespaceDeclaration() didn't exist.
So, here you have the code to generate the beginning of my file, if ever it's useful to someone as I found it a little bit complicated to find out:
For this:
<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd">
     <ID>serie1_04/00011</ID>
     <cbc:CopyIndicator>false</cbc:CopyIndicator>
</Invoice>
The code is:
Element rootElement = new Element("Invoice", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0");
rootElement.addNamespaceDeclaration(Namespace.getNamespace("cbc", "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"));("schemaLocation", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd", Namespace.getNamespace("xsi", "http://www.w3.org/2000/10/XMLSchema-instance" ));
rootElement.setAttribute(schemaLoc);
Document invoiceDocument = new Document(rootElement);
// ID
rootElement.addContent(new Element("ID", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0").setText(invoice.getId_serie_desc() + "_" + invoice.getNum_factura()));
// cbc:CopyIndicator
rootElement.addContent(new Element("CopyIndicator", "cbc",
"urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0").setText(copyIndicator));
Thank you for your answers.
Susana

WSDL incorrect - in XSD elements always must be the root element?

Hi!
First of all, sorry about my english, but I'm not accustomed to write in this language ;-)
We're trying to publish a Webservice with JAXWS and with a classes generated via JAXB parsing a group of XSD files, always in a maven project with java 5.
More explained the steps we are trying to follow:
1) parse the XSD files with JAXB and generate a JAR file to be included like a dependency in the webapp
2) use the classes packaged in the JAR in other maven project and define and deploy a webapp with the webservice using JAXWS defining a SEI that uses and returns a Type included in the JAR generated in the previous step. Here it is the interface that implements the SEI:
@WebMethod
     public TESTELEMENT test(
               @WebParam(name = "test")
               TESTELEMENT element);The problem seems to be that if the elements in the original XSD files aren't root elements the WSDL generated is incorrect.
Here there are the XSD files we are using and the WSDL error result (XMLSpy dixit, "ns1:Example" must refer to an existing element).
Anyone knows what happens?
Thank you in advance and sorry about this large message!
+--- start of TEST.XSD --+
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="TEST_TYPE.xsd"/>

<xs:element name="TEST_ELEMENT">
<xs:annotation>
<xs:documentation>Blablabla</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="Example" type="TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>+-- end --+
+--- start of TEST_TYPE.xsd --+
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="TestType">
<xs:annotation>
<xs:documentation>Example type</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>+-- end --+
+-- start WSDL error --+
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="TestBO" targetNamespace="http://our.package.test/" xmlns:ns1="http://our.package.test/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Example" type="tns:TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TestType">
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://our.package.test" xmlns:ns1="http://example.work/test" xmlns:tns="http://our.package.test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
<xs:sequence>
<xs:element minOccurs="0" name="test">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/> **
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="test">
<wsdl:part element="ns1:test" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="testResponse">
<wsdl:part element="ns1:testResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="TestBO">
<wsdl:operation name="test">
<wsdl:input message="ns1:test" name="test">
</wsdl:input>
<wsdl:output message="ns1:testResponse" name="testResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>+-- end --+

Hi again.
About my last post, say that the WSDL generated, in fact, was generated with CXF, sorry.
Using JAXWS (wsgen to be more explicit) the WSDL results still are not ok, as you can see, the error is in the last ns1:Example reference in ServeiTestBO_schema1.xsd, that XMLSpy says that doesn't exists :-( :
+--- ServeiTestBOImplService.wsdl [ServeiTestBOImpl - SEI] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://impl.our.package.test/" name="ServeiTestBOImplService" xmlns:tns="http://impl.our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://our.package.test/" location="ServeiTestBO.wsdl"/>
<binding name="ServeiTestBOImplPortBinding" type="ns1:ServeiTestBO" xmlns:ns1="http://our.package.test/">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="test">
      <soap:operation soapAction=""/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ServeiTestBOImplService">
    <port name="ServeiTestBOImplPort" binding="tns:ServeiTestBOImplPortBinding">
      <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
    </port>
</service>
</definitions>+--- ServeiTestBO.wsdl [SEI interface] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <xsd:schema>
      <xsd:import namespace="http://our.package.test/" schemaLocation="ServeiTestBO_schema1.xsd"/>
    </xsd:schema>
    <xsd:schema>
      <xsd:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
    </xsd:schema>
</types>
<message name="test">
    <part name="parameters" element="tns:test"/>
</message>
<message name="testResponse">
    <part name="parameters" element="tns:testResponse"/>
</message>
<portType name="ServeiTestBO">
    <operation name="test">
      <input message="tns:test"/>
      <output message="tns:testResponse"/>
    </operation>
</portType>
</definitions>+--- ServeiTestBO_schema1.xsd *[with error in the last "ns1:Example"]* ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema version="1.0" targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:ns1="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
    <xs:sequence>
      <xs:element name="test" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
    <xs:sequence>
      <xs:element name="return" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:schema>
--- ServeiTestBO_schema2.xsd ---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Example" type="tns:TestType" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:complexType name="TestType">
    <xs:sequence>
      <xs:element name="Element_A" type="xs:string"/>
      <xs:element name="Elment_B" type="xs:boolean"/>
      <xs:element name="Sex" type="tns:SexType"/>
    </xs:sequence>
</xs:complexType>
<xs:simpleType name="SexType">
    <xs:restriction base="xs:string">
      <xs:enumeration value="M"/>
      <xs:enumeration value="W"/>
    </xs:restriction>
</xs:simpleType>
</xs:schema>Thanks in advance again.

Parsing an empty source. Root element expected! error in fcc using MTB

Hi experts,
While converting a flat file to xml using MTB , i'm facing this error in mapping.
" com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping .....
Parsing an empty source. Root element expected! "
Whereas the audit log in file channel - Communication channel monitoring shows that , the payload transformed but i'm unable to view the source message.
Please let me know the resolution if anyone has faced the same issue..
thanks,
younus

hi,
you want to convert yor receivee structure or sender??
see these links about FCC to see how they do it.
File Receiver with Content Conversion
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
Type of separatos
http://help.sap.com/saphelp_nw04/helpdata/en/05/7fdf3d0eb8af5ee10000000a114084/frameset.htm
Troubleshooting the File Adapter
/people/shabarish.vijayakumar/blog/2007/07/26/troubleshooting-the-file-adapter-last-updated-on-02-july10
Converting File Content in a Sender Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
Converting File Content in the Receiver Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
Thanks
Rodrigo
PD: Reward points if useful
Edited by: Rodrigo Pertierra on May 14, 2008 12:11 PM

B1if Error: Parsing an empty source. Root element expected!

Dear experts,
i have created a scenario from SAP PI to SAP B1if.
Under On package i have created multiple scenarios and all were working succesfully.
But i added another scenario now and tested its giving the below error.
infact now , when i am testing the scenarios (which were working succesfully before), all of them are giving the same error as below:
SAP B1iP detected an error:
Emitted HTTP-Code
500 - Internal Server Error
Internal Reason
Parsing an empty source. Root element expected!
Full Internal Error Message
com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.bizprocessor.BizProcException: BPE001 Nested exception: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.bizprocessor.BizProcException: BPE001 Nested exception: com.sap.b1i.utilities.UtilException: UTE001 Nested exception: javax.xml.transform.TransformerConfigurationException: Could not load stylesheet. java.io.IOException: Parsing an empty source. Root element expected!
i am givng the correct input message with root nodes etc but still i am getting the error.
Please help!!
Thanks.

hi,
you want to convert yor receivee structure or sender??
see these links about FCC to see how they do it.
File Receiver with Content Conversion
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
Type of separatos
http://help.sap.com/saphelp_nw04/helpdata/en/05/7fdf3d0eb8af5ee10000000a114084/frameset.htm
Troubleshooting the File Adapter
/people/shabarish.vijayakumar/blog/2007/07/26/troubleshooting-the-file-adapter-last-updated-on-02-july10
Converting File Content in a Sender Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
Converting File Content in the Receiver Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
Thanks
Rodrigo
PD: Reward points if useful
Edited by: Rodrigo Pertierra on May 14, 2008 12:11 PM

Root element added in existing mapping PI 7.1

Similar Messages

Maybe you are looking for