Error while building xml document

Hi Everyone,
I have a problem while building xml document.
I have developed my java files using IBM Eclipse 3.0 and i had no problem while executing the files.
But while i am trying to execute the same code in jdk/bin, xml document is not working..
No error encountered while compiling but while executing when i try to print the xml string it just gives the root element name like [root : null]
Can anyone suggest some solution?

To the values element add xmlns:xsi and xsi:noNamespaceSchemaLocation.
<values xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="file:///c:/schema.xsd">schema.xsd is schema file.

Similar Messages

  • Heap space error while creating XML document from Resultset

    I am getting Heap space error while creating XML document from Resultset.
    It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
    I am already using -Xms32m -Xmx1024m
    Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
    here is my code:
    stmt = conn.prepareStatement(sql);
    result = stmt.executeQuery();
    result.setFetchSize(999);
    Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
    JDBCUtil.write(doc, fileName);
    public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
        throws ParserConfigurationException, SQLException {
            DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = factory.newDocumentBuilder();
            Document doc = builder.newDocument();
            Element results = doc.createElement("sims");
            results.setAttribute("bank", bankId);
            results.setAttribute("record_type", "HEADER");
            results.setAttribute("file_type", interfaceFileType);
            results.setAttribute("version", version);
            doc.appendChild(results);
            ResultSetMetaData rsmd = rs.getMetaData();
            int colCount = rsmd.getColumnCount();
            String columnName="";
            Object value;
            while (rs.next()) {
                Element row = doc.createElement("rec");
                results.appendChild(row);
                for (int i = 1; i <= colCount; i++) {
                    columnName = rsmd.getColumnLabel(i);
                    value = rs.getObject(i);
                    Element node = doc.createElement(columnName);
                    if(value != null)
                        node.appendChild(doc.createTextNode(value.toString()));
                    else
                        node.appendChild(doc.createTextNode(""));
                    row.appendChild(node);
            return doc;
    public static void write(Document document, String filename) {
            //long start = System.currentTimeMillis();
            // lets write to a file
            OutputFormat format = new OutputFormat(document); // Serialize DOM
            format.setIndent(2);
            format.setLineSeparator(System.getProperty("line.separator"));
            format.setLineWidth(80);
            try {
                FileWriter writer = new FileWriter(filename);
                BufferedWriter buf = new BufferedWriter(writer);
                XMLSerializer FileSerial = new XMLSerializer(writer, format);
                FileSerial.asDOMSerializer(); // As a DOM Serializer
                FileSerial.serialize(document);
                writer.close();
            } catch (IOException ioe) {
                ioe.printStackTrace();
            //long end = System.currentTimeMillis();
            //System.err.println("W3C File write time :" + (end - start) + "  " + filename);
        }

    you can increase your heap size..... try setting this as your environment variable.....
    variable: JAVA_OPTS
    value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

  • Error while getting xml document  with default connection in 8iJServer

    I had used GZIP utility to zip and store the document in
    the CLOB. If i use thin drivers and GZIP to retieve this document it works fine.
    instead of thin drivers if i use oracle8iJserver defalut
    connection i get the follwing error
    :Error while getting xml document Not in GZIP format.
    your response is appreciated.
    thanks
    sanjay.

    Hi Yepin Jin,
    I am facing the same issue did you solved it?
    Regards,
    Orlando Covault

  • Very urgent help needed- Error while passing XML document to Oracle stored

    Hi !
    I have been struggling a lot to call Oracle 9i stored procedure passing Stringbuilder object type from ASP.NET
    I am using Visual Studio 2008 Professional, OS: Windows XP and Oracle: 9.2.0.1.0
    Following is the procedure:
    CREATE or REPLACE PROCEDURE loadCompanyInfo (clobxml IN clob) IS
    -- Declare a CLOB variable
    ciXML clob;
    BEGIN
    -- Store the Purchase Order XML in the CLOB variable
    ciXML := clobxml;
    -- Insert the Purchase Order XML into an XMLType column
    INSERT INTO companyinfotbl (companyinfo) VALUES (XMLTYPE(ciXML));
    commit;
    --Handle the exceptions
    EXCEPTION
    WHEN OTHERS THEN
    raise_application_error(-20101, 'Exception occurred in loadCompanyInfo procedure :'||SQLERRM);
    END loadCompanyInfo ;
    And following is the ASP.net code:
    StringBuilder b = new StringBuilder();
    b.Append("<?xml version=\"1.0\" encoding=\"utf-8\" ?>");
    b.Append("<item>");
    b.Append("<price>500</price>");
    b.Append("<description>some item</description>");
    b.Append("<quantity>5</quantity>");
    b.Append("</item>");
    //Here you'll have the Xml as a string
    string myXmlString1 = b.ToString();
    //string result;
    using (OracleConnection objConn = new OracleConnection("Data Source=testdb; User ID=testuser; Password=pwd1"))
    OracleCommand objCmd = new OracleCommand();
    objCmd.Connection = objConn;
    objCmd.CommandText = "loadCompanyInfo";
    objCmd.CommandType = CommandType.StoredProcedure;
    //OracleParameter pmyXmlString1 = new OracleParameter("pmyXmlString1", new OracleString(myXmlString1));
    objCmd.Parameters.Add("myXmlString1", OracleType.clob);
    objCmd.Parameters.Add(myXmlString1).Direction = ParameterDirection.Input;
    //objCmd.Parameters.Add("result", OracleType.VarChar).Direction = ParameterDirection.Output;
    try
    objConn.Open();
    objCmd.ExecuteNonQuery();
    catch (Exception ex)
    Label1.Text = "Exception: {0}" + ex.ToString();
    objConn.Close();
    When I am trying to execute it, I am getting the following error:
    Exception: {0}System.Data.OracleClient.OracleException: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'LOADCOMPANYINFO' ORA-06550: line 1, column 7: PL/SQL: Statement ignored at System.Data.OracleClient.OracleConnection.CheckError(OciErrorHandle errorHandle, Int32 rc) at System.Data.OracleClient.OracleCommand.Execute(OciStatementHandle statementHandle, CommandBehavior behavior, Boolean needRowid, OciRowidDescriptor& rowidDescriptor, ArrayList& resultParameterOrdinals) at System.Data.OracleClient.OracleCommand.ExecuteNonQueryInternal(Boolean needRowid, OciRowidDescriptor& rowidDescriptor) at System.Data.OracleClient.OracleCommand.ExecuteNonQuery() at Default.Button1Click(Object sender, EventArgs e)
    I understand from this that the .net type is not the correct one, but I am not sure how to correct it. I could not find any proper example in any documentation that I came across. Most of the examples give information on how to read but not how to insert XML into Oracle table by calling Stored Procedure.
    Can you please help me to solve this problem? I hope that you can help solve this.
    Also, can you please give me an example of passing XML document XMLdocument to Oracle Stored procedure.
    In both the cases, if you can provide the working code then it would be of great help.
    Thanks,

    Hi ,
    Additional to the Above error details my BPEL code looks like this:
    <process name="BPELProcess1"
    targetNamespace="http://xmlns.oracle.com/Application10/Project10/BPELProcess1"
    xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:client="http://xmlns.oracle.com/Application10/Project10/BPELProcess1"
    xmlns:ora="http://schemas.oracle.com/xpath/extension"
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
    <partnerLinks>
    <partnerLink name="bpelprocess1_client" partnerLinkType="client:BPELProcess1" myRole="BPELProcess1Provider" partnerRole="BPELProcess1Requester"/>
    </partnerLinks>
    <variables>
    <variable name="inputVariable" messageType="client:BPELProcess1RequestMessage"/>
    <variable name="outputVariable" messageType="client:BPELProcess1ResponseMessage"/>
    </variables>
    <sequence name="main">
    <receive name="receiveInput" partnerLink="bpelprocess1_client" portType="client:BPELProcess1" operation="process" variable="inputVariable" createInstance="yes"/>
    <invoke name="callbackClient" partnerLink="bpelprocess1_client" portType="client:BPELProcess1Callback" operation="processResponse" inputVariable="outputVariable"/>
    </sequence>
    </process>
    Kindly help if anyone has faced this Issue before.
    Regards,
    Rakshitha

  • Error while parsing xml document that file name is Japanese.

    who can help me.
    when my xml file name is Japanese. Error occurs while parsing.
    the error message is "ORA-20100: Error occurred while parsing: No such file or directory"
    thanks.

    Hi,
    When I am trying to parse the XML file, I am getting
    the following error. When I run it on Windows having
    JDK1.4 it is working fine. But when I am running it
    on UNIX having JDK1.2, I am getting this ERROR.
    org.xml.sax.SAXParseException: Illegal character at
    end of document, <.
    Any help is appreiciated.I am just guessing, but I would imagine that some of the classes of your JDK 1.4 API have code that is not backwards compatible with earlier versions. There were a few significant changes to the language when 1.4 was released. You would have to read the release notes of 1.4 and also check the API documentation for the classes you are using to parse the XML.
    Also, there are some subtle differences between the OS versions of the Java compiler. You are using two different versions of the Java language and two different versions of operating system code.

  • Error while saving xml document in table

    I am using dbms_xmlsave.insert to
    insert records in the table.
    The procedure works fine when the xml file size is less then 1 Mb.
    But when the file size is around 4 MB
    I get the error java.lang.outofMemoryError.
    Is there any limitation of number of records that can be saved or is there any parameter or any file required to be tuned.
    null

    Try increase JAVA_POOL size or set BATCH_SIZE
    to be small.

  • Bursting Program errors with "Error while generating the Document"

    Hello Folks
    Here is my bursting control file
    <?xml version="1.0" encoding="UTF-8"?>
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
    <xapi:globalData location="stream">
    </xapi:globalData >
    <xapi:request select="/XMLEXCEL1/LIST_G_Q0">
    <xapi:delivery>
    <xapi:email server="mycompany.com" port="25" from="[email protected]"
    reply-to ="[email protected]">
    <xapi:message id="1234" to="[email protected]"
    attachment="true" content-type="html/text"
    subject="Employee Report for Empno"> Dear
    Please review the attached document</xapi:message>
    </xapi:email>
    </xapi:delivery>
    <xapi:document key="123" output-type="XLS" delivery="1234"
    output="XMLEXCEL1" >
    <xapi:template type="RTF" location="xdo://AR.XMLEXCEL1.en.00/?getSource=true">
    </xapi:template>
    </xapi:document>
    </xapi:request>
    </xapi:requestset>
    this is the output of bursting status report:
    <?xml version="1.0" encoding="UTF-8"?>
    <BURS_REPORT><REQUESTID>40403415</REQUESTID>
    <PARENT_REQUESTID>40403339</PARENT_REQUESTID>
    <REPORT_DESC>XMLEXCEL1</REPORT_DESC>
    <OUTPUT_FILE>/opt/local/application/orafin/applmgr/out/outfaud/S1759.zip
    </OUTPUT_FILE>
    <DOCUMENT_STATUS>
    <KEY>123</KEY>
    <OUTPUT_TYPE>XLS</OUTPUT_TYPE>
    <DELIVERY></DELIVERY>
    <OUTPUT>
    </OUTPUT>
    <STATUS>fail</STATUS>
    <LOG>Error while generating the Document...</LOG>
    </DOCUMENT_STATUS>
    </BURS_REPORT>
    Can anyone help on this please.

    can anyone help me?

  • Error while generating the Document...  Bursting Status Report

    Hey all,
    I am getting some errors in a production environment when trying to burst out some invoice data.
    This process has been pretty robust and out of 1000+ invoices a day, I can only find 4 that are failing regularily.
    Why am I mentioning?, just to show that I am thinking this is a data issue, but just cannot see anything that stands out.
    I can take the xml output and run it through my development suite on my local machine and all runs fine.
    Just when it is running live through the db is when it fails.
    Here is the Bursting output that shows the error....
    <?xml version="1.0" encoding="UTF-8"?>
    <BURS_REPORT>
    <REQUESTID>27044820</REQUESTID>
    <PARENT_REQUESTID>27044726</PARENT_REQUESTID>
    <REPORT_DESC>Invoice Print Selected Invoices</REPORT_DESC>
    <OUTPUT_FILE>[$OUT_DIR]/o27044820.zip</OUTPUT_FILE>
    <DOCUMENT_STATUS>
    <KEY></KEY>
    <OUTPUT_TYPE>pdf</OUTPUT_TYPE>
    <DELIVERY></DELIVERY>
    <OUTPUT></OUTPUT>
    <STATUS>fail</STATUS>
    <LOG>Error while generating the Document...</LOG>
    </DOCUMENT_STATUS>
    </BURS_REPORT>
    The problem is that this output doesn't necessarily help, nor can I find any hints in the OPP logs.
    So... the question becomes...
    Any ideas on where I can look to resolve this issue?+
    Or where I can find any clues at, that would possible point at the issue?+
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    BI Publisher 5.6.3
    Thanks
    Hayden,

    Tim,
    Thanks for the suggestion, always seems to slip my mind that the Bursting Report has debug on it.
    As far as what is generating the XML, it is oracle's standard, only slightly modified ... ;), invoice generating report, RAXINV_SEL.
    Well RAXINV_SEL, or RAXINV_NEW, doesn't matter, same code, that is the executable.
    I have turned on the debug, for both the source xml and the burst request, and unfortunately, still nothing stands out to me.
    I was really expecting to see something in the burst log, pasted at the bottom...
    but, it yet avoids me.
    If I had to guess, I would bet the user went, in our terminology, "slashwit crazy", or example "model /w options", in some description.
    But can't seem to find which field it is blowing up on, since we are catching these special characters in several places already, and slashwit is littered throughout the output.
    I was also looking in the bursting control file for the special xml tags identified there, as those would require no slashes. But those are all clean.
    Hayden,
    XML Publisher: Version : 11.5.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XDOBURSTREP module: XML Publisher Report Bursting Program
    Current system time is 21-SEP-2009 10:43:12
    XML/BI Publisher Version : 5.6.3
    Request ID: 27048106
    All Parameters: ReportRequestID=27044726:DebugFlag=Y
    Report Req ID: 27044726
    Debug Flag: Y
    Updating request description
    Updated description
    Retrieving XML request information
    Node Name:{node}
    Preparing parameters
    null output =/u007/app/applmgr/{instance}/out/{instance}/o27048106.out
    inputfilename =/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
    Data XML File:/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
    Set Bursting parameters..
    Temp. Directory:/u007/app/applmgr/{instance}/temp
    [092109_104315337][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
    [092109_104315340][][STATEMENT] setOAProperties called..
    Bursting propertes.....
    {burstng-source=EBS, font.Free 3 of 9.normal.normal=truetype./usr/java/jre/lib/fonts/FREE3OF9.TTF, font.Times New Roman.normal.normal=truetype./usr/java/jre/lib/fonts/TIMES.TTF, system-temp-dir=/u007/app/applmgr/{instance}/temp, font.Arial.italic.normal=truetype./usr/java/jre/lib/fonts/ARIALI.TTF, user-variable:cp:parent_request_id=27044726, user-variable:cp:application_short_name=XDO, font.Courier New.normal.bold=truetype./usr/java/jre/lib/fonts/COURBD.TTF, font.Times New Roman.normal.bold=truetype./usr/java/jre/lib/fonts/TIMESBD.TTF, user-variable:cp:request_id=27048106, font.Arial.normal.normal=truetype./usr/java/jre/lib/fonts/ARIAL.TTF, font.Courier New.normal.normal=truetype./usr/java/jre/lib/fonts/COUR.TTF, user-variable.OA_MEDIA=http://diierp.corio.com:8002/OA_MEDIA, font.Courier New.italic.bold=truetype./usr/java/jre/lib/fonts/COURBI.TTF, user-variable:cp:org_id=83, user-variable:cp:DebugFlag=Y, font.Times New Roman.italic.bold=truetype./usr/java/jre/lib/fonts/TIMESBI.TTF, user-variable:cp:responsibility=51270, font.Arial.italic.bold=truetype./usr/java/jre/lib/fonts/ARIALBI.TTF, font.Courier New.italic.normal=truetype./usr/java/jre/lib/fonts/COURI.TTF, user-variable:cp:user=HAYDEN, user-variable:cp:reportdescription=Invoice Print Selected Invoices, user-variable:cp:language=en, font.Times New Roman.italic.normal=truetype./usr/java/jre/lib/fonts/TIMESI.TTF, user-variable:cp:ReportRequestID=27044726, user-variable:cp:locale=en-US, user-variable:cp:territory=US, font.Arial.normal.bold=truetype./usr/java/jre/lib/fonts/ARIALBD.TTF}
    Start bursting process..
    Bursting process complete..
    Generating Bursting Status Report..
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 27048106 on node {node} at 21-SEP-2009 10:43:19.
    Post-processing of request 27048106 completed at 21-SEP-2009 10:43:20.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 21-SEP-2009 10:43:20
    ---------------------------------------------------------------------------

  • Error while importing .xml file in Datatype

    Hi SDN,
    I am getting this error while importing .xml file in Datatype.
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
    Actually I have created datatype in my development box..
    but my client doesn't want to develop in development box.
    so i have exported that datatype as xsd from datatype editor.
    and while importing into sandbox datatype editor i am getting this error..
    Any help please......

    Hi Rajeev,
    now i have an .xml file its not importing into datatype...
    error is
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
      <?xml version="1.0" encoding="UTF-8" ?>
      <xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:complexType name="DT_PLANNINGSCHEDULE">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
      </xsd:annotation>
      <xsd:sequence>
      <xsd:element name="PlanningSchedule_Output">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PlanningScheduleHeader">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleIssueDate" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="SchedulePurpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Purpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PurposeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleTypeCoded" type="xsd:string">
    <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="SellerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipFromParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipToParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Language">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LanguageCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationGroupedPlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Location">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BasePlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LineItemNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerLineItemNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemIdentifiers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNumbers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="StandardPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ProductIdentifier" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemDescription" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfItemReferences">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceTypeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="PrimaryReference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Reference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="RefNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ForecastFrequencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="CommitmentLevelCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleDates">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfDateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Date">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="DateQualifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleQuantities">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfQuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityValue" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="UnitOfMeasurement">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="UOMCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>

  • Error while retreiving xml file from database

    Hi-
    I am trying to configure Planning and getting the following error message at instance configuration step:
    "Error while retreiving xml file from database"
    We looked at PlanningSystemDB.properties, changes server name to its ip, reinstalled planning, made sure both auth methods are selected (sql server and windows), created new relational repository.. still the same error.
    Here is the contents of the configtool error file:
    (Dec 11, 2008, 04:36:44 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:37:09 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:38:41 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:07 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:12 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:39:22 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    (Dec 11, 2008, 04:40:46 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
    (Dec 11, 2008, 04:41:05 PM), com.hyperion.cis.config.CmsRegistrationUtil, ERROR, Failed to authenticate user = admin
    (Dec 11, 2008, 04:48:28 PM), com.hyperion.cis.DBConfigurator, ERROR, Invalid SQL statement: begin transaction IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PROPERTIES]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PROPERTIES IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APP_CLUSTER_DTL]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APP_CLUSTER_DTL IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_APPLICATION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_APPLICATION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_DATASOURCE]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_DATASOURCE IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_CLUSTER]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_CLUSTER IF EXISTS (select * from sysobjects where id = object_id(N'[HSP_ACTION]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSP_ACTION IF EXISTS (select * from sysobjects where id = object_id(N'[HSPSYS_PI_INFO]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) DROP TABLE HSPSYS_PI_INFO commit begin transaction CREATE TABLE HSP_ACTION ( ID INTEGER NOT NULL IDENTITY, CONSTRAINT PK_HSP_ACTION PRIMARY KEY(ID) , FROM_ID INTEGER, TO_ID INTEGER, ACTION_ID INTEGER, OBJECT_TYPE INTEGER, PRIMARY_KEY VARCHAR(255), ACTION_TIME DATETIME ); CREATE TABLE HSPSYS_CLUSTER ( CLUSTER_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), CONSTRAINT PK_HSPCLUSTER PRIMARY KEY(CLUSTER_ID) ); CREATE TABLE HSPSYS_DATASOURCE ( DATASOURCE_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), APP_ID INTEGER, RDB_SERVER_URL VARCHAR(255), RDB_TYPE VARCHAR(255) NOT NULL, RDB_CATALOG_NAME VARCHAR(255) NOT NULL, RDB_USER VARCHAR(255) NOT NULL, RDB_PASSWORD VARCHAR(255), RDB_DRIVER VARCHAR(255) NOT NULL, ESS_SERVER VARCHAR(255) NOT NULL, ESS_USER VARCHAR(255) NOT NULL, ESS_PASSWORD VARCHAR(255), CONSTRAINT PK_HSPDTASRC PRIMARY KEY(DATASOURCE_ID) ); CREATE TABLE HSPSYS_APPLICATION ( APP_ID INTEGER NOT NULL, NAME VARCHAR(255) NOT NULL, DESCRIPTION VARCHAR(255), DATASOURCE_ID INTEGER NOT NULL, CONSTRAINT FK_HSPAPP_DSID FOREIGN KEY(DATASOURCE_ID) REFERENCES HSPSYS_DATASOURCE, VERSION VARCHAR(255) NOT NULL, CONSTRAINT PK_HSPAPP PRIMARY KEY(APP_ID) ); CREATE TABLE HSPSYS_APP_CLUSTER_DTL ( APP_ID INTEGER NOT NULL , CONSTRAINT FK_HSP_APP_ID FOREIGN KEY (APP_ID) REFERENCES HSPSYS_APPLICATION , CLUSTER_ID INTEGER NOT NULL, CONSTRAINT FK_HSPCS_CLID FOREIGN KEY(CLUSTER_ID) REFERENCES HSPSYS_CLUSTER, CONSTRAINT PK_APP_CLSTR_DTL PRIMARY KEY(CLUSTER_ID, APP_ID) ); CREATE TABLE HSPSYS_PROPERTIES ( PROPERTY_ID INTEGER NOT NULL, OBJECT_ID INTEGER NOT NULL, PROPERTY_NAME VARCHAR(255) NOT NULL, PROPERTY_VALUE VARCHAR(255), CONSTRAINT PK_HSPPROP PRIMARY KEY(PROPERTY_ID, OBJECT_ID, PROPERTY_NAME) ); CREATE TABLE HSPSYS_PI_INFO ( XML_FILE NTEXT NOT NULL ); commit
    (Dec 11, 2008, 04:50:32 PM), com.hyperion.planning.PIRegistrationPanelManager, ERROR, Exception :Error while retreiving xml file from database.
    Thanks for any help.

    After spending 2+ hrs with Hyperion Support nothing got resolved.. Just to give more background on this problem, we originally reconfigured all Hyperion components to use different SQL server, that is when the problem started happening as soon as we got to Planning Instance Configuration. Could this be the situations when old server name is still somewhere in the system?.. Could this be Shared Services problem.
    Here is another quote from SharedServices_Security.log
    2008-12-12 15:08:48,249 [http-58080-Processor1] WARN com.hyperion.css.spi.impl.nv.NativeProvider.getHierarchicalRoleTree(Unknown Source) - Exception getting Child Roles in hierarchy due to Illegal or invalid id.dflt passed in. Please check the argument.
    2008-12-12 15:31:18,121 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
    2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
    2008-12-12 15:31:29,808 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 1016
    2008-12-12 15:31:30,823 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
    2008-12-12 15:31:41,229 [http-58080-Processor4] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:31:41,229 [http-58080-Processor4] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
    2008-12-12 15:38:01,938 [main] WARN com.hyperion.css.common.configuration.CSSConfigurationImplXML.<init>(Unknown Source) - Skipping the validation of the configuration because the required validating parser library not found or errors in validation. This does not guarantee the proper initialization of the component.
    2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.resolveCircularDependency(Unknown Source) - INFO: Time to resolve circular dependency on the Cache for provider: DIPORTAL is : 0
    2008-12-12 15:38:13,454 [Thread-8] WARN com.hyperion.css.spi.impl.msad.MSADCacheUpdater.refreshProviderCache(Unknown Source) - INFO: Time to build Cache for provider: DIPORTAL in millis is : 813
    2008-12-12 15:38:35,453 [main] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /F:/Hyperion/deployments/Tomcat5/SharedServices9/config/CSS.xml.
    2008-12-12 15:42:09,776 [http-58080-Processor3] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:42:09,776 [http-58080-Processor3] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.
    2008-12-12 15:42:09,776 [http-58080-Processor2] ERROR com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - Unable to get CSS.xml file or the file may be read only
    2008-12-12 15:42:09,776 [http-58080-Processor2] WARN com.hyperion.css.CSSAPIImpl.initialize(Unknown Source) - The system has already been configured; skipping attempt to configure the system again with the new config file /null.

  • Error while building javaeetutorial5

    When I try to build "bookstore" from javaeetutorial5 I get this error:
    Buildfile: build.xml
    -pre-init:
    init:
    default-ear:
    -pre-compile:
    bpp-actual-compilation:
    [echo] Compiling bookstore
    [javac] Compiling 11 source files to /opt/javaeetutorial5/examples/web/bookstore/build/classes
    BUILD FAILED
    /opt/javaeetutorial5/examples/bp-project/command-line-ant-tasks.xml:89: /opt/javaeetutorial5/examples/web/bookstore/c:/Sun/AppServer not found.
    Total time: 1 second
    The solution is to edit the file /javaeetutorial5/examples/bp-project/build.properties.sample
    --david                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Hi David,
    Yes, the problem came from the ../bp-project/build.properties & ../bp-project/app-server.properties files. As indicated from your error messages "/opt/javaeetutorial5/examples/web/bookstore/c:/Sun/AppServer not found." It seems you are using AppServer on a solaris machine while those configuration files are default for window enviroment "c:/Sun/AppServer not found."
    Here is what you should to do:
    -Copy build.properties.sample to build.properties
    -Edit the variables below for the correct path:
    javaee.home=<The installation directory of your AppServer>
    javaee.server.name=<machine name> (localhost)
    javaee.server.port=<The port number for the server instance> (8080)
    javaee.server.username=<The administrator username>
    javaee.server.passwordfile=</path/to/passwordfile>
    Note:
    Inside passwordfile add: AS_ADMIN_PASSWORD=<The administrator password>
    javaee.adminserver.port=<The port number for admin server> (4848)
    -Do the same thing for app-server.properties file (optional)
    You can find the information above from the link below
    http://java.sun.com/javaee/5/docs/tutorial/doc/
    Section: About The Examples
    -davis

  • Error while Building Flex

    hi ,
    I m getting an error while building flex application
    Error Description
    "An internal Build Error has occured" Right click for more
    information"
    In my flex application there are around 5000 line of code .
    i am binding 2000 Xml to the application
    this much line of code causing a error
    Please Help Me out
    ThanX

    Code Snippet could be useful here in us understanding the issue.

  • "Error while using XML iview" with XML iview template

    Our portal platform: HP-UX,  WAS 6.40 JAVA, EP 6.0 SP14
    We created an XML iview using XML iview template and configured the XML source URL with RSS feeder addresses such as"https://forums.sdn.sap.com/rss/rssmessages.jsp?forumID=41". And then select RSS to XHTMLB as the XML transformation format and save.  When I try to preview the iview, I always got error "Error while using XML iview, please contact your system administrator".  Here is the log and among which I found an error "java.net.UnknownHostException: news.163.com".  Does this indicate that the Portal server is not able to interpret the address of the URL host?
    #1.5#000F20196FBC0063000000080000623300043FCBAE39EA79#1196043941051#com.sap.portal.httpConnectivity.transformationService#sap.com/irj#com.sap.portal.httpConnectivity.transformationService.transformerservice#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_19##0#0#Error##Plain###Error during transformation using pipe: transformer-com.sap.portal.transformationservice-RSS_TO_XHTMLB-1.0;transformer-com.sap.portal.transformationservice-XHTMLBSAXHandler-1.0#
    #1.5#000F20196FBC00630000000A0000623300043FCBAE39EDB0#1196043941051#com.sap.portal.httpConnectivity.xmlIViewsRuntime#sap.com/irj#com.sap.portal.httpConnectivity.xmlIViewsRuntime#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/System/Server#Plain###transform - exception raised during transformation. Make sure that the input source is valid and that all used transformers exists.#
    #1.5#000F20196FBC005B0000001E0000623300043FCBCC12043B#1196044441749#com.sap.portal.httpConnectivity.transformationService#sap.com/irj#com.sap.portal.httpConnectivity.transformationService.java.lang.Class#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_37##0#0#Error##Java###Error openning connection when getting input stream for URL:http://news.163.com/special/00011K6L/rss_newstop.xml
    [EXCEPTION]
    #1#java.net.UnknownHostException: news.163.com
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153)
         at java.net.Socket.connect(Socket.java:474)
         at java.net.Socket.connect(Socket.java:424)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:306)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
         at sun.net.www.http.HttpClient.New(HttpClient.java:339)
         at sun.net.www.http.HttpClient.New(HttpClient.java:320)
         at sun.net.www.http.HttpClient.New(HttpClient.java:315)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:522)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:499)
         at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:378)
         at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:391)
         at com.sapportals.portal.pb.contentservice.fetcher.DataFetcher.OpenConnection(DataFetcher.java:117)
         at com.sap.portal.httpconnectivity.transformationservice.xmlsource.HTTPStreamSource.getInputStream(HTTPStreamSource.java:295)
         at com.sap.portal.httpconnectivity.transformationservice.PipeTransformer.transform(PipeTransformer.java:131)
         at com.sap.portal.httpconnectivity.transformationservice.EPBaseTransformer.transform(EPBaseTransformer.java:257)
         at com.sap.portal.httpconnectivity.transformationservice.TransformerService.transform(TransformerService.java:284)
         at com.sap.portal.httpconnectivity.xmltransformationiview.runtime.XMLTransformationIView.transform(XMLTransformationIView.java:222)
         at com.sap.portal.httpconnectivity.xmltransformationiview.runtime.XMLTransformationIView.doContent(XMLTransformationIView.java:87)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    And then I tried to upload an XML file on the portal server through KM and created another XML iview.  I got the same error message "Error while using XML iview....". But I found that the log contained different message:
    #1.5#000F20196FBC0059000000090000623300043FCC25CCAC4B#1196045947167#com.sap.portal.httpConnectivity.transformationService#sap.com/irj#com.sap.portal.httpConnectivity.transformationService.transformerservice#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_34##0#0#Error##Plain###Error during transformation using pipe: transformer-com.sap.portal.transformationservice-RSS_TO_XHTMLB-1.0;transformer-com.sap.portal.transformationservice-XHTMLBSAXHandler-1.0#
    #1.5#000F20196FBC00590000000B0000623300043FCC25CCAEDC#1196045947168#com.sap.portal.httpConnectivity.xmlIViewsRuntime#sap.com/irj#com.sap.portal.httpConnectivity.xmlIViewsRuntime#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Plain###transform - exception raised during transformation. Make sure that the input source is valid and that all used transformers exists.#
    #1.5#000F20196FBC005C000000180000623300043FCC5EB48FCF#1196046901893#com.sap.portal.httpConnectivity.xmlIViewsRuntime#sap.com/irj#com.sap.portal.httpConnectivity.xmlIViewsRuntime#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Plain###transform - exception raised during transformation. Make sure that the input source is valid and that all used transformers exists.#
    #1.5#000F20196FBC0066000000020000623300043FCC61683438#1196046947221#com.sap.portal.httpConnectivity.xmlIViewsRuntime#sap.com/irj#com.sap.portal.httpConnectivity.xmlIViewsRuntime#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Server#Plain###transform - exception raised during transformation. Make sure that the input source is valid and that all used transformers exists.#
    #1.5#000F20196FBC00570000000D0000623300043FCC7B6DCFB3#1196047383789#com.sap.portal.httpConnectivity.transformationService#sap.com/irj#com.sap.portal.httpConnectivity.transformationService.java.lang.Class#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Java###Error openning connection when getting input stream for URL:http://bfepdev.bf.ctc.com:50000/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/Links/rss.xml
    [EXCEPTION]
    #1#java.io.IOException: Server returned HTTP response code: 401 for URL: http://bfepdev.bf.ctc.com:50000/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/Links/rss.xml
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at sun.net.www.protocol.http.HttpURLConnection$3.run(HttpURLConnection.java:840)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:834)
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:601)
         at com.sapportals.portal.ivs.http.HttpClient.getResponseInputStream(HttpClient.java:615)
         at com.sapportals.portal.pb.contentservice.fetcher.DataFetcher.getInputStreamResponse(DataFetcher.java:182)
         at com.sap.portal.httpconnectivity.transformationservice.xmlsource.HTTPStreamSource.getInputStream(HTTPStreamSource.java:296)
         at com.sap.portal.httpconnectivity.transformationservice.PipeTransformer.transform(PipeTransformer.java:131)
         at com.sap.portal.httpconnectivity.transformationservice.EPBaseTransformer.transform(EPBaseTransformer.java:257)
         at com.sap.portal.httpconnectivity.transformationservice.TransformerService.transform(TransformerService.java:284)
         at com.sap.portal.httpconnectivity.xmltransformationiview.runtime.XMLTransformationIView.transform(XMLTransformationIView.java:222)
         at com.sap.portal.httpconnectivity.xmltransformationiview.runtime.XMLTransformationIView.doContent(XMLTransformationIView.java:87)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: http://bfepdev.bf.ctc.com:50000/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/Links/rss.xml
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:794)
         at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
         at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:395)
         at com.sapportals.portal.pb.contentservice.fetcher.DataFetcher.OpenConnection(DataFetcher.java:117)
         at com.sap.portal.httpconnectivity.transformationservice.xmlsource.HTTPStreamSource.getInputStream(HTTPStreamSource.java:295)
         ... 37 more
    #1.5#000F20196FBC00570000000E0000623300043FCC7B6DD77E#1196047383800#com.sap.portal.httpConnectivity.transformationService#sap.com/irj#com.sap.portal.httpConnectivity.transformationService.transformerservice#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Error during transformation using pipe: transformer-com.sap.portal.transformationservice-RSS_TO_XHTMLB-1.0;transformer-com.sap.portal.transformationservice-XHTMLBSAXHandler-1.0#
    #1.5#000F20196FBC0057000000100000623300043FCC7B6DD9C8#1196047383801#com.sap.portal.httpConnectivity.xmlIViewsRuntime#sap.com/irj#com.sap.portal.httpConnectivity.xmlIViewsRuntime#Administrator#1176##bfepdev_EPD_5623650#Administrator#7a7283a09bc511dca79a000f20196fbc#SAPEngine_Application_Thread[impl:3]_30##0#0#Error#1#/System/Server#Plain###transform - exception raised during transformation. Make sure that the input source is valid and that all used transformers exists.#
    Anyone has any idea on this? thanks.

    Hi Yepin Jin,
    I am facing the same issue did you solved it?
    Regards,
    Orlando Covault

  • Error while importing .xml files in informatica

    Dear Rajendra, Please use this.
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <my:MainFields xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.microsoft.com/office/infopath/2003/myXSD/2010-10-14T12:46:24 myschema.xsd " xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD/2010-10-14T12:46:24"> i used same like this my side its working. Please let me know. Thanks & RegardsKasireddy+966545281845

    Hi All, Please help out getting below error while reading .xml file in informaitca 9.5.0 error:: FATAL: Error at (file D:/userdata/local/Desktop/documents/2015_07_22_NE_5003.xml, line 2, char 52 ): An exception occurred! Type:RuntimeException, Message:Could not open DTD file 'D:/userdata/ongole/Desktop/documents/InventoryInfo.xml'.  Let me know. how to overcome this issue. Regards,Rajendra

  • Error while creating delivary document

    Hi
    i got error while creating delivary document
    "Delevivary documents could not be created"
    Thanks&regards
    kishore kumar

    Hi Kishore,
    Please check the sales order is this relevent for the delivery or not.
    Check the copy control settings between your sales document type and delivery document type in VTLA transaction.
    Check the incompletion log for the sales order.
    I hope it will help you,
    Regards,
    Murali.

