SAP Israel Workers Halt System Failure Response as Labor Dispute Escalates

SAP employees in Israel have begun refusing to address system failures in parts of the company’s software, marking an escalation in an ongoing labor dispute tied to the cancellation of a collective agreement.

The action, reported on April 28 by CTech and confirmed in statements from the Histadrut and UNI Global Union, is the first in a series of planned organizational sanctions. Workers said the move is expected to cause disruptions and delays for some customers and could expand in scope if negotiations do not progress.

“Starting today, failures in certain systems will not be handled,” the union said in a statement. “This is the first step in a series of organizational sanctions, which are expected to expand and intensify in the near future.”

Dispute Centers on Collective Agreement Cancellation

The conflict began roughly two months ago after SAP management initiated a process to terminate its existing collective agreement with employees in Israel, following what it described as unresolved gaps in negotiations.

According to SAP, the agreement that was signed in 2017 “was designed for a different era and does not reflect today’s needs.” The company said it is seeking a new framework aligned with “the AI era and the current realities of the industry,” emphasizing the need for greater flexibility and agility in its operating model.

The Histadrut declared a formal labor dispute approximately three weeks before the sanctions began. Despite ongoing negotiations, talks have stalled, with the union opposing the unilateral cancellation of the agreement.

Gad Ravid, chairman of the workers’ union, said the actions would continue to escalate if management does not reverse course: “We will not allow unilateral harm to Israeli workers. […] If management does not change course immediately, we will continue to escalate our actions.”

Sanctions Target Operational Leverage

The current measures are designed to apply pressure without immediately halting all operations. By focusing on system failure response, workers are targeting a critical support function that directly affects customer experience and service continuity.

Additional actions have already signaled broader escalation. On April 16, SAP employees and representatives from other labor groups held a protest outside the home of SAP Israel CEO Orna Kleinmann, drawing more than 100 participants and highlighting growing support within the country’s labor movement.

UNI Global Union also warned that further steps, including a potential shutdown of SAP’s Israeli operations, remain under consideration if negotiations fail to produce an agreement.

SAP said it will continue to deliver services to customers and negotiate in good faith. “We respect the workers’ union’s legitimate right to take industrial action,” the company said, adding that it remains committed to reaching a new agreement that reflects the role of its Israeli workforce.

What This Means for SAPinsiders

Localized labor disputes can have direct operational impact. The decision to halt system failure response highlights how targeted actions within a single region can affect service delivery. SAP customers with dependencies on Israeli teams may experience delays in issue resolution if the dispute escalates or expands.

The dispute reflects tension between flexibility and workforce protections. SAP’s push to update agreements for what it describes as the “AI era” points to broader shifts in how the company structures work and operations. For enterprise customers, these changes can influence delivery models, support structures, and long-term service stability.

Global delivery models are being tested under new pressures. SAP operates through a distributed network of R&D and support centers. Disruptions in one location raise questions about redundancy, workload distribution, and resilience. Customers may need to reassess how support coverage is structured across regions as labor dynamics evolve.