Error while creating a system from a par file

Hi all,
I am trying to integrate a web app to our portal.
When i am trying to create a from a par file (any par file ,even the system defined parfiles), i am getting the following error.
    Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:43_07/07/10_0005_8678350
Refer to the log file for details about this exception.
Please suggest me what to do??
Thanks in advance

hi Sandeep,
thanks for the quick reply
below is the error from the default trace file
  error 2010-07-08 10:13:32:132 10:13_08/07/10_0001_8678350
[EXCEPTION]
java.lang.ClassCastException... [see details]
n/a com.sap.portal.prt.runtime sap.com/irj delep01 Server 0 0_86783
Full Message Text
10:13_08/07/10_0001_8678350
[EXCEPTION]
java.lang.ClassCastException
at com.sap.portal.pcm.NewObjectDescriptor.addText(NewObjectDescriptor.java:167)
at com.sap.portal.pcm.NewObjectDescriptor.putTextAttribute(NewObjectDescriptor.java:115)
at com.sap.portal.pcm.iviewserver.NewIVSObjectDescriptor.setTitle(NewIVSObjectDescriptor.java:447)
at com.sap.portal.admin.wizard.AbstractPCMWizard.setSpecialAttributes(AbstractPCMWizard.java:578)
at com.sap.portal.admin.wizard.AbstractPCMWizard.finalizeDescriptor(AbstractPCMWizard.java:297)
at com.sap.portal.admin.wizard.panes.SavePane.doAfterSubmit(SavePane.java:113)
at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:356)
at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174)
at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99)
at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Similar Messages

  • Heap space error while creating XML document from Resultset

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

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

  • CIM_ERR_ALREADY_EXISTS: Error while creating Business System

    Hi,
    I am getting following error while creating Business System in SLD, the Technical System is already created from RZ70 transaction in the IDES system
    Error Creating business system: CIM_ERR_ALREADY_EXISTS: Instance already exists://inbbssun01/sld/active:SAP_LogicalALESystem.CreattionClassName="SAP_LogicalALESystem", Name = "LSIDES800.SystemName.800.SystemName.IDS.SystemNumber.0020224902.SystemHome.idesecc"
    Thanks,
    RP

    Hi,
    This error means that a business system with this name(or associated with this technical system) is already there in SLD.
    You need to check that before you try creating it (might be someone else have created it before)
    Updated
    If you have created and deleted a business system and then trying to recreate one then you need to delete all the instance of it from Content Management (in SLD)
    Regards
    Suraj
    Edited by: S.R.Suraj on Nov 9, 2009 12:34 AM

  • Portal Runtime Error while creating  new system in portal content

    Hi
      Can anyone  solve my problem, i am geting error while creating new system in p ortal content
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
    Component Name : com.sap.portal.admin.templateselectionwizard.default
    com/sap/portal/iviewserver/cache/OClass.
    Exception id: 11:29_26/12/06_0014_5891950
    See the details for the exception ID in the log file

    Hi,
    Check this link for creating system object
    http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
    Regards
    Arun

  • RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6

    Hi
    Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
    Component Name : com.sap.portal.admin.templateselectionwizard.default
    com/sap/portal/iviewserver/cache/OClass.
    Exception id: 11:29_26/12/06_0014_5891950
    See the details for the exception ID in the log file
    thanks in advance
    Rock

    hi,
    check the log file and let me the the error.
    manish

  • Error while creating MDM system on Portal

    Hi All,
    I am trying to create MDM system in EP. MDM is 5.5 SP06. EP is 7.0 . We have upgraded the MDM sca files on Portal from SP05 to SP06.
    While creating the system , after entering the server, we are getting the following error.
    com.sap.mdm.internal.protocol.manual.ServerException: File failed a crc check
    Please help
    Regards
    Shilpa

    Hi Shilpa,
    If this is your MDM build version 5.5.63.80 SP06. It means you are using MDM 5.5 SP06 Patch3 hotfix 80.
    You need to find the Sca file of compatible with this version.
    So they should be
    - MDMJAVAAPI06_03.sca
    - BPMDMAPPLN06_03.sca
    - BPMDMTECHN06_03.sca
    The hotfix number can slightly differ but the Support pack and patch number must match.
    You need to follow this link:
    http://service.sap.com/swdc
    (download MDM support packages) Download>support packages and patches>entry by application
    group>sap netweaver>sap mdm>sap mdm 5.5>Entry by component>Portal content
    Then select which MDM portal content you want and check what is the version of those available sca files.
    based on the availablity of the sca files you need to upgrade/downgrade or server.
    As compatibility between the server version and sca files is a must for proper functioning.If its not possible to change your mdm server version then you can ask your Basis team to hunt the matching sca files for you.
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Error while creating SOURCE SYSTEM

    Hi All,
    I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
    <b>Error in source system RXX_100
    Message no. RSAR502
    Diagnosis
    With Remote Function Call to system RXX_100 error Screen output without connection to user.  ccurred.
    Procedure
    Remove the cause of the error.</b>
    Kindly provide me suggestions and DOCS related to the same.
    Suitable points will be awarded for replies.
    Expecting your kind reply,
    Vineeth

    Hi ,
    In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
    973555 - System must be open for creating/connecting source systems
    Thanks,
    Shanaka

  • Error while creating a system object for R3 in portal

    Hi,
    I am getting error while trying to create a system object in portal.
    Following are the details I used :
    Under WAS...
    Web AS Host Name :<XXXX>:8001
    Web AS path: /sap/bc/bsp/sap/
    Web AS protocol : http
    Under User management:
    Authentication Ticket Type : SAP Logon Ticket
    Logon Method :SAPLOGONTICKET
    User Mapping Type : admin,user
    Under Connector:
    SAP Client : <Client NO>
    SAP System ID : <System ID>
    SAP System No : <System No>
    System Type : SAP_R3
    While trying with connection test... I am getting like this:
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
    5. The host name <FQDN Server Name> was resolved successfully.
    6. The server sapdwh01 could not be pinged successfully.
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
    Kindly help.
    Regards,
    Niraj
    Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

    I created a SAP Transactional iView for transaction SE80.
    Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
    Got portal Runtime error :
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 12:57_11/12/08_0003_2795650
    See the details for the exception ID in the log file.
    Regards,
    Niraj

  • Error While Creating Essbase Database From Hyperion Planning

    Hi,
    While creating the Essbase Database From the 'Manage Database' in Hyperion Planning, I am getting the following error:
    com.hyperion.planning.olap.EssbaseException: Account (1060000)
    It gets stuck at Adding Dimensions.
    I have tried reconfiguring Planning, but no luck.
    My Relation Repository is MS SQL Server 2005 and the Essbase and Shared Services are on a Linux box.
    I am getting the following error in the Planning log
    [12-Nov-2009 10:50:41]: Propegating external event[ FROM_ID: 68b6dbf1 Class: class com.hyperion.planning.sql.HspLock Object Type: -1 Primary Key: 50001 ]
    [12-Nov-2009 10:50:41]: Processing cube: Plan1
    [12-Nov-2009 10:50:41]: Setting System CFG properties for Attribute Dimensions
    [12-Nov-2009 10:50:41]: Adding dimension: Account
    [12-Nov-2009 10:50:41]: Closing outlines
    com.hyperion.planning.olap.EssbaseException: Account (1060000)
         at com.hyperion.planning.olap.HspEssbaseOutlineAPI.EssAddMemberEx(Native Method)
         at com.hyperion.planning.olap.HspCubeRefreshTask.addDimension(Unknown Source)
         at com.hyperion.planning.olap.HspCubeRefreshTask.addDimensionsAndMembers(Unknown Source)
         at com.hyperion.planning.olap.HspCubeRefreshTask.buildOutlines(Unknown Source)
         at com.hyperion.planning.olap.HspCubeRefreshTask.run(Unknown Source)
         at com.hyperion.planning.HspJSImpl.runCubeRefresh(Unknown Source)
         at com.hyperion.planning.HyperionPlanningBean.runCubeRefresh(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
         at sun.rmi.transport.Transport$1.run(Transport.java:153)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
         at java.lang.Thread.run(Thread.java:595)
    Thanks for your help.
    Edited by: user524093 on Nov 12, 2009 4:38 PM

    Have you tried restarting the services and giving it a try?
    Which version of Essbase/Planning are you on?
    If your Essbase server name has more than 30 characters, please use NODENAME with short server name.

  • Error While Creating Runtime Systems on an Existing Track in NWDI

    Hi,
    There is already a track in NWDI with No runtime Systems.
    I have to create the RunTime Systems to do development on this track.
    When I try to select the Development checkbox in Runtime systems,
    select configure  without wizard, Gave   Deploy Host name: **********.com
                Deploy Port :50018  (SDM port)
               Deploy PSWD:  SDM Pswd
    It gives me a warning..
    Synchronization of Runtime System triggered for system dev. Log can be found at
    http://*****************************LogViewer?LogName=%2Fsapmnt%2FEPQ%2Fglobal%2FTCS%2FLOG%2FEPQ_WHRBD_D2010081322030045.log&Bsname=EPQ_WHRBD_D
    When i go to the  log file
    I see this Error Message
    20100813180502 Info   :cannot create a connection for the buildspace:  EPQ_WHRBD_D //connect to deploy tool failed:Server <Host Name> did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to <Host name> at port 50018: Connection timed out:could be due to invalid address
    Can you please tell me what could be the Reason.
    Basis has already opened the Ports : http port and SDM Port.
    I am able to ping the server from cmd prompt.
    Points will be allocated for the answer.
    Thanks.
    Venkat

    Hi,
    There's no need to update CMS or to check whether the buildspace is open, do not click on JSPM flag (unless you need nwdi control at upgrade)...
    The error message means only that from the host where you configure the RTS the SDM cannot be reached or logon request cannot be accepted.
    This can be either , because the
    - SDM password is wrong (you checked it already)
    - the port is wrong (you also checked it. If this is really a 700 RTS, i.e. it has SDM, and the instance number is 00, then the port is really 50018, so this should be fine as well. Only mention, because as of 71X we use the P4 port 5<xx>04 for the deploy controller, as there's no more SDM). Still you can use "netstat -a" to see the status of the ports.
    - The host is wrong. I agree with Dao, check not only FQDN, but also IP address.
    Using this guide you can always check whether the entered data is correct:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002
    Best regards,
    Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

  • Error while creating user id from MDM JAVA API in 7.1 SP7

    Hi,
    We are trying to create user id in MDM 7.1 SP7 using JAVA API in SAP Portal. When trying to create user id, we are getting below error. If you have any solution please let us know.
    com.sap.mdm.commands.CommandException: MDM repository data is out-of-date or is locked by another MDM Server. Refresh the data and try the operation again. If the error persists, contact the system administrator
    Thanks,
    Vinit Pugaliya

    URGENT** How to change  OIM user password from outside OIM

  • Error while creating Technical System

    Hi
    i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
    When i press next, It is throwing this error. Do anyone have any idea about this.
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
        at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
        at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
        at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        ... 27 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
    Web Dynpro Code Generation Infos
    sap.com/tcsldwd~main
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~landscape
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcsldwd~businesssystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~technicalsystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    sap.com/tcsldwd~softwarecatalog
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~namereservation
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    Detailed Error Information
    Detailed Exception Chain
    java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
         at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
         at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Thanks in Advance
    Vijay Raheja

    HI Michal Krawczyk,
    Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
    It is asking me for :
    -URL of target SLD system, e.g. http://host:port/
    -User
    -Password.
    What should i give here. WHat will be port for R/3 system to which i want to connect.
    Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
    Thanks,
    Vijay Raheja

  • Error While Create Business Components From Tables Wizard -- need help asap

    Hi , i have created a view and while create Business Components through wizard for that view i am getting following error.
    ENTITY CREATION FAILED FOR THE FOLLOWING DATABASE OBJECT
    NO PRIMARY KEY ATTRIBUTES AND DOES NOT SUPPORT ROWID . USE ENTITY WIZARD TO CREATE THE ENTITY OBJECT.
    very urgent.
    Regards
    bhanu prakash

    thanks shay .
    Jdeveloper version :: 10.1.3.1.0
    view Syntax is :
    SELECT
    oh.order_number||'- ('||ol.line_number||'-'||ol.shipment_number||')' so_line,
    oh.cust_po_number customer_po,
    ol.flow_status_code status,
    ol.shipping_method_code carrier,
    ol.ordered_item item_no,
    nvl(xxapplication_express_pkg.getcustomerpart(ol.inventory_item_id, hca.cust_account_id), ' ') customer_item_number,
    nvl(mtl.description , 'na') description,
    nvl(org.organization_name , 'oak park') ship_from,
    hcsu.location||' ('||hl.city||' '||hl.state||' '||hl.postal_code||')' ship_to,
    nvl(ol.promise_date, sysdate) promised_date,
    nvl(ol.ordered_quantity, 0) order_quality ,
    xxapps.xx_eg_calculated_onhand(ol.line_id) available_qty,
    nvl(ol.shipped_quantity, 0) shipped_quality ,
    ol.order_quantity_uom uom,
    hp.party_name customer_name,
    jrs.name sales_person_name,
    0 refer
    FROM
    oe_order_headers_all oh,
    oe_order_lines_all ol,
    hz_cust_accounts hca,
    hz_parties hp ,
    hz_cust_site_uses_all hcsu,
    hz_cust_acct_sites_all hcas,
    hz_party_sites hps,
    hz_locations hl,
    org_organization_definitions org ,
    mtl_system_items_b mtl ,
    jtf_rs_salesreps jrs
    WHERE
    oh.header_id = ol.header_id and
    oh.org_id = ol.org_id and
    oh.sold_to_org_id = hca.cust_account_id and
    hca.party_id = hp.party_id and
    hcas.cust_account_id = hca.cust_account_id and
    hcsu.cust_acct_site_id = hcas.cust_acct_site_id and
    hcas.party_site_id = hps.party_site_id and
    hps.location_id = hl.location_id and
    hcsu.site_use_id = oh.ship_to_org_id and
    hcsu.site_use_code = 'SHIP_TO' and
    org.organization_id = ol.ship_from_org_id and
    org.organization_id = mtl.organization_id and
    ol.inventory_item_id = mtl.inventory_item_id and
    ol.ship_from_org_id = mtl.organization_id and
    ol.salesrep_id = jrs.salesrep_id and
    ol.org_id = jrs.org_id
    Regards
    Bhanu Prakash

  • Error while creating ERP Quotation from CRM Opportunity in CRM WebUI

    Dear all,
    We have implemented Best Practise Scenarios but have a problem in the following: C63-Opportunity Management-Creating ERP quotation from opportunity
    I have maintained all necessary customising mentioned in Best practises documnet and could select a quotation(AG) as follow on transaction from Opportunity, but get an error message " Material 23 is not defined for sales org.1000, distr.chan.10, language ENu201D in the ERP quotation screen even though material 23 is created in ERP for Sales Org 1000 & DC 10. I have downloaded the material from ECC and it is available in CRM also.
    The weird thing , when the error message pops up in the ERP quotation screen if I delete the material and enter the same material, I get no error.
    If I have 3 materials in opportunity then the error message is there for all the 3 materials when I create an ERP Quotation & after deleting all the 3 & reentering I get no error and am able to save ERP order.
    We have CRM 2007 connected to ECC 6.0
    Please help resolve the above error.
    Thanks
    Teyna

    hi,
    have you created org from middleware thorugh r/3. Is your hierarchy and category same as that mentioned in best practice documents?
    Regards
    Pankaj kumar

  • Error While Creating Technical System for SNC

    Hi There,
    I am trying to create technical system for SNC in SLD, I am not able to seee SNC as a s/w component/product in the list.
    when I checked the list of components in SLD, I found SNC is there under product "SCMSNC" but this product is not in the list of products.
    Please help me how I can get "SCMSNC" product in the product list.
    Thanks,
    Nishant

    Can you please explain it little bit clearly?
    I think you first create product, then SWC and then try to create Technical system.
    While you will create the Technical system, in the last step it will ask you for installed products.
    There you can specify ur product.
    Thanks,
    Hetal

Maybe you are looking for

  • Error message by periodic weekly: No output from the 1 file processed

    Hi there, since four weeks, I got a problem with the maintenance script periodic weekly. Up to December 22nd, the script did, what it should do: rebuilding the database of locate and whatis, rotating log-files. Since one week later, I got the error m

  • Issue in MaxL

    Hi all, Iam using MaxL statements for validating and backup of the databases. The statements are as follows: MAXL> alter database app1.db1 validate using error_file "E:\hyperion\samp.txt"; MAXL> export database app1.db1 data to data_file "d:exp.txt";

  • Itunes won't burn my cds anymore. Please help.

    Whenever I try burning cds from itunes, it indicates that the music is being burned, but it does it incredibly fast. Then when I try to listen to the cd in a cd player, it makes a funny noise and nothing happens. It seems that itunes is somehow manag

  • Something called SkyDrive on my computer

    I have an HP Touchsmart 600 PC. It came set on British settings, which I changed to U.S.  But there is something in the Windows Photo Gallery called Skydrive which says it will eliminate my pictures in June.  I have no clue what Skydrive is. Do I sim

  • Server 2012 R2 support in SHarePoint 2013

    When 2012 R2 is released will SharePoint 2013 be able to run on it? i've seen there are issues with Preview currently....my server admins would rather build machines in r2 for long term but asked my preference.