CSS & Web Dynpros

Hello Portal Developers,
We want to develop a webdympro and we want to define it theme as standar portal theme (as Universal Work List iViews).
Iu2019m wondering if I can integrate a Cascading Style Sheet pattern of reference an Portal Theme into a WebDynpro using some kind of tool to make it, maybe a NetWeaver Development Studiou2019s option. Do you know is possible and how can I do it?
Thanks in advance
Any suggestions are welcome
Virginia

Hi,
Here are related links
Change CSS in Web Dynpro?
Using CSS for portal theme
old css for webdynpro
Using customized css in a portal application
css theme files
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/045dc49d-0e01-0010-f097-fdbeb1b68aee
regards,
Pradeep

Similar Messages

  • Change CSS in Web Dynpro?

    Hi,
    Is there a way to change CSS( like background, font etc..) in Web Dynpro?
    If yes, how please..
    Thanks.
    Adibo..:)

    Hi,
    How can I see which CSS / STYLESHEET am I using..
    When I startr web dynpro and see source, I can't find stylesheet..I see this:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html dir="ltr">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <title>ZZ_AA_RM2 [Web Dynpro voor ABAP]</title>
    <script type="text/javascript" language="JavaScript" src="/sap/public/bc/webdynpro/ssr/SAPWebFramework.js?00037"></script>
    <script type="text/javascript" language="JavaScript">
    var frame_A = "B8565B8D826AE747B1262BE0CCBF3261_A";
    var frame_B = "B8565B8D826AE747B1262BE0CCBF3261_B";
    var lastShowFrame;
    var lastHiddenFrame;
    var responseCounter;
    var is_suspend = false;
    SAP_bindPageToDomain();
    function Loader() {
    function exitApplication() {
    //only send unload template in case of it is not a suspend
    if (!is_suspend)
    img=new Image;
    img.src="zz_aa_rm2/~ucfUNLOAD?sap-contextid=SID%3aANON%3aNLGMSAP01_R3D_00%3aHGXA2LFUGVJ4MFDzsUQKTDfs4SCyitT-WGhwfsoR-NEW&sap-wd-clientWindowId=17327";
    for(i=0;i<70;i++){ tmp=document.body.outerHTML; while(tmp)tmp=tmp.slice(1) }
    document.getElementById("B8565B8D826AE747B1262BE0CCBF3261_FRAMESET").onunload = null;
    ETC......

  • Using css with web dynpro

    Hi
    I have an application, where i have to use my own css files. regarding this i found one post (with the same heading as this post)  in the forum where the method was specified and also it was mentioned that in the visual admin, in the property sheet of the application, the property for this has to be set true.
    When we checked here, we are able to find the path and corresponding property sheet in SP9. But we are using SP14.  In this version the specified path for the application and property sheet of that application couldn't be traced.
    Is it possible that in SP14 version, the path might  be somewhere else? If so,can anybody please provide with the updated path.
    Thanks & regards,
    Puneet

    The source of Web Dynpro generated files aren't *.java files, but *.wdcontroller files
    I'm not familiar with PMD, but you might need to add the extra file extension
    (Being it Java source encapsulated in XML, you may run into a plethora of other issues, but you could give it a try)

  • Theming Options for Web Dynpro ABAP/Java - Custom CSS

    What options are available for creating a custom CSS for WDA?  My project is going towards SAPUI5, and they want to apply the same look and feeavl to their Web Dynpro applications.
    I know the Theme Designer is an option - but this customer is running on NW 7.3.  Obviously to get the WD CSS to look similar UI5, it will require changing all of the WD selectors.
    Finally, we have a 7.4 Sandbox.  If I build the theme there, is it backwards compatible to their 7.3 landscape?

    UI Theme Designer is the only supported way and it is available for NW 7.3 as well, assuming you are up to date on Support Packages. As long as you create a theme with UI Theme Designer the theme will work in any system that supports the same, there might be small functional and visual differences though depending on the SP levels of the source and target systems. SAP recommendation is to always use the latest version available to create (and consume) themes. You could start by using the Cloud version of UI Theme Designer, export and import into your own system. That said your NW 7.3 system needs to support UI Theme Designer to be able to use custom themes created by it.

  • Using CSS for Web dynpro application in EP

    Hi,
    I have some CSS (Style sheets) which I need to apply to the portal, so that all the web dynpro applications can have the same look and feel.
    I read something about Theme Editor in EP. Can I somehow use that to import the CSS contents into the EP theme?
    Any pointer to using CSS for Web Dynpro applications will be appreciated.
    Thanks.
    Puneet

    Hi,
    Go thorugh the follwing Web Dynpro Java
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/nw04stack09themes.zip
    To know how to use it and for the steps to be followed please follow the tutorial here
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to edit web dynpro themes.pdf
    the last url gives you a step by step procedure with wizards..
    Regards,
    RK

  • ABAP Web Dynpro CSS Stylesheets

    Hallo,
    I have a question concerning "ABAP Web Dynpro". My current task is to implement an application for our company intranet. This application must have the look an feel (corporate design) of the company I'm working for. How can I manage this by using ABAP Web Dynpros?
    Where can the Stylesheets be found and how can I change them in order to fit our corporate design.
    While answering please consider that I am a raw beginner concerning ABAP Web Dynpros.
    Thank you in advance.
    Kerstin Röck

    You need to Change the Themes , For that you need ThemeEditor. You can download that from SDN. First install that and then Download the theme from Mime repository. and then Create a Theme Editor project (It is basically NWDS which consists of ThemEditior plug in).
    Here you can change the CSS properties and then Go back and create a New theme under the Respective mime Repository.
    Search in SDN also you get lot of articles and Forum questions.

  • Trying to run a Web Dynpro Simple Sample with no luck??

    Hi I have downloaded a Web Dynpro and BPM simple sample application from this location: The problem is after configuring the CE instance and setting everything up, when i Deploy and Run this app i get the following error displayed can some one please help?? 500 Internal Server Error SAP NetWeaver Application Server/Java AS The initial exception that caused the request to fail, was: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) ... 115 more See full exception chain for details. Failed to process request. Please contact your system administrator. 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). For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811. Correction Hints Exception could be caused by the development component: tcwdwebdynpro Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases. System Environment Client Web Dynpro Client Type AJAX Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; LLY-EMA-EN; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; LLY-EMA-EN; LLY-EMA-EN) Client Type msie7 Client Type Profile ie6 ActiveX enabled Java Applets enabled Accessibility mode disabled Inline CSS false Validate by rendering true Server Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.2001.20091210105536.0000', change number: '79724', codeline: NW720_01_REL J2EE Engine 7.20.3710.69682.20090922144234 System ID (SID) CE1 Server Node ID |3191650|31916|Server 00 00_31916|YHP30964.ema.lilly.com/40.205.138.181|SERVER|RUNNING Java VM SAP Java Server VM, version:6.1.007, vendor: SAP AG Operating system Windows XP, version: 5.1, architecture: x86 Application Java EE Application (deployable object) ides.com/soacmpssc~salsord Web Dynpro Application CreateSalesOrderApp Request URI /webdynpro/resources/ides.com/soacmpssc~salsord/CreateSalesOrderApp Version vendor: 'ides.com', name: 'soa/cmp/ssc/salsord', location: 'localDevelopment', counter: '20100329143545', change number: 'null' Session & Other Session Locale en_GB Session Timezone Greenwich Mean Time Time of Failure Mon Mar 29 15:38:53 BST 2010 (Java Time: 1269873533200) Session User ClientUser(id=USER.PRIVATE_DATASOURCE.un:Administrator, name=Administrator) Http Session Id tCJhFjXUItrW3M0cACKdKt9MDaBiM0upJwFiszAA_SAP Client Window Id Application Session Id b2a8d9023b4011dfb81f001b7889332c Web Dynpro Code Generation Infos ides.com/soacmpssc~salsord WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:22+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:22+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) sap.com/tcwdapi WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:32+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:55+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) Detailed Error Information Detailed Exception Chain com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session b2a8d9023b4011dfb81f001b7889332c. The causing exception is nested. RID=b2a8d9003b4011dfbdb7001b7889332c at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:606) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:335) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87) at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:98) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:79) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:566) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1438) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:603) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:71) ... 48 more Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'ERP_META' and WS interface 'SalesOrderBasicDataByBuyerAndBasicDataQueryResponse_In'. One possible reason is that the metadata destination 'ERP_META' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:558) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:457) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:425) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:399) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:334) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:307) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:93) at com.ides.soa.cmp.ssc.salsord.findsomodel.FindSOModel.<init>(FindSOModel.java:114) at com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd.<init>(CreateSalesOrd.java:732) at com.ides.soa.cmp.ssc.salsord.createsalesord.wdp.InternalCreateSalesOrd.<init>(InternalCreateSalesOrd.java:8892) ... 53 more

    Hi Anixan
    Please update the SAP AS Java at windows >> Preference >> SAP AS Java >> Add new SAP >> Put instance Hostname like 'CE1' and Instance Number like '00'. Then please verify that is connected or not in NWDS at windows >> show view >> Others >> Server >> Servers
    **Also update the Update your server IP address and host name in host file entry at (Start > RUN > drivers > etc > host file)
    and update JAVA_HOME system enviromental variable in my computer (My computer > Priperties >> Advance >> Startup and Recovery >> Enviromental Variable >> System Variables >> Add new JAVA_HOME parameter with path for installed Java JDK)
    Please check here http://help.sap.com/saphelp_nw70/helpdata/EN/43/3976df43b33575e10000000a11466f/content.htm
    Hope it helps
    Regards
    Arun

  • Web Dynpro ABAP Stylesheet - Portal Integration

    We have a Web Dynpro ABAP being displayed through a Portal iView.  The Portal server and the Web Dynpro ABAP server are separate.  Our problem is in getting the Web Dynpro ABAP to use the stylesheet of the Portal.
    We can make this work by forcing an external stylesheet (via application parameters, global Dynpro settings, or passed on the end of the URL), but we have to hard-code the full URI of the Portal stylesheet.  This would be very hard to manage if we hard-code every iView's CSS location (or set every individual Web Dynpro's application parameters), and we want instead for the Portal to supply whatever the user's stylesheet is dynamically. 
    So what we want is: if we change the Portal stylesheet, the Portal would just pass the new stylesheet URI to our ABAP Web Dynpro iViews without manual modification of the iViews.
    Here is an example of what works:
    http://our-abap-server.com/sap/bc/webdynpro/sap/cprojects?sap-ep-themeroot=https://our-portal-server.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/ourportalstylesheetname
    Shouldn't the Portal iView automatically pass sap-cssurl or sap-ep-themeroot to Web Dynpro ABAP?  We have "Supply Portal Stylesheet" checked on the iView… it just doesn't pass anything to the Web Dynpro ABAP.  Why wouldn't SAP pass this parameter dynamically to the Web Dynpro ABAPs?  Is this a product error? 
    There seems to be a great deal of confusion about this on the SDN message forums... I think this may be the core issue.
    We are using a 7.0 SP13 Portal with an ECC 6.0 SP12 backend.

    Now that you mention it, I ran into that exact same issue  -- the application parameters didn't work for hard-coding the theme.  The fix ended up being the web server semicolon thing I mentioned earlier (that was why the parameter didn't make it to the backend). 
    The themeroot is automatically sent to the backend from the portal, so you shouldn't really have to manually send it as a parameter anyways.
    I'd suggest talking to your network guys.  Also this could be the result of the SP you are on (we're on 13 for the portal and the backend system -- maybe this feature doesn't work in some earlier SP's?).  There are also some options to force the theme as a WD application parameter on the backend side, which you could check into.  Details on those are here:
    [http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/fb57412df8091de10000000a155106/frameset.htm]
    Also you could look at the requests being made by installing HttpAnalyzer in your browser.  You can inspect "post" parameters going from the portal to the backend system.  One of those posts (the first one to the backend system) should contain the parameter sap-cssurl (same kind of thing as sp-ep-themeroot).  This is where our problem turned up as this parameter was not being posted.
    Lastly, make sure that your frontend portal and backend portal are in the same domain.  For instance:
    frontend.domain.com
    backend.domain.com
    If your backend and frontend are in different domains it messes all kinds of things up, including stylesheets I think.  If you can't get around this, then read about domain relaxing (but I highly recommend getting the domains the same).
    When we started, ours were:
    portal.dx.company.com
    sap.company.com
    This created all kinds of problems.  Putting our systems in the same domain with the same protocol and fixing our little semicolon web server problem fixed basically all of our portal complaints.  Up until that time, we had also had many problems with session management (backend sessions were getting stuck until the HTTP timeout).
    That's all I know.   Good luck.

  • Creating mobile web dynpro application which customized theme

    Hi guys,
    I have created a mobile web dynpro application and a theme with Theme Editor. Then I have appended this theme with the sap-cssurl parameter to my application.
    <b>my_application? sap-cssurl=http://host:port/webdynpro/resources/sap.com/tcwddispwda/global/SSR/themes/MyTheme</b>
    It works well in my first testing on my laptop.
    In order to test it on my mobile device I have also appended sap-wd-client parameter to my application. Now my URL looks like
    <b>my_application? sap-cssurl=http://host:port/webdynpro/resources/sap.com/tcwddispwda/global/SSR/themes/MyTheme&sap-wd-client=PieClient</b>
    It doesn’t work. My application layout looks as if I don’t use the theme. Did somebody have the same problem and can help me by finding a solution.
    Thanks for your answers.
    Marita

    Hi Marita,
    Mobile Web Dynpro supports several handheld mobile devices. I guess yours is a Pocket PC. Except the newest Pocket PC 2003, all the other versions don't have CSS support. Therefore the current Pocket PC client "PieClient" of Web Dynpro lacks the ability for customized themes. On the other hand, themes are supported for more advanced devices, such as Nokia Communicator 9500/9300.
    Regards,
    Wei

  • How to modify themes in web dynpro abap

    How can we identify which css file and class are used in web dynpro abap iview ?? I m new to web dynpro abap application. I need to change the look and feel of the page developed in web dynpro abap.
    How i can use css files to change the UI of the page and how can i reach to the css file and class of  a particular page developed in web dynpro abap. When we run the abap application on browser we don't get view source of it. Please tell me the ways to find the css and class files to modify them

    >
    Narendra wrote:
    > Hi,
    >
    > You can create one .css and .js page of page type Page with Flow Logic.and can make use in your normal .htm page..
    >
    >
    > Regards,
    > Narendra.
    I don't believe that your answer applies to Web Dynpro ABAP.  Page with Flog Logic sounds like BSP.  Please make sure you are posting about the correct technology.

  • Style Sheets in Web Dynpro ABAP

    hi gurus ,
    can we add our css in abap web dynpro?
    is it possible or its using by default portal css.
    if it is possible ,please tell me the way.
    warm regards.

    Hi,
    see the
    [documentation|http://help.sap.com/saphelp_nw70/helpdata/en/46/89af7fbe4d429ee10000000a1553f7/frameset.htm] and take a look at threads with similar queries in this forum.
    Regards, Heidi

  • How to call custom themes for Web Dynpro ABAP Application?

    Hi,
    I need to change the appearance of Web Dynpro ABAP application. So far I followed below steps,
    1.     Created theme folder u2018testngou2019 (SE80->MIME Repositoty -> SAP->PUBLIC->BC->UR->nw5->themes -> u2018testngou2019 ).
    2.     used program BSP_UPDATE_MIMEREPOS to dowmloaod content of  u2018sap_tradeshowu2019 (SE80->MIME Repositoty -> SAP->PUBLIC->BC->UR->nw5->themes -> sap_tradeshowu2019) to desktop.
    3.     Modified the themes using Eclipse Theme Editor.
    4.     used program BSP_UPDATE_MIMEREPOS to upload modified themes to MIME repository u2018testngou2019  (SE80->MIME Repositoty -> SAP->PUBLIC->BC->UR->nw5->themes ->  u2018testngou2019) .
    My current URL is like http://server.name:XXXX/sap/bc/webdynpro/sap/hrrcf_a_startpage_int_cand?sap-client=XXX.
    Now I want to know how custom themes called for Web Dynpro ABAP Application.
    Is my approach correct?
    ...Naddy

    Hi Naddy,
    What you used is one way and even I failed when tried that method,
    Instead go to SE38 - WD_THEMES - and you need to upload the zip file and you need to follow a folder structure.
    it is case sensitive, atleast the zip file.
    Make a zip file by name "Project.zip" -
    Create a Folder Project and have the below folder structure,
    1  data - all the properties files and also the designinfo file, below is the code
    2  themes - (to get all the files download the theme from portal and you will have all the folders)
       2.1  ur
         2.1.1 name of the theme
           2.1.1.1 common
           2.1.1.2 csf
           2.1.1.3  r
           2.1.1.4  ur - all the css files (would be good if you can get the files from the server.)
           2.1.1.5   WSRP
    3  war - empty folder
    *.designinfo
    isVisible=true
    version=7.0.14.1.0
    isDefault=false
    isSapDesign=false
    designName=**** name of the theme
    Once done create a zip file and click on Start Import and give the path and will ask for transport request, it will take a while to upload once done as mentioned in the use the parameter sap-ep-themeroot="path"
    This will resolve the issue.
    Cheers-
    Pramod
    reward points if helpful

  • Lost colors in my abap web dynpro iview when i publish portal

    hello everybody,
    i have a strange problem:
    i create a abap web dynpro application and i create a iview in portal for publish it.
    everything work good
    today we decide to publish in internet the portal using an alias. so we changed all reference in system configuration (w.a.s. url).
    the portal work correctly but we see the abap dynpro iview in whitout color. Only test
    it seems he lost css style link....
    any suggestion?

    somebody can help me?
    maybe is lost .css file?

  • Using Portal Theme for a Web Dynpro ABAP Application

    Hello everyone,
    I've created a web-dynpro abap application that I display on one of my portal pages using a Web-dynpro iView.
    Somehow, the WDA app never reads the portal theme properties and has the default SAP roadshow theme colors. I've tried almost everything including passing the theme as an application parameter using WDTHEMEROOT and WDFORCEEXTERNALSTYLESHEET params.
    Documentation states that the application should automatically read the portal's theme, but it never does.
    Interestingly, I have one more web-dynpro java application that works fine and uses the portal theme correctly.
    Am I missing anything? Are there special considerations for WDA apps to adapt to the current portal theme?
    Any ideas, suggestions, solutions would be greatly appreciated.

    >Am I missing anything? Are there special considerations for WDA apps to adapt to the current portal theme?
    What are the release and support package levels of both your ABAP system and your portal?  If the ABAP AS has a later release or SP level than the portal, the Web Dynpro framework will always fall back to using the theme of the backend ABAP system.  This is to protect the application rendering.  Running with a theme (CSS and JavaScript) from an older release or support package level could cause the application to render incorrectly.

  • EREC: theme for Web Dynpro ABAP pages (external candidate)

    Hello,
    I have created a custom theme in the SAP Netweaver Portal for my customer and now I have the requirement to use the same theme for my stand-alone Web Dynpro ABAP applications (pages for the external candidate). Is it possible to use the same stylesheet as in the portal, without having to recreate a theme?
    I tried several options, but none of them did work:
    A. Downloading the portal theme as a ZIP file and then uploading it in ERP using the report BSP_UPDATE_MIMEREPOS (after unzipping) to a location /SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME. After that, I call my application with the additional URL parameter sap-wd-themeroot=/SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME but it does not work (the app is displayed with the default sap_tradeshow stylesheet)
    B. I also tried calling my app using the URL parameter sap-cssurl=/SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME but here again, it does not work (the app is displayed with the default sap_tradeshow stylesheet)
    C. Downloading the portal theme as a ZIP file and then uploading it (zipped) using the report WD_THEMES, but here I receive the error "no themes found in the ZIP file". I have the same error if I upload only the ur.zip I receive from the portal (instead of uploading the whole *.zip file)
    I checked the UR versions both in portal & ERP, and we had a lower version in the portal than in the ERP, so we upgraded the portal version according to SAP note 1446099. Now we have a higher version in the portal than in the ERP. We regenrated the portal theme and downloaded it again, but with the same result.
    Does anyone have an idea what could be the solution to our problem?
    Thanks in advance!

    I would recommend to try another way. If it is possible to access any SAP Portal from outside you can use two URL Parameters to integrate the Portal style sheets in a standalone WDA application. The parameter sap-cssurl contains the absolute URL address to the style sheet and parameter sap-cssversion the current SAP Portal style sheet version. For all external facing scenarios it is important to use the whitelist mechanism to block unknown URLs.
    Example
    ?sap-cssurl=http://myportal.myserver.com:50000/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/mytheme/ur/ur_ie6.css
    &sap-cssversion=7.11.5.20.0
    I canu2019t recommend to raise manually the version number. You will not get an consistent system this way. The meta data (project.zip) are outdated and of course you will get an outdated theme.

Maybe you are looking for