Javascript error in Standard MDM IViews on portal

Hello Xperts,
I have deployed standard MDM IViews on my  portal.
In standard Resultset IView, there is a provision of saving results by using My Bags option. When I click on My Bags option and then New Bag, it throws javascript error.
Details of systems are as below.
MDM API version 5.5
Portal Version EP 7 SP07.
Appreaciate any inputs for this.
Ashutosh

Hi Anu,
Thanks for the reply.
we are able to login to Data Manager with Mapped ID's and I even tried creating new IViews. Nothing worked.
As you suggested, will try restarting the portal server.
Thanks
Satish

Similar Messages

  • Configure MDM iviews in portal

    Iam trying to configure MDM iviews in portal, When i try to upload the MDMJAVAAPI04_3.sca file i get the below error
    Iam using MDM 5.5 service pack 4
    <i>===========================================================================
    Deployment started Fri Jun 01 16:02:19 IST 2007
    ===========================================================================
    Starting Deployment of com.sap.mdm.tech.mdm4j
    Aborted: development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'SAP AG'/'5.50.20061217101225.0000'/'0', grouped by software component 'MDM_JAVA_API'/'sap.com'/'SAP AG'/'1000.5.50.4.3.20061227155701''/'0':
    Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    Deployment of com.sap.mdm.tech.mdm4j finished with Error (Duration 2964 ms)
    Starting Deployment of MDM_JAVA_API
    Aborted: software component 'MDM_JAVA_API'/'sap.com'/'SAP AG'/'1000.5.50.4.3.20061227155701''/'0':
    Failed deployment of SDAs:
    development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'SAP AG'/'5.50.20061217101225.0000'/'0' : aborted
    Please, look at error logs above for more information!
    Deployment of MDM_JAVA_API finished with Error (Duration 1272 ms)</i>
    My SDM password and portal administrator password are the same. But dont know why it says login failure.
    Please help
    If some one has the detailed steps for configuring the mdm iviews in portal please help

    Hi Suresh,
    I also have some requirement to use MDM standard iViews.
    Can u give me the list of scas and sdas which i need to deploy on the portal srever.
    I have already deployed the following scas and sdas.
    1.com.sap.mdm.tech.mdm4j.sda
    2.com.sap.mdm.tech.connector.sda
    3.BPMDMTECHN00_0.sca
    4.BPMDMAPPLI00_0.sca
    i am also using MDM 5.5 sp04 and EP7.0
    after deploying these jars, i am getting the MDM system template but after that it gives me runtime exception
    Following is the runtime exception while creating system
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    iView not found: com.sap.pct.mdm.tech.systems.MDMSystemWizard.
    Exception id: 12:43_05/06/07_0049_11774250
    See the details for the exception ID in the log file
    Thanks in advance,
    Regards Shruti.

  • Calling of WS from standard MDM iView

    Hi all,
    I am having standard MDM iViews on the portal which are used to fetch data from MDM repository.
    Now i want to call a WS using the data filled on the standard MDM iView.
    Is there any way to call a WS from portal iView.
    Aur u can suggest any other way to call the WS.
    Thanks in advance.
    Regards ,
    Shruti.

    hi shruti...
    try these links.....
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9d6132b0-0801-0010-86a1-d7308895761a
    Consuming WebService in Visual Composer-1
    http://help.sap.com/saphelp_nw04/helpdata/en/82/6a0e7bbe744276bf393654b9b576ed/frameset.htm
    Regards,
    Sudheer

  • Error in Standard MDM Search IViews

    Hi All,
    We are using MDM Standard search IViews in our project.
    From past 2 days all the search IView are giving  *Error performing search Can not authenticate user session *
    I tested the System Connection and it is working fine.
    I checked the user mapping and every thing is fine.
    and we have not done any changes too.
    can some one help me in knowing what could be the reason
    Regards,
    Satish

    Hi Anu,
    Thanks for the reply.
    we are able to login to Data Manager with Mapped ID's and I even tried creating new IViews. Nothing worked.
    As you suggested, will try restarting the portal server.
    Thanks
    Satish

  • MDM iviews in Portal throws error in key Mapping

    Hi,
    I have EP7 with SP15 and MDM 6.0, recently upgraded. Before upgrade we have an application which uses the MDM iviews and maps the fields of one table to other and displays in some other iview.
    The application was working fine before upgrade of MDM. But after upgrade, the mapping seems not working.
    My scenario is as : Using MDM Search iview, I search records from MDM repository, Main Table. This result is displayed in MDM Result iview. From this result iview, I select a record. From this selected record, a field is mapped to the other table. The mapped record, then, is displayed in MDM Details Iview.
    After MDM upgrade, whenever we select a record from the result of table 1,the mapped iview throws erros :
    Error occurred: Error performing search. com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter,  com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter (see log for details)
    when serached log : it says error in <table 1>-Key mapping  <table1> is first table.
    We have used EPCF eventing for MDM iviews.
    has anyone out there faced same issue ?
    Please let me know your views.
    Regards,
    Abhijeet

    Hi Abhijeet ,
    check the below wiki
    findout anything is needed related to keymappings
    "if Keymapping is selected, your Result Set iView only displays fields that are related to key mapping.This step depends on the search table selected and the schema of the repository that you are connected to"
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/set%2biviews
    check the search table and schema of repository properties you connected
    Koti Reddy

  • Error in deploying VC iView on Portal

    hi all,
    i have created an applicaton which will fetch data from SAP R/3 and will be shown in an iView which is made in VC.
    when i try to deploy that iView in Portal , i get an compilation error ,
    the error is
    "Error in executing a process for compilation, .\GUIMachine_Business_Packages\testbi_21811\com.autogen.guimachine.testbi.iView_TestBI\src.core\Iview_testbi_ctl.java:62: cannot resolve symbol
    symbol  : constructor BWQueryFunction (java.lang.String,com.sapportals.guimachine.ep5kit.Iview_testbi_ctl,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,int,java.lang.String)
    location: class com.sap.portal.guimachine.bikit.runtime.BWQueryFunction
       BWQueryFunction BWQGQR = new BWQueryFunction ("BWQGQR", this, profile.getProperty("System1"), "/sap/bw/xml/soap/queryview", "ZVC_CUBE", "VCQUERY1", "", 2, 500,"KEY");
                                                     ^
    1 error
    how could i solve this problem.
    please help me to solve this error
    Regards
    Naveen Gupta

    Hi,
    If you are using Ep 6.0 Sp 15 then you have to deploy the BIKIT for Sp 13 on the portal using SDM.
    This will solve Your  problem.
    Regards,
    Naveen Gupta

  • Error while creating MDM system on Portal

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

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

  • Getting javascript error while accessing URL iview

    Hi All,
    I have created a URL iview. There is a search functionality in this iview when we search any text then it is giving javascript error (Permission Denied).
    When we use the search functionality of that URL directly in the browser then it is working fine.
    Please Help.

    The URL that is being invoked may not like running inside an IFRAME. Not all URLs work correctly as iViews
    See what happens if you tell the iView to launch in a new window...

  • Javascript error in web Dynpro iViews

    Hello,
    I've developed a web Dynpro page which accesses the default database ( maxdb). This page is working fine when tested by calling the application from the browser.
    Now I've created an web dynpro iview in portal ( EP-6 SP15- Sneak preview). I get java script errors - <i>SSR undefined</i> and none of the drop down boxes are populated.
    Can anyone help me out in this?
    Thanks,
    Sudhakar

    Probably the stylesheets of your Portal are not compatible to the used Web Dynpro version.
    Armin

  • Error while creating webdynpro iview after  portal upgrade to ehp1

    Hello  All
    We have upgraded  our portal from 7.0  sp  15   to  portal  7.01  sp  3    .
    After upgrade we can create  iviews using portal components  but we are not able to create  iview using Iview template
    We are getting following  error  while creating  webdynpro java  iview
    java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.initTemplates(PageTemplateSelection.java:229)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.wdDoModifyView(PageTemplateSelection.java:172)
         at com.sap.newpage.pagewizardpanes.wdp.InternalPageTemplateSelection.wdDoModifyView(InternalPageTemplateSelection.java:305)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         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:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1300)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         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)
    Regards
    Rajendra

    Hello Rajendra,
    please can you tell me, if you finally get a Solution for this Problem about  iviews creation with template Error after upgrade.
    Thanks and take Care
    Gedeon

  • Standard MDM iView for Creation of Record

    Hi All,
    We have requirement to create a record in MDM through Portal.
    Are there any standard iViews available in Portal content of MDM, which can create or update a record in MDM repository?
    In the Portal content we have found following two SCA
    BPMDMAPPLI04_0.SCA
    BPMDMTECHN04_0.SCA
    We have deployed them on the portal server, we are able to see search and itemdetail iViews for standard repository.
    But we are not able to see iViews for creation of record.
    In one of the document it has been given that SP 04 extended (imporved) functionality offers Data Entry and Maintenance (CURD operations) can also be performed.
    But availability of the iViews not mentioned anywhere.
    Anyone has already implemented such kind of functionality or scenario?
    Thanks and regards,
    Shruti.

    Hi Mandar,
    I have followed the same PDF also.
    But I am not able to find out the SCA's which are mentioned in the above document for GP and CAF.
    I tried searching on service market place also.
    In portal Contenet of SP 04 i have found only two SCA's
    BPMDMAPPLI04_0.SCA
    BPMDMTECHN04_0.SCA
    I am not able to find following SCA files.
    H2G_GuidedProcedures.sda
    H2G_SourceCode.zip
    Can tell me how do i get those SCA's?
    Thanks in Advance
    Shruti.
    Edited by: Shruti Shah on Mar 12, 2008 6:19 AM

  • ESS Error in standard Address iView (2004s)

    Hi All,
    NW2004s SP9
    The satandard Address application has a few errors am not sure if it is specific to our implementation as I did not find notes nor any SDN messages.
    In the address application the "Address Line 2" is greyed out and is just a display field even in edit mode.
    The phone number Label is not seen in the application. For the phone number just the area code is avialable for input and the 6 numbers plus the LAbel saying Telephone are not getting displayed.
    Its like
    Blank(Supposed to be Label "Telephone Number"      Area code(P0006-AREAC visible)  Blank(supposed to be P0006-TELNR}
    So its
    example
    Space ..... 716 Space
    when it should have been
    Telephone number   716 123456
    I have seen the web dynpro application source code and it does appear that the fields do exist and are in visible mode.
    The same was the case with address Line 2 field, it was visible and input field, but is just display field when the application is run.
    Did anyone face this issue???
    regards
    Sam

    Shardha,
    Thanks a lot for offering to help me out. my email id is
    [email protected] / [email protected]
    regards
    Sammer
    Message was edited by:
            sameer chilama

  • Pop ups on Standard MDM Portal iViews throw Portal Runtime Error

    Hi all,
    We are facing some issues with MDM Standard Search iViews in Portal. We have configured MDM standard iViews using MDM Search Texts iView, MDM Result Set iView, MDM Search Picklists iView, MDM Item Details etc. We are facing a problem with the MDM Search Picklists iViews wherein we have to click the ellipses button to open the pop up. Whenever we open the pop up, the pop up shows Portal Runtime Error. Please find the screenshot below:
    http://img209.imageshack.us/img209/1138/portalruntimeerror.jpg
    The MDM System is working fine. The other Standard iViews are also working fine. The surprising thing is that, when the Super Admin role is assigned to the user, the iViews start working perfectly as shown below:
    http://img696.imageshack.us/img696/6808/worksfinethisway.jpg
    I have checked the permissions also on all these iViews as well as the System object and did not find any problem. Moreoever, this was working fine till some days back. All of a sudden these iViews have stopped working. Please guide me as to what can be the reason for this and any possible solutions.
    Thanks in advance.
    Regards,
    Ankur

    I would check the logs but it sounds like a permission error to me.  Can you or your basis resources modify the Security Zones?
    System Administration -> Permissions -> expand Security Zones folder -> right click on com.sap.pct.mdm.appl.masteriviews and select Open Permissions -> in the assign permissions section add read permissions for a particular user, role, or group which the user getting the error is part of, check the End User checkbox -> Save.  Login to the portal and try again.
    -Greg

  • LDAP users Faicng Error While Accessing the ESS Iviews in Portal

    Hi,
    My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
    UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.     
    Please contact your system administrator     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                    at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                    at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.java:220)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
                    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)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                    at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                    at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                    ... 76 more
    Thanks & Regrads,
    Subba Rao

    Hi,
    Now every user facing the same error while accessing ESS Iviews from Portal.
    in ST22 Dump is created.
    What happened?                                                                                |
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_XSS_CAT_BUFFER=============CP " in include
    "CL_XSS_CAT_BUFFER=============CM00C " in
    line 50:
    ""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
    " programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
    "COMM", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    |    come across a statement that unfortunately cannot be executed.
    What we need to resolve the above issue.
    Thanks & Regards,
    Subba Rao

  • Clickable URL in a MDM iView

    Hi
    Are there any possibilities to make a clickable URL in a MDM iview. I have a field in my repository with an URL and would like to make it clickable in the portal. This is possible i the SRM_MDM user intreface, but how is it done with standard MDM iViews.
    Regards
    John-Kjell

    Hi John-Kjell,
    This can be achieved by using HTML Text field. Simply add a Lookup field that is referrencing this table and you will see the URL as Clickable.
    Please note that having too much HTML Text fields ni the repository can have a downside in performance.
    Hope this helps,
    Idan

Maybe you are looking for