{"id":115031,"date":"2026-02-04T15:41:13","date_gmt":"2026-02-04T14:41:13","guid":{"rendered":"https:\/\/simplifier.io\/news\/why-mann-schroeder-is-not-waiting-for-the-next-sap-project\/"},"modified":"2026-07-14T08:26:59","modified_gmt":"2026-07-14T06:26:59","slug":"why-mann-schroeder-is-not-waiting-for-the-next-sap-project","status":"publish","type":"post","link":"https:\/\/simplifier.io\/en\/events\/why-mann-schroeder-is-not-waiting-for-the-next-sap-project\/","title":{"rendered":"Why Mann & Schr\u00f6der is not waiting for the next SAP project"},"content":{"rendered":"

Digitization rarely fails because of a lack of ideas, but rather because of the realities on the ground: SAP Core, non-SAP systems, production, data sources everywhere, backlogs piling up, and scarce resources. Then AI comes along, and everyone hopes for a major leap forward. But without clean data and processes, it often amounts to nothing more than a good demo. <\/p>\n

In the session at ITOK26 of IT Onlinemagazin<\/a>, we talked to Adrian Dexheimer<\/a> from Mann & Schr\u00f6der Cosmetics Group about exactly that. And what sticks is not so much a tool as an approach: think side by side, prioritize use cases, deliver quickly, but with clear guidelines for governance, security and operation. <\/p>\n

The crucial point: AI needs a foundation<\/h2>\n

A practical learning from the conversation: In AI projects, a lot of time is not spent on the model itself, but on making it suitable for the enterprise. Data connection, roles, authorizations, cost control, deployment, operation. It is precisely these topics that ultimately decide whether AI works in everyday life or only in the proof of concept. <\/p>\n

That’s why it’s worth looking at the foundation underneath: Integration, data, workflows and applications that neatly connect these building blocks.<\/p>\n

From theory to practice: use cases that really work<\/h2>\n

Mann & Schr\u00f6der did not stop at one pilot. In the talk, several implemented applications were mentioned that are left lying around for a long time in many organizations because they are too small for a major project, but too important for “we’ll do it later”. <\/p>\n

Examples from the session<\/h3>\n
    \n
  1. \n

    Print data process with documents and PDF handling directly in the browser<\/p>\n<\/li>\n

  2. \n

    Connection of a laboratory database with feedback of measured values to SAP<\/p>\n<\/li>\n

  3. \n

    Master data pool for product data including synchronization<\/p>\n<\/li>\n

  4. \n

    Field service solution for orders and status information with SAP access<\/p>\n<\/li>\n<\/ol>\n

    Why workflows are more than just a technical detail<\/h2>\n

     <\/p>\n

    \n

    Workflows create clarity.<\/p>\n<\/blockquote>\n

    As soon as a process is clearly described, roles, statuses, handovers and responsibilities become visible. This not only helps with implementation, but also with acceptance and maintainability. The application is then not “an app”, but a clean process with comprehensible logic. <\/p>\n

    Cooperation that works<\/h2>\n

    Instead of handovers between the business department and IT, a tandem was described: Process Owner in the business department and Product Owner in IT. This sounds simple, but in practice it makes all the difference because requirements are not “thrown over the fence”, but are created together. <\/p>\n

    Conclusion<\/h2>\n

    If you wait for the one big transformation project, you lose time. If you start side by side, consistently deliver use cases and take governance seriously, you can achieve results faster without touching the SAP core and without inheriting chaos later on. <\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/section>