Error while importing .SCA files in track

Hi Folks,
I tried importing following .SCA files into a nwdi track but it Finished with Errors.
ENGFACADE
ENGINEAPI
FRAMEWORK
WD-RUNTIME
By logs i got information that
'File is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Note: I am trying to setup nwdi track for CE developments and following this  [Document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
Following .SCA files are imported successfully
SAPBUILDT
SAPJEE
SAPJTECHS
Please help me to resolve this issue.
Thanks in anticipation.
Mandeep Virk

Hi John,
Following are the log details
20100309050525 Info   :Starting Step CBS-make at 2010-03-09 05:05:25.0359 -6:00
20100309050526 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before starting the import
20100309050526 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Starting the import now.
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/base.tools.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/com.sap.base.technology.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/deploy.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.j2ee14.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.lm.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.migration.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcbljcoapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcblvsiapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjeappconfigurationapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjecrossapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebcontainerpublic~api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebservicesapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebserviceslib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/webservices.lib.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info   :=================================================================
20100309050611 Info   :buildspace = D01_Demo_D   build request id = 23
20100309050611 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before asking for build results
20100309050611 Info   :waiting for CBS queue activity
20100309050641 Info   :build process already running: waiting for another period of 30000 ms
20100309050641 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Asking for build results now.
20100309050641 Fatal  :processing of build request is not finished successfully, final status is:FAILED (more details in CBS log )
20100309050641 Info   :no confirmation of request 23 because the status is not 'succeeded'
20100309050641 Info   :=================================================================
20100309050641 Info   :Remove software component ENGFACADE from further processing, because archive import failed
20100309050641 Info   :Step CBS-make ended with result 'error' at 2010-03-09 05:06:41.0702 -6:00
- Mandeep Virk

