Obfuscation on SAP User Interfaces

Can anyone provide me with information on how to implement display-only obfuscation for both SAP GUI for Windows and SAP Enterprise Portal?  For example, when a SSN is displayed, on an ESS screen in the portal, display it as "XXX-XX-9999".

In ABAP you can simply use:
screen-invisible = 1
... or use a global constant typed to the field(s) with a value set to '************' which will then always be displayed.
If you want a part to be visible then just concatenate that part with the invisible part or use a subsequent field.
Not sure how the JAVA folks do it, but the search term "MASK" should be helpfull in the SDN Java or portal forums.
In the ABAP and Java programmers security guides on service.sap.com/securityguides there are some code snippets as well. They relate to passwords if I remember correctly but would work generally for UI programming.
Cheers,
Julius

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • Error while deploying IDM 7.1 user interface file on Netweaver Java AS sys

    Hi,
    I am in process of installing IDM 7.1 in my landscape.  I have done IC, RC in one system with windows 2003 + oracle.  On other system I have Netweaver 7.0 SP14 Java AS system.  I have configured as per SAP documentation. 
    While deploying IDM user interface 7.1 on SAP Netweaver Java system 7.0, I get following error in SDM:
    Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_710\IDMIC00_0.sca'
    May 11, 2011 5:16:12 PM  Error: Unresolved dependencies found for the following SDAs:
    1.: development component 'tc/idm/wd/model'/'sap.com'/'MAIN_IDM710_C'/'3542284'/'0'
    dependency:
    name:     'tc/ddic/runtime/facade'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/wd/api'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'engine.j2ee14.facade'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/bl/logging/api'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/wd/legacy'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/bl/exception/lib'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/aii/base/offline/facade'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name:     'tc/bl/jrfc/api'
    vendor:     'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    Deployment will be aborted.
    May 12, 2011 11:04:09... Info: Loading archive 'E:\software\IDM\DATA_UNITS\IC_UIS_700\IDMIC00_0.sca'
    Please advise,
    Thanks,
    Digesh

    Hi,
    SMP : http://service.sap.com/swdc -> SAP NetWeaver and complementary products" SAP NW IDENTITY MANAGEMENT" SAP NW IDENTITY MANAGEMENT 7.1
    You would need to deploy the NW IDM IC 7.10 UIS FOR NW 7.00 component.
    Regards,
    Srikishan

  • 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

  • Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

    Hi all,
    I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
    <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIAdapterFramework</SAP:Category>  
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>  
    <SAP:P1 />  
    <SAP:P2 />  
    <SAP:P3 />  
    <SAP:P4 />  
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>  
    <SAP:Stack />  
    <SAP:Retry>M</SAP:Retry>  
    </SAP:Error>
    The entire trace is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    --> 
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> 
    <Trace level="1" type="T">Party normalization: sender</Trace>  
    <Trace level="3" type="T">Sender scheme external =</Trace>  
    <Trace level="3" type="T">Sender agency external =</Trace>  
    <Trace level="3" type="T">Sender party external =</Trace>  
    <Trace level="3" type="T">Sender party normalized =</Trace>  
    <Trace level="1" type="T">Determining the sender agreement</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>  
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>  
    <Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>  
    <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>  
    <Trace level="1" type="T">Remote address = 10.66.10.160</Trace>  
    <Trace level="1" type="T">User = SFUSER</Trace>  
    <Trace level="1" type="T">Process ID: 760</Trace>  
    <Trace level="1" type="T">Work Process ID: 10</Trace>  
    <Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"> 
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>  
    <Trace level="1" type="T">Hop engine type = IS</Trace>  
    <Trace level="1" type="T">Hop adapter name = XI</Trace>  
    <Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV"> 
    <Trace level="3" type="T">No triggers found. OK.</Trace>  
    </Trace>
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    <Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>  
    <Trace level="1" type="T">ACL Check is performed</Trace>  
    <Trace level="1" type="T">XML validation is executed</Trace>  
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>  
    <Trace level="1" type="T">QOS = BE</Trace>  
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>  
    <Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>  
    <Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>  
    <Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>  
    <Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>  
    <Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>  
    <Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>  
    <Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>  
    <Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>  
    <Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>  
    <Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>  
    <Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>  
    <Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>  
    <Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>  
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="2" type="T">Persisting original message</Trace>  
    <Trace level="3" type="T">Message-Version = 000</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>  
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>  
    <Trace level="3" type="T">PLSRVTYPE =</Trace>  
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>  
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>  
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>  
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>  
    <Trace level="3" type="T" />  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"> 
    <Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Skip Inbound Validation =</Trace>  
    <Trace level="3" type="T">Skip Outbound Validation =</Trace>  
    <Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>  
    <Trace level="1" type="T">Reading sender agreement</Trace>  
    <Trace level="1" type="T">Message does not contain a sender agreement</Trace>  
    <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>  
    </Trace>
    </Trace>
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>  
    <Trace level="3" type="T">Message-Version = 001</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T

    HI,
    Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
    Patch level of XIAF:
    1. customers SAP PI level is
    Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
    Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
    2. our SAP PI level is
    Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
    Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
    Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
    Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding  AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
    What do you think ?
    Thanks

  • Select-options in WDJ user interface

    Hi Experts,
    I would like to know why select-options found in SAP GUI screens is not available in WDJ. WDA however has provided this. Is there a possibility that this might be added sometime soon? Or may I please know the reason for omission.
    Warm Regards,
    Abdullah

    no, what I mean is the select-options user interface component. Where in you can specify a range. For example: I can enter a range of employee numbers to be selected for a particular report. In that same control, I can omit some of the employees that I dont want. You can also check the following link for the select-options feature in WDA.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09fec07-0dab-2a10-dbbe-c9a26bdff03e

  • Dynamic user interfaces

    Hello,
    here's a little teaser for user interface experts out there:
    I wonder what kind of techniques ABAP offers for creating dynamic user interfaces.
    When talking of 'dynamic' I imagine something like an arbitrary number of 'containers' where other programs (classes f.ex.) can draw their own user interface into.
    In Java this could be realized with the container concept in swing.
    I have done some research on this topic and the results are so far:
    a plain dynpro: seems to have no dynamic at all -> not an option
    a plain dynpro with a tabstrip: in case the number of tabs CAN be set at runtime AND the subscreens CAN be drawn from inside separate classes -> a definite option otherwise not an option
    any kind of web-frontend (BSP, JSP etc.): web-frontends are not allowed by company restrictions -> not an option
    dynamic documents: I could not find many information on these yet (also not on sdn). In case that an arbitrary number of parts of the dynamic document can be created from inside separate classes -> an option otherwise not an option
    I will be happy about any further information on this topic.
    Best regards,
    Patrick Baer

    I spent some time today doing research on BSP's and built a "BSP-Viewer" embedded into the SAP-GUI. Though I like the concept of BSP's a lot (like I did already with JSP's) but company restricitions are too strict. So BSP's are out of the play.
    After the discussion I started to play around with the different containers and basically I'm quite pleased with them and the "cl_gui_container_bar" allows an arbirtary number of "subscreens" which matches my requirements.
    But as usual there's still a downside:
    I found no option to built text labels and text fields into a container. Unless this is possible I can't give this approach a chance. I already found some postings which seemed to confirm that this is in fact not possible but I can't really believe it. At least from what it looks like it seems to me that the object navigator utilizes both: splitters, containers and all the stuff AS WELL AS the "classical" elements like text boxes, labels and so on.
    Any ideas on how to combine the container concept with text fields, labels maybe whole dynpros or subscreens ?
    Best regards,
    Patrick Baer

  • Not able to change user interface setting screen  (SMCR) in solman 7.1sp3

    Hi,
    I am trying to change the  change advisory board to Developer in request for change(SMCR) screen in General data navigation bar.
    So i changed in partner schema -> define partner determination procedure ->SMCR0001(change request)  ->user interface settings, like SAP solution manager 7.0 EHP1 version. not working
    But solman 7.1 mapped to CRM UI using Business role SOLMANPRO using logical link and direct link group.
    Plz help to change the user interface settings in SMCR screen?
    Rg,
    Karthik

    Hi Andy,
    Please check the below link
    https://websmp102.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000311362008E
    It help to change the Label in SMCR screen. if you face any issue post it.
    After changing the Label , how to change the partner function in
    background for particular field.
    Ex. I have changed Change Advisory to Developer, but Parties involved
    shows only CAB partner function.So how to change the partner function
    after change the label for particular field.
    Any idea?
    Rg,
    Karthik

Maybe you are looking for