MyEclipse configuration jdk1.7 run-time error

My operating system is: fedora 18/32 bit
MyEclipse version is: 10
1. First I uninstall the system comes with: open - jdk1.6 [forced discharge]
2. Then from oracle website and download the latest version of the jdk1.7
3. I am in terminal execution javac, and Java compiler take package statement Java files can be normal operation.
4. When I will jdk1.7 [local system, not MyEclipse own] attached to the MyEclipse and no error, when I was in MyEclipse inside implementation class, tip: could not find the main class or unable to load.
Question:
Please inform me about how to install your own MyEclipse additional the JDK. Or how to repair this problem? thank you
The Java file is as follows:
package com.w1520.test
public class Test{
public static void main (String []args){
            System.out.println("Hello World");//
Exception:
Exception in thread "main" java.lang.NoClassDefFoundError: JavaDemo (wrong name: com/w1520/JavaDemo/JavaDemo)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)Edited by: 989477 on 2013-2-21 上午3:15

I agree with gimbal. Find a MyEclipse support forum.
Moderatpr action: I'm locking this thread.

Similar Messages

  • Interface Mapping run time error...java.lang.nullpointerException  thrown

    Hi,
    I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
    Interface Mapping run time error...java.lang.nullpointerException  thrown during application mapping.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>CAMEL_BS_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>Camel_BService_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
      <SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
      <SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
      <SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20070108</SAP:Date>
      <SAP:Time>224350</SAP:Time>
      <SAP:Host>gbdci550</SAP:Host>
      <SAP:SystemId>PI7</SAP:SystemId>
      <SAP:SystemNr>03</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>DB6</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>014</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
      <SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>168</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>67</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>
    Please I request to give me some hint how to troubleshoot this issue.
    Thanks a lot,
    Srujan

    Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
    i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
    Here is the Java exception
    Mappage d'interface
    Can someone be helpful for that ?
    Regards
    Laurent
    Message was edited by:
            Laurent Gitton

  • Run time error while testing a service through transaction SICF/SOAMANAGER

    Hi all,
    We created a service for publishing the function module in web services through WSDL. When we try to test the service using SICF transaction / SOAMANAGER transaction, we get a run time error.
    We are not sure whether any other  settings or steps required for testing the web services..
    Could you please let us know which steps/configurations we are missing?
    Details of the run time error.
    Service cannot be reached
    What has happened?
    URL http://in.ap1.sy.com:8000/wsnavigator call was terminated because the corresponding service is not available.
    Note
    The termination occurred in system ECC with error code 404 and for the reason Not found.
    The selected virtual host was 0 .
    What can I do?
    Please select a valid URL.
    If you do not yet have a user ID, contact your system administrator.
    ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:J-i:INSISCSAPIDES_ECC_00-v:0-s:404-r:Notfound
    HTTP 404 - Not found
    Your SAP Internet Communication Framework Team
    Thanks
    Siva