Maybe you are looking for

  • Jabber for windows 9.2.6 client

    hi i have just upgraded some of my cisco jabber for windows clients to the latest release 9.2.6 (upgraded from 9.2.3) i noticed that the first time the client startsup i get certificate warnings for our CUCM-PUB, SUB, CUC device and CUPS server. (all

  • I replaced the hard drive and ram on my 2010 macbook, but its still unusably slow! Why??

    I replaced the harddrive and the ram on my 2010 white unibody macbook about two months ago. I only put a few documents on it, i did not reinstall all of my files. I have only downloaded the minium amount of items on the computer since then, and it is

  • Design Question - Command Line Argument Processor

    Folks, I'm a java and OO newbie... I've been going through Sun's java tutorials I've "enhanced" Sun's RegexTestHarness.java (using Aaron Renn's gnu.getopt package) to expose the various Pattern.FLAGS on the command line. Whilst it does work the argue

  • Source systems vanishes from RSA1 after renaming of the LSN after BDLS

    Dear BW/BI Experts,            We are doing BW3.1 upgarde to BI7.0........After system copy there is need of rename of logical system for BP1 to BD1 (Prod. to Dev. and Dev. is our new Target BW system ) and From RP1 to RQ1. Before renaming I checked

  • Substatus need to default with D   while creating Appraisal doc

    Hi  Friends Am  using few  FM  to create appraisal docs in  In Review status  and In planning status based on selection  screen choose radio button     now in  my new req   i need to  default  documents sub status with  D  (  Mid Year-Self Appraisal