Hi Experts,

We are facing below exception in Production portal default trace.

com.sap.sql.log.OpenSQLException#Cannot assign a java.lang.String object of length 290 to host variable 1 which has JDBC type VARCHAR(105).#com.sap.sql.log.OpenSQLException: Cannot assign a java.lang.String object of length 290 to host variable 1 which has JDBC type VARCHAR(105).

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)

at com.sap.sql.types.GenericResultColumn.checkLength(GenericResultColumn.java:213)

at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:63)

at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)

at com.sapportals.portal.pcd.pl.ShortStringTable.select(ShortStringTable.java:111)

at com.sapportals.portal.pcd.pl.ShortStringConverter.shortToLong(ShortStringConverter.java:120)

at com.sapportals.portal.pcd.pl.PlFactory.convertShortNameToName(PlFactory.java:1155)

at com.sapportals.portal.pcd.gl.PcdObjectFactory.convertShortNameToUrl(PcdObjectFactory.java:176)

at com.sap.portal.unification.LocalScenarioHelper.fetchIPortalRole(LocalScenarioHelper.java:314)

at com.sap.portal.unification.LocalScenario.getDefaultTarget(LocalScenario.java:95)

at com.sap.portal.unification.ObjectBasedNavigation.getDefaultTarget(ObjectBasedNavigation.java:95)

at com.sap.portal.unification.ObjectBasedNavigation.getDefaultTarget(ObjectBasedNavigation.java:78)

at com.sap.portal.navigation.ObjBasedNavigation.resolveOBN(ObjBasedNavigation.java:326)

at com.sap.portal.navigation.ObjBasedNavigation.doContent(ObjBasedNavigation.java:530)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:207)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:112)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:249)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:561)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Kindly help us in resolving the above issue.

Thanks and Regards,

Devi

Hi,

I have been tasked with looking into some alerts coming from a clients SolMan regarding some "Java Jobs" running on a Netweaver portal.

I have never worked on a Java only system before.  And I'm struggling!

Under Opereations > Jobs > Java Scheduler there are two reoccurring jobs running:

• BPMMailReaderJob
• GalaxyTimerJob

Frankly, I have no idea what either of these jobs do.   The BPM job ends with return code 0.  However the other job ends with return code 24.

I cannot for the life in me find what return code 24 is.   And am i even looking in the right place?!

Sorry to be a newbie!

If anyone can spare two minutes to offer some pointers I'd be grateful.

Thanks

Hi Experts,

ESS services are not working sometimes.

Recently we got error when we open ESS services like Leave Request, We have restarted the EP server then automatically it has resolved. Now we are getting same like that?

Why we get these type of errors.

Can any one provide the permanent solution for this.

Regards,

Vamshi Krishna

Hi All ,

I added the Internal “Read More…” link to a document, but it does not get displayed – please look into it.

Note, that External Link if added is displayed.

Image may be NSFW.
Clik here to view.

which type of  documents in the KM Content folders to be added .to add them in alerts internal link as shown above ss ,I mean in which extension .

can any one reply to this query .

Thanks & Regards

Deepika

Hello All,

Portal version : 7.4

SAP BI Version : 7.4 SP10

I have created a SAP BI system object (attached screenshot) and a SAP BI iView (codelink = com.sap.portal.appintegrator.sap.BWReport) screenshot attached.

Portal and BI are running on different servers.

When I open iView, it is not picking up Portal theme. Reports are shown in SAP Tradeshow theme.

In Portal, we have 3 themes, (3 different desktops depending on set of users).

Hence, we cannot just download & give any one theme to BI team.

It is mandatory that portal dynamically sends the theme to BI side.

Any idea how is this possible?

Thanks & Regards,

Amey

Hi,

I need to increase the font size of text that appear in drop down fields. I have created a custom theme but there is not option for font size of values in "Input fields and dropdown fields". Any idea how to achieve it?

Image may be NSFW.
Clik here to view.

Regards,

Navya.

Dear Experts,

We are planning for our ESS/MSS Portal landscape contains  NW7.0 Dualstack with Backend Ecc6EHP5(nuc)   to NW7.4 with Back end ECC6EHP7(UC)

