16 Replies Latest reply: Apr 6, 2011 11:13 PM by Bugesh Veesamsetty RSS

CC5.2 - SAP Adapter Configuration problem

Sridhar Vandanapu
Currently Being Moderated

Hi All,

 

When I am trying to activate SAP Adapter in CC it's generating following error.

 

Please advice.

 

com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.virsa.cc.modelvirsaxsr3_01.types.So_Text001

could not be loaded: com.sap.dictionary.runtime.DdException:

 

Following error occured in Back end system while trying to modifying any role in authorizatin tab.

 

SAP Adapter has a problem, SOD violations will not be checked !!!

Please check with your system Administrator

Technical Info:

com.sap.engine.services.rfcengine.RFCException: Bean /VIRSA/RT_JAVA_RISK_ANALYSI

 

Is above error related to SAP Adapter activation in CC.

 

Deployed RTA 5.2 in backend system (700) with patch level 3.

Deployed CC5.2 on Java standalone 640 system with patch level 1.

I have configured JCO's and tested successfully.

SLD is up and running.

RFC connection established and tested successfully in backend system.

Risk Terminator configured using /n/virsa/zrtcnfg in backend system.

 

I am new to java environment, I have followed above steps based on Config docuement and some of the SAP Notes.

 

Appreciate your valuble suggetions / help.

 

Regards,

