Most SAP consultants are used to thinking about process, data, controls, workflow, and system behavior inside a largely digital landscape. Even when projects touch real operations, the consultant’s main focus is still usually the system view of the business.

Embodied AI points to a future in which SAP does not only help people decide what should happen next, but may also play a greater role in directing what happens in the physical world.

For now, embodied AI in SAP is an emerging direction rather than a standard delivery model.

The recent stories around BITZER, ANYbotics, UTUM’s SafetyGuard prototype, NVIDIA, and other partner-led work are useful because they show that SAP is taking the subject seriously. 

This is a developing story about what may be appearing on the horizon of SAP development, and where some parts of SAP consulting could gradually move.

New areas in SAP usually appear first as extensions to existing work. That seems a sensible way to think about embodied AI as well. Rather than imagining a completely separate new consulting category arriving overnight, it is more realistic to see it as a possible future extension of disciplines that already interact with automation, operational data, and physical execution.

Why the subject has started to feel more real

Part of the reason embodied AI has started to attract attention is that early examples are beginning to attach the idea to familiar operational areas.

In the BITZER proof of concept, the conversation is about warehouse activity, picking, inspection, and the link between SAP process logic and physical task execution.

In the ANYbotics examples, the topic is not a general debate about machine intelligence. It is industrial inspection, asset monitoring, and how observations from a physical system may feed into maintenance and service processes.

In the UTUM SafetyGuard work, the main theme is safety and machinery inspection, rather than warehouse execution or production activity as the primary use case.

SAP people rarely respond strongly to a concept until they can see where it touches a module, a process chain, or a familiar implementation problem. Once the discussion becomes linked to warehouse orders, asset inspections, production support, visual checks, or shop-floor activity, it becomes easier to imagine how it might one day affect consulting work.

These examples are signs of direction. They are not yet proof that embodied AI is about to become a routine part of SAP programs. The public material remains centered on pilots, prototypes, and exploration. That means consultants can afford to be curious without acting as though a new specialist market has already fully formed.

Where it could begin to affect existing SAP disciplines

When embodied AI does develop further inside the SAP world, the first effects are unlikely to be evenly spread. Some disciplines are much closer to this type of development than others.

EWM is the clearest early example in SAP’s current public material. Warehousing has always been one of the SAP domains where process logic and physical execution work closely together. Warehouse tasks already lead to movement, confirmation, exception handling, and interaction with automation. Because of that, EWM is one of the most natural places for more intelligent physical execution to emerge. If SAP continues down this path, EWM consultants may gradually see more discussion around how warehouse orders, events, robotic systems, and agent-led logic relate to one another. That means EWM may be one of the first disciplines where this direction becomes visible in a practical way.

PM is another obvious candidate. Maintenance work already depends on signals, inspections, observations, follow-up actions, and operating judgement. The interesting possibility here is that more forms of inspection and data capture may increasingly come from more autonomous physical systems rather than only from people or static equipment. If that happens, PM work may slowly widen at the edges. Consultants in that area may find themselves discussing how these physical observations feed into notifications, service decisions, or work-order processes inside SAP.

PP and MES-related work also sit near this horizon, although the public evidence here is still more speculative. If AI-driven physical execution becomes more credible over time, production support, material staging, and parts of shop-floor coordination could become more closely linked to agent-led process logic. MES-related work would sit naturally near that change because it already operates at the boundary between SAP and operational execution.

QM work is often bound up with inspection, classification, observation, and decisions about whether something passes, fails, or needs review. Visual inspection is one of the more obvious areas where embodied AI could eventually have an effect. SAP and its partner ecosystem have already explored related ideas through augmented reality tools for inspection, maintenance, and service work, including AR-guided support linked to SAP Field Service Management. That does not prove embodied AI is about to reshape QM in the near term, but it does suggest that SAP has been moving gradually toward richer forms of physical inspection support for some time.

What makes this interesting from a consulting point of view

Most SAP consultants are never going to become robotics specialists, and there is no strong reason they should. The more interesting question is whether this kind of development slowly changes the extent of certain SAP disciplines. If it does, then the effect on consulting work is likely to be gradual and uneven. It will probably show up first in areas that already deal with automation, execution, and operational complexity.