Similar Messages

  • Error while importing sca file in local development

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

  • 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 importing swf file in to Crystal Xcelsius Designer 4.5

    help me...., Error while importing swf file in to Crystal Xcelsius Designer 4.5

    I read in the book called "CRYSTAL XCELSIUS for DUMMIES" on page 243 under topic called Nesting a Dashboard within another Dashboard.
    sorry i used the wrong word embed, here i am importing the swf using image component.
    My requirement is somethis like this parent child dependency menu.
    eg: i have to two tabs 1)alphabets 2) Numerics  First levet menu
    if you click alphabets tab then the following menu A/B/C/D/..... Z i have diff charts.. under each alphabet.
    If you click numberic tab then the follwing menu should one/two/three/.......ten  here also i have diff charts under number
    in over to avoid complexity in dynamic visibility i divided the into 3 dashboards.  1- alphabets 2- number and 3 -importing both swfs.. everything works fine except first tab and last tab under alphabets and numerics.
    If some one help me with some alernative ... would be great.
    Thanks

  • Error while adding .sca files in DI Track

    Hi,
    I have 4 different tracks in DI for:
    1. ESS
    2.  MSS
    3.  A
    4.  B
    The software component in A and B is same.
    Now i have to add CAF related SCA files in Track A.
    I add those as dependencies. After adding, i also synchronize the dependencies.
    When i click on save, it doesnt display popup for save. Instead, a popup is displayed regarding "Where-Used Check" stating" Following runtime systems already used elsewhere in CMS domain" and below this displays the list of the remaining 3 tracks. It has 2 buttons: continue and cancel. If i continue on cancel, it gives the error:
    Unexpected error; inform your system administrator: User not authorized. (Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<hostname>:50100/CBSWebService/CBSHttpSOAP?style=rpc")
    I am not able to figure out the reason for this.
    Thanks & regards,
    Anupreet

    Hi,
    Please check out these links on the same issue -
    Re: HTTP/1.0 401 Unauthorized
    Re: MSS PCR Error
    http://help.sap.com/saphelp_nw04/Helpdata/EN/ab/08194116bfb167e10000000a155106/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d9a978-5f59-2a10-1cae-d4cf0c92a0f2
    Hope the above links would solve the issue.
    Regards
    Lekha

  • Error while importing PAR file from local system.

    Hi Experts,
    While importing PAR file into my NWDS, I am encountered by some strange error.
    Please refer below screenshot for your reference.
    After clicking on "OK" button of the above error popup, another popup emerge with different error, please find below the screenshot for this error.
    Please let me know the reason and resolution of this error. It will be very helpful for me.
    Thanks in advance.
    Thanks and Regards,
    sarvesh Agarwal

    Hi ,
    Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
    x.par is enough to import not x.par.bak.
    Thanks,

  • Error while importing WSDL file created in JDeveloper inside BS

    Hi All,
    I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
    The error in OSB is 'The Resource Mapped Does not exist'

    Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
    Regards,
    Anuj

  • Error while importing zip file for second time to B2B through ant script

    [echo] args=import
    importstatus:
    [echo] Commandline arguments 1: [import]
    [echo] Import with overwrite=true
    [echo] B2BCommandLineUtility: importRepository: Error messages:
    [echo] MDS-00521: error while reading document /soa/b2b/tpa_JOvrtiV-7030143
    019445112136.xml from metadata repository
    [echo] MDS-00520: failure to read document /soa/b2b/tpa_JOvrtiV-70301430194
    45112136.xml because it is not in the metadata repository
    [echo] MDS-00911: Document with name "/soa/b2b/tpa_JOvrtiV-7030143019445112
    136.xml" and version 16 does not exist in the repository.
    [echo] ORA-01403: no data found
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
    [echo] ORA-06512: at line 1
    [echo]
    [echo] ORA-01403: no data found
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
    [echo] ORA-06512: at line 1
    [echo]
    [echo] ORA-01403: no data found
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407
    [echo] ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603
    [echo] ORA-06512: at line 1
    [echo]
    [echo]
    Can anybody plz help???
    Thanks in Advance!!!

    Hi,
    Even I am getting the same error while importing the .zip file for the second time through B2B console-->Administration-->Import/export tab.
    But again it works for the third time..
    Error Message:
    Import of file OriginalProject.zip failed. MDS-00521: error while reading document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml from metadata repository MDS-00520: failure to read document /soa/b2b/tpa_MnjhBHh-70301432125893445241.xml because it is not in the metadata repository MDS-00911: Document with name "/soa/b2b/tpa_MnjhBHh-70301432125893445241.xml" and version 34 does not exist in the repository. ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1 ORA-01403: no data found ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 407 ORA-06512: at "DEV_MDS.MDS_INTERNAL_SHREDDED", line 603 ORA-06512: at line 1
    Please help...

  • Error while Importing Wsdl file of of 189 KB to XI Server.

    Hi,
    I am working on SAP NW 7.0.This is the Error I am getting while importing wsdl file of 189 KB to XI server.
    Error :
    Connection Interrupted.
    Connection to server lost.
    You can log on again once the server is available again.
    Do you want to log on again.
    Asking for password.
    Another WSDL file of 8 KB successfully imported to XI server.
    Please provide your reply on this asap.
    Regards
    Nilesh.

    check this,
    Note 1334387 - WSDL Import wizard fails with connection timeout exception
    Regards,
    Ravi

  • Error while Importing MDL File

    Hi All,
    While Importing a MDL File, I am getting the following Error. Can someone help me asap.
    mport started at Apr 6, 2010 10:20:09 AM
    Project "PUBLIC_PROJECT"
    Error occurred importing from file "C:\oracle\product\10.2.0\db_2\owb\bin\admin\ETLDEV-20100405_2210.mdl".
    oracle.wh.util.Assert: Repository Connection Error: The connection to the repository was lost, because of the following database error: Closed Connection Exit OWB without committing.
         at oracle.wh.util.Assert.owbAssert(Assert.java:51)
         at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:186)
         at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:156)
         at oracle.wh.ui.common.UIExceptionHandler.handle(UIExceptionHandler.java:152)
         at oracle.wh.util.SQLExceptionHandler.handle(SQLExceptionHandler.java:65)
         at oracle.wh.repos.pdl.lock.OracleLock.release(OracleLock.java:153)
         at oracle.wh.repos.pdl.lock.OracleLockOptimizer.unlock(OracleLockOptimizer.java:138)
         at oracle.wh.repos.pdl.lock.LockOperation.execute(LockOperation.java:90)
         at oracle.wh.repos.pdl.lock.LockOperationSet.execute(LockOperationSet.java:51)
         at oracle.wh.repos.pdl.lock.LockMaster.downgradeToExclude(LockMaster.java:222)
         at oracle.wh.repos.pdl.lock.LockMaster.destroyLockHolder(LockMaster.java:199)
         at oracle.wh.repos.pdl.lock.RequestToHolderMap.endRequest(RequestToHolderMap.java:83)
         at oracle.wh.repos.pdl.lock.RequestToHolderMap.closeFolderForCreate(RequestToHolderMap.java:39)
         at oracle.wh.repos.pdl.lock.LockModuleImpl.closeFolderForCreate(LockModuleImpl.java:61)
         at oracle.wh.repos.pdl.dispatcher.EventDispatcherImpl.closeFolderForCreate(EventDispatcherImpl.java:174)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLLockManager.releaseMDLImportLocks(MDLLockManager.java:456)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.releaseImportLocks(MDLImport.java:1531)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1981)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
         at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.internalRunImport(MDLUpgradeImportTransaction.java:218)
         at oracle.wh.ui.metadataloader.Import.MDLUpgradeImportTransaction.run(MDLUpgradeImportTransaction.java:319)
    Thanks,
    SM

    Did the instance go down whilst doing this?
    Is there more to the log before where you started it?
    Cheers
    David

  • "DBSTATUS_UNAVAILABLE" Error while importing Excel File

    Hello,
    I am getting following error while importing data from Excel 2003 to SQL server using SSIS 2008,  [Excel Source [1]] Error: There was an error with output "Excel Source Output" (9) on component "Excel Source" (1). The column status
    returned was: "DBSTATUS_UNAVAILABLE".
    If i open the excel file and done any editing then the same file loads without any issue. Can you guide me why it's  happening ? , i have edited "TypeGuessRow" property to 0 , IMEX = 1 but no help.
    Thanks

    Hi Ved_Prakash,
    The error is generic and can occur due to various causes. In order to troubleshoot this issue, I need to clarify some information:
    Could you please post some sample data for that column in the error message?
    Have you modify some properties after accessing data from that Excel file?
    Since the error message is incomplete, could you post other error messages from the Output pane?
    Besides, we can also use
    SQL Server Import Export Wizard to import Excel into SQL Server database.
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • 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 importing par file

    dear Experts,
    i am facing a problem while importing par.bak file. the error message comes
    "indexed store transactions did not commit properly"
    Reason
    sorry an error occurred creating new project
    then once i click ok
    i get the error
    com.sap.portal.plugins.config-archiver caused exception during the "unpack" operation
    any one has the solution for this

    Hi ,
    Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
    x.par is enough to import not x.par.bak.
    Thanks,

  • Error while Importing lcmbiar file

    I had created the universe & needed report , now I want to export the same and import into another BO Server. As a first step , I exported all the needed files to lcmbiar file and while importing in the new server , I receive the below error
    Sorry, Promotion management application is unable to process your request.
    The error from the server is: while trying to invoke the method com.businessobjects.lcm.core.ILCM.getAdminManager() of an object loaded from local variable 'lcmEngine'
    Note : Server OS &SP are both same & BO version is also same on both the servers.
    Please hlep

    Did the instance go down whilst doing this?
    Is there more to the log before where you started it?
    Cheers
    David

  • Error while importing tpz file into XI Design

    Hi All,
    When i am trying to import latest exported tpz file from Dev system into Q system i am getting below error.
    Also the tpz file i am importing , with same file name already i have imported earlier into Q system through other Dev system. Now i am importing the exported file through prod fix environment dev system. Please help me , how to import the file without this error. Also, how to avaoid duplicate file name for importing tpz files or overwrite exiting imported tpz file which is having same file name.
    Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00136623) violated  at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.executeBatch(Oracle10gPreparedStatement.java:100) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:991) at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:270) at com.tssap.dtr.pvc.basics.transaction.StatementReleasingConnection.executeBatch(StatementReleasingConnection.java:297) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.fireSQLBatches(DefaultIntegrator.java:1072) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.executeDBUpdates(DefaultIntegrator.java:384) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.integrate(DefaultIntegrator.java:337) at com.tssap.dtr.pvc.versionmg.VersionSet.integrate(VersionSet.java:183) at com.sap.aii.ib.server.pvcadapt.ImmutableVersionSet.integrate(ImmutableVersionSet.java:197) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl._integrateUnconditionally(VersionSetIntegratorImpl.java:300) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:119) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52) at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261) at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174) at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480) at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:546) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362) at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151) at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75) at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730) at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Thanks in advance.
    Rajesh
    Edited by: rajesh amrabad on Sep 11, 2008 10:35 PM

    In addition to abobe answers,
    Keep this .tpz file at below mentioned location
    \usr\sap\<SID>\SYS\global\xi\repository_server\import\XI7_0_SAP_BASIS_7.00_09_00.tpz
    then login to the IR and peoceed as Tools -
    > import design objects. Her you will get this .tpz file, just import it.
    follow the steps given in this link and check if you are doing the correct thing.
    http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
    The steps that you require are listed below,
    1) You must have the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER to be able to export and import XI content.
    2)You import the XI content by first copying the provided export files into an import directory on the host of the Integration Builder and then importing the files into the Integration Repository.
    3)Copy the export files into the import directory for the Integration Repository (<systemDir>\xi\repository_server\import).If the files are packed, you must unpack them before importing.The actual export files have the extension .tpz. You must not unpack these files.
    4)The import directory is created the first time you call the Integration Builder.
    5)Start the Integration Builder and call the Integration Repository.
    To do this, perform the following steps:
    a. Log on to the SAP system on which your Integration Builder has been installed.
    b. Open the Integration Builder start page by calling it either from your user menu or with Transaction SXMB_IFR.
    c. Choose Integration Repository.
    Choose Tools u00AE Import design objects to import the XI content.
    6)Only the files from the import directory are offered to be imported. The sequence in which
    you import the export files is not important.
    7)After a successful import, the Integration Builder moves the imported TPZ files into the directory <systemDir>/xi/repository_server/importedFiles. The support package stack of imported software component versions is displayed on the Details tab page for the relevant software component version in the Integration Builder. If an error occurs, this information is important for support.
    Hope i have been of some help.

Maybe you are looking for