cancel
Showing results for 
Search instead for 
Did you mean: 

Facing issue with Decentralized FFID

02-25-2026 12:34 PM
KarthikKumar31 Explorer
646 views 7 comments
0 Likes
SAP Managed Tags
Subscribe

Hi Folks,

I am logging into the SAP system using my user ID and ran the transaction /GRCPI/GRIA_EAM.

I could see the list of Firefighters assigned to me, so I clicked the Logon button for one of the Firefighter IDs.

I then entered the reason code and activity details, and clicked the checkmark to open the Firefighter session.

After this, FFID remote window is not opening at all. Could you anyone please help here.

0 Likes

Accepted Solutions (0)

Answers (1)

Answers (1)

Mate
Product and Topic Expert
Product and Topic Expert
0 Likes

HI KarthikKumar31,

I suggest to check SU53 for missing authorizations and/or check whether the maintained RFC connection (Plugin SPRO parameter 1000) works properly. You should also check the authorization of the FFID and the RFC user as well with SU53. These are the most probable reasons from the symptoms you described (however not the only ones). If these are not gives any answer I suggest to open a Customer Case for the issue for a proper analysis.

Best regards, Mate

olgavlachova
Participant
0 Likes
Hi @Mate, good direction! Especially in case of issues happened non-dialog user, I prefer to start STAUTHTRACE filtered to only this specified user account. STAUTHTRACE will record all checks, successful and failed ones. It shows what happened while FFID walked through logon. Much more useful details, compared to SU53 that displays only the result of last authority check. Good luck and fingers crossed @KarthikKumar31 BR, Olga
Mate
Product and Topic Expert
Product and Topic Expert
0 Likes
Hi olgavlachova. Indeed STAUTHTRACE is a better tool than SU53, however it is also more complex and requires additional authorization(s) which an enduser not neccessary has. SU53 is good for quickly check the last auth checks, STAUTHTRACE is for analysing the issue. For starting to determine the root cause of this particular case, SU53 is enough, then you can go further with STAUTHTRACE. Best regards, Mate
KarthikKumar31
Explorer
0 Likes
Hi Mate, Olga, Thank for the replies. We checked all the related RFCs and Authorizations. However, we couldn't find anything conclusive. We have also raised a case with SAP for the same. Still awaiting feedback. STAUTHTRACE was not checked. Let me check this and get back. Thanks again!! Best Regards, Karthik
KarthikKumar31
Explorer
0 Likes
Hi Mate, Olga, we could not find anything from STRUST. Also, there is no solution yet provided in the SAP Case. Thanks and Regards, Karthik Kumar
PujaSingh
Newcomer
0 Likes
Hi Karthik, did you get any solution from SAP on this issue?
KarthikKumar31
Explorer
0 Likes
Hi Puja, No still no resolution!