Error when  importing xml data

I am getting the following error when loading xml datafile to my Oracle XE database table. This data I exported from htmldb.oracle.com.
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00222: error received from SAX callback function
please help
George

George,
I expect that this is simply an incompatibility with the date format that was used for XML Import/Export as part of XE Beta. This is a bug that has been fixed for XE production and you will be able to freely export from HTML DB 2.0 and import into XE and vice versa.
Your NLS settings do not control this. The date format used for XML Export is fixed - a canonical date format is always used.
If you want to be able to import into XE Beta, your date fields probably look like:
<HIREDATE>2005-12-03T00:00:00.000</HIREDATE>Just remove the trailing .000 from your date entries.
<HIREDATE>2005-12-03T00:00:00</HIREDATE>
Note: This will only be necessary for XE Beta. You should not have to do this for XE Production.
Joel

Similar Messages

  • Error when import XML

    I am dealing with a INDD file with XML structure, after import the XML there is always an error occured when I validate it
    How to declare it in DTD? Or any way to avoid it?

    Especially if you are importing XML with tables, I would recommend creating an ID document with tables, either use the auto-tagging or create your own tags based upon your XML, then exporting it to look how the XML is formed.
    Using the namespace as part of the table element should look roughly like this in your XML:
    <Table xmlns:aid="http://ns.adobe.com/AdobeInDesign/4.0/" aid:table="table" aid:trows="8" aid:tcols="5">
    The above is simply from a quick export of a table in ID. But note that the definitions, the declaration, of what the element parts are follows the namespace portion.
    Mike

  • Error when importing XML

    Hi,
    I get the following error when using the XML import on a Ehp1 SP05 system:
    The termination type was: RABAX_STATE
    The ABAP call stack was:
          Method: CONVERT_BACKEND_EXCEPTION of program CL_FDT_WD_SERVICE=============CP
          Method: IF_FDT_WD_MODEL~SET_MODEL_BY_NODE of program CL_FDT_WD_XML_IMPORT==========CP
          Method: IF_FDT_WD_MODEL~SET_MODEL of program CL_FDT_WD_MODEL===============CP
          Method: UPLOAD_XML_CONTENT of program /1BCWDY/J821P21RQVHRTD23IRHU==CP
          Method: IF_COMPONENTCONTROLLER~UPLOAD_XML_CONTENT of program /1BCWDY/J821P21RQVHRTD23IRHU==CP
          Method: ONACTIONUPLOAD_XML of program /1BCWDY/J821P21RQVHRTD23IRHU==CP
          Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/J821P21RQVHRTD23IRHU==CP
          Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
          Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================CP
          Method: DO_HANDLE_ACTION_EVENT of program CL_WDR_WINDOW_PHASE_MODEL=====CP
    When importing the same XML file into an Ehp2 system i get the following error:
    Problem in the import of Element AGE ID 00505683359D02DE9FB4330FBD00035D
    No valid comparison settings
    No active version found for time stamp 20.09.2010 07:41:06  Display Help
    No active version found for time stamp 20.09.2010 07:41:06  Display Help
    No active version found for time stamp 20.09.2010 07:41:06  Display Help
    No active version found for time stamp 20.09.2010 07:41:06  Display Help
    Errors when saving Entscheidungstabelle CUST_NEEDS_DT
    Element AGE (ID 00505683359D02DE9FB4330FBD00035D) has not been saved to the database yet
    Errors when saving Function
    Element AGE (ID 00505683359D02DE9FB4330FBD00035D) has not been saved to the database yet
    Errors when saving Entscheidungsbaum 
    Element AGE (ID 00505683359D02DE9FB4330FBD00035D) has not been saved to the database yet
    Errors when saving Function 
    Element AGE (ID 00505683359D02DE9FB4330FBD00035D) has not been saved to the database yet
    Object(s) contains error, imported but not activated
    Business transaction coverage check cannot be done due to column Element BP_TYPE  Display
    I eventually got the import to partially work in the Ehp2 system but there are objects missing such as a function.
    The XML was exported from a Ehp2 system
    Cheers
    Phillip

    Not all the objects were active before exporting.
    Thanks to Matthias for the help.

  • Error when importing from Data Feeds

    SQL Server 2012 SSAS. Very funny error. I cannot same issue in forums:
    Errors in the high-level relational engine. The following exception occurred while the managed IDbCommand interface was being used: The remote server returned an error: (407) Proxy Authentication Required..
    An error occurred while processing the partition XXXXX
    The current operation was cancelled because another operation in the transaction failed.
    When I go through the import everything seems to be fine: it successfully connects to the report/data feed, it lets me preview and filter tablix displaying information, but when I click Finish, it throws the error on import.
    What could it be? I have configured credentials and Proxy in SQL Server Agent.

    Hi Alexandre, I am glad you found a workaround for this, but as this is a bug in our export code we would really appreciate you creating a Connect bug to track this. We will do our best to get this addressed on our side. To file
    a connect bug for this issue go to https://connect.microsoft.com/SQLServer/feedback/CreateFeedback.aspx and
    use the category "Developer Tools(SSDT, BIDS, etc.)". We're trying to track all bugs through connect as it helps us prioritize issues customers are running into, and track the fix status
    publicly.
    Thanks,
    Kevin

  • Getting the below error  when importing base data

    Hi.. I am trying to import base data using the command ant importBaseData command.
    The following is the content in my dasEnv.Bat:
    set ATGJRE=D:\Program Files\Java\jdk1.6.0_18\bin\java
    set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
    set WL_VERSION=10.3
    Please help me out
    Following is the error i am getting:
    _publishingFileRepository:
    [exec] Application Server: weblogic
    [exec] The following installed ATG components are being used to launch:
    [exec] ATGPlatform version 9.2 installed at C:\ATG\ATG9.2
    [exec]
    [exec] Created ".\servers\baseDataImport\startDynamo.jar" in 8,046ms.
    [exec] -------------------
    [exec] JAVA_ARGS: -Djava.security.policy=lib/java.policy -Datg.dynamo.home="." -Datg.dynamo.root=".\.." -Datg.dynamo.display= -Djava.protocol.handler.pkgs=atg.net.www.protocol -Djava.naming.factory.url.pkgs=atg.
    .dynamo.layers= -Dsun.rmi.dgc.server.gcInterval=3600000
    [exec] -------------------
    [exec] DYNAMO_MODULES: @@atg/env/Startup.modules@@
    [exec] -------------------
    [exec] CONFIGPATH: @@atg/env/Startup.configPath@@;..\DAS\config\dtmconfig.jar;localconfig;servers\baseDataImport\localconfig;..\DAF\config\dafconfig.jar
    [exec] -------------------
    [exec] CLASSPATH: .\locallib;D:\Program Files\Java\jdk1.6.0_18\lib;C:\ATG\ATG9.2\eGarage\core\conf;C:\Python-2.5-wince-dev\lib;C:\ATG\ATG9.2\RL\lib;C:\ATG\ATG9.2\PublishingAgent\base\lib;C:\ATG\ATG9.2\home\serve
    [exec] -------------------
    [exec] PATH: D:\Program Files\Java\jdk1.6.0_18\bin;C:\Oracle\Middleware\wlserver_10.3\common\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\W
    ;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\Microsoft Application Virt
    in32\ice
    [exec] **** info Mon Sep 26 15:15:52 CEST 2011 1317042952556 /DPSLicense atg.service.ServiceResources->dynamoPrintExpirationDate : This license will expire on Sat Nov 24 05:59:59 CET 2210
    [exec] **** info Mon Sep 26 15:15:52 CEST 2011 1317042952564 /DPSLicense DPS is licensed to License User - Production
    [exec] **** info Mon Sep 26 15:15:52 CEST 2011 1317042952564 /DPSLicense atg.service.ServiceResources->unlimitedLicenseMsg : This product is licensed for an unlimited number of CPUs.
    [exec] **** info Mon Sep 26 15:15:53 CEST 2011 1317042953770 /atg/epub/version/VersionManagerRepository SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:53 CEST 2011 1317042953927 /atg/dynamo/server/SQLRepositoryEventServer Service /atg/dynamo/server/SQLRepositoryEventServer listening at http://HYDHTC76776L:49716/
    [exec] **** info Mon Sep 26 15:15:53 CEST 2011 1317042953992 /atg/epub/process/ProcessData-ver SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:53 CEST 2011 1317042953993 /atg/epub/process/ProcessDataRepository SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:54 CEST 2011 1317042954086 /atg/epub/file/PublishingFiles-ver SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:54 CEST 2011 1317042954096 /atg/epub/file/PublishingFileRepository SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:54 CEST 2011 1317042954413 /atg/userprofiling/InternalProfileRepository SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:54 CEST 2011 1317042954644 /atg/dynamo/security/AdminSqlRepository SQL Repository startup complete
    [exec] **** info Mon Sep 26 15:15:54 CEST 2011 1317042954645 /atg/dynamo/security/AdminAccountInitializer Initializing account database /atg/dynamo/security/AdminAccountManager from /atg/dynamo/security/
    [exec]
    [exec] Nucleus running
    [exec]
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955379 / Unable to create class atg.deployment.server.DeploymentServer for configuration /atg/epub/DeploymentServer java.lang.NoClassDefFoundError
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / Unable to resolve component /atg/epub/Configuration java.lang.NoClassDefFoundError: javax/ejb/FinderException
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.Class.forName0(Native Method)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.Class.forName(Class.java:247)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.PropertyEditors.getPropertyEditor(PropertyEditors.java:254)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.getProperty(BeanConfigurator.java:731)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.configureStateProperty(BeanConfigurator.java:683)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.configureStateProperty(BeanConfigurator.java:594)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.configureState(BeanConfigurator.java:418)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.PropertyConfiguration.configureState(PropertyConfiguration.java:809)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.PropertyConfiguration.configureService(PropertyConfiguration.java:748)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SingleNucleusConfigurator.configureService(SingleNucleusConfigurator.java:62)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureService(NucleusNameResolver.java:1319)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureAndStartService(NucleusNameResolver.java:1119)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:787)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:569)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:550)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.resolveName(NucleusNameResolver.java:394)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.resolveName(NucleusNameResolver.java:1051)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.ConfigurationRef.getValue(ConfigurationRef.java:81)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.ConfigurationRefProperty.getValue(ConfigurationRefProperty.java:82)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleComponentState.setBeanProperty(SimpleComponentState.java:357)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleConfigurationState.saveToBean(SimpleConfigurationState.java:218)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleConfigurationState.configureBean(SimpleConfigurationState.java:241)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.configureBean(BeanConfigurator.java:275)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.PropertyConfiguration.configureService(PropertyConfiguration.java:752)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SingleNucleusConfigurator.configureService(SingleNucleusConfigurator.java:62)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureService(NucleusNameResolver.java:1319)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureAndStartService(NucleusNameResolver.java:1119)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:787)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:569)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:550)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.resolveName(NucleusNameResolver.java:394)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.resolveName(NucleusNameResolver.java:1051)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.ConfigurationRefArray.getValue(ConfigurationRefArray.java:146)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleComponentState.setBeanProperty(SimpleComponentState.java:357)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleConfigurationState.saveToBean(SimpleConfigurationState.java:218)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SimpleConfigurationState.configureBean(SimpleConfigurationState.java:241)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.BeanConfigurator.configureBean(BeanConfigurator.java:275)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.PropertyConfiguration.configureService(PropertyConfiguration.java:752)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.SingleNucleusConfigurator.configureService(SingleNucleusConfigurator.java:62)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureService(NucleusNameResolver.java:1319)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.configureAndStartService(NucleusNameResolver.java:1119)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:787)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:569)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.createFromName(NucleusNameResolver.java:550)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.NucleusNameResolver.resolveName(NucleusNameResolver.java:394)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.Nucleus.resolveName(Nucleus.java:2648)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.GenericService.resolveName(GenericService.java:315)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.nucleus.GenericService.resolveName(GenericService.java:367)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.adapter.gsa.xml.TemplateParser.runParser(TemplateParser.java:5498)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at atg.adapter.gsa.xml.TemplateParser.main(TemplateParser.java:5072)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / Caused by :java.lang.ClassNotFoundException: javax.ejb.FinderException
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.security.AccessController.doPrivileged(Native Method)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.Class.forName0(Native Method)
    [exec] **** Error Mon Sep 26 15:15:55 CEST 2011 1317042955407 / at java.lang.Class.forName(Class.java:247)

    It is not able to find the class javax/ejb/FinderException
    Please include one of the jars from below location and run the script again.
    http://www.findjar.com/class/javax/ejb/FinderException.html
    If any class is missing after then, please include that jar as well.
    Peace
    Shaik

  • Error when importing Customer data

    Hi
    I am generating idoc using transaction BD12 in R3. Then I am importing data from XI using import manager with standard map provided by SAP <b>00_DEBMAS05_R3</b> & i get this error "Map Sales Data field to import qualifiers". I have updated all data from R3 check tables before performing the import. Have i missed out any step in import process or is there some thing fundamentally wrong with what i am doing?
    Thanks

    I guess the mapping is incomplete.
    First check what are the display fields for the Qualified table in question.
    Check if all the Display Fields of the concerned Qualified table are mapped.
    Check if Value mapping was performed for all the display fields which require field mapping.
    Right click on the Source fields and create the Compound field for the Sales data if required.
    Then map the Compound field to the Qualified Field.
    Do the Auto mapping for the compound field.
    Go to the import Status tab, you should not get the error now.

  • 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>

  • Using importdata to import xml data into dynamic PDF form

    Hi again,
    Me and my colleagues have a problem using the importData service to import some xml data into an empty PDF form (represented as an XFA input variable).
    In the server log I get the error that Only XDP data is supported for XFA forms, however I only have the xml data and not the entire xdp available.
    Is this really not possible to to (like importing xml data to a form is possible in the Designer when creating forms).
    I hope the scenario is understandable
    Sincerely
    Kim Christensen
    Dafolo A/S
    Denmark
    PS: During the various projects I am working on I keep running into problems...however I am totally new to LiveCycle so I consider this very informative learning steps and appreciate all your help :-)

    Hi again,<br /><br />I have been experimenting a little with both the renderPDFForm and importData services. However I don't seem to be ble to make them work as I  need them to.<br /><br />My scenario is simple, I have one (call it a template xdp/PDF form) and lots of data in xml files (around 1000), that I need to import into the template. Therefore I have set up a "Watched Folder" to take the xml as a document (I guess this is a requirement) and then I need either the renderPDF or importData services to import the xml data into the template.<br /><br />I would like to know how I should setup the services to make this work.<br /><br />When I try to use importdata I setup the following:<br /><br />PDF document: set to be the template i need to import the xml to)<br /><br />Input data: the document variable (an xml file) that is passed to the   Watched Folder<br /><br />Data merged PDF: set to an out xfaform<br /><br />When I do this I get an Coercion error in the server log:<br /><br />2007-11-15 13:27:05,324 ERROR [com.adobe.workflow.AWS] stalling action-instance: 1506 with message: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.<br />     at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:656)<br />     at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:878)<br />     at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:803)<br />     at com.adobe.workflow.datatype.runtime.support.AbstractDataTypeRuntimeHandler.coerceFrom(Abs tractDataTypeRuntimeHandler.java:64)<br />     at com.adobe.workflow.datatype.runtime.support.AbstractComplexDataTypeRuntimeHandler.getNode (AbstractComplexDataTypeRuntimeHandler.java:47)<br />     at com.adobe.workflow.dom.VariableElement.setBoundValue(VariableElement.java:93)<br />     at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionCo ntextImpl.java:729)<br />     at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataWithExpression(PATEx ecutionContextImpl.java:335)<br />     at com.adobe.idp.workflow.dsc.service.SetValueService.execute(SetValueService.java:46)<br />...<br />Caused by: ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: <document state="passive" senderVersion="3" persistent="false" senderPersistent="true" passivated="true" senderPassivated="true" deserialized="true" senderHostId="127.0.0.1/172.16.10.125" callbackId="0" senderCallbackId="7" callbackRef="null" isLocalizable="true" isTransactionBound="false" defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="8039" contentType="application/xml" length="-1"><cacheId/><localBackendId/><globalBackendId/><senderLocalBackendId/><senderGl obalBackendId/><inline><?xml version="1.0" encoding="UTF-8"?><br /><form1><br />  <sub_BlanketTop /><br />  <sub_SubjectTop><br />    <f...</inline><senderPullServantJndiName>adobe/idp/DocumentPullServant/adobejb_server1</s enderPullServantJndiName><attributes file="c:\NCRConvert\ProcessForm\stage\Wx450d4b32843a0b0bcb8ef99e\NCR-00564_dXAE3soH.xml"/ ></document> of type: com.adobe.idp.Document to type: interface org.w3c.dom.Document<br />     at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)<br />     at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)<br /><br />However it is possible to manually import the xml data in Acrobat Professional without any problems.<br /><br />When I use the renderPDFForm with the following settings:<br /><br />Form to render: literal value that points to the template<br /><br />Form data: document variable from watched folder (xml)<br /><br />Content Root URI: repository://<br /><br />With these settings I also get a coercion error, however it does not seem to be exactly the same.<br /><br />Sincerely<br />Kim

  • Transport Error when Importing appset in target system

    We are receiving the below error when importing the appset TEST in Quality system.
    We have include all the objects in the transport by setting UJT_TRANS_CHG to D for all TLOGO objects.
    Any clues to what the problem could be?
    Post-import method RS_AFTER_IMPORT started for APPS L, date and time: 20110519104427
    Post-processing taking place in client 100
    Start of the after-import method RS_APPS_AFTER_IMPORT for object type(s) APPS (Activation Mode)
    Start After Import for AppSet TEST in Client 100 for RFC BI system
    Import Step UPDPTAB completed without errors
    Import Step ADMIN_DEF_UPD completed without errors
    Import Step FILE_SERV_UPD completed without errors
    Import Step DATA_TABLE_UPD completed without errors
    After Import method for AppSet TEST finished successfully
    Start of data checker messages
    Missing File/Dir:
    Missing File/Dir:
    Dimension COSTCENTER's master is empty!
    Dimension DATASRC's master is empty!
    Dimension PROFITCENTER's master is empty!
    BPF: Error reading master data
    Invalid attribute name (ACCTYPE) in dimension (CO_ENTITY)
    BPF: Validation error; Previous step has no matched step region "BR02"
    BPF: Validation error; Previous step has no matched step region "BR05"
    Start of the after-import method RS_APPS_AFTER_IMPORT for object type(s) APPS (Delete Mode)
    Nothing to delete.
    End of after import methode RS_APPS_AFTER_IMPORT (Delete Mode) - runtime: 00:00:00
    Errors occurred during post-handling RS_AFTER_IMPORT for APPS L
    RS_AFTER_IMPORT belongs to package RS
    The errors affect the following components:
        BW-WHM (Warehouse Management)
    Post-import method RS_AFTER_IMPORT completed for APPS L, date and time: 20110519104506
    Post-import methods of change/transport request BPDK900158 completed
          Start of subsequent processing ... 20110519104427
          End of subsequent processing... 20110519104506
    Execute reports for change/transport request: BPDK900158
    Reports for change/transport request BPDK900158 have been executed
          Start of................ 20110519104506
          End of.................. 20110519104506
    Execution of programs after import (XPRA)
    End date and time : 20110519104506
    Ended with return code:  ===> 8 <===

    Hi Naresh,
    Thanks for reply.
    We have checked driver dim and region dim(s) members. Its looks fine. Even though we are facing import error.
    As per basis guidance we have executed program  SE38--> UJA_DATA_CHECKER  on source system appset. And observed there are several errors showing up related to BPFs & Invalid attribute name ACCTYPE for CO_ENTITY dimension.
    If any of you faced similar issue. Please share your input in this regard.
    Regards
    Amit

  • About the exporting and importing xml data file in the pdf form

    Hi all,
    I need help for importing xml data file in the pdf form. When I write some thing in the text field with fill color and typeface (font) and exported xml data using email button. When I imported that xml file in the same pdf file that is used for exporting the xml data then all the data are shown in the control but not color and font typeface. Anyone has suggestion for solving this problem. Please help me for solving this problem.
    Thank you
    Saroj Neupane

    Can you post a sample form and data to [email protected] and I will have a look.

  • SSMS 2012:XML File Query: Importing XML data using a CTE-Incorrect syntax near 'BLOB'?

    Hi all,
    From https://www.simple-talk.com/content/print.aspx?article=1756, I mimicked to create the following sql code to do Importing XML data using a CTE:
    ---Importing XML data using a CTE -----Ad-Hoc XML File Query--simple-talk---1020AM 27 Feb 2015
    ---query the XML Blob using a CTE (pulling from the XML file each time
    USE OPENXMLtesting1
    GO
    With XmlFile (Contents) AS (
    SELECT CONVERT (XML, BulkColumn)
    FROM OPENROWSET (BULK 'C:\XML FilesMicrosoft-Samples\books.xml', SINGLE BLOB) AS XmlData
    SELECT
    FROM XmlFile
    GO
    I got the following message:
    Msg 102, Level 15, State 1, Line 4
    Incorrect syntax near 'BLOB'.
    I have no ideas why it is incorrect in that code statment. Please kindly help, advise and respond.
    Thanks in advance,
    Scott Chang
    P. S. The books.xml file was copied from the Microsoft samples:
    <?xml version="1.0"?>
    <catalog>
    <book id="bk101">
    <author>Gambardella, Matthew</author>
    <title>XML Developer's Guide</title>
    <genre>Computer</genre>
    <price>44.95</price>
    <publish_date>2000-10-01</publish_date>
    <description>An in-depth look at creating applications
    with XML.</description>
    </book>
    <book id="bk102">
    <author>Ralls, Kim</author>
    <title>Midnight Rain</title>
    <genre>Fantasy</genre>
    <price>5.95</price>
    <publish_date>2000-12-16</publish_date>
    <description>A former architect battles corporate zombies,
    an evil sorceress, and her own childhood to become queen
    of the world.</description>
    </book>
    <book id="bk103">
    <author>Corets, Eva</author>
    <title>Maeve Ascendant</title>
    <genre>Fantasy</genre>
    <price>5.95</price>
    <publish_date>2000-11-17</publish_date>
    <description>After the collapse of a nanotechnology
    society in England, the young survivors lay the
    foundation for a new society.</description>
    </book>
    <book id="bk104">
    <author>Corets, Eva</author>
    <title>Oberon's Legacy</title>
    <genre>Fantasy</genre>
    <price>5.95</price>
    <publish_date>2001-03-10</publish_date>
    <description>In post-apocalypse England, the mysterious
    agent known only as Oberon helps to create a new life
    for the inhabitants of London. Sequel to Maeve
    Ascendant.</description>
    </book>
    <book id="bk105">
    <author>Corets, Eva</author>
    <title>The Sundered Grail</title>
    <genre>Fantasy</genre>
    <price>5.95</price>
    <publish_date>2001-09-10</publish_date>
    <description>The two daughters of Maeve, half-sisters,
    battle one another for control of England. Sequel to
    Oberon's Legacy.</description>
    </book>
    <book id="bk106">
    <author>Randall, Cynthia</author>
    <title>Lover Birds</title>
    <genre>Romance</genre>
    <price>4.95</price>
    <publish_date>2000-09-02</publish_date>
    <description>When Carla meets Paul at an ornithology
    conference, tempers fly as feathers get ruffled.</description>
    </book>
    <book id="bk107">
    <author>Thurman, Paula</author>
    <title>Splish Splash</title>
    <genre>Romance</genre>
    <price>4.95</price>
    <publish_date>2000-11-02</publish_date>
    <description>A deep sea diver finds true love twenty
    thousand leagues beneath the sea.</description>
    </book>
    <book id="bk108">
    <author>Knorr, Stefan</author>
    <title>Creepy Crawlies</title>
    <genre>Horror</genre>
    <price>4.95</price>
    <publish_date>2000-12-06</publish_date>
    <description>An anthology of horror stories about roaches,
    centipedes, scorpions and other insects.</description>
    </book>
    <book id="bk109">
    <author>Kress, Peter</author>
    <title>Paradox Lost</title>
    <genre>Science Fiction</genre>
    <price>6.95</price>
    <publish_date>2000-11-02</publish_date>
    <description>After an inadvertant trip through a Heisenberg
    Uncertainty Device, James Salway discovers the problems
    of being quantum.</description>
    </book>
    <book id="bk110">
    <author>O'Brien, Tim</author>
    <title>Microsoft .NET: The Programming Bible</title>
    <genre>Computer</genre>
    <price>36.95</price>
    <publish_date>2000-12-09</publish_date>
    <description>Microsoft's .NET initiative is explored in
    detail in this deep programmer's reference.</description>
    </book>
    <book id="bk111">
    <author>O'Brien, Tim</author>
    <title>MSXML3: A Comprehensive Guide</title>
    <genre>Computer</genre>
    <price>36.95</price>
    <publish_date>2000-12-01</publish_date>
    <description>The Microsoft MSXML3 parser is covered in
    detail, with attention to XML DOM interfaces, XSLT processing,
    SAX and more.</description>
    </book>
    <book id="bk112">
    <author>Galos, Mike</author>
    <title>Visual Studio 7: A Comprehensive Guide</title>
    <genre>Computer</genre>
    <price>49.95</price>
    <publish_date>2001-04-16</publish_date>
    <description>Microsoft Visual Studio 7 is explored in depth,
    looking at how Visual Basic, Visual C++, C#, and ASP+ are
    integrated into a comprehensive development
    environment.</description>
    </book>
    </catalog>

    I found the mistakes I made and I corrected them. The newly revised/corrected code is:
    USE OPENXMLtesting1
    GO
    With XmlFile (Contents) AS (
    SELECT CONVERT (XML, BulkColumn)
    FROM OPENROWSET (BULK 'C:\Temp\books.xml', SINGLE_BLOB) AS XmlData
    SELECT *
    FROM XmlFile
    GO
    It worked: Results
         Contents
    1  <catalog><book.id="bk101"><author>Gambardella.M...
    If I clicked on this, I got a listing of the whole book.xml!!  I don't know what it means.  Please comment and respond.
    Thanks,
    Scott Chang

  • Error when import BI content 3.5.3

    Hi All
    I have error when import BI content 3.5.3 step at Tcode 'SAINT' (file SAPKIBIFIH.car) for mySAP ERP 2004 (ECC 5.0 IDES).
    The error occur in step 3/5 after enter SAINT:Passw request.
    System shown information "<b>Queue SAPKLTHQ10 has not yet been confirmed</b>".
    In step 4/5 sytem shown statue/remarks "<b>The Add-on installation terminated during phase PROLOGUE</b>".
    I think about installation THAI font package at Tcode "SMLT" uncompleted.
    I run report <b>"RSCPINST"</b> at Tcode "SE38" for editing codepage after that the system shown error message "<b>MDMP is not supported foe SAP Business Information Warehouse. Message no.RIN010"</b> Please see sap note 563975.
    <b>Note:</b> When  i import Thai font package "SAPKLTHQ10" using Tcode "SMLT" the system shown error message "TL1277" in define schedule job step.
    Message no. TL137
    Diagnosis
    You want to start the post-import methods for special texts (calendar texts, terminology, and glossary) for language Thai.
    Before this can happen, the system checks whether this server is prepared for this language. The system also checks whether the language environment can be switched dynamically on this server (see ABAP command SET LOCAL LANGUAGE).
    System response
    The system established that the language environment cannot be switched to language Thai.
    The language transport is stopped at this point.
    Procedure
    The switch of the language environment may fail for the following reasons:
    1. The database codepage is not up-to-date.
    2. The codepage information for language Thai is not up-to-date.
    3. Locales for language Thai do not exist, or are invalid, at the operating system level.
    4. The profile parameter zcsa/installed_languages has to be adjusted.
    If an error occurs, proceed as follows:
    1. Find out the name of the server on which the language import job ran. Log on to this server.
    2. Check the language configuration using report RSCPINST. Solve the reported problem there.
    If your system consists of multiple application servers and not all of them have authorization for language Thai, continue the language import on a server that has authorization for language Thai.
    plaese help me to solve this problem.
    thank a lot for all solutions.
    Mooping.

    This is a long story that you write, but your problem seems just that you must "Confirm the queue". Is that correct?
    Without this step no further Support Packages can be inserted into the system. Confirming the queue is done by one of the buttons in the SPAM transaction. Just put the mouse on the buttons and read the quick help to differentiate between the buttons.
    I have never had a problem like this but I think it can happen if, together with the new BI version you also include one or more support packs. This happens automatically if these packages are available, so you may not even have noticed it.

  • Error when importing CO Hierarchies from R/3 DEV to R/3 QAS

    Dear SDN,
    I am getting the following error when importing Cost center and cost element hierarchies from R/3 DEV to R/3 QAS...
    Object OSOA  0COSTCENTER_0101_HIER has not yet been imported successfully
    Object OSOA  0COSTELMNT_0102_HIER has not yet been imported successfully
    Ended with Return code ===8...
    But The two hierarchies were available in R/3 QAS and also i am able to utilise..
    My doubt is if i transport these hierarchies from R/3 QAS to R/3 Production any major issues...
    Now i want to test a data in BW DEV from R/3 Production data...
    So, I am planning to transport These hierarchies from R/3 QAS to R/3 PROD...
    Here we do not have BW QAS...So, getting data from R/3Production to BW DEV and testing...
    After testing Directly use in BW Production...
    So, Please suggest me why when importing these hierarchies errors occuring???
    Help will be greatly appreciated with points...
    Thanks in advance...

    Hi Venkat,
    Please go through the following threads...
    Hierarchy  Transports
    Transporting cost center and profit center standard hierarchies
    /community [original link is broken]://Transporting a hierarchy
    Transport Hierarchy
    Khaja

  • CPM error: Graphic: Invalid XML data format

    Hi guru's
    When I execute a cockpit the system shows the error: "Graphic: Invalid XML data format"
    We have BI 7.0 and SEM-BW 600 SAPKGS6014
    What can I do.
    Thanks
    Jose

    Hi guru's
    I still with the problem, I found a  Note 768114 - Message 'Invalid XML format' if chart should be displayed. the note decribe my proble exactly. But the correction in the note are only until version 400 of SEM any our company is in 600.
    With this clue, maybe you can help me.
    Jose

  • Error when updating the data from DSO to cube

    Hi,
    I am getting the error when uploading the data from the ods to cube.
    The following is the error message.
    Unable to determine period for date 20090101, fiscal year variant Z2: Error #
    How can i solve this issue.
    Regards
    Annie

    Hi ,
    fiscal year variant, go into Customizing for Financial Accounting (FI) under Financial Accounting Global Settings >>>Fiscal Year >>>Maintain Fiscal Year Variant.
    check this link ..
    http://help.sap.com/saphelp_scm41/helpdata/en/50/0d89f2ad919c40b95b9ae7583c8c96/frameset.htm
    http://help.sap.com/saphelp_scm41/helpdata/en/50/0d89f2ad919c40b95b9ae7583c8c96/content.htm
    Regards,
    shikha

Maybe you are looking for

  • Consuming a webservice of MII in Xcelsius 2008

    Hello Everyone ! I have created a webservice in MII 12.1. I tested it in SoapUI. It is working fine. I created a separate webservice using SAP. Tried to consume in Xcelsius 2008. It is also working fine. But, the webservice created in MII 12.1 which

  • Why am I receiving millions of meeting invites since Jan 4th 2014?

    Searched the forum for this issue but could not find anything. I am seeing a pop-up notification 2~3 times every day this week on my iPhone 5s running the latest iOS 7.0.4. Yesterday, the notification was:   "33,554,432 Invitations"  Today, it is dis

  • Unable to create Content Repository

    Hi All, We have installed SAP Content Server6.4 with MAXDB on windows server 2003 IIS6.0 successfuly. After that i have created content repositoy through OAC0 & Category through OACT. When we try to execute Create content repository through CSADMIN w

  • Two string references pointing to the same object

    Look at the following code snippet         String   s1 = "hello";         String   s2 = "world";         String   s3 = "welcome";         String   s4 = "here";         String   s5 = "hello";   They say that references s1 and s5 point to the same obje

  • ICSERVER not running?

    Hi, we are running into the ABAP (BSP) error CX_BSP_WD_HTTP_RESPONSE_ERROR when trying to launch TA CRM_IC in our CRM system. We found SAP note# 722908 which told us that the ICSERVER is not running! The log file os this service contains an entry sta