Jco Destinations not available in GRC AC 5.3

Hello,
We have installed GRC AC 5.3 with latest patch and configured SLD configuration. It is working fine but the standard virsa Jco destinations are not visible.
Is there any additional settings required to get that Jco destinations?
Regards,
Kumar Rayudu

Hi Kumar,
JCo destinations not showing might be happening because of following two reasons
1. AC capabilities are not deployed properly as mentioned by our friends in this message.
2. Might be an issue with SLD Data Supplier in Visual Admin(VA):
To resolve this logon to VA and select "SLD Data Supplier" under services. On right hand side bottom, you will see
tabs of "Information", "HTTP Settings" & "CIM Client Generation Settings".
Make sure entries in these tabs are correct and check for Data Transfer through SLD in these tabs. Once these tests are passed. Restart who system (not just J2ee).
If the issue still persists, redploy AC capabilities via SDM with "Deployment Configuration" is set to "Update deployed SDA/SCAs that have any version".
Hope this resolves your issue.
Best Regards,
Sirish Gullapalli.

Similar Messages

  • FF ID is not available in GRC system.

    Hi All,
    i have configured FF in GRC system and have dine following activities
    1. maintain connection setting in SPRO.
    2. created FF id in ECC system and assigned FF standard role.
    3. run all necessary synchronization job.
    4. assign owner.
    but FF id is not available in GRC system.
    can you you please help me.?

    Hi Alessandro,
    Thanks for your replay. please find my configuration in details.
    1. Parmid 4000=1,
                   4010=SAP_GRAC_SPM_FFID
    2. Maintain maintain connection SUPMG in SPRO > GRC > Common Connection Setting > Integration Framework > Maintain Connection Settings.
    3. Create FFid in ECC DEV system.
    4. assign role SAP_GRAC_SPM_FFID to FFid.
    5. create FF id owner and FF id controller.
    6.Run Syn.
    but when want to assign controller to the FF ID then found FF is not available.

  • JCO Destinations Not Maintainable from Web Dynpro Content Administrator

    I have Netweaver Preview 04s installed.  Both SLD and app server are running on the same local machine. 
    1) I have tested connection to SLD from WD Content Admin OK Message.
    2) I have created the two destinations using WD Content admin with
        sucess message that it was created in SLD, but the destinations do not
        appear under maintain JCO Destinations of WD Content Admin after creation.
    3) The JCO Destinations are not found in SLD when the wd app is deployed.
    4) The JCO Destinations are found under the deployed components within WD
        Content admin but listed as Status Not defined.  The create link is enabled but
        trying to re-create the items leads to error that they are already defined in SLD.
    5) I have added SLD admin privileges to the Administrator user.
    6) The Test, Ping etc are disabled greyed-out on the two destinations. Only create
        is enabled but this leads to the error message that it has already been defined
        in SLD.
    7) I have clicked on start assigned SLD and checked status is running.
    I don't know how the WD Content Admin can detect the destinations have already been created and yet the destinations do not appear under the Maintain JCO destinations column, nor is it possible to test etc.   I should note that Netweaver Admin indicates that SLD is not accessible.  As I indicated, I did check that connection worked from WD Content Admin.

    John,
    If you have more than one user Id's to login in to the Portal,then try to login with Super Admin role and then check the JCo connections there.
    Search for the JCo connections you have created and test them.
    Also have you given J2EE host name and SAP logon information correctly or not, do check them once.
    regards
    Anil Dichpally

  • Control recipe destination not available in Process order

    Hi PP-PI Gurus,
    When i am sending the process maessages to destinations,i am getting the error"No control receipe destination available in process order".
    When we create master recipe using X-steps, there is no option to enter comtrol recipe destination. Infact we asssign the destination in X-step tree.
    When the control recipe is created for a process order using x-steps, the operations overview will not have the control recipe destination.
    When the status of the control recipe is sent to destination(PI02),the system throws the above error.
    Any help on  how to resolve this error.
    Thanks in advance.
    Mani

    Hi Dhavel,
    Whether it is PI_CRST or PI_CRST2 i am getting the same error message.
    When i am working with Conventional Characterestics based process instructions in my recipe, everything is working fine.
    When i use X-steps instead of process instructions in master recipe to create the control recipe, i am facing this error.
    So it is clear that , when we are using Execution steps(X-steps) to create PI sheet,there needs some extra settings.
    Any body working with X-steps in process order ,request your help please to resolve this issue.
    Mani.

  • Crystal Reports Job Server - Default destinations not available

    Greetings,
    Currently I'm installing Crystal Reports XI onto a new server.
    When scheduling reports they are stuck in a 'pending' status which records the following error in the windows event log:
    Transport System exception for backend plugin DLL type newIJob():: Couldn't get IJob interface: CORBA exception! Object type is: CrystalEnterprise.Report and detail: IDL:omg.org/CORBA/UserException:1.0
    . Details: %2.
    After further investigation I discovered the Crystal reports job server has no defaul destinations, however the servers Destination Job Server and Program Job Server do have the default instances.
    Firstly I assume the error reported in the event log is due to there are no destinations, as the scheduler won't know where to send out to.
    Can anyone help in advising how to ensure the reports server had some default destinations?
    I have restarted the server and rebooted the Crystal reports server too.
    Thanks
    Rob

    Hi RobWhalley,
    Could you provide me which version of Crystal Reports Server XI  you use?
    you could find useful below articles.
    [1202926 - Scheduled reports in Crystal Reports Server XI Release 2 stays in 'Pending' state |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233303332333933323336%7D.do]
    [1477380 - Crystal Reports in Pending status|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333433373337333333383330%7D.do]
    And please check job server is enabled and under the CMC > Server > Crystal Job Server > RightClick on the server > Destination to File System.
    And you can increase the maximun concurrent job value through CMC>Servers>CrystalReportJobServer>Properties.
    Regards
    Rameez Shaikh

  • Share destinations not available

    I have deleted the FCPX preference and now there are no destinations in the destiations preference and restore is not avalable reinstalling FCPX did not help either. Any help welcome.
    cheers angus

    By any chance, was FCP X open when you deleted preferences?
    Us this app to trash pref files.

  • JCo Destinations are not visible

    Hi Friends,
    I created JCo destinationation in WebDynpro Console by clicking the button "JCO Create Destination", getting message created successfully.
    If I click the button "Maintain JCO Destinations", not able to see the destination. If I create new one again with the same name it is not allowing me.
    Please help in this.
    Regards,
    Lakshmi Prasad.

    Hi Lakshmi,
    I think there is problem with your SLD.
    Please check your SLD is running and also check the SLD Data Suplier fetching data successful or not in the Visual Administrator.
    Thanks
    Arun Jaiswal

  • No such JCO destination is defined in the SLD

    Hi All,
    Following JCo are not available in Portal 7.0 for MSS configuration.
    Already MSS Buss Pkg has been deployed in Portal.
    u2022     SAP_R3_SelfServiceGenericsFIN
    u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
    u2022     SAP_cProjects
    u2022     SAP_cProjects_MetaData
    Getting mention error for MSS application:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaDataFIN' in the SLD. No such JCO destination is defined in the SLD.
    Please suggest for resolution.
    Regards,
    SK

    You have to get this fixed through BASIS / Web Dynpro Content Administrator.
    Check under Content administrator -> Webdynpro whether all the JCO connections are working fine.
    Setting Up JCo Connections for MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/15d2060e344c2fbf22e526104c24bb/frameset.htm
    Once the ESS / MSS Business Packages are deployed, as a part of the post deployment steps JCO set up is to be completed
    Below JCO are to be set up for MSS -
    ●      General connections:
    ○       SAP_R3_SelfServiceGenerics
    ○       SAP_R3_SelfServiceGenerics_MetaData
    ●       Connections for the Team area:
    ○       SAP_R3_HumanResources
    ○       SAP_R3_HumanResources_MetaData
    ●      Connections for the Budget area:
    ○       SAP_R3_Financials
    ○       SAP_R3_Financials_MetaData
    ○       SAP_R3_SelfServiceGenericsFIN
    ○       SAP_R3_SelfServiceGenerics_MetaDataFIN
    Set up the following for branching to the details screen from Travel work items in the universal worklist:
    ○       SAP_R3_Travel
    ○       SAP_R3_Travel_MetaData
    ●      Connections for the Projects area:
    ○       SAP_cProjects
    ○       SAP_cProjects_MetaData

  • Wrong JCO destination used at Runtime

    hi,
    I created a Model using the following JCO Destinations
    'WD_RFC_METADATA_DEST_HCM'
    When I run the application, it gives me folowing error
    Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD
    Where is it getting this 'WD_RFC_METADATA_DEST'  ? though my JCO destination name is 'WD_RFC_METADATA_DEST_HCM'
    Thanks !
    seventyros

    Hi,
    Make sure you deploying to the SAME server where you have configured and maintained the JCo destination.
    Also check the server name and port when you are running your WD application and server name and port you are using for WD content administration.
    Also What is the version of your NWDS ?
    In NWDS 7.1, we would require a totally different way to maintain the JCo destinations comparing to the past.
    We now have to maintain the JCo destinations not in the JCo Connection Administrator, but in the NWA under u201CConfiguration Managementu201D - > Security -> Destinations.
    This [doc|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09527da-39a7-2b10-9f99-c6a007e516a5?overridelayout=true] explains the same...
    Regards,
    Vijay.

  • Create JCO destination option not available

    Dear All,
    I am trying to make a JCO connection in CE.
    However the buttons for
    "Create JCo Destination","Maintain JCo Destinations" are disabled.
    The status for built-in JCO destinations  WD_MODELDATA_DEST
    WD_RFC_METADATA_DEST is shown as unknown.
    The "Enable" button is also disabled.
    Also i am getting the error "Connection to System Landscape Directory (SLD) could not be opened successfully".
    Can anyone please help me in this.
    Thanks and regards,
    Mayuresh.

    Hi Mayuresh,
    In nwa go to Configuration Management->Infrastructure->SLD Data Supplier Connection->Destinations.
    Create a Destination.
    Ping the destination to check if it is successful.
    After that you can create a JCO Connection.
    Regards
    pankaj

  • Can not create jco destination  500   Internal Server Error  after sp 13

    hi friends
    i have strange problem in my landscape with webdynpro -
    >Web Dynpro Tool Applications----->Content Administrator  -
    >login as  j2ee_admin  in 
    Web Dynpro Content Administrator  page  when start click on  ceartin Jco destination  i am facing this problem  -
    >6
    1. i can not create any  jco destination .
    2. is there any other  way to create jco destination to back end (arfc connection to retrive the back end data .
    3 . we are using one meta and one model data for all the application in my enviroment we do have some performance issus because one arfc connection is it correct?
    4 . what is best scanario to our applications(bussiness package ) we do have 30 diffrent application can i
    have 30 arfc connections .
    5.with  one arfc how much data can i retive per 1 min is there any performance tunning docment is there for the  ep tunning .
    <6>error is showing like this
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    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).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat May 24 22:16:36 PKT 2008
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale en_US
    Time of Failure Thu Jul 03 01:56:32 PKT 2008 (Java Time: 1215032192285)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         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:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    thanks in advance  to all the friends spending there valuable time to read this thread
    any  suggtions  are realy help for my issue
    this is very high  priorty issue in our  landscape
    regards
    raja

    thanks to all for helping

  • Error-The RFC destination EDSCLNT900 is not available in ICWC

    Hi All,
    I'm working on CRM Utilities 2007. In the ICWC, I'm getting the error 'The RFC destination EDSCLNT900 is not available'. Kindly help me in resolving this error.
    Regards,
    Archana.
    Edited by: archu_sap on Jul 15, 2009 10:30 AM
    Edited by: archu_sap on Jul 15, 2009 10:33 AM

    Hi,
    You have to maintaine RFC Destination EDSCLNT900 in the CRM system.
    generally we have to maintain RFC (t-code SM59) in the sytem where Function Module is present.
    Suppose you are having FM in ECC system  and you want to call in CRMsystem,  then you have to maintain RFC destination (EDSCLNT900) in ECC system.
    Thanks & Regards.
    ShreeMohan

  • The RFC Destination ALESERVER is not available

    Hi ,
    I am getting the error message " The RFC Destination ALESERVER is not available "  in my CRM Web UI screen.But when I login with another User ID , this error message is not showing.
    RFC connections are maintained  in transaction SM59 and BD97.but I m still facing with this issue.
    Please advice what could be the cause of error.
    Regards,
    Ravi

    Hello,
    please check in SM59 the LOGON-User for this RFC-Destination.
    Maybee the user where it works is maintained, the other not.
    Or if there is a general RFC-User maintained the user where it does not work has maybee not the authorization in the target.
    Best regards
    Manfred

  • Message Servers not appearing when creating JCO Destination

    Hello Experts,
    I had created a  System Object in the Portal system landscape based on System Template (Template) and choosed SAP system with load balancing (to connect to R/3 server).
    Given parameters to Connector, ITS, WAS and User management, when i test the connection test on these settings, All are successful except the connector settings. but when run the transaction code(System Administration -> support-> portal runtime-> SAP Transaction) by selecting this message server, it is executing.
    And i want this message server to be selected when creating JCO destination.
    This System Object is not showing in the message servers dropdown box selection when creating the JCO destinations.
    What may be the issue.
    Could anyone help me in solving this.
    Thanks in advance
    Regards
    Sunil

    Hi,
    Have you checked the Technical systems in the SLD ?   When you click on check sld , you appear an SLD url ,,,
    Typing the same URL in browser and loging inwith SLD USER .... have you seen all the technical system which you want to appear while creating the JCO's ..
    Regards,
    Srini

  • Error in Jco Destination Create (MsgServerName is not defined).

    Hi,
    When I try to create a Metadata Jco Destination, the system show the message "MsgServerName is not defined" and cancel the operation.
    I can create Modeldata Jco Destination correctly. The problem is only on Metadata Jco Destination.
    Thanks.
    Ariel.

    Hi Alex,
    Please see the below link in which discussed the issue for "MsgServerName is not defined". 
    JCo Destinations: Message Server connection not defined
    /message/8658127#8658127 [original link is broken]
    Maintain JCO Destination, cannot set the server and logon group
    Also check the [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
    Hope it helps
    Regards,
    Arun

Maybe you are looking for