on 08-25-2015 10:10 AM
No Record for consolidated Log Report in EAM whereas FF Log is being captured.
Implemented Note: 1775432
Hello,
Check authorization of RFC user in the backend with Objects are S_ADMIN_FCD and S_TOOLS_EX.
Regards
Baithi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ayushi,
I recommend to set Parameter 4018 to YES so that you have detailed Information in SLG1 application log. This helps to determine the cause of the disruption.
Please set to YES and then run the job again. After that post the SLG1 log here so that we can see what is missing.
Regards,
Alessandro
as explained twice already, by individual reports, i mean Transaction log and System log, as examples, and not FF log summary or reason code
Transaction log will show the t-codes executed by FF id, and will be stored in GRACACTUSAGE, through FF log sync job. Could you check in FF log summary report, what are the t-codes executed by the FF id. if no t-codes have been executed, then Transaction log will be empty.
System log might be empty for a FF session, as observed, from my own System log report(only failed RFC calls were logged).
All System logs constitute all these logs(Transaction and System logs, etc), and give you the report. So, if there are no individual reports, then All System logs will also be empty.
regards
plaban
That is required on target system, apart from other necessary RFC access,
on GRC system,
look for table GRACFFLOG if it has records.
if yes then it should show based on auth object of user in GRC system.
like if you are trying to access report you should have access.
GRAC_USER
GRAC_FFOWN
S_USER_GRP
PLOG
Regards,
Prasant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.