SAP SSM 2007 - Administrator's user interface

Hello,
I've a problem concerning SAP Strategy Managment 2007 (pilot).
I get a "Page not found" when logging into the Administrator's user interface http://localhost/pilot/pipadmin .
It opens a pop_up window with the path: http://localhost/pilot/scriptmain.pw?userinfo=/pilot/pipadmin/adminstart4.htm, but it doesn't work. IIS and Jboss are working correctly und the jboss_server.log contains no error.
Has someone an idea?
Thanks and best regards,
Robert Männel

Hi Chris,
thanks for your reply! Pilot Extended Listener; Pilot Listener; WWW and JBOSS are running and I started Pilot Extended Listener before Jboss, but it doesn't work.
It tries to open http://localhost/pilot/scriptmain.pw?userinfo=/pilot/pipadmin/adminstart4.htm but there isn't a file "scriptmain.pw" in the pilot directory, only the file "scriptmain.pip". Maybe it is missing?!
best regards,
Rob

Similar Messages

  • Iws6sp3 Configuring virtual server administrator�s user interface

    Hi I am trying to configure my virtual server admininstrator interface. I followed the admin guide iws60 816-1379-01 May 2001, Chapter 13 "Using Virtual Servers" page 307. I followed all the steps however when I go to my browser, what should I type in for the URL?
    Example given:
    server_name:port/user-app/server_instance/virtual_server_ID
    Q1. should mine will be:
    http://127.0.0.1:8889/user-app/test.mytest.com/https-test.mytest.com
    if I am trying out my default virtual server?
    Q2. If I have created another virtual server called, esample.indoors.com will that by my vistual_server_id?
    Q3. Why after adding the extra codes into my server.xml, I cannot access my default admin port which is 8888?
    Below is my server.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- declare any variables to be used in the server.xml file in the ATTLIST below -->
    <!DOCTYPE SERVER SYSTEM "server.dtd" [
    <!ATTLIST VARS
    docroot CDATA #IMPLIED
    adminusers CDATA #IMPLIED
    webapps_file CDATA #IMPLIED
    webapps_enable CDATA #IMPLIED
    accesslog CDATA #IMPLIED
    user CDATA #IMPLIED
    group CDATA #IMPLIED
    chroot CDATA #IMPLIED
    dir CDATA #IMPLIED
    nice CDATA #IMPLIED
    >
    ]>
    <SERVER legacyls="ls1">
    <VARS accesslog="E:/iPlanet/iws6sp3/https-admserv/logs/access"/>
    <LS id="ls1" ip="0.0.0.0" port="8888" security="off" acceptorthreads="1">
    <CONNECTIONGROUP id="group1" matchingip="default" servername="test.mytest.com" defaultvs="https-admserv"/>
    </LS>
    <MIME id="mime1" file="mime.types" />
    <ACLFILE id="acl1" file="E:/iPlanet/iws6sp3/httpacl/generated.https-admserv.acl" />
    <VSCLASS id="defaultclass" objectfile="obj.conf" rootobject="default" acceptlanguage="on">
    <VS id="https-admserv" connections="group1" mime="mime1" urlhosts="test.mytest.com" aclids="acl1">
    <VARS webapps_file="web-apps.xml" webapps_enable="on"/>
    <USERDB id="default" database="default" />
    </VS>
    </VSCLASS>
    <LS id="ls5" ip="0.0.0.0" port="8889" security="off" acceptorthreads="1" blocking="no">
    <CONNECTIONGROUP id="group5" matchingip="default" servername="test.mytest.com"
    defaultvs="useradmin"/>
    </LS>
    <VSCLASS id="userclass" objectfile="userclass.obj.conf" rootobject="default" acceptlanguage="on">
    <VS id="useradmin" connections="group5" state="on" mime="mime1" urlhosts="user-app" aclids="acl1">
    <VARS webapps_file="user-apps.xml" webapps_enable="on"/>
    <USERDB id="default" database="default" />
    </VS>
    </VSCLASS>
    </SERVER>

    Hi Chris,
    thanks for your reply! Pilot Extended Listener; Pilot Listener; WWW and JBOSS are running and I started Pilot Extended Listener before Jboss, but it doesn't work.
    It tries to open http://localhost/pilot/scriptmain.pw?userinfo=/pilot/pipadmin/adminstart4.htm but there isn't a file "scriptmain.pw" in the pilot directory, only the file "scriptmain.pip". Maybe it is missing?!
    best regards,
    Rob

  • EIC SAP HCM - ( Activity ) Flexible User Interface

    Hi All,
    We are implemennting EIC with EHP4, There is a badi to add custom attributes for an activiy.
    BADI : HREIC_ACT_CUSTOM_ATTR
    Enhancement Spot :HREIC_CUSTOM_ACTIVITY_ATTR
    as per my understanding we need to use the methods to edit and save any custom attribute we want to define for an activity. I am not able to understand how to show that attribute on the BSP page ActivityAttributesView.htm in BSP application HREIC_VP.
    If anyone has experience of using thsi BADI. Please explaing me how to use this BADI to display attributes on the BSP page.
    Regards,
    Puneet

    Dear Madhu,
    In the IMG, you will have to look at the following path for the step-wise WDA configuration :
    SAP e-Recruiting ->Technical Settings -> User Interfaces ->Settings for user interfaces with WDA.
    There is also an overview note which will talk in-depth about the settings(Just after the above mentioned node in IMG) & options one need to consider for the WDA screens.
    The basic thing to consider is if you want to separate your front-end from your back-end for WDA.In separated systems no sensitive data is located outside the company's firewall.
    The main advantage in using the WDA screens is that it is based on the latest UI technology & the latest functionalities released by SAP are only supported in WDA screens & not BSP.
    And WDA screens are available as of ECC 6.0 SP08 onwards.
    As of Enhancement Package 3, only the internal & external candidate screens are available in WDA. The rest are in BSP.
    In enhancement Package 4 which was just released, the Recruiter screens are also available in WDA.
    Regards,
    Sowmya
    Edited by: Sowmya Kadambi on Jan 19, 2009 11:17 AM
    Edited by: Sowmya Kadambi on Jan 19, 2009 11:28 AM

  • Filter on product search in SAP CRM 2007 User Interface

    Hi Experts,
    I have the following requirement: we need to have the possibility to filter the Products in the Product search in the user interface based on the User's sales organization. Meaning that, if a user belongs to Sales Organization A, he will be able to see ONLY the products belonging to sales organization A.
    Can anybody of you Experts, suggest a way to implement this via standard SAP and not via an enhancment if possible?
    Thanks in advance to all of you.
    MC

    Hi Michele,
    maybe have a look at BAdIs COM_PRODUCT_SEARCH and COM_PRODUCT_SE. Did not try them myself but they are for enhancing searches in product.
    cheers Carsten

  • Fields default on SAP CRM 2007 User Interface

    Hi Experts!
    I need to have a field in the search screen of products on the User Interface alsways prefilled to a default value for all the users.
    I haven't figured out how to do this via Component Configuration, but only via enhancment.
    Can you please suggest whether there is a standard way to do it?
    thanks

    HI Michele,
    As far as my understanding, there is no standard way of configuration for this. Enahncement would be the possible option, i understand that you have already done this.
    One option u have is the Working context in CRM 2007. this is role specific and it is predefined attributes that can be defaulted.
    Regards,
    Vinay

  • FAQ: User Interface Guidelines for CRM 2007 are now available

    The CRM UI Concept Team has made the UI Guidelines for CRM Web Client User Interface (CRM 2007 UI) available to the BPX community:
    This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
    The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
    We hope that you will find this information useful.
    Enjoy the new CRM UI! [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)_ |http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf]
    Edited by: Zhaojie Liu on Jun 10, 2009 10:08 AM

    Hi,
    not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
    Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
    Hope this helps
    Best regards
    Ingo

  • User Interface Guidelines for CRM 2007 are now available

    The CRM UI Concept Team has made the [UI Guidelines for CRM Web Client User Interface (CRM 2007 UI)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/302d8152-002b-2b10-34bd-9ff3c712dd4b] available to the BPX community:
    This document provides an overview of the on-premise as well as the off-premise versions of the SAP CRM Web Client User Interface (UI). It contains the properties and principles of the SAP CRM Web Client UI that are already committed and available. For planned features, refer to the corresponding specification documents.
    The information in the guidelines starts with general topics, followed by details. The sections are organized with high-level topics like Page Types and Navigation Schema first, followed by the consecutive sections describing which building blocks and elements of the UI populate the various pages. A section typically starts with one or more screenshots of a central UI element with a generic explanation. The subsequent sections explain the detailed aspects of each element.
    We hope that you will find this information useful.
    Enjoy the new CRM UI!
    Feel free to provide your feedback.
    Edited by: Florian Weigmann  on Jul 17, 2008 9:14 PM

    Hi,
    not sure why your download stops.. you can also try to download via this link: [http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf|http://www.sapdesignguild.org/resources/CRM-UI-Guidelines-Customers.pdf] (Document is 17,4MB of size)
    Here the guidelines also have been posted together with an article about the CRM 2007 Web Client UI.
    Hope this helps
    Best regards
    Ingo

  • How to add a new Field to the WEB User Interface in CRM 2007

    Dear experts,
    I have been struggling to add a new field to the (CRM 2007) user interface from available fields for a specific view.
    I have maintained settings in BS__WD_CMPWBàRuntime Repository editoràComponentàViewàConfigurationàNew ConfigurationàAvailable FieldsàField Propertiesàand save.
    But the field is only appearing in display mode in the Web UI, which doesnu2019t allows any user input.
    I need your help to resolve the issue, I would be grateful if you could provide step-by-step documentation with screenshots or any other kind of documentation.
    Each suggestion will be appreciated.
    Best regards,
    Raghu ram.

    Hi Raghu Ram,
    I think you added a new custom field using some method like EEWB etc.,
    Then, you are adding the field onto the UI using UI Configuration Tool .. right ?
    These are the steps to diagnose:
    Method 1.Check the field properties in the model browser first.
      It should be showing 'C' i.e., CHANGEABLE. If it is showing as 'R', it is only READABLE.
      In such a case you need to find a BADI to change the field properties.
      For example, in Marketing Applications OBJ BADI has a method CHANGE FIELD PROPERTIES for this purpose.
    Method 2. Debug and check what is the value coming for RV_DISABLED parameter in the GET_I method in BSP_WD_CMPWB. This should be FALSE.
    Method 3. Check what are the field properties in the UI Configuration tool.
    Make sure it is not a display only field.
    Regards,
    Masood Imrani S.

  • This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic.

    Hi there,
    I was wondering whether anyone could tell me which feature in Windows 7 produces this message "This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of
    the package to basic." and whether it can be turned off in Windows to prevent this message from appearing when installing certain programs that aren't WHQL certified. At first I thought it was the UAC control that generated this message but found out
    that it wasn't and then thought it was the DEP control and found out that it wasn't this either. I'm only seem to be getting this message when installing FileDirector Component Service Version 3 on a few of our workstations which is an add-on that allows file
    integration with Office and is part of FileDirector WinClient Version 3.
    Your help would be much appreciated.
    Many thanks,
    RocknRollTim
    P.S. I know of a way to bypass this message but would ideally not like to have the feature turned on and for the message not to be appear for non WHQL certified program installations in order to make non WHQL certified program installations in the future much
    easier, more simpler and straightforward to carry out. I was redirected by a moderator off the Microsoft Community Forum.

    Hi,
    You can try following options to disable this prompt, but we don't recommend you to do so since this feature helps you to protect your computer.
    Option 1: Run command as admin:
    bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
    bcdedit -set TESTSIGNING ON
    Restart your computer to apply changes.
    Option 2: Disable in GPO:
    1.Type gpedit.msc in the Run dialog and press Enter.
    2.In the Group Policy Editor, navigate to User Configuration → Administrative Templates → System → Driver Installation.
    3.Double-click on Code signing for device drivers in the right-side pane as shown above.
    4.In the windows that opens, choose Enabled. In the Options, choose Ignore as shown. Then click on the OK button to save the settings.
    Restart your computer to apply changes.
    Kate Li
    TechNet Community Support
    Unmarked as Answer based on OP's request. 
    https://social.technet.microsoft.com/Forums/en-US/35ab1279-c3a1-46be-9f7d-45e8606c1410/this-advertised-application-will-not-be-installed-because-it-might-be-unsafe-contact-your?forum=w7itproappcompat
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Introduction of User Interfaces in SAP CRM

    Can someone tell the progression on how the SAP CRM  User interfaces (UI) were launched? for example, which  CRM versions supported which UIs (PCUI, WEBUI etc)
    Thanks
    or else, is there a documentation that provides differences and commonalities between CRM UIs

    Hi,
    concerning CRM User Interfaces it is very simple:
    1. WebClient UI: is the only supported User Interface for Users since CRM 5.1 and this is also the way forward from SAP point-of-view. SAP keeps investing in improving the WebClient UI for CRM in the coming releases.
    2. SAP GUI: is only used for Adminstrative tasks, customizing and developments in CRM.
    3. PCUI: is no longer supported since CRM 5.1
    Kind regards,
    Carl

  • Configuration of SAP MDG User Interface in Customer Namespace - 7.0

    Hello All.
    I have been constantly reading about the mentioned content,
    SAP MDG user interfaces from one single place. A dedicated WebDynpro application is provided to manage all user interface configurations.
    You can also copy a standard SAP user interface configuration to the customer namespace and configure it to your requirements.
    Can anyone give more details about the SAP MDG User Interface or share any links which denotes the same in detail.
    Any Help Appreciated !!.
    Regards,
    Shankar

    The document mentioned in the link does not state anything related to use user interface in customer namespace as suggested by sap in Innovations page. this is more about FPM applications.
    Can you please suggest how do we use MDG User Interface in the customer environment directly as suggested by SAP.
    Regards,
    shankar

  • SSM 7.0 - SSM User Interface user access and utilization

    Hi,
    Does anybody know how to obtain the SMM User Interface access and utilization of the users?
    I mean User Interface access statistics like:
    - Number of loggins per day, week, month.
    - Last loggin
    - Tab used
    - Minutes log inn
    Thank you very much in advance.
    Kind regards,
    Santiago

    Santiago,
    Strategy Management does not track that kind of usage of the system. Any tracking like that might be something that NetWeaver CE could do, but that would be a question for the NetWeaver CE Forum as I couldn't provide guidance on how to set it up.
    Regards,
    Bob

  • Error while creating a callable object - User Interface

    Hello,
    When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
    Is there any body who allready had somthing like this.
    Greetings
    Kurt

    Hi Raja Akella,
    I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
    I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
    In the visual administrator i get the following  errors.
    <b>Error 1</b>
    Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         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)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 2</b>
    Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         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)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 3</b>
    Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
    Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
    thanks in advance
    Kurt

  • SAP SSM Standard vs SAP SSM Enterprise

    Hi Everyone,
    We would like to utilize SAP Strategy Management, however, we are still in the process of reviewing the functionality. Right now we are tangled between SSM Standard and SSM Enterprise. Can anyone give us an idea what's the difference between the two? And we were advised that SSM Enterprise has integration templates available; how can we get those templates? In a cost standpoint, what will be the recommended of the two?
    Thank you very much for sharing your thoughts on this.
    PS. Were can we get a detailed documentation of the functionality of the two.
    Rally

    Rally,
    SSM uses Contexts as a way of cascading strategy throughout an organization. Each Context within SSM can have different goal diagrams as well as having more specific objectives. Think of a Context as how an organization looks at their business. A Context can be regions, it can be functional areas - finance, HR, manufacturing, marketing, etc., it can be lines of business - gas delivery, electrical delivery, customer service, or combinations of those.
    Since individual users are accessing SSM, the administrator could designate which Contexts they have access to. That way the Southeast Region's salespeople could see their objectives and KPIs for the Southeast, but for no other region. A sales manager could have access to several of the regions they were responsible for.
    A multidimensional Model is associated with Contexts and it, as well, can be used to provide the appropriate data and metrics for users. A Model is what is constructed to define the type of data, its dimensions, measures, and KPIs.
    As far as functionality and features goes, there is no difference between Edge and Enterprise. Edge has all of the same tabs available: Home, Strategy, Scorecards, Dashboards, Initiatives, and Reports. It allows Operational Reviews, Comments, Alerts, and the same individual perference settings as Enterprise. The limitations for Edge should still meet the needs of small or medium sized organizations.
    EPM is the suite of applications of which SSM is a part. For the difference between 7.0 and 7.5, each of the individual products will have their own enhancements as well as additional integration with other products in the suite. The 7.5 versions of EPM products are still in the Ramp Up process, while I believe the 7.0 versions are in general availability. SSM is available as an individual application or can be purchased as part of the EPM suite.
    Regards,
    Bob

  • Difference between SAP-CRM 2007 UI and previous version UI.

    hi,
    anyone knows the differences difference between SAP-CRM 2007 UI and previous version UI.
    anykind of links or files are helpful.
    regards.
    raman.

    Hi,
    actually quite a late response and I think all the rather technically focuses comments have already been given, incl. the link to a really good slide deck, that explains all the technical architecture details on what exactly we did.
    From an end user perspective some other statements on what we did:
    (1) From an information architecture and visualization perspective we acted based on feedback from our customers in the last years, which led to some restructuring of the screen, e.g. moving the navigation bar from the top area of the screen (horizontal) to the left hand side --> sounds simple but users tend to have problem seeing thing at the top of the screen. We also decided to arrange the information for e.g. an account or an opportunity not in a tab oriented format. Again usability tests in CRM had shown that users often find it hard to see and understand that tabs contain additional information. We now show the details in assignment blocks below the header information in a scrollable format. Vertical scrolling is a behavior of a screen that most users know from their internet experience. Those are just two exampels of what we did in this area
    (2) We also have put a large focus on well known web behaviors, like drag & drop and personalization in general, knowing that on the one hand side, no matter what standard UI we deliver, users tend to adapt it exactly based on their needs and wishes. So you will find really easy to understand personalization options everywhere in the new CRM Web Client UI. To achieve this we used lots of web 2.0 techologies that enable especially these easy interactive capabilitites.
    (3) Finally, and this relates directly to the arguments mentioned in (2) we focused as well on really easy UI configuration. Again, in every customer project user interface changes are made, to adapt the SAP default to the customers needs. here we invested a lot to make the 60-80% most common UI changes done in projects as easy as possible, that even non-technical people can generally do it (like Power users).
    Hope this clarifies some arguments what from the users point of view has been done and what the advantages are.
    When you follow the same link as mentioned by Nadine above, you can also find a presentation UI Concept, which explains all the details rather from a users perspective.
    Best regards and enjoy the new UI ..and every feedback is very much welcome, only with your feedback we can improve the solution even more.
    Ingo

Maybe you are looking for