on 06-24-2011 12:41 AM
Hello,
I was wondering if the log reports that get emailed to the controllers contain SOD Risks committed by the FF ID and the critical tcodes committed by the FFID.
When you schedule the /VIRSA/ZVFATBAK report it only executes the transactions and any changes that the Basis tables record via CDHDR and CDPOS tables.
But how do you get the SOD risks and critical transactions to show up on the log reports that get automatically generated to be sent via email to controllers.
The config table settings in our SPM table is set to check against RAR table for SOD and Critical Transactions.
Is there any other job that needs to be scheduled to include that in the log reports to be mailed.
Does anyone have FF 5.3 installed in their end where they get the SOD violations reports from the logs of the FF ids reported via email and/or even running via log reports execution from back end or front end GRC SPM? Would greatly appreciate any feedback.
Thanks,
Hina
Edited by: Alley1 on Jun 24, 2011 1:41 AM
if my memory is right, I've seen this problem was marked as fixed in SP14 or SP15...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply Luis and Benno,
But I don't see any information on the release notes 1168121 for SP 14-16 where they mention this has been fixed. We are going to apply SP15 or 16 in the next 2 weeks or so and see if this resolves the issue. Upon speaking with SAP and their development team, they still do not have the SPM SOD violations report working to the par it should be. It used to run really fast ,now it's very slow even if you try to execute the sod violations log report if checking against RAR system. We still haven't been able to resolve tat issue with them. I thought I come here to ask if any of you have had performance issues when running SOD violations log reports in SPM against the RAR system connection and also if your log reports that get generated automatically contain the SOD risks and critical transactions executions committed by the FF id.
Would greatly appreciate any feedback regarding this. We haven't had much luck with SAP support resolving this issue for the past two weeks. Their statement was that most clients only run SPM for transaction usage reports which is done only in backend. But if you offer the service to connect to the GRC front end RAR to do SOD violations against the FF id logs, and critical actions log, then your service should work and not have issues with these reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.