It’s 6 p.m. on the last day of the month and period-end postings are blocked. The person who can fix it doesn’t have the access, and the person who has the access doesn’t know the fix. Every SAP shop eventually faces this moment. The wrong answer is to give a few people powerful access permanently “just in case”. The right answer is emergency access that is borrowed, logged and reviewed, which SAP calls firefighting.
SAP Emergency Access Management (EAM) is the part of SAP Access Control that lets a user temporarily borrow elevated access to fix an urgent problem in production. The user gives a reason, works for a limited time, and every action is logged. Afterwards, an independent controller reviews the log. Those four steps turn a loophole into a control auditors accept.
In one sentence: SAP firefighting gives people powerful access only when they need it, records everything they do with it, and makes someone else check the record.
Key takeaways
- EAM access is borrowed, time-limited, logged and reviewed by someone independent.
- Choose ID-based or role-based firefighting with configuration parameter 4000; only one can be active.
- Firefighter IDs are service users carrying the role named in parameter 4010.
- Logs only reach controllers if the log sync job,
GRAC_SPM_LOG_SYNC_UPDATE, runs regularly. - Unreviewed logs are among the most common EAM audit findings.
Who does what in SAP firefighting?
| Role | Responsibility |
|---|---|
| Firefighter | The person who needs emergency access to do a task |
| Firefighter ID or role | The elevated access itself |
| Owner | Decides who may use a firefighter ID and who reviews it |
| Controller | Reviews the activity logs after each session, and may approve use in advance |
| Administrator | Configures EAM and maintains assignments |
The one rule that matters most: the controller must never be someone who uses that firefighter ID. A self-review isn’t a review.
ID-based or role-based firefighting: which should you choose?
Access Control supports two styles, set with configuration parameter 4000 (1 for ID-based, 2 for role-based). Only one can be active at a time.
| Question | ID-based | Role-based |
|---|---|---|
| How access is granted | The firefighter checks out a separate service user that holds the elevated roles | A firefighter role is assigned temporarily to the user’s own account |
| Whose name is in the log | The firefighter ID, linked to the real person | The user’s own ID |
| Separation of normal and emergency work | Very clear | Less clear, since both happen under one user |
| Typical choice | Teams that want a clear split between normal and emergency work | Organizations that want fewer extra users |
Both styles can run centralized, from the EAM launchpad in the GRC system, or decentralized, from the launchpad in the target system with transaction /GRCPI/GRIA_EAM. Decentralized firefighting matters when the GRC system itself is down during an incident. You can only run one session at a time.
How do you set up ID-based firefighting?
- Set the core parameters in SPRO under Access Control, Maintain Configuration Settings (see the table below).
- Create the firefighter ID role in each target system, usually a copy of
SAP_GRAC_SPM_FFID, with exactly the name you entered in parameter 4010. SAP KBA 1668255 explains why the names must match. - Create firefighter IDs in
SU01as service users, assign the 4010 role plus the elevated roles each ID needs. - Sync master data so GRC sees the new IDs, then assign owners, controllers and firefighters in the GRC launchpad.
- Define reason codes so every session has a structured reason as well as free text.
- Schedule the log jobs so session logs reach controllers.
| Parameter | Meaning | Common setting |
|---|---|---|
| 4000 | Application type | 1 (ID-based) |
| 4001 | Default firefighter validity period in days | Short, set by policy |
| 4003 to 4006 | Retrieve change, system, audit and OS command logs | Yes |
| 4007 | Send log report execution notification immediately | Yes |
| 4008 | Send firefighter ID login notification | Yes |
| 4009 | Log report execution notification | Yes |
| 4010 | Firefighter ID role name | Your copy of SAP_GRAC_SPM_FFID |
Retrieving the audit log only helps if the Security Audit Log is active in the target system. Check that before go-live.
Why do firefighter logs go missing?
Logs travel from the target system to GRC through background jobs. The main one is GRAC_SPM_LOG_SYNC_UPDATE, usually scheduled hourly. If it stops, fails on a broken connector or runs for hours, controllers get no review tasks and nobody notices. SAP’s knowledge base has many articles on exactly these failures. A few habits prevent most of them:
- Monitor the log sync job like any other critical job, with an alert on failure.
- Check connectors after every system copy or RFC change.
- Use the time-based report
GRAC_EAM_LOG_SYNC_TIMEBASEDto retrieve missing logs and retrigger review workflows, as SAP KBA 2072462 describes. - Compare the number of sessions with the number of completed reviews every month. They should match.
How should a controller review a firefighter session?
A good review answers three questions:
- Was the use justified? Does the reason point to a real incident or ticket?
- Did the activity match the reason? Were the transactions and changes consistent with the task?
- Did anything unexpected happen? Changes to users, roles, bank details or security settings need an explanation, even when they look harmless.
Here’s a fictional example. A finance support analyst uses a firefighter ID to open posting period 11 with OB52, which matches the ticket. The log also shows SU01 unlocking a colleague’s user. The controller checks the service desk and confirms the colleague had locked herself out and asked for help. No misuse, but two findings: user administration doesn’t belong in a finance firefighter ID, and activity must stay within the reason. The fix was to remove user administration from the ID through a normal change. A “reviewed, no issues” stamp would have missed all of it.
What are the best practices for firefighter IDs?
- Keep IDs narrow. Separate IDs for finance, logistics, Basis and security make reviews meaningful.
- Avoid SAP_ALL where you can. If you keep one disaster ID, restrict and monitor it heavily.
- Set short validity periods so assignments expire on their own.
- Require a ticket number in every reason.
- Recertify assignments regularly, like any other access.
- Watch for repeat “emergencies”. If the same task appears every month, such as opening posting periods, design a normal controlled role for it.
- Report monthly on sessions, overdue reviews and exceptions.
Frequently asked questions
What is a firefighter ID in SAP?
A firefighter ID is a service user in the target system that holds elevated roles for emergencies. Authorized users check it out through SAP Access Control for a limited time, and everything they do is logged.
What does parameter 4010 do in SAP GRC?
It holds the name of the role that marks a user as a firefighter ID. That role must exist with exactly the same name in every target system and be assigned to each firefighter ID.
Who should review firefighter logs?
A controller who is independent of the firefighter, usually someone in internal controls or the business area that owns the ID. Reviews should happen within a few working days.
Why are firefighter logs not reaching the controller?
Usually the log sync job GRAC_SPM_LOG_SYNC_UPDATE isn’t running, is failing on a connector, or the notification parameters are off. Check the job log and connector status first.
The bottom line
Emergency access is unavoidable in production SAP systems. Firefighting makes it safe by keeping access borrowed and time-limited, collecting complete logs and having someone independent review every session. Get parameter 4000 and 4010 right, keep the log sync job healthy and treat every review exception as a chance to narrow an ID. For context, see what SAP GRC covers and why segregation of duties matters.
Sources: SAP Community: ID-based and role-based firefighting; SAP KBA 1668255: Firefighter ID role name for parameter 4010; SAP KBA 2072462: Time-based EAM log sync; SAP KBA 2102916: Decentralized firefighting.