We have planned for CU&UC Conversion for the back-end systems, but getting doubt in Upgrade of the Portal systems.

We are planning below 2 approaches for Portal Upgrade please suggest which one will be more safer and less time consuming

Plan 1:

1.Splitting the Dual stack system , importing the Java stack on other server and then performing the post activities

2.After successful testing of each and every applications of Pure Java portal along with Back-end then uninstall of Java stack from Dual stack .

3.Perform Individual Upgrade of Pure JAVA Portal and ABAP systems to NW 7.4

4.Perform post activities and adoption of all applications like back end webdynpro abap serives, customized applications etc

5.After Successful testing will go for Production setup.

Plan 2:

1.Installation of New Portal 7.4 along with relevant  ESS/MSS Packages and then migration of PAR files , and also migration/development of each and every used application in old NW70 portal to NW74 system as per feasible ways and then after successful of entire system , will setup the Production Portal environment.

Please suggest in the above scenarios, as per my understanding in upgrade(DSplit takes place) or New installation we are moving to new servers as long as backend system also , so in both cases we need to adopt the all Webdynpro Services and some other required things also . Experts please advise how can we proceed in Our Landscape Scenario.

Regards,

Samba.

Hi All,

After web dispatcher UWL work items are not working

we are changing the system object properties and clear the cache also.

but still it shows the error like can not connect to the provider.

as per note 1133821 we configure UWL and it is working fine.

Please help me

Regards

Rajesh

Dear Portal Developers,

                                      I am new to Portal development can you guys please share me some sample code of inserting some data into table via RFC.

Note : Please do not post hello world link fed up with it.

I have deployed a SAPUI5 application on the EP (Version 7.31 SP 12). This is working fine with the corresponing URL. Now I want to add this to the Fiori launchpad, so I want to add this application as iView. I have created the iView with System: 'SAP_LocalSystem' but when I start the application from my Fiori launchpad I get the following exception:

com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><UI5RelativePath>&sap-language=<Request.Language>&sap-client=<System.client>&sap-locale=<Request.Locale>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 120. Cannot process expression <System.client> because Invalid System Attribute:

System:    'SAP_LocalSystem',

Attribute: 'client'.

at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:561)

at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)

at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)

at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)

at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)

at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)

at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)

at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)

at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)

at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:341)

at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:734)

at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)

at com.sapportals.portal.prt.connection.ServletConnection._handleRequest(ServletConnection.java:224)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:101)

at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

...

Is there any way to get the iView working?

Hi Experts,

We are facing a problem with Standard ESS/MSS services. When we click on any service like Leave Management it taking long time to open the services and displaying below exception.

Exception occured during processing of Web Dynpro application sap.com/ess~lea/LeaveRequest. The causing exception is nested.

[EXCEPTION]

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)

at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:259)

at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:104)

at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)

at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)

at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:842)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1072)

at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)

at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)

at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)

at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)

at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

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:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176

To resolve the issue we have implemented the below note and restarted the server, checked the SLD JCo's.

1234847 - Analysing WebDynpro session LockException.

After making the changes ESS/MSS are working fine, again we are facing same the issue with above exception.

We are looking for the permanent solution to resolve the issue.

Kindly suggest on above.

Thanks,

Devi.

Hi,

we have our own Framework Page and Desktop. But there is a lot of overhead loading from SAP into it.

e.g.

- the complete Theme (css)

- Javascript code

- Html Code

is there a way to delete this code? (we are using NW7.3)

I want a clean Framework Page only with own code.

Thanks

Hi experts,

Is it possible to exchange themes between an SAP Portal (7.4) and the SAP NetWeaver Gateway if both are using the SAP UI Theme Designer?

We are currently developing SAP UI5 applications on top of the SAP NetWeaver Gateway using a custom branding. Therefore we need to create a custom theme within the SAP NetWeaver Gateway.

But as those applications should also be visible via the SAP Portal we could probably extend the Portal Theme directly. (Within the portal iView there is an option to use the portal theme instead of the Gateway theme.) On the other hand we do not want to maintain the theme information on two systems as some of the applications should also run standalone - therefore the gateway theme has to be maintained at all.

