Summary

-5E1Hjygn54KXbDrTccWcnhQjIvdzRST6tzArq9pVMWT61T-ymAWTAg3IMJX2upjDlwfuTiVKPxzRYEQb0RazVGgxcZmGgdXfNPdoCkOiSs2bSSoB6zJAg==
Edit Back

Properties

  • Meeting Date: Unknown
  • Meeting Type: Call
  • Note Type: Summary
  • Attendees: Scott Warner, GLLR

1. Meeting Summary

I spoke with GLLR to get the latest status on the SAP outage and understand whether we needed to hold employees home again. The issue appears to have been caused by a bad SAP transport or mass data import from HQ that significantly impacted the environment. HQ locked all user access while they triage the issue, and the current expectation is that they may need to roll back data to a point before the import.

At the time of the call, the system was confirmed to remain down for the rest of the day, and there was concern it might not be available by the next shift start either. My immediate focus was operational impact on teams whose work is dependent on SAP, including AP, Warehouse, and Repair. I made clear that if SAP remained unavailable into the next morning, I would need to use the emergency notification system to tell employees not to report in.

GLLR provided the HQ points of contact managing the incident so I can check status early the next morning and make a timely call. My likely approach, if there is still uncertainty, is to issue a 2-hour delay rather than canceling the full day outright. Overall, this was a short coordination call centered on minimizing unnecessary labor disruption while staying responsive to the system recovery status.

2. Attendee List

  • Scott Warner
  • GLLR

3. Action Items

  • [GLLR] Send me the HQ contact information for the primary SAP incident contacts, including Todd and Carsten.
  • [Scott Warner] Check with the HQ SAP contacts early the next morning for a system status update.
  • [Scott Warner] Decide whether to send an emergency notification instructing SAP-dependent employees not to report to work if the outage continues.
  • [Scott Warner] Consider implementing a 2-hour delay as an initial response if SAP status remains uncertain in the morning.
  • [GLLR] Notify me if any additional updates come through later that day or in the evening.

4. Relevant Timelines

  • Rest of day: SAP was not expected to be restored that day.
  • By 7:00 AM next shift: There was concern SAP might still not be available, though this was not independently confirmed by GLLR.
  • Early next morning: I need to contact the HQ incident leads to determine system status before deciding on workforce messaging.
  • If status remains unclear in the morning: My likely response is a 2-hour delay for SAP-dependent teams.

5. Additional Notes

  • The root cause was described as an SAP transport or data import error from HQ, but details were still vague.
  • HQ locked user access to avoid additional changes while they assess recovery options.
  • A rollback of SAP data was considered the likely path, which reinforces the need to avoid normal business activity until the environment is stabilized.
  • The operational priority is balancing two risks: bringing employees in without system access versus unnecessarily sending them home.
  • The affected groups I referenced were AP, Warehouse, and Repair, with the broader principle applying to anyone tied directly to SAP.