Working with Fire-Fighter IDs

You may have to use Fire Fighter (Virsa) IDs in the production environment to perform certain activities. Since logon to these FF IDs are performed via your regular user ID, direct logon with this FF IDs many not be possible or you may not know the password for these IDs.

Background: FF IDs are specially created user ID with usually additional and very specific security rights. A separate SAP logon session is launched from a Virsa transaction that would use one of these IDs and then you can perform a specific task. Since that SAP session tied to that FF ID can only be launched from Virsa transaction code, Process Runner user does not know how to use SAP session launched by FF ID.

There are few alternatives while working with Fire Fighter IDs:

1.Use GUI Scripting. You use the same method as today and select FF Id you want to use and launch SAP session using that ID. Then go to Process Runner and use GUI Scripting technology (for recording or running a process file). Process Runner will show you any existing FF-ID session. You can select that session for recording or running. You would be now using your FF-ID session with Process Runner.

Please note that GUI Scripting must be enabled on the server to use this method. Click here, to know how to enable GUI Scripting. Transaction (TX), BAPI (BA) or Data Extractor (DE) technology cannot use this method. If you want to use these technologies, please see two other alternatives described below. Both of the methods described below will need help from your SAP Security coordinator.

2.If you can request the password for FF ID, you may directly use FF user ID and password to perform recording or running any Process file. If required, User Type of the FF ID user may be set to C (Communication Data). This will prevent any SAP dialogue logon with that user ID.

Please note that in this case recording cannot be performed using FF ID but any process file can be ran/executed with such FF IDs. We suggest that you use another ID/System to perform recording or perform recording directly in SAP first and use Import Recording function of Process Runner.

3.You can use Process Runner Logon Shortcut method to capture password and use Logon Shortcut file for recording and running within Process Runner. Logon Shortcut file encrypts the logon credentials and stores them in a file in My Documents\Innowera\iLogonFiles folder. Security personnel may create this encrypted logon shortcut files for specific FFID and provide to Process Runner users. If Process Runner user places that file in My Documents\Innowera\iLogonFiles folder, it will be available within Process Runner logon pad to that user.

Logon Shortcut file provide mechanism to restrict access of shortcut file by date and by user/computer.

Additional notes:

Process Runner keeps detailed log of various activities performed in two separate XML file and can be accessed via Log and Stat icons. These files are stored permanently in My Documents\Innowera\Other folder.

Additionally, if you have implemented Innowera Dashboard enterprise application, these files are centrally available as permanent log. These log and stat files could serve as an additional audit log of the usage via FF-IDs.

Next:

How to resolve “Assign assignment in program SAPLSDTX” error message