RFC issue in RAR 5.3 Risk Terminator

Hi,
We have RAR 5.3 with Risk Terminator configured. Since last couple of days, Risk Terminator is not working for one of our back end system.
Getting below error message :
"SAP Adapter has a problem, SOD violations will not be checked !!!
Please check with your system Administrator
Technical Info:
senderAgreement not found: lookup of binding via CPA-cache failed for AdapterTyp"
I have verified the configuration setting and confirmed below things:
1. Config program do have RFC destination which is defined with registered program GRCRTTOCC5X
2. The same program name is defined in the RAR connector with Outbount selected
3. The SAP Adapter is Green. I have turned it off / on
It was working well till few days back.
Any suggestion would help a lot.
Adeep

Hi Deepak,
Can you change your Program ID (GRCRTTOCC5X) to any other name in your back end as well as RAR Report name also.
It will work.
Regards
Shiva.
Edited by: Siva K Kumar on Jul 27, 2010 7:36 PM

Similar Messages

Risk Terminator ECC 6 - CC 5.2 - RFC Test: Program not registered

Dear board,
I am configuring the risk terminator functionality and stumble accross problems with the setup of the RFC destination from ECC to the CC. The connection test fails with "ERROR: program GRCRTTOCC5X not registered".
The RFC connection is of type TCP/IP, Registered Server Program, Default Gateway Value and Gateway host/service information I took from another working rfc connection.
The RFC connection is equal to the one set up in the RT configuration transaction, I have set up a dedicated connector on the CC with direction outound and GRCRTTOCC5X as report.
I have furthermore noticed that I am not able to active the SAP Adapter in the CC yet, a JCO error appears.
Any ideas?
Kind regards and many thanks,
Richard

Hi Richard,
I am sorry to bother you and distract with this query, but couldn't find your email in your profile.
Could you please contact me regarding your SPNego problem discussed in
SPNego - Windows integrated Single-Sign On not working - How to debug?
We are facing the same issue and I was curious whether you had a solution?
Thanks so much, Emir
My email is emirce at gmail dotcom.

Problem with RFC for Risk Terminator - GRC 5.2 SP12

We are having a problem with the RFC connection for Risk Terminator in one of our SAP environments. It is working in our 'DV3' environment, but not in our 'RT3' environment. Everything is set up just the same in both environments and all SAP Adaptors show green.
This was working in RT3 when we first upgraded to GRC 5.2 last November, but it now gives me an error when I do an update with PFCG and it calls RT. The error message and our Basis support group both say the RFC needs to be 'registered', but our SAP Support contact during our upgrade said it does not, and I can't find any documentation that says this is required also. Plus it was working before even though it was unregistered.
What is causing this problem and how do I resolve it?
Also, if these RFCs do not have to be registered, is there some documentation that states this that I can show to our Basis group?
Thanks.

What about the question of the RFC needing to be registered? This is the solution our Basis group thinks is required, so it will be hard to get them to do anything else until this issue has been addressed.
Thanks.

Risk terminator - Works in one system but not in the other

Hi
I have two SAP systems which is connected to one GRC system. Risk Terminator works well for the one system but does not work at all for the other.
I have done the necessary configuration, set-up the RFC connector, tested the connectors, tested the connections from the GRC system. All seems fine but when I create a role in PFCG risk terminator does not seem to be trigged at all in my one system.
Please advise
Regards
Mo

I would check the adapter for the other system and that the external program is maintained correctly along with all the settings in /VIRSA/ZRTCNFG

Risk Terminator error CPIC-CALL: 'ThSAPCMRCV' : cmR

Hi,
I have configured risk terminator. I have tested the RFC connection and it seems fine and referenced this in the configuration. However I get an error when I go to add a role to a user. It attempts to execute a risk analysis and then returns an error.
connection to partner 'X' broken / CPIC-CALL: 'ThSAPCMRCV' : cmR
I seem to have all configuration set correctly. Except for one question- do I need a unique report name for each system connector e.g. if I use GRCRTTOCC5X for my R/3 system, can I also use it for SRM system?
Anyone have any ideas about this error?
Thanks,
Niamh

Hi Sunny,
after some testing I figured out the problem. Because I am working with an ECC6.0 system that has been upgraded, I needed to check the unicode flag on the risk terminator RFC connection. It now works and I am no longer getting the error.
Niamh

GRC AC 10.0 Risk Terminator Bug