    Please ask you Basis admin to perform the following.
    1) Check wether the Java Stack ( Portal, BI system etc) is avaliable in your landscape.
    2) Execute tcode SOAMANAGER in ECC system. This will take you to a new browser where you have to login with your SAP username and password. Under SOA MANAGEMENT you can see Technical Configuration tab>click on System Global Settings>and select Access Information J2EE server. Here provide the hostname and the port number. Save the entries.
    3)Execute tcode SMICM>Goto>Services. Here you can check for the HTTP Service Name/Port number
    4) Activate the required services from tcode SICF
    Thanks,
    Sridhar

  • Run time error while creating Ecommerce Order

    Dear Friends,
    we are using ECC 6.0, Ecommerce 5.0 applications run internet sales.
    After selecting the requried products from the product catalog while trying to save the order I am getting a Run time error and also my session is getting logged out of the web shop.
    I have searched the threads on similar issue, but found no clue yet..
    Any help is highly appreciated.
    Regards
    Sadhu Kishore

    #1.5 #005056A31282001C0000000400001AD800047FB93365B5C7#1266333314895#/Applications/BusinessLogic#sap.com/crmentitlementinquiry#com.sap.isa.core.jmx.ext.ExtBootstrapper#Viw~t0yxJv!nzcjy*!6#67##n/a##157475101b0e11dfb011005056a31282#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/BusinessLogic#Java###Error in CCMS reporting: #1#unable to register MBeans#
    24309   #1.5 #005056A3128200280000000000001AD800047FB938DA2ACD#1266333406410#/Applications/BusinessLogic#sap.com/crm~b2c#com.sap.isa.core.init.InitDescription.getInitializable#Guest#0##n/a##4c1152a01b0e11df8c0b005056a31282#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.advisor.backend.tst.AdvisorBackendTST#
    24310   #1.5 #005056A31282002A0000000000001AD800047FB93AB6F382#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Administrator#129##n/a##5eb1b1c01b0e11df9db4005056a31282#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
    24311   #1.5 #005056A31282002B0000000000001AD800047FB93AB6FCE4#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c11b0e11dfb98f005056a31282#Thread[Thread-129,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
    24312   #1.5 #005056A31282002C0000000000001AD800047FB93AB6FF9E#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c21b0e11dfa58b005056a31282#Thread[Thread-130,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
    24313   #1.5 #005056A31282002F0000000000001AD800047FB93BC6D909#1266333455473#/Applications/BusinessLogic#sap.com/crm~cviews#com.sap.isa.core.init.InitDescription.getInitializable#Administrator#133##n/a##694fbe101b0e11dfcc96005056a31282#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.useradmin.handler.UseradminInitHandler#
    24314   #1.5 #005056A3128200330000000000001AD800047FB93DD62A70#1266333490035#/Applications/Common/Infrastructure#sap.com/crmicss_b2c#org.apache.commons.digester.Digester#Guest#0##n/a##7de97c301b0e11df9146005056a31282#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#org.apache.commons.digester.Digester#Java###system.forward.info#1#com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crmicss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)(:main:, row=0, col=0) -> com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crm~icss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)#
    24315   #1.5 #005056A3128200220000001000001AD800047FB961D04BAD#1266334093676#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.maintenanceobject.backend.MaintenanceObjectHelper#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/Applications/Common/Infrastructure#Plain###Cache already initialized#
    24316   #1.5 #005056A3128200220000001200001AD800047FB961F0F65E#1266334095816#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24317   #1.5 #005056A3128200220000001300001AD800047FB961F1C37B#1266334095879#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24318   #1.5 #005056A3128200220000001400001AD800047FB961F25A6B#1266334095910#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24319   #1.5 #005056A3128200220000001500001AD800047FB961F2E857#1266334095941#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24320   #1.5 #005056A3128200220000001600001AD800047FB961F403B4#1266334096019#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24321   #1.5 #005056A3128200220000001700001AD800047FB961F43A81#1266334096035#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24322   #1.5 #005056A3128200220000001800001AD800047FB961F46D0E#1266334096051#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24323   #1.5 #005056A3128200220000001900001AD800047FB961F49D86#1266334096066#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
    24324   #1.5 #005056A3128200340000000000001AD800047FB962954A0E#1266334106598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.DocumentHandler#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.isa.isacore.DocumentHandler#Plain###b2b.dochandler.warn.notontop#
    24325   #1.5 #005056A3128200290000004400001AD800047FB962D270BC#1266334110598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
    24326   #1.5 #005056A3128200350000000000001AD800047FB963A12DA7#1266334124145#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_5##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
    24327   #1.5 #005056A3128200320000000100001AD800047FB963FE1C13#1266334130239#/Applications/BusinessLogic#sap.com/crm~b2b#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: 'CMRCV'
    24328   null
    24329   #parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null' 
    24330   Properties: {lang=en, passwd=?, sysnr=00, client=020, user=uname, ashost=hostXX, jco.client.type=A, maxcon=100, codepage=1100}
    24331   Client not connected#
    24332   #1.5 #005056A3128200320000000300001AD800047FB963FE781C#1266334130271#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.action.order.MaintainBasketSimulateAction#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###A runtime exception occurred on the highest level#
    24333   #1.5 #005056A3128200320000000500001AD800047FB963FEEFEB#1266334130302#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.core.util.MessageListDisplayer#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###An exception has occurred: .#

  • While creating a student through piqstc getting abap run time error

    Hi Experts,
    I am new to SLCM,
    By following Micheal Fan's Basic configuration document,
    I have done the basic configuration required  for creating a student & maintaining  the student file,
    But while trying to create a student through PIQST00/PIQSTC getting abap run time error,
    Attaching the txt file for complete view of abap error.
    Please guide how to resolve this error.
    Regards,
    Prashanti Swain

    Hi Rob,
    Thanks a ton, for your quick reply,
    But I have not understood the reason of the issue.
    As i said I followed Micheal Fan's Document for configuration,
    in that document there is no configuration  step is defined for Vendor master data.
    Could you please explain it in a more detail way.
    Regards,
    Prashanti Swain

  • While doing SO, im getting run time error - reg;

    Hi,
    While doing sales order and whenever im doing save its  getting runtime error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    Short dump has not been completely stored (too big)
    Short text
        The current application triggered a termination with a short dump.
    What happened?
        The current application program detected a situation which really
        should not occur. Therefore, a termination with a short dump was
        triggered on purpose by the key word MESSAGE (type X).
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        Short text of error message:
        Maintain the current CRM release (table CRMPAROLTP)
        Long text of error message:
         Diagnosis
             Various transfer errors occur when transferring SAP sales orders to
             CRM or there is no status update or the status update has errors
             when transferring from CRM to the SAP system. This is caused by an
             incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
             no entry is maintained at all.
         System Response
             To avoid data inconsistencies, this message causes a short dump.
         Procedure
             Maintain table CRMPAROLTP in your SAP system as is described in SAP
             Note 691710 and then repeat the process again.
         Procedure for System Administration
        Technical information about the message:
        Message class....... "V3"
        Number.............. 302
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "MESSAGE_TYPE_X" " "
        "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
        "BAPIDATEN_ERMITTELN"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
        3. If the problem occurs in a problem of your own or a modified SAP
        program: The source code of the program
           In the editor, choose "Utilities->More
        Utilities->Upload/Download->Download".
        4. Details about the conditions under which the error occurred or which
        actions and input led to the error.
    System environment
        SAP-Release 700
        Application server... "personal"
        Network address...... "192.168.2.11"
        Operating system..... "Windows NT"
        Release.............. "5.2"
        Hardware type........ "4x Intel 80686"
        Character length.... 16 Bits
        Pointer length....... 32 Bits
        Work process number.. 1
        Shortdump setting.... "full"
        Database server... "PERSONAL"
        Database type..... "ORACLE"
        Database name..... "GCU"
        Database user ID.. "SAPSR3"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Aug 29 2006 00:18:21"
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
        Database version. "OCI_10201_SHARE (10.2.0.1.0) "
        Patch level. 75
        Patch text.. " "
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
        SAP database version. 700
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
        Memory consumption
        Roll.... 8176
        EM...... 30311496
        Heap.... 0
        Page.... 139264
        MM Used. 14538320
        MM Free. 91952
    User and Transaction
        Client.............. 100
        User................ "INFO_SD"
        Language key........ "E"
        Transaction......... "VA01 "
        Program............. "SAPMV45A"
        Screen.............. "SAPMV45A 4001"
        Screen line......... 65
    Information on where terminated
        Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
        The main program was "SAPMV45A ".
        In the source code you have the termination point in line 338
        of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
    Edited by: kiran35086 on Dec 14, 2011 6:30 AM

    Dear  kiran,
    This might be many reasons.If you have not done  configuration properly system will take you to dump(Run time error).
    Try read the diagnosis possibly you may understand the problem.
    If not You coordinate with your technical team.
    Thanks&Regards
    Raghu.k

  • Run time error in MIGO after maintaining tax code

    Hello Experts,
    I had configured the new tax code ,which is working fine for the PO document ZLOC domestic and the account category Z.
    While doing the MIGO for purchase document type ZGEN general purchase , I am getting run time error:
      "Division by 0 (type P) in program "SAPLJ1IEX".
    When I debugged the code i found that inside FM: 'J_1IEX_DEFAULT_EXCISE_DUTY'
    one another FM is being called: 'J_1I6_UNIT_CONVERSION' which is returning the value "ls_ekpo-menge" as 0(Zero).
    later in the code when "ls_ekpo-menge" used in calculation then divide by 0 runtime error is coming.
    Please suggest what need to be done.
    Is there anything related to tax code? How should I correct it?

    Hi,
            There is not value in that field for PO quantity / Value it is missing while doing MIGO. Check whether you have maintained values for all required fields.
    Kiran

  • Run time error while create Vendor master via MK01

    Dear Experts,
    when i try to create vendor master by MK01.....system throws run time error as below:
    "The exception 'CX_BADI_MULTIPLY_IMPLEMENTED' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CVI_MAP_TITLE=================CP' has to be
    terminated."
    My current system is ECC 6 along with DBM. Business partner configuration is activated in the current system. I am getting this error after BP configuration. Could you please help me to fix this issue?.......Is it due to configuration or a dump from abap program?
    Regards
    Vetrivelan

    Hii,
       please search sdn before posting the threads.
    check these  links, it may help u............
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    CX_BADI_NOT_IMPLEMENTED
    thanks.

  • ABAP run time error

    Dear ALL,
    When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
    we are getting following run time error
    Hoe to resolve this?
    Runtime Errors         SAPSQL_INVALID_FIELDNAME                                                    
    Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS                                                
    Date and Time          15.01.2009 16:04:19                                                         
    Short dump has not been completely stored (too big)                                                                               
    Short text                                                                               
    A dynamically specified column name is unknown.                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLV61Z" had to be terminated because it has                       
        come across a statement that unfortunately cannot be executed.                                
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                        
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   
        at and manage termination messages, and you can also                                          
        keep them for a long time.                                                                    
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                      
        The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was                 
         not caught in                                                                               
    procedure "SEL_KONDTAB" "(FORM)", nor was it propagated by a RAISING clause.                  
        Since the caller of the procedure could not have anticipated that the                         
        exception would occur, the current program is terminated.                                     
        The reason for the exception is:                                                              
        An Open SQL clause was specified dynamically. The contained field name                        
        "ALAND" does not exist in any of the database tables from the FROM clause.                    
    How to correct the error                                                                               
    Check the field name in the SELECT clause.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                        
        find an interim solution in an SAP Note.                                                      
        If you have access to SAP Notes, carry out a search with the following                        
        keywords:                                                                               
    "SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"                                     
        "SAPLV61Z" or "LV61ZU01"                                                                      
        "SEL_KONDTAB"                                                                               
    If you cannot solve the problem yourself and want to send an error                            
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                        
           Restrict the time interval to 10 minutes before and five minutes                           
        after the short dump. Then choose "System->List->Save->Local File                             
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                           
        program: The source code of the program                                                       
           In the editor, choose "Utilities->More                                                     
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                       
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                                
        "SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the                    
        RAISING clause of the procedure.                                                              
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "slgsap-prd"                                                            
        Network address...... "10.140.1.11"                                                           
        Operating system..... "Windows NT"                                                            
        Release.............. "5.2"                                                                   
        Hardware type........ "8x AMD64 Level"                                                        
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 0                                                                       
        Shortdump setting.... "full"                                                                               
    Database server... "SLGSAP-PRD"                                                               
        Database type..... "MSSQL"                                                                    
        Database name..... "PRD"                                                                      
        Database user ID.. "prd"                                                                               
    Terminal................. "SD0123l"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "May 6 2008 00:13:21"                                                       
        create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                              
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 159                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                              
        SAP database version. 700                                                                     
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                
         NT 6.0"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 20949200                                                                               
    Heap.... 0                                                                               
    Page.... 196608                                                                               
    MM Used. 15928048                                                                               
    MM Free. 828016                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                      
        User................ "ADMIN"                                                                  
        Language key........ "E"                                                                      
        Transaction......... "VA01 "                                                                  
        Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"                                                                               
    Program............. "SAPLV61Z"                                                               
        Screen.............. "SAPMV45A 4900"                                                          
        Screen line......... 930                                                                      
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".                       
        The main program was "SAPMV45A ".                                                                               
    In the source code you have the termination point in line 672                                 
        of the (Include) program "LV61ZU01".                                                          
        The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"                    
         occurred in                                                                               
    procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor                      
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "SAPLV61Z "; its source code begins in line                       
        260 of the (Include program "LV61ZU01 ".                                                      
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    642     if se_prestep              = yes or                                                     
      643        se_read_only_one_record = yes.                                                       
      644       if t681-ksdat is initial.                                                             
      645         if se_read_all_prestep is initial.                                                  
      646           select * from (t681-kotab) appending table <cond_tab>                             
      647                  up to 1 rows                                                               
      648                  where kappl  = se_kappl                                                    
      649                  and   kschl  = se_kschl                                                    
      650                  and   (coding_tab).                                                        
      651           h_subrc = sy-subrc.                                                               
      652         else.                                                                               
    653           select * from (t681-kotab) appending table <cond_tab>                             
      654                  where kappl  = se_kappl                                                    
      655                  and   kschl  = se_kschl                                                    
      656                  and   (coding_tab).                                                        
      657         endif.                                                                               
    658                                                                               
    659 * it is enough to find one record in prestep                                                
      660 * (care must be taken with pool tables - depending on database this                         
      661 *  will cost performance instead of saving)                                                 
      662         if select_split ne 0 and h_subrc ne 0.                                              
      663           modify coding_tab from coding_alter index select_split.                           
      664           select * from (t681-kotab) appending table <cond_tab>                             
      665                  up to 1 rows                                                               
      666                  where kappl  = se_kappl                                                    
      667                  and   kschl  = se_kschl                                                    
      668                  and   (coding_tab).                                                        
      669         endif.                                                                               
    670       else.                                                                               
    671         if se_read_all_prestep is initial.                                                  
    >>>>>           select * from (t681-kotab) appending table <cond_tab>                             
      673                  up to 1 rows                                                               
      674                  where kappl  = se_kappl     
    Regards,
    Akshay
    Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
    Edited by: Akshay Dalal on Jan 17, 2009 6:30 AM

    Dear Akshay,
    We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
    Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
    There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
    Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
    Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely.

  • How to debug  a run time error encountered while executing ZFunction Module

    Hi all,
    My requirement is to create a ZFunction Module that Generated a sales order
    for multiple line items and works for both Variant Configurable material and a Normal Material.
    I am using BAPI_SLSTRANSACT_CREATEMULTI in my Zfunction Module to create a
    Sales order
    My ZFunction Module works well if I give normal material as input.
    It also works well and generates a sales order if I give all Variant Configurable materials as input.
    But if I give both Variant Configurable material and a normal material it throws a run time error.
    Can some one tell me what is wrong? can some one suggest me how to debug this run time error
    Termination occurred in the ABAP program "SAPLCRM_CONFIG_OW" - in                            
    "CONFIG_TO_CBASE".                                                                          
    The main program was "RS_TESTFRAME_CALL ".                                                                               
    In the source code you have the termination point in line 63
    of the (Include) program "LCRM_CONFIG_OWF02".                                                
    Source Code Extract                                                                               
    Line SourceCde                                                                               
    |   33|                                       LT_CUXI_CUPRT                                       
    |   34|                                       LT_CUXI_CUVAL                                       
    |   35|                                       LT_CUXI_CUVK                                        
    |   36|                                       LS_CUXI_CUCFG.                                      
    37
    |   38|  PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.                              
    39
    |   40|* set config to cbase                                                                      
    |   41|  CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'                                                  
    |   42|       EXPORTING                                                                           
    |   43|            I_CFG_HEADER          = LS_CUXI_CUCFG                                          
    |   44|            I_ROOT_INSTANCE       = CV_INT_OBJ_NO                                          
    |   45|            I_LOGSYS              = LV_LOGSYS                                              
    |   46|       IMPORTING                                                                           
    |   47|            E_ROOT_INSTANCE       = CV_INT_OBJ_NO                                          
    |   48|       TABLES                                                                               
    |   49|            I_TAB_INSTANCES       = LT_CUXI_CUINS                                          
    |   50|            I_TAB_PART_OF         = LT_CUXI_CUPRT                                          
    |   51|            I_TAB_VALUES          = LT_CUXI_CUVAL                                          
    |   52|            I_TAB_VAR_KEYS        = LT_CUXI_CUVK                                           
    |   53|            I_TAB_RESTRICTIONS    = LT_CUXI_CURES                                          
    |   54|       EXCEPTIONS                                                                          
    |   55|            INVALID_INSTANCE      = 1                                                      
    |   56|            INTERNAL_ERROR        = 2                                                     
    57
    OTHERS                = 3.                                                        58
    |   59|  IF SY-SUBRC <> 0.                                                        
    |   60|    if sy-msgno is initial.                                                      
    |   61|      MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
    |   62|    else.                                                                             
    |>>>>>|      MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
    |   64|              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    |   65|    endif.                                                                               
    |   66|  ENDIF.                                                                               
    67
    |   68|ENDFORM.                               " CONFIG_TO_CBASE                                   

    Hey Amit...
    Can I Create a Sales order for VC and Non VC items using BAPI_SLSTRANSACT_CREATEMULTI
    Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
    I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
    Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
    Some one please help me u2026I am just stuggling to get this doneu2026
    I dint find any posts that gives me information about this error.
    CUX1 034 u201CNo root instance found in header datau201D                                                                               
    In the source code you have the termination point in line 63                                   of the (Include) program "LCRM_CONFIG_OWF02".

  • How to send Run time errors alerts to email ?

    Dear Friends,
    I am using SAP CRM ABAP 6.0. I am checking run time errors in ST22 transaction. Usually, i check in morning or evening, based on my free time. I feel, dificully in this. so, i need to configure in somewhere for send this runtime error alerts to my office mail id.
    We are sending report outputs to our office id. But, i dont know, how to send run time errors with log or with out log to emai id?
    thanks in advance.
    Rajagopal
    Chennai - INDIA

    Thanks Dieter.
    Now, i have set the background job as per your suggestions. but, i have below doubts:
    1. I added my office mail id in spool list receipient. This background job alert mail goes to business work place inbox (SBWP). But, i need, in my outlook mail box.
    2. This background job gives all months runtime errors. but, only i need today & yesterday only. I checked in ST22 for create variant. Unfortunately, i did not get option. so, how to set variant?
    Thanks in advance.
    Rajagopal
    Chennai - INDIA.

  • Internal Order abap run time error

    hi,
    I am using sap ecc 6.00 ides i have not authoroty to access oss notes.
    I newly configurated internal order. But when i tried to post a document in fb50, an abap run time error happen like following
    Run time error message type x
    error analysis
    rror analysis
       Short text of error message:
       Error GENERAL_ERROR MESSAGES_ACTIVE_REQUIRED
       Long text of error message:
        Diagnosis
            The following program error or handling error has occurred.
            Error information:
            GENERAL_ERROR
            MESSAGES_ACTIVE_REQUIRED
        System Response
            Processing is terminated.
        Procedure
            If you cannot solve the problem yourself using the error
            information, note down this information and the entries which led
            to the error. Contact your system administrator for further
            assistance.
       Technical information about the message:
       Message class....... "K5"
       Number.............. 011
    please help

    Hi,
       Please apply note 1361352 and check if the issue is resolved
    regards
    Waman

  • Run Time Error 40002

    I am attempting to connect to an Oracle database on an Alpha 4100 running on openVMS from an NT 4.0 (service pak 6) machine in VB code.
    I have set up an ODBC driver DSN and have used the Oracle SQL NetEasy Configuration to set up the connection.
    Following is the code I am using to try to connect, but I get a "Run Time Error 40002" when I click ok to connect. Any help would be appreciated.
    Private Sub Command1_Click()
    Dim result As rdoResultset
    Dim cn As New rdoConnection
    Dim en As rdoEnvironment
    Set en = rdoEngine.rdoEnvironments(0)
    With en
    .CursorDriver = rdUseOdbc
    .LoginTimeout = 20
    .UserName = "aksadm"
    End With
    With cn
    .Connect = "DSN=cgl1test;UID=ak;PWD=ak;UIDDBMS=aks;PWDDBMS=ak"
    .LoginTimeout = 20
    .CursorDriver = rdUseOdbc
    .EstablishConnection
    End With
    cnEH:
    Dim er As rdoError
    Debug.Print Err, Error
    For Each er In rdoErrors
    Debug.Print er.Description, er.Number
    Next er
    Resume Next
    End Sub
    Sincerely
    Bruce Stuart

    I assume 'cgl1test' is set up as a DSN using the Oracle8 ODBC driver.
    - We ship a tool called 'ODBCTest' that lets you test new DSN's to ensure you're able to connect. If you use this tool, are you able to connect with the 'cgl1test' DSN?
    - Why do you have the parameters
    UIDDBMS=aks;PWDDBMS=ak
    in your connection string? Our ODBC driver doesn't have these options. The fact that you have two apparent user names leads me also to suspect that the login may be failing because of a bad username.
    Justin Cave
    ODBC Development

  • Run time error CONVT_OVERFLOW

    dear Sir
    we have window 7 for new oc as soon runned teh program cv01n i got run time error msg  CX_SY_CONVERSION_OVERFLOW,plese guide
    Runtime Errors         CONVT_OVERFLOW                                                              
    Except.                CX_SY_CONVERSION_OVERFLOW                                                   
    Date and Time          03.05.2010 14:26:31                                                                               
    Short text                                                                               
    Overflow when converting from "-1"                                                           
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLCV120" had to be terminated because it has                     
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                       
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                     
        The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not               
         caught in                                                                               
    procedure "SYS_GET_WINDOW_SYSTEM" "(FORM)", nor was it propagated by a RAISING               
         clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                        
        exception would occur, the current program is terminated.                                    
        The reason for the exception is:                                                             
        When attempting to convert the value "-1", an overflow occurred.                             
    How to correct the error                                                                         
        If the error occurred in your own ABAP program or in an SAP                                  
        program you modified, try to remove the error.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                       
        find an interim solution in an SAP Note.                                                     
        If you have access to SAP Notes, carry out a search with the following                       
        keywords:                                                                               
    "CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"                                                 
        "SAPLCV120" or "LCV120F28"                                                                   
        "SYS_GET_WINDOW_SYSTEM"                                                                               
    If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                               
        "SYS_GET_WINDOW_SYSTEM" "(FORM)", or its possible occurrence must be declared                
         in the                                                                               
    RAISING clause of the procedure.                                                             
        To prevent the exception, note the following:                                                
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "APP2"                                                                 
        Network address...... "132.147.166.13"                                                       
        Operating system..... "Windows NT"                                                           
        Release.............. "5.2"                                                                  
        Hardware type........ "2x IA64 Level 3"                                                      
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "DB"                                                                      
        Database type..... "MSSQL"                                                                   
        Database name..... "ELP"                                                                     
        Database user ID.. "elp"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 23 2009 22:38:30"                                                     
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                             
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 221                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
        SAP database version. 700                                                                    
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows               
         NT 6.0"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 29328880                                                                               
    Heap.... 0                                                                               
    Page.... 655360                                                                               
    MM Used. 3095760                                                                               
    MM Free. 1091456                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                     
        User................ "CPTN_SAPC5"                                                            
        Language key........ "E"                                                                     
        Transaction......... "CV03N "                                                                
        Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"                                                                               
    Program............. "SAPLCV120"                                                             
        Screen.............. "SAPLCV110 0101"                                                        
        Screen line......... 3  
    regards
    kunal

    Hi Kunal,
    you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
    then you can display these files.
    Regards,
    Ravindra

  • Run time error '9' while installing BIP Desktop 10.1.3.4.1 for Windows

    Hi,
    I've been getting 'run time error '9' Subscript out of range error while installing BIP Desktop.
    I have MS Word 2003 and the laptop's OS is Windows XP SP3. I have searched the net and this forum for suggestions
    and followed what was recommended (install .NET framework 2.0, make sure no MS Office processes are not running while
    installing the software, Admin rights at Registry level on BI Publisher folder etc..) but no use.
    This is a new laptop which I just received. On my existing laptop (which has similar configuration), I've installed BIP long time
    ago and do not remember facing this error. If any one has come across this problem recently and was able to trouble shoot it,
    please share with me how you were able to overcome the problem.
    Thanks and Regards,
    Srini

    Hello,
    Since I haven't heard from any one, I have opened a service request with Oracle support.
    Support recommended that I down load a desktop publisher from edelivery.oracle.com but even that didn't help.
    Will keep you posted.
    Regards,
    Srini

Maybe you are looking for