Sri Vandan.

  • Re: CC5.2 - SAP Adapter Configuration problem
    Amol Bharti
    Currently Being Moderated

    Hello Sridhar,

     

    This error occurs when you try to implement Risk Terminator for that purpose you have to activate adapter.

     

    In order to resolve this issue please apply SAP notes 1060673 and 1062037 and then Apply SAP note no. 1145048

     

    Best Regards,

    Amol Bharti

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    Already I have implemented above notes twice in my system also bounced ABAP & J2E systems. But still I am getting same error. Find below my configuration.

     

    RFC Destination: EC6GRCCONN

    Program ID: AB12345789 (Succesfully rigistered through JCO RFC provider)

     

    RFC test succeeded.

     

    In CC Connector:

     

    System ID:         E6S

    Sys Name:         E6S_GRC

    Sys Type:           SAP

    Conn type:          Adaptive RFC

    JCO Dest:           yhsapr06_E6S_800

    SAP Gateway:     yhsapr06.yashsap.com

    Report Name:       AB12345789

     

    Selected Outbound conn and unicode system options.

     

    JCO destinations test also succeeded.

     

    FYI: Java instance is fresh installation and I haven't configured any thing other than specified in CC5.2 config document.

    SLD, IGS has been configured and we have added only one back end system.

     

    Please advice.

     

    Regards,

    Sri Vandan.

    • Re: CC5.2 - SAP Adapter Configuration problem
      Amol Bharti
      Currently Being Moderated

      Try the following.

       

      Execute transaction SM30 & Enter "SSM_CUST" & click on display.The following 4 entries must be maintained there in the table:

       

      NAME VALUE

       

      a.SAP_AFTER_PROF_GEN /VIRSA/Z_AFTER_PROF_GEN

      b.SAP_BEFORE_PROF_GEN /VIRSA/Z_BEFORE_PROF_GEN

      c.SAP_EXIT_USERS_SAVE /VIRSA/Z_EXIT_USERS_SAVE

      d.SAP_SINGLE_USERPROF /VIRSA/Z_SINGLE_USERPROF

       

      You can create them manually, make sure that the entries

      are made as suggested & there are no typing mistakes in the module names.

       

      Also

       

       

      1. Always activate adapter in front end to register server program then create RFC, also check RFC connection test for unicode as well if you system is unicode.

       

      2. Re confirm the SAP gateway service is correct, in my case it is (sapgw00) do not enter gateway host but gateway service.

      To confirm your gateway service go to transaction /nRSGWLST

       

      3. Make sure your system is unicode, if it is not don't select this option at all.

       

      4. In RFC do not enter Gateway Host, infect keep it blank but enter Gateway service which has to be same in connector as SAP Gateway. in my case it is sapgw00 everywhere.

       

      5. After the creation and testing of rfc connection, go to transaction /N/VIRSA/ZRTCNFG  and configure it as per your requirement, do not activate all the option at once but only activate PFCG plug in. later on you can activate all other options as well. this for tweaking purpose only.

       

       

       

      after doing all these steps, make sure sap adapter signal is green and rfc connection is successful. I hope there should be no error coming at backend now, now test creating arole in PFCG to confirm.

       

      If still you face the problem, just restart your J2EE and again activate adapter in frontend, it should work.

       

      I hope the above explanation helps,

      Amol Bharti

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi All,

     

    Can you please help me on this problem.

     

    Also please advice me said ABAP error and CC (Java) error both are inter linked or different?

     

    Regards,

    Sri Vandan.

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    Thanks for the reply.

     

    Already the said entries are exist in the back end system SSM_CUST table.

     

    I have changed SAP Gateway from Gateway host to Gatway service (sapgw00) in connector.

     

    J2EE has been restarted.

     

    System is unicode.

     

    RFC is OK and I haven't entered Gateway Host field in RFC.

     

    But when try to activate my SAP Adapter in CC it is giving following error message.

     

    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Interface Controller does not exist for Component Instance VirsaXSR3_01 in Component Usage VirsaXSR3_01

     

    After configuring /N/VIRSA/ZRTCNFG transaction I have tried to modify one role and got same old error in back end system.

     

    Please advice.

     

    Regards,

    Sri Vandan.

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    RFC test has been succeded.

     

    After restarting J2EE I am trying to activate Adapter and getting same error.

     

    Regards,

    Sri Vandan.

    • Re: CC5.2 - SAP Adapter Configuration problem
      Amol Bharti
      Currently Being Moderated

      Ok let's do one more thing.

       

      Go to the Visual Administration server and under services select the Cluster JCO RFC Provider --> Runtime

       

      Here if you see any entries related to TCP/IP connector you created for Risk Terminator, delete them all,  do not delete any other entries. At the moment your RFC is working because you have made a manual entry in Visual administrator JCo cluster. we do not want to do this but we want to register program on server through CC adapter. So for this

       

      again restart J2EE, after this your RFC connection should not be working, this is what i expect.

       

      I repeat, What we want is to register server program through CC adapter and not through Visual administrator.

       

      So next thing is to activate CC adapter you can go ahead and test RFC connection but, if the signal is still not green then try to change your report id in connector and make it ABEFHIJKLM, what i have seen is that you have numeric characters in your report name So let's take a chance here and make all the character alpha only.  save it now when you go to adapter you will find that the report name you mentioned in connector is basicly application ID shown in Program ID column of adapter.

       

      do not activate at the moment, go to your RFC in sm59 and change your program id to ABEFHIJKLM. and save it, still the RFC connection will be failing.

       

      Now restart J2EE, again go to CC adapter and activate it, this time i expect it should show green signal. then come to your RFC connection and check if it is working now.

       

      If it is working just go to PFCg and create a role to test it.

       

      Best Regards,

      Amol Bharti

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    Thanks for the reply.

     

    As per your advice I have followed all the steps such as:

     

    Clean up the Back end system RFC's.

    Clean up the CC configuration.

    Removing registered program ID's through visual admin.

    Follow the naming convention for Report name in CC.

    Restrart the J2EE server.

     

    But still I am getting same error while  activating the Adapter.

     

    Please advice.

     

    Regards,

    Sri Vandan.

    • Re: CC5.2 - SAP Adapter Configuration problem
      Amol Bharti
      Currently Being Moderated

      Hello Sridhar,

       

      I checked your first post again and what i see is.

       

      Deployed RTA 5.2 in backend system (700) with patch level 3.

      Deployed CC5.2 on Java standalone 640 system with patch level 1.

       

      From this what i understand is you have SAP WAS 640 and you installed VIRSA RTA 520_700 for Basis or may be HR as well.

       

      and SP level of RTA is 0003,  here you need to upgrade your RTA level. mine is 0010 for basis and for HR it's 0008

       

      I think you need to upgrade first.

       

      Best Regards,

      Amol Bharti

       

      Edited by: Amol Bharti on Aug 28, 2008 3:29 PM

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    Will try to upgrade my RTA patch level to 10 and get back to you with the status.

     

    As per my knowledge we can apply the patches to fix up the bugs but not for config related errors. I don't thing so this will help me to resolve the problem.

     

    Do I need to configure anything else other than above procedure in ABAP / Java side?

     

    Regards,

    Sri Vandan.

    • Re: CC5.2 - SAP Adapter Configuration problem
      Amol Bharti
      Currently Being Moderated

      No nothing else to do, just upgrade your RTA SP level.

      There are many bugs which were related to config itself got fixed for me. Adapter is basicly connecting your front end with backend RFC and registering a program at server end. So i think upgrading might help us in one or the other way.

       

      I have sent you an e-mail with a quick demonstration presentation on Risk Terminator. I hope that helps.

       

      Best Regards,

      Amol Bharti

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi Amol,

     

    Sorry for late reply.

     

    Today I have upgraded RTA patch level to 10, but after applying the patches also I am getting following error while clicking on SAP Adaptor (Diamond).

     

    First Click error:

     

    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.virsa.cc.modelvirsaxsr3_01.types.So_Text001 could not be loaded: com.sap.dictionary.runtime.DdException:

     

    Subsequent click errors:

     

    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Interface Controller does not exist for Component Instance VirsaXSR3_01 in Component Usage VirsaXSR3_01

     

    I have one doubt, in the final step of adding the back end system in SLD it will shows the product / component info. In the components window I haven't seen any RTA products.

     

    Is this related to my problem?

     

    Regards,

    Sri Vandan.

  • Re: CC5.2 - SAP Adapter Configuration problem
    Sridhar Vandanapu
    Currently Being Moderated

    Hi All,

     

    Thanks a lot for spending your valuble time on this thread.

     

    After upgrading my RTA also I am getting same error while activating Adapter. But it's got resolved using SAPJCO in Connector.

     

    Is there any problem with SAPJCO instead of using Adaptive RFC connection?

     

    Regards,

    Sri Vandan.

    • Re: CC5.2 - SAP Adapter Configuration problem
      Bugesh Veesamsetty
      Currently Being Moderated

      Hello Experts,

       

      I had similar error (Interface Controller does not exist for Component Instance VirsaXSR3_XX in Component Usage VirsaXSR3_XX) when attempting to run risk analysis for a system connected using Adaptive RFC....after reading thru the thread, I changed the connection to SAPJCO. This fixed the issue...

      Is there a logical reason why SAPJCO works and the Adaptive RFC doesn't?

       

      All my other system connectors are of type Adaptive RFC.

       

      Thanks,

      Bugesh

Actions