Hello All,
We have been experiencing a strange behavior while running Risk Terminator. It works well when we generate the role by calling the transaction PFCG in target development system , however when we go to Roles tab from Su01 and go to pfcg screen , Risk Terminator is not triggered at all. Is this a bug or a known behavior ? Its human to navigate to pfcg via su01 . Whats wrong with it ?
Regards,
Anthony

Dear Anthony,
Yes , this is a known bug and the programming corrections are delivered by SAP on 20.12.2011 via SNOTE 1666294 RT is not triggering when user click on role via SU01. We reported this to SAP a month back and now we have a note. problem should be solved .
Detailed analysis of the NOTE :
Sy-tcode is a runtime variable which is globally available once a transaction is called . This value is preserved in the session and is active till there is a call to another transaction , While navigating from SU01 to PFCG interestingly the SY-TCODE is filled with blank value and the actual bug is here .
Ideally SAP should have activated the RT exit in plug in for S_TCODE value and not for SY-tcode alone or both to be robust.
It is indeed " human " to navigate to roles pfcg via su01 but There are more than 100 ways of reaching pfcg from other transaction then should SAP correct it for all SY-TCODE value like how now they have corrected it for SY-TCODE = ' ' . We don't know from which other is it going to be blank..
Best Regards,
Vishal Padiyar

GRC AC 10.0 Risk Analysis -Risk Terminator Vs BRM-Role Management

Hi All,
After having seen the configuration for Risk Analysis- Risk Terminator and Role Management , I observed that there is very little difference for eg parameters 1085 and 3011 ,3014 . If we configure all three parameters to TRUE which one would take effect ?Can anyone let us know under what circumstances we must configure RT and Role Management . BRM to has a whole lot of new features which supercede RT.
Best Regards,
Vishal

Hi Vishal,
The parameters will be invoked in different scenarios. 1085 is specific to when roles are generated in the SAP Backend system using risk terminator and therefore this will have no impact if you are using BRM to generate the roles.
3011 & 3014 are specific to BRM and govern different behaviours. 3011 will facilitate the risk analysis prior to triggering the generation steps in the methodology and 3014 will allow the roles to be generated despite any permission risks that are returned.
They are not exclusive and actually work together. For instance, you may want to have a block on generation of roles when there are open conflicts identified and therefore you should have 3011 set to YES and 3014 set to NO. If both are set to YES, then you could propagate conflicts in the roles.
You can use Risk Terminator if you wish to continue to develop roles within the SAP system itself rather than to rely on the GRC BRM system wholly.
There are still wide discussions and differing opinions about which represents the best approach for this and so it depends on your organisation as to which process you follow.
The parameter descriptions in question are:
1085 - Stop Role Generation if violations exist
3011 - Conduct Risk Analysis before Role Generation
3014 - Allow role generation with Permission Level violations
Regards, Simon

GRC Access Controls v5.3 RAR Batch Job Risk Analysis Incr Analysis

Hi All!
re: GRC Access Controls v5.3 RAR Batch Job Risk Analysis Incr Analysis
Can anyone list or direct me to a help link that has the progress list of processes that are contained in this batch job?
Thanks!

Hi All,
I have answered my own question. The processes are:
User Permission Analysis
Profile Action Analysis
Role Action Analysis
User Action Analysis
Role Permission Analysis
-john

CCMS: CEN configuration - Registration Failed due to RFC : Issue Resolved.