That is also why the subject is worth tracking for consultancies. Not because it is already a mature line of business, but because it may become a useful growth area for firms that already sit near these operational disciplines.

Why it matters more for some consultants than others

If embodied AI stays on its current path, the consultants most likely to notice it first are the ones whose work already sits close to operational execution.

That does not only mean warehouse specialists. It also includes consultants around maintenance, production support, shop-floor integration, quality-related process work, and other roles where SAP logic already affects what people or machines do in the real world.

Over time, some consultants may find that their existing specialism starts to stretch a little. An EWM consultant may need more familiarity with the way AI-driven task handling fits into a warehouse process. A PM consultant may become more interested in how physical inspection data enters the maintenance chain. A PP or MES-related consultant may start seeing more discussion about how production support, execution, and agent-led decision logic connect.

The topic should probably be considered with curiosity: not to assume that every operational consultant now needs a detailed embodied AI strategy, but simply to recognise that SAP is exploring an area that could, in time, widen the practical scope of several familiar disciplines. Consultants who already work close to those areas may find it useful to watch how the topic develops.

A future extension of consulting work

A warehouse consultant may still be dealing with task allocation, exception handling, automation boundaries, and execution visibility. A maintenance consultant may still be dealing with inspection logic, notifications, follow-up actions, and operational risk. A production consultant may still be dealing with the relationship between planning, release, and execution. The difference would be that some of those discussions begin to include more intelligent physical systems as part of the process.

The value is likely to be found through understanding how SAP processes, business rules, and operational decision-making connect to a physical execution layer that is becoming more flexible and more context-aware. For some consultants, that may eventually become a useful adjacent capability. For some consultancies, it may become a natural extension of an existing practice.

A consultancy with a strong base in EWM, manufacturing, PM, shop-floor integration, or industrial process work is more likely to find a route into this area. Clients tend to trust expansion at the edge of a known capability more than a dramatic claim to a brand-new one. If embodied AI becomes more commercially meaningful over time, that pattern will probably hold here as well.

The consultancy angle

Even though the delivery market still looks early, the consultancy angle is already worth noting because SAP consultancies often grow by following the edges of platform development before those edges become mainstream. That means building enough understanding to have better conversations than other firms when the topic starts coming up in client discussions.

Clients may hear about warehouse robotics, industrial inspection, agentic AI, digital twins, or physical AI and ask where SAP fits into the picture. A consultancy that can explain that calmly, without overselling it, will be able to put it into perspective, without dismissing the topic too quickly or describing it as though wide-scale adoption is already just around the corner.

A consultancy can treat embodied AI as a developing area that may slowly create new work around operational SAP disciplines, while also being honest that most customers are not yet at the point of rolling it into standard delivery patterns. That kind of measured view tells clients that the firm understands the direction of travel without pretending the road is shorter than it is.

If embodied AI matures further, the firms most likely to benefit are probably those that have already built credibility around the process areas closest to it. They may find new opportunities in architecture discussion, integration planning, innovation workshops, operational advisory work, partner collaboration, or carefully scoped pilot support.

Embodied AI is on the horizon

The most balanced way to think about embodied AI in SAP is probably this: it is real enough to matter, early enough to treat cautiously, and close enough to some established SAP disciplines to be worth watching now.

The public evidence still comes from pilots, prototypes, co-innovation work, and partner-led exploration. That means it would be easy to overstate its short-term effect. It would be just as easy, though, to ignore the fact that SAP is clearly experimenting in directions that could eventually stretch the scope of disciplines such as EWM, PM, PP, QM, and MES-related work.

That is what makes it an interesting horizon topic. It suggests that some parts of SAP consulting may slowly move closer to conversations about physical execution, inspection, automation, and intelligent task handling. It hints at future consultancy growth in areas where ERP process logic meets far more advanced operational systems.

For now, that may be enough. Embodied AI is not about to redefine the whole SAP market. Consultants do, however, have good reason to notice it. Some developments are worth paying attention to long before they become common, simply because they show where the platform may be heading next. Embodied AI in SAP looks very much like one of those developments.

If you are an SAP professional looking for a new role in the SAP ecosystem our team of dedicated recruitment consultants can match you with your ideal employer and negotiate a competitive compensation package for your extremely valuable skills, so join our exclusive community at IgniteSAP.