cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager RFC issues

Former Member
0 Kudos

Hi Folks,

We are facing problem with RFC connection from Quality to Solution Manager. It says " No authroization for trusted system" however the RFC connection from Solman to Quality is working fine.

in SMSY -> RFC connection test working fine and able to fetch the qas to solman system. We have give all required authorization including SAP_ALL, SAP_NEW and S_RFC_XX Objects also assigned.

It would be of great help if some one can help us on this.

Regards,

Vinod

Accepted Solutions (0)

Answers (5)

Answers (5)

umeshjagadesh
Advisor
Advisor
0 Kudos


HI vinod ,

Can you please check the trusted connectivity SMT1 in solution manager .

There will be an entry in the QUality system SMT1 which tells that Solman system is the trusted system similarly if you would have configured the BACK rfc check with it.

If you are  still facing error make the SOlution manager system as trusted in the QUA and viceversa .

Regards,

Umesh

Former Member
0 Kudos

Hi

Please check the "Troubleshooting in Trusted/trustng system" part in below link

[http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm]

Hope this help to fix the issue,

Thanks,

Jansi

raguraman_c
Active Contributor
0 Kudos

hi,

Check SMT1 in your satellite system.

Feel free to revert back.

-=-Ragu

Former Member
0 Kudos

HI Rahu,

We have recently did system refersh from production to qulaity since then QAS EWA is not working. in SMT1 transaction i see trusting system entires are showing production system name instead of QAS system details.

Can you please let us know what are the post reresh activities to be performed to change the solution manager entries.

Also we observerved that PSAPSR3 table space filling up rapidly. are there any known issues with growing psapsr3 table space.

Any useful suggessions are welcome.

Regards,

Vinod

Former Member
0 Kudos

HI Vinod,

Note down the users assigned in quality system rfc in smsy and delete the user and clear all RFC of quality system, in smt1 delete the quality system sid in both system in quality system and is solution manager then finally regenerate the RFCu2019s,

Regards,

Rakesh

Former Member
0 Kudos

Are you on SP26? Then I'm getting the same error. Apparently a bug was introduced in that release and development is working on it. I will post a follow-up here when the issue is resolved.

Regards,

Sean

Former Member
0 Kudos

Hi Vinod,

Which id you are used to configured in SMSY use same user id or follow below steps on currnet user id

Go to t code -> SMSY select -> system then goto -> SID select lient delete old RFC then you generate new RFC

next go to dswp -> genertate new EWA report

Regards,

Kalees

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hi there,

Please login into the quality system, then check the authorizations of the user in the quality system. What is the RFC which has issues, and what is the scenario you are using? if this happens during creation of support messages from the quality system you can just change the RFC and have it configured not to be a trusted connection. In other cases this may not be done though.

Best regards,

Miguel Ariñ