Hi There!
I was trying for CEN-CCMS setup and I was bale to connect my other systems to the CEN, infact I was able to connect all the system, but somehow my DEV box is detached from the CEN box. When I try to run sapccmsr -R -j2ee pf= to register with CEN, at the end of when I enter the details of "csmreg" user of CEN, throws the following error.
INFO: Updated saprfc.ini in agent work directory /usr/sap/ccms/DEV_02/sapccmsr
ERROR: Registration failed: Can't get version of DEV. RfcRc = 2, C_CALL_FAILED
RFC Error Info for SALS_MS_GET_LOCAL_MS_INFO
message:
status: EXCEPTION C_CALL_FAILED RAISED
intstat:
INFO: dsr: dsrlib unloaded.
EXITING with code 1
Illegal instruction (core dumped}
In SM59, the TCP/IP rfc name with those program ID throws error. "Error when opening RFC connection". If I creadted the Program-ID in VA, then SM59 will pass the test connection, but its not the resolution, the DEV box is still detached from CEN.
I redo the configuration with new CSMCONF too
If I check the "monitored Remote System/RZ21 on CEN, it throws:
> Connection test to destination DEV_CCMS_COLLECT terminated with ERRORS
> Error when calling the underlying C function (function 'SALS_MS_GET_L..
I followed the SAP's monitoring guide for NW04s-SP-13
PI-7.0, SP-14
Thanks anyways
vipin
Issue Resolved.
Edited by: Vipin Sagar on Jul 22, 2008 4:08 AM

Hi All,
can any one share the solution for the above error.
I am getting the same error for one of the systems. other systems are working fine.
Thanks and regards,
Sunny

Issues with WebDav over SSL via Terminal Server when Accessing SharePoint 2013

Hi All,
We have deployed a terminal server from which multiple users access and heavily use SharePoint 2013 (hosted on a separate server). The SharePoint site is published to the internet and is operating over an SSL certificate. Over the last few months we have
been encountering a randomly occurring issue where all the users become unable to use Open with Explorer or mapped drives to access the site. During this time they can still access the site through the browser OK and download files etc. This issue sometimes
reoccurs every few days, although at points it hasn't occurred for a couple of weeks before resurfacing.
Current Terminal Server Config
TS 2008 R2 Enterprise
Site added to Trusted Sites. (have checked during broken time and still recognized as trusted)
Using IE 11, site added as compatibility view
Registries updated as below
reg add HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /v AuthForwardServerList /t REG_MULTI_SZ /d "*.clientsite.com"
reg add HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /v BasicAuthLevel /t REG_DWORD /d 2 /f
reg add HKCU\Software\Microsoft\Office\14.0\Common\Internet /v BasicAuthLevel /t REG_DWORD /d 2 /f
registry added for tabprocgrowth added to 2
My test result are below:
Restarting the SharePoint server or the terminal server will resolve the behaviour
until the issue occurs again.
Users on the terminal server can still open the
ttps://clientsite2.harrierhc.com
URL (this url is bound to the same UCC cert) with open with explorer during this time.
While users are unable to access the ttps://clientsite.harrierhc.com
URL, if they access the same site from WebDAV with a separate binding (e.g. ttp://clientsite the behaviour works fine.
All other users not on the terminal server can still use the open with explorer behaviour during this time.
IIS reset on the SP Server & restarting the web client service on the terminal server have no impact
Reimporting the IIS certs have no impact
There are numerous errors in both server’s event logs but none at the time of the issue instigation.
Clearing the IE cached certificates has no impact
Going to IE properties for the site and clicking the ‘Install Certificate’ has no impact
Any ideas or suggestions would be much appreciated. If you need any more info let me know. (sorry for the ttps:// links cant be posted until my account is verified?
Thanks again

Hiya,
are there any load balancers involved?

SAP R/3 to External System RFC issue

Hi Experts,
We have one Peculiar issue in our SAP R/3. Request you to help me in resolving this.
Order Processing:
During Sales Orders Processing, for every line item a RFC is being initiated from SAP R/3 to an external system called Trilogy Pricer to get the Pricing data. Trilogy Pricer sends the Pricing data to SAP R/3 and the respective Orders are being processed in SAP R/3.
Current Issue:
The issue we are facing is that, once the Pricing data is sent to SAP R/3, Trilogy Pricer expects an acknowledgement (RFC_OK) from SAP R/3 in order to release the RFC connection. Intermittently, Trilogy Pricer is not receiving this or any kind of acknowledgement from SAP R/3 causing the connection to hang which is causing several problems.
For example:
On every business day, there will be 50,000 Sales orders.
So, 5 or 10 sales orders are getting hanged every day.
We tried to simulate this issue in Dev and Stage environments by processing 30,000 to 40,000 sales orders.
But we were unsuccessful, which means all the RFC connections were being closed as the external system is able to get the acknowledgements for all those orders from SAP R/3.
We are having this problem only in Prod.
Any thoughts to solve this issue is highly appreciated.
Advance thanks for your great help.
Thanks and Regards,
Srinivasa

Hi I am not sure if it was similar issue, but I once had a kindaa problem I solved using
CALL FUNCTION func STARTING NEW TASK task
[DESTINATION {dest}]
[{PERFORMING subr}|ON END OF TASK].

SAP R/3 to External System RFC issue during Sales Order Processing

Hi Experts,
We have one Peculiar issue in our SAP R/3. Request you to help me in resolving this.
Order Processing:
During Sales Orders Processing, for every line item a RFC is being initiated from SAP R/3 to an external system called Trilogy Pricer to get the Pricing data.
Trilogy Pricer sends the Pricing data to SAP R/3 and the respective Orders are being processed in SAP R/3.
Current Issue:
The issue we are facing is that, once the Pricing data is sent to SAP R/3, Trilogy Pricer expects an acknowledgement (RFC_OK) from SAP R/3 in order to release the RFC connection. Intermittently, Trilogy Pricer is not receiving this or any kind of acknowledgement from SAP R/3 causing the connection to hang which is causing several problems.
For example:
On every business day, there will be 50,000 Sales orders.
So, 5 or 10 sales orders are getting hanged every day.
We tried to simulate this issue in Dev and Stage environments by processing 30,000 to 40,000 sales orders.
But we were unsuccessful, which means all the RFC connections were being closed as the external system is able to get the acknowledgements for all those orders from SAP R/3.
We are having this problem only in Prod.
Any thoughts to solve this issue is highly appreciated.
Advance thanks for your great help.
Thanks and Regards,
Srinivasa

Hi I am not sure if it was similar issue, but I once had a kindaa problem I solved using
CALL FUNCTION func STARTING NEW TASK task
[DESTINATION {dest}]
[{PERFORMING subr}|ON END OF TASK].

IDoc - XI - RFC Issues

Trying to set up an IDoc->XI->RFC Scenario. Am able to receive the IDoc into XI but are having issues getting this to the other system via RFC.
Status in Monitor for Processed XML Messages (SXMB_MONI) is "Recorded for Outbound Processing". When I "display" the specifics I see the Inbound Message was processed fine but the Receiver Grouping is set to "Recorded for Outbound Processing".
I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.
Hoping someone has seen this and can help me get whatever I'm missing set up!
Thanks!

Hi,
Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.
This status is OK.
I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
>> in SMQ2 what is the status ? Is it running/sysfail etc ?
If it is SYSFAIL, then double click on that and check the exact error.
Else, you can go to SMQR or SXMB_ADM->Manage Queues->QRFC monitor-> .. then go to specified Queue name(whatever having the problem) and deregister it. Then go to SMQ2 and execute/activate the Queue . This time you will not get the info "Queue is registered...." Then go again SMQR and Re-reigister it.
For more ~
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Re: Recorded for Outbound Processing
Hope this helps,
Regards,
Moorthy

RFC issue in Triggering workflow

Hi,
I am trying to trigger a custom workflow from EP in Newly set up ECC 6.0 system.
Problem here is, Business object Event is getting triggered in R/3 with custom workflow as reciever, but the workflow is not going to the first stepThe event trace (SWEL) gives following information,
Action Receiver started correctly
RFC Status Logon not possible (error in license check)
I have checked the configuration in SWU3, all where fine, also the RFC WORKFLOW_LOCAL_100 tested successfully. The ECC6.0 has the full license.
Please let me know why this has happened? How can it be solved? Please reply ASAP.
Thanks,
Shrinivas

Hi,
WF-BATCH has validity till 12/31/9999 and also the workflow initiator has SAP_ALL authorization,
Still the issue has not been solved. New thing i noticed this this problem happens intermittently !
For some time it is working fine, some other time its giving the same RFC error.
Thanks,
Shrinivas

XI TO BI - RFC Issue

Hi,
In XI to BI integration, am importing an RFC from BI to XI. After importing I noticed in one of the field name the character "/" are replaced with "_".
Following is the field name in RFC in BI " /BIC/ZTYPE_ADJ" after importing that in XI it becomes like this "_-BIC_-ZTYPE_ADJ". Even the RFC name changes
Original Name : /BIC/CQZGG_GR_00001000
After importing : -BIC-CQZGG_GR_00001000
The issue is actually with the field name which is not passing the value because of this conversion. BI is not recognizing the field name.
Any thoughts on this.
Thanks
Ashok

Ashok,
>Following is the field name in RFC in BI " /BIC/ZTYPE_ADJ" after importing that in XI it becomes like this "_-BIC_-ZTYPE_ADJ".
You need to connect thru Proxy code.
Cheers
Agasthuri

RFC issue in RAR 5.3 Risk Terminator

Similar Messages

Maybe you are looking for