Our idea was to export the already finally created custom portal theme and to import it as basis for the new custom gateway theme. Any changes in the Gateway theme then need to be exported in Gateway and imported in Portal.

But if we switch off the UI theme designer in Portal the exported ZIP file has no valid content to be imported to Gateway. And if we enable the UI theme designer and export the theme via standard transport package the resulting EPA file is only valid for portal transports.

That's why our question:

Is it somehow possible to exchange themes between an SAP Portal (7.4) and the SAP NetWeaver Gateway if both are using the SAP UI Theme Designer?

regards

René

Hello Friends

My requirement is to create URL iview and Point to UI5 application which is deployed in SAP ECC as BSP application .

System :

SAP Dev021

SAP DEV022 - to build application

SAP Dev025 - holds test data

I have to create a URL iview pointing to DEV System and client 025 ,

Issue is here the QA team  dose not want to mention Sap-client  025 in Iview Properties .

If i remove this properties from Iview it Point to Dev021

and i can not find any place in HTTP system object to mention client information , please refer below images

URL Iview Created : QA team Requested to remove the URL Parameter SAP -client = 025

if i remove it by default it point to Dev 021

Image may be NSFW.
Clik here to view.

HTTP object created as below , Here i can only mention the System and not the client

Any suggestion ?

Image may be NSFW.
Clik here to view.

Kindly help and suggest ?

points would be rewarded :-)

Regards,

Armaan

Hello Experts,

I have created a transaction Iview on Portal 7.31. It is accessed by the users who are only dialog users but not those who are system users on back-end.  For your reference i have attached the error screen shot. Is there any way so that the users who are system users can access this Iview?

Dear Portal Experts,

                                In my there are two portals sandbox and development iviews are not loading completely in development server portal. Please refer the below attached screen shots for your reference.

Note : 1.The first screen shots the iview is loading properly in sandbox.

          2.But coming to development server the iview is not loading completely as in it is being loaded in sandbox.

Please help me out.

Hello All,

I have a UWL XML where SAPTransactionLauncher type action handlers are present.

I noticed that when a workitem opens via this, the standard green colored 'back' button in SAP GUI is not visible.

Could you please let me know if it is possible to control/direct this via UWL config XML?

Thanks & Regards,

Amey

Hello.,

I've a custom transaction which is directly embedded on portal. the output of this transaction is ALV grid. Am not able to select directory when I try to export it to Local File. 

Please note, we were able to download before SAP patch upgrade. Now, we have upgraded to EHP7, since then we are facing this issue.

Quick help is appreciated. please look at the screenshot which I would see when I click on export/LocalFile

I found on scn

As Administrator, you can choose not to display the Change Launchpad button at runtime so that users are unable to make changes to a launchpad. To do this, set the application parameter NO_CHANGE_LIST_BUTTON to X or the URL parameter NO_CHANGE_LIST_BUTTON=X.

But I cant find proper way to do that. Please help me regarding this.

Good day good people

I need advice with issues we are having.

We have upgraded recently to NW 7.4 Stack05.

We went live mid June 2014.  No issues with any roles.

Manager Self Service role - WDA add-on 1.0.

Desktop and framework =Ajax

We had to update again and have recently installed Stack07 Patch2 on the Portal.

HR version is NW 7.4 EHP7 SP 7.

Desktop and framework =Ajax

Manager Self Service role - WDA add-on 1.0.

Issue:

When one click on the Manager Self Service Role then it opens the MSS Overview and the menu on the 3rd Level Navigation.

The issue starts when one clicks on Team, or on Talent Management etc.

The system redirects the user to Employee Self Service, but the 3rd Level Navigation still have the MSS functionality populated.

If one remove the ESS role, then the system redirects to the first entrypoint on MSS which is the Overview.

This happens with the custom MSS Role and the SAP Standard MSS Role.

We have a simular problem with the Portfolio Management role (PPM6)

Has anyone had this issue before.

Please advice

Regards

Wynand Visser