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.

Similar Messages

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

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

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

Soap response Error when processing XML CF.

Hello,
I have problems with soap response and wondered if you could give some advice.
Every time I send my message via soap I get the following error:
com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error when processing XML CF.
Is it possible that the communication is aborted and my response message mapping is never started?
(Additional info: I tried to create an integration process and am not able to evaluate the response.)
Thanks a lot for your help.
Regards,
Julia

hi,
do you see any more error details in :
http://xiserver:port/MessagingSystem/monitor
did you check logs in visual admin ?
>>>>Is it possible that the communication is aborted and my response message mapping is never started?
yes - if the response is not ok the mapping may not be started
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

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 "Queue SAPKLTHQ10 has not yet been confirmed".
In step 4/5 sytem shown statue/remarks "The Add-on installation terminated during phase PROLOGUE".
I think about installation THAI font package at Tcode "SMLT" uncompleted.
I run report "RSCPINST" at Tcode "SE38" for editing codepage after that the system shown error message "MDMP is not supported foe SAP Business Information Warehouse. Message no.RIN010" Please see sap note 563975.
Note: 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

Error when importing ST_PI 2005_1_620

Hi
I am getting error when importing ST-PI 2005_1_620 in of our system.
Here is the details on the log:
Follow-up action PRGN_AFTER_IMP_ACTGROUP_ACGR for ACGR L started at 20081027152321
Invalid object D_MD_DATA in role SAP_SDCCN_ALL deleted
Invalid object D_MD_DATA in role SAP_SDCCN_ALL deleted
Invalid object D_MD_DATA in role SAP_SDCCN_ALL deleted
Invalid object D_MD_DATA in role SAP_SDCCN_ALL deleted
Errors occurred during post-handling PRGN_AFTER_IMP_ACTGROUP_ACGR for ACGR L
PRGN_AFTER_IMP_ACTGROUP_ACGR belongs to package S_PROFGEN
The errors affect the following components:
BC-SEC-USR-PFC (Authorization and Role Management)
Follow-up action PRGN_AFTER_IMP_ACTGROUP_ACGR for ACGR L ended at 20081027152325
Looking for your expert advise.
Thanks

Invalid object D_MD_DATA in role SAP_SDCCN_ALL deleted
Have you reviewed the role?
Regards
Juan

ORA-907 ERROR WHEN IMPORT (COMMENT 처리)

제품 : ORACLE SERVER
작성날짜 : 1997-10-15
ORA-907 ERROR WHEN IMPORT (COMMENT 처리)
========================================
ORA-907: missing right parenthesis error
이 error 는 export 한 table 을 create 시 comment 를 사용한 경우 발생하는 ORACLE error 이다.
이는 version 8.0.4 에서 fix 되었다.
이를 해결하기 위해서는 미리 table create script 를 돌려 temp_table 을
create 하십시오.
이 때 comment 를 모두 뺀 상태로 create 한다. 또는 /* */ 는 괜찮다.
이후 INSERT INTO temp_table select * from original_table ;
을 실행합니다.
즉 original_table 을 temp_table 로 copy 한 후
drop table original_table;
rename temp_table to original_table ;
을 한 후 table을 다시 export해서 다른 machine으로 import한다.
또 이 -- 를 없애는 방법으로 아래의 C program을 이용할 수 있다.
/* file name : cnvt_dmp.c
* This program is to covert double dash remark expression
* C language stype remark expression.
#include <stdio.h>
#define MAXWORDS 4
char s_reserve[4][100]={ "NOT NULL", "CONSTRAINTS",")",","};
int dash2remark();
void main(argc,argv)
int argc;
char *argv[];
FILE f_in, f_out;
int i,j,lreserve;
int chr1,chr2;
char str1[100],str2[100],str3[100];
if( argc != 3 ) {
printf(" usage : cnvt_dmp infile.dmp outfile.dmp \n");
exit(0);
if( (f_in = fopen(argv[1],"r")) == NULL ) {
printf("could't open the source file.: %s\n",argv[1]);
exit(0);
if( (f_out = fopen(argv[2],"w")) == NULL ) {
printf("대상화일을 생성할 수가 없습니다.\n");
exit(0);
j = i = 0;
while( (chr1 = fgetc(f_in)) != EOF && !ferror(f_in)) {
if( chr1 == 'D' ) {
str1[0]='D';
fputc(chr1, f_out) ;
for(i=1;i<7;i++) {
chr1 = fgetc(f_in);
str1[i] = chr1;
fputc(chr1, f_out) ;
str1[7] = 0;
strcpy( str2,"DEFAULT");
if ( strcmp( "DEFAULT",str1) == 0 ) {
lreserve = 0;
i =0;
while( (chr2 = fgetc(f_in))!= ','){
if ( chr2 == ')') break;
str2[i] = chr2;
if ( chr2 == '-' )
lreserve = 1;
i++;
str2[i] = chr2;
str2[i+1] = 0;
printf(" lreserv => %d, str2=>%s\n",lreserve,str2);
if (lreserve) {
dash2remark(f_in,f_out,str2);
else {
for( i=0;i<strlen(str2);i++) fputc(str2,f_out);
else {
fputc(chr1, f_out );
fclose(f_out);
fclose(f_in);
return;
int dash2remark( f_in,f_out,str)
FILE f_in,f_out;
char *str;
int i,j,start_pos=-1,end_pos=-1;
for( i=0; i < strlen(str); i++ ) {
if ( str[i] == '-') {
start_pos = i;
for( j =0 ; j < MAXWORDS; j++){
if (strncmp(s_reserve[j],str+i,strlen(s_reserve[j]))== 0){
end_pos = i;
if ( start_pos > 0 ) {
for(i=0;i< (start_pos-1); i++)
fputc( str[i],f_out);
fputc('/',f_out); fputc('*',f_out);
for(i =i+2;i<(end_pos-1);i++)
fputc(str[i],f_out);
fputc('*',f_out); fputc('/',f_out);fputc(' ',f_out);
for(i;i<strlen(str);i++)
fputc(str[i],f_out);
else {
for(i=0;i<strlen(str);i++)
fputc(str[i],f_out);
return(1);
이상입니다.

Hi, i think that the problem is around the rollback segments.The solution is bring other rollback segments ONLINE state, if not exist others rollbackup,then you need create the other rollback segments and bring online state.
If you need more information, you will must see the next DOC-ID on Metalink site,
Note:121971.1
Luck.
Have a good day.
Regards.

"error when importing object" when selecting variant

Hello,
we recently migrated from 4.6 to 4.7.
For some programs, when selecting a variant, this gives a runtime error, like
Error when importing object "C131A2"
What is the cause of this? Because the values in the variant aren't valid anymore?
How can this be solved?
Thanks in advance for the help

Glad to help - you'll likely have to run it after every upgrade (for different reports).
Rob

Error when importing from Excel in SAP

Hello experts,
My gets error when importing price list using the import form Xl menu :
(-1200) DBMCconnBase::EndTransaction SQLEndTran sqlState 08S01, nativeErr: 0, errText:[Microsoft][SQL Native Client] Communication link failure
This happens only when connected with SAP Client, it never happens when connected in terminal server directly on SAP server.
Server 2003, MSSQL 2005 SP2
SAP 2007 Sp01 PL08 HF01
This has always been working before, it has stopped working when he changed the motherboard 3 weeks ago. Nothing else have changed.
Any idea where to look at?
Thanks!
Chris

hello Gordon,
Thanks for your answer. that would have probaly fix the issue
my techs fixed the issue by doing the 2 following thinks, i don't know if only one of them would have fix it.
1. in the boot.ini file there was a /3G in the end, restricting the memory to 1G for the OS. The tech deleted it.
2. in management studio, the technician changed the memory reserved for sql from 9/12 to 14/16Gb
there was probably not enough RAM available for the import.
since that change it works well.
Thanks again!
Christophe

Org.apache.jasper.JasperException; JCO error when Importing SAP Roles in C

Hello experts,
I have installed BOXI 3.1 SP3, Integration kit SP2, BW/BI 7.0 and ECC 6.0 on Windows 2008/64bit.
My goal is to import the roles into CMS from SAP BW/BI but getting the follwoing errors:
JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc
C:\Windows\SysWOW64\sapjcorfc.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform.
java.library.path [C:\Windows\SysWOW64\;D:\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\]
org.apache.jasper.JasperException
I followed the note 1292144 - JCO error when Importing SAP Roles in CMC,but unfortunately without success.
I installed SAP JCo Release 2.1.9 (64bit)
Best regards
Lutz
Edited by: Lutz Heinrich on Aug 12, 2010 4:17 PM

Install the 32bit version of the Java connector. BOBJ is 32bit so even on 64bit Windows you need the 32bit version of the Java Connector.
Regards,
Stratos

CL_SFW_SYSTEM_SETTINGS error when importing SPs

When we want to import the support packages SAP_BASIS, SAP_ABA, SAP_BW,
PI-BASIS untill packages level 7 ( we come from level 4) and the HR
untill package level 26 we run into the short text error when importing
the basis, aba, pi-basis and bw package.
I tried to use the following notes:
1281321 but this gives the error: DEQUEUE_ENQBADIIMPL_ENH
1483283 but this fails also as when I perform tp unlock_EU <SID>
pf=/usr/sap/<sid>trans/bin/TP_DOMAIN_<SID>.PFL it tells me it need to be done
via SE03.
1532661 this one sents me to note 1414700 and 1366282 but the last ones
sents you back to 1483283 and note 1414700 when I want to implement it
with snote it tells me I need to use transaction SE03 for system settings.
Is there any other option to get this issue fixed? as we need to upgradesome other systems aswell with these support packages
Dump message is:
Runtime error SYNTAX_ERROR
Datum en tijd 27.06.2011 14:05:47
Korte tekst
 Syntax error in program "CL_SFW_SYSTEM_SETTINGS========CP ".
Wat is er gebeurd?
 Error in the ABAP Application Program
 The current ABAP program "CL_SFW_RO_FACTORY=============CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
 The following syntax error occurred in program
 "CL_SFW_SYSTEM_SETTINGS========CP " in include
 "CL_SFW_SYSTEM_SETTINGS========CCIMP " in
 line 215:
 "Type "SFW_BF_STATE_CHANGE" is unknown"
 The include has been created and last changed by:
 Created by: "SAP "
 Last changed by: "SAP "
 Error in the ABAP Application Program
 The current ABAP program "CL_SFW_RO_FACTORY=============CP" had to be
 terminated because it has
come across a statement that unfortunately cannot be executed.
enanalyse
The following syntax error was found in the program
CL_SFW_SYSTEM_SETTINGS========CP :
"Type "SFW_BF_STATE_CHANGE" is unknown"
Startpunt van runtime error
 Programma CL_SFW_RO_FACTORY=============CP
 Include CL_SFW_RO_FACTORY=============CCIMP
 Regel 1.889
 Moduletype (METHOD)
 Modulenaam INIT
1862 obj = obj.
1863 ENDMETHOD. "create_object
1864
1865 method get_instance_for_locals.
1866 create object reg.
1867 reg->obj_factory = factory.
1868 ENDMETHOD. "get_instance_for_locals
1869
1870 ENDCLASS. "lcl_sfw_obj_registry IMPLEMENTATION
1871
1872
1873 ----
1874 * CLASS lcl_sfw_system_settings IMPLEMENTATION
1875 ----
1876 *
1877 ----
1878 class lcl_sfw_system_settings implementation.
1879
1880 method get_instance.
1881 if ( singleton is initial ).
1882 create object singleton.
1883 singleton->init( ).
1884 endif.
1885 instance = singleton.
1886 ENDMETHOD. "get_instance
1887
1888 method init.
>>>>> me->system_settings = cl_sfw_system_settings=>get_instance( ).
1890 ENDMETHOD. "init
1891
Edited by: C. Bults on Jun 27, 2011 2:35 PM
Removed customer system name

The following is the solution.
Symptom
When you import the Support Packages SAP_BASIS 7.00 Support Package 14 and
Support Package16 in a queue, the runtime error SYNTAX_ERROR occurs in
class CL_SFW_SYSTEM_SETTINGS (program CL_SFW_SYSTEM_SETTINGS========CP).
More Terms
Syntax error, CL_SFW_SYSTEM_SETTINGS, SPAM, SYNTAX_ERROR,
CL_SFW_SYSTEM_SETTINGS========CP
Cause and Prerequisites
This problem is due to a program error.
Solution
Option 1:
Import Support Package 14 and Support Package 16 in separate queues.
Option 2:
After the error mentioned above occurred, regenerate the enhancement spot
SFW_SWITCH_CHANGED in transaction SE18.
To do this proceed as follows:
1. Call transaction SE18.
2. Enter the enhancement spot SFW_SWITCH_CHANGED.
3. Choose "Display".
4. Choose the menu option "Enhancement Spot -> Activate".
You can now import the queue using the Support Package Manager

Error when importing object P_lis

Hello Experts ,
I have a task assigned to me where i have to write a program to get all the reports and their variants( variants without space and non obselete variants)
When i am trying to access the variant SDCAS_ADRSEL , I am getting a dump "Error when importing object P_lis ". It has got only one variant JOJO1 in the vari table . Please help me out with this.

Hi Aditya,
You might need to provide a few more details on the dump.
I.e.
Exact details of the error that occured.
Where the error occurred
You can grab these out of the dump in ST22. That should help people out, to help understand what you are doing, as it's not really clear from your current description.
Cheers,
Katan

Error when importing XML

Similar Messages

Maybe you are looking for