Signal-Cockpit.

Why now

An explicit S/4HANA roll-in signal usually means the program is moving beyond abstract planning into cross-functional execution. In that phase, companies migrating to S/4 typically have to decide which historical ERP data and documents stay in the new core, which move to archive access, and who owns that decision across business and IT. Those choices can materially affect HANA sizing, migration scope, compliance handling, and the timeline for retiring legacy environments later.

Angles

• Cross-department ownership may be fragmented The posting explicitly mentions "several cross-department interlinkages." That makes legacy-data ownership a practical issue: archive scope, document access, and retention decisions may sit between SAP program, business process owners, and compliance rather than in one team.
• Roll-in model raises template vs. local legacy questions Because the evidence points to an "S/4HANA roll-in," a relevant angle is whether legacy ERP data and old documents are being handled centrally as part of the roll-in template or left to local/business-unit decisions.
• Multi-brand manufacturing context can complicate historical document access BSH describes a global brand portfolio including Bosch, Siemens, Gaggenau, Neff and local brands. In S/4 programs like this, access to historical order, delivery, invoice, and service-related documents often has to work consistently even when operational processes are being standardized.

Flags

• Signal comes from a working-student posting, so the role may be adjacent to the core ERP program rather than a direct SAP transformation lead hire.
• The job title is AI Transformation; the S/4HANA signal appears in the snippet, not as the primary title focus.
• Decision-making may sit at group level given the global brand structure mentioned in the posting.

Personen

• B. B.SAP S4 Hana Project Roll-In Process Owner at BSH Hausgeräte AG98%
• W. K.Service Delivery Manager Platform Consulting and Enabling bei BSH Hausgeräte GmbH90%
• C. B.Project Leader IT Coordination bei BSH Hausgeräte GmbH84%

Belege

• Working Student AI Transformation (m/f/d)
• Working Student AI Transformation (m/f/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies are in an active S/4HANA transformation, decisions around what remains in the active ERP scope versus what can stay in archive or legacy access often affect system sizing, migration effort, and later decommissioning options. In infrastructure-heavy phases, these tradeoffs usually become more concrete because migration, environments, and testing have to be aligned against a target footprint.

Angles

• Infrastructure lead role suggests sizing decisions are becoming tangible The specific hire is for "Teil-Projektleitung Infrastruktur im Stabsprojekt SAP S/4HANA (w/m/d)". That usually means target environments, capacity, and cutover dependencies are being shaped now rather than later.
• Migration and testing are explicitly in scope The posting says: "Koordinieren der Systembereitstellung sowie Abstimmung mit Entwicklung, Migration und Testing". That creates a concrete opening to discuss how legacy data volume influences migration cycles, test system load, and non-production landscape setup.
• Utility context implies operational and retention-sensitive document history As a water and wastewater utility, Berliner Wasserbetriebe likely operates with long-lived operational and commercial records. In S/4 programs, those document histories often need a clear split between day-to-day access and archive/legacy access, especially if old systems are to be reduced later.

Flags

• Evidence is limited to one role and short snippets; no explicit timeline, ECC reference, or named legacy systems are provided.
• The posting is for a partial infrastructure project lead, so the ultimate archive/legacy decision may sit with a central program office, SAP lead, or enterprise architecture team.
• Utility-specific document examples should be used carefully in outreach as hypotheses, not as asserted facts about their current landscape.

Personen

• O. S.Projektleiter SAP S/4HANA98%
• G. K.Leitung Informationstechnologie / IT-Leitung95%
• D. R.IT Projekt Office / IT-Stabsprojekt S/4HANA86%
• J. S.Teamleiter Finanzanwendungen und Logistik SAP82%

Belege

• Teil-Projektleitung Infrastruktur im Stabsprojekt SAP S/4HANA (w/m/d)
• Teil-Projektleitung Infrastruktur im Stabsprojekt SAP S/4HANA (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies are hiring subproject leaders for SAP S/4HANA FI and MM plus PMO support, the program is typically in active design and implementation. In this phase, decisions about which legacy data and documents must remain operationally accessible versus moved to archive often shape HANA sizing, migration scope, and the later effort to decommission old environments.

Angles

• FI workstream: finance document retention and day-to-day access They are hiring a "Teilprojektleitung SAP S/4HANA FI (w/m/d)" with focus on "SAP S/4HANA Finance (FI-GL, FI-AP, FI-AR, FI-AA)". That creates a concrete entry point around which finance records and historical accounting documents need to stay directly accessible in the new setup versus archived separately.
• MM workstream: procurement document footprint in a transport operator They are hiring a "Teilprojektleitung SAP S/4HANA MM (w/m/d)" for Materials Management. For a public transport operator, MM typically carries large volumes of purchasing and goods-movement documents; that makes legacy MM scope a practical discussion alongside the S/4HANA implementation.
• PMO involvement suggests cross-functional governance window The work student posting names support for "Projektleitung und das Project Management Office (PMO)" in the "SAP S/4HANA Einführungsprojekt". That is a useful angle because archive and legacy-data decisions often cut across FI, MM and program governance rather than sitting in one module alone.

Flags

• The evidence proves an active S/4HANA introduction, but not a named archiving or legacy-decommissioning workstream.
• Ownership may be cross-functional: FI, MM and PMO are all being staffed, so no single module lead may own legacy-data decisions alone.
• Public transport operators can have broader governance and procurement structures, so the final decision maker may sit above the hiring roles.

Personen

• A. G.IT Projektmanager SAP S 4 HANA97%
• M. W.Teamleiter SAP Applikationsmanagement93%
• K. S.Strategische IT-Einkäuferin89%
• R. N.IT Architekt und Anwendungsbetreuer82%

Belege

• Teilprojektleitung SAP S/4HANA FI (w/m/d)
• Teilprojektleitung SAP S/4HANA MM (w/m/d)
• Werkstudent Projektmanagement SAP S/4HANA (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies in the middle of S/4 programs typically have to decide how much ECC-era data and document history must stay operational in the new core versus move to an archive or legacy access model. That choice can affect HANA sizing, migration scope, and later decommissioning effort. In global rollouts, the issue often gets harder because process teams, master data governance, audit needs, and plant or quality documentation all intersect across regions and functions.

Angles

• P2P rollout scope across global S/4 program The Global Key User Purchase to Pay role is explicitly meant to "Support and co‑lead global SAP S/4HANA rollout activities". That makes P2P document history and day-to-day access to older purchasing data a concrete discussion point for the rollout team, not just an IT backend topic.
• Governance and audit readiness in plant-facing systems The IT Project Manager - Product & Plant Systems role calls out "documentation completeness, and audit readiness" across R&D, Quality, and Manufacturing domains. For a food and beverage manufacturer, retention and access to quality, manufacturing, and maintenance-related records can become a practical legacy-data design issue during ERP transformation.
• Cross-functional footprint beyond finance alone Hero is not only hiring for procurement transformation but also for Product & Plant Systems covering PLM and CMMS. That suggests the S/4-related transformation touches both transactional ERP processes and plant/product documentation landscapes, which can complicate decisions on what historical data stays live versus moves to archive access.

Flags

• Evidence comes from job postings only; no confirmed timeline, migration phase, or named program beyond global SAP S/4HANA rollouts.
• The postings indicate global scope, so ownership may sit with a central or group-level team rather than locally in Germany.
• No explicit mention of archiving, ECC decommissioning, or current archive setup in the evidence.

Personen

• P. S.Group Chief Procurement Officer (Hero Cycle & Hero HIVE)97%
• D. K.Global SAP Application Expert at Hero Group96%
• R. K.Chief Operations Officer, leading manufacturing, procurement, quality and digital at Hero MotoCorp94%

Belege

• Global Key User Purchase to Pay
• Global Key User Purchase to Pay
• IT-Projektmanager/in - Product & Plant Systems

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies moving Finance to S/4HANA typically have to decide early which historical ERP data and business documents must remain active in the new core versus which can move to an archive or legacy access layer. That matters even more when the target scope includes finance, vendor invoice processes, and compliance reporting, because old accounting documents, invoice images, and audit-relevant records can otherwise inflate HANA scope and complicate cutover. In many S/4 programs, that archive boundary gets set implicitly by solution design and sizing decisions rather than through a dedicated legacy-data workstream.

Angles

• LUCA is explicitly a finance-to-S/4 program with compliance risk in scope The posting frames LUCA around upgrading METRO's Finance to SAP S/4HANA 'to ensure business continuity and avoid security and compliance risks.' That creates a concrete opening to discuss how legacy finance records and audit-relevant documents are handled during the move, not just the target design.
• VIM and finance document processes suggest large volumes of retained invoice records The S/4 Finance architect role calls for experience in 'Vendor Invoice Management' alongside GL, AP and AR. That points to a document-heavy finance landscape where historical invoice content and related metadata may need a distinct treatment from active transactional data.
• Document Reporting and Compliance makes retention and evidence access a live design issue The role explicitly mentions 'Document Reporting and Compliance' and alignment to 'compliance standards.' For S/4 programs, that is a specific angle to explore whether old reporting-relevant finance documents stay in the new core, remain in legacy, or move into a compliant archive with continued access.
• Ariba plus S/4 integration raises the boundary question for indirect procurement documents METRO is also hiring an SAP Ariba Solution Architect for LUCA, covering 'SAP Buying and Invoicing' and integration between Ariba and S/4HANA. That makes the handling of historical procurement and invoice documents more specific than a generic S/4 conversation.
• Global template alignment may pressure standardization of legacy access The Finance architect is expected to align solutions with 'Metro's global template, enterprise architecture, SAP best practices, and compliance standards.' That is a concrete cue that legacy-data handling may need to be standardized centrally rather than solved country by country.

Flags

• Evidence is limited to job-posting snippets; no migration timeline, source ECC scope, or current archive setup is stated.
• The Ariba role may reflect a broader procurement workstream adjacent to LUCA, not necessarily the same decision-maker for archiving.
• 'Global template' suggests decisions could be centralized above local business units or country organizations.
• No explicit mention of legacy-system decommissioning or existing archive pain in the evidence.

Personen

• F. K.Stream Lead P2D (SAP S/4Hana Implementation Project)94%
• D. S.SAP Project Manager - Digital Finance & Procurement Program at METRO AG92%
• S. L.Squad Lead Financial Reporting and Planning @METRO AG86%
• R. S.Lead - Enterprise Architect Stream80%
• A. U.Head of Global Business Services74%

Belege

• SAP Ariba Solution Architect (all genders)
• Solution Architect - SAP S4/HANA Finance (all genders)
• SAP Ariba Solution Architect (all genders)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a timely archiving conversation because companies in active S/4 programs typically have to decide early what stays as active data in the new system versus what can remain accessible in an archive or legacy-retirement setup. That decision often affects HANA sizing, migration effort, data-quality work, and later decommissioning of old systems if historical documents and legacy access are still needed after go-live.

Angles

• Legacy-system scope is explicitly in play The posting directly mentions "Migration bestehender Stammdaten aus Altsystemen in SAP S/4HANA". That gives a concrete opening to discuss which legacy data must be active in S/4 versus which historical records can remain outside the core system while still being accessible.
• Master-data objects named in the role suggest a concrete cutover boundary The role calls out SAP master data objects including "Materialstamm, Arbeitspläne, Arbeitsplätze, Kunden-/Lieferantenstamm, Business Partner". Those objects create a specific discussion point around how much historical context tied to these records needs to move into S/4 for day-to-day operations versus stay in an archive-access model.
• Go-live coordination across business functions raises ownership questions The posting includes "Begleitung der Go-Live-Phase" and "enge Zusammenarbeit mit den Fachbereichen und externen Dienstleistern". That makes it relevant to ask which team decides the boundary between active operational data and archived legacy content before go-live dependencies harden.

Flags

• Evidence is from a single role reposted multiple times, not multiple distinct openings.
• The posting appears tied to Asperg, so the program scope may be local or entity-specific rather than group-wide.
• The evidence is strongest on master-data migration and S/4 introduction; archiving or legacy decommissioning is not mentioned explicitly in the posting.
• Decision-making may sit with a broader group or regional SAP organization rather than the hiring manager for this role.

Personen

• A. L.Teamleiter SAP bei Mitsubishi Chemical Europe98%
• M. S.Head of Information Technology Operations, EMEA94%
• j. k.Sr. Manager (ICT) at Mitsubishi Chemical Group APAC89%

Belege

• SAP Specialist (m/w/d) – mit Schwerpunkt S/4HANA
• SAP Specialist (m/w/d) – mit Schwerpunkt S/4HANA
• SAP Specialist (m/w/d) – mit Schwerpunkt S/4HANA

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies run an S/4 or broader ERP transformation through a PMO, legacy-data scope tends to get fixed earlier than expected, often alongside sizing, workstream design, and cutover planning. In life sciences environments, teams also need to think about which historical documents and records must remain accessible for operational or compliance reasons after the new core goes live.

Angles

• QIAbase PMO is a concrete entry point The posting explicitly names the "QIAbase Program Management Office (PMO)". That suggests transformation governance is centralized enough that archive scope, legacy access, and decommissioning decisions may be coordinated through a program office rather than left to individual teams.
• Life sciences legacy access is usually broader than finance-only retention Because QIAGEN is a life sciences company and the role supports digital transformation in the QIAbase PMO, a relevant discussion is not just ERP tables but also which historical business and compliance-relevant documents need day-to-day access after transformation.

Flags

• The evidence shows a digital transformation PMO role, but does not explicitly mention SAP, ECC, or S/4HANA in the provided text.
• The posting is for a working student, so the ad itself may not reflect the senior ownership of ERP and legacy-data decisions.
• QIAGEN is described in the posting as a global life sciences company; transformation decisions could be made at group level rather than locally in Germany.

Personen

• S. A.Senior IT Service Manager SAP95%
• J. P. B.IT Service Manager SAP BASIS @ QIAGEN94%
• J. S.IT Business Consultant (SAP)93%
• M. O.Project Manager Digital HR Transformation90%
• J. W.Senior IT Director - Head of Enterprise Platforms88%

Belege

• Working Student (f/m/d) - Project Management and Digital Transformation
• Working Student (f/m/d) - Project Management and Digital Transformation

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

The signal suggests Rottendorf Pharma is already past the initial SAP S/4HANA go-live and is now in the stabilization and optimization phase for supply chain and logistics. In S/4 programs, this is often the point where legacy-data decisions become operational: teams see which historical ERP and document access is still needed day to day, while HANA sizing, archive separation, and old-system retirement options become more concrete. For pharma manufacturers, retained access to historical logistics and batch-related records can complicate that step if it was not explicitly separated from active transactional scope.

Angles

• Post-go-live supply chain stabilization creates a practical legacy split decision The hired role is explicitly responsible for "Stabilisierung und Weiterentwicklung" of the SAP S/4HANA and EWM landscape after go-live. That usually means operational teams are now discovering which historical logistics data still needs fast access versus what can move into compliant archive access.
• S/4HANA plus EWM increases the need to separate active from historical logistics records Because the posting names both SAP S/4HANA and EWM, the relevant legacy scope is not just classic ERP data but also warehouse and delivery-related history that supply chain users may still consult after go-live.
• Pharma logistics adds retention sensitivity around historical records As a pharmaceuticals company, legacy logistics history can intersect with regulated document retention needs such as batch, delivery, and warehouse-related records, making compliant archive access and later legacy-system shutdown harder to ignore once the new landscape is live.

Flags

• Evidence comes from one repeated posting only; signal depth is limited.
• The posting is for a supply chain excellence role, so the ultimate archive or legacy-data decision may sit with central IT or a broader SAP program team.
• The evidence confirms post-go-live S/4HANA and EWM work, but does not state anything explicit about ECC, archiving, or legacy-system decommissioning.

Personen

• E. S.Supply Chain Manager91%
• B. S.Head Of Logistics90%
• B. D.DGT-SAP Development Manager88%
• J. P.Supply Chain Management86%

Belege

• Supply Chain Excellence Specialist (m/w/d) – SAP S/4HANA & EWM
• Supply Chain Excellence Specialist (m/w/d) – SAP S/4HANA & EWM

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a strong transformation signal because the posting describes active delivery responsibility for an ECC to S/4HANA migration rather than generic SAP operations. In S/4 programs, companies typically have to decide early how much ECC legacy data stays in the migration scope versus moves into an archive or legacy-access model, because that choice affects HANA sizing, migration effort, testing scope, and what users still need day to day after Go-Live.

Angles

• ECC-to-S/4 scope already includes data migration The role explicitly owns 'Data Migration' within the ECC to S/4HANA program. That creates a concrete opening to discuss whether all historical SAP data is really in scope for migration or whether part of the ECC legacy should remain accessible outside S/4.
• SAP and Siemens Teamcenter interface landscape The posting names interface design between business stakeholders and IT service owners for 'SAP ERP, Siemens Teamcenter'. For TKMS, a legacy-data approach may need to account not only for SAP records but also for how old ERP-linked documents and references are accessed across the SAP/PLM boundary after migration.
• Cut-over and Go-Live coordination raises legacy access decisions The second posting includes 'Koordination von Change-Management, Cut-over- und Go-Live-Aktivitäten'. In that phase, teams usually need a clear answer on what users still require from ECC day to day at Go-Live versus what can be served from an archive or legacy-access layer.
• Custom code evaluation can expose historical-data dependencies Because the role includes 'Custom Code Evaluation', TKMS likely has to identify reports, transactions, or processes that still depend on historical ECC data. That is a practical angle for discussing which legacy data must stay operationally reachable without carrying everything into S/4.

Flags

• The evidence comes from job postings only; no confirmed timeline, phase dates, or named program governance are provided.
• The posting spans multiple locations, so the S/4 decision-making may be centralized above the local hiring site.
• The advertised role is architecture-focused; the final owner of archiving or legacy decommissioning decisions may sit elsewhere.
• Industry context is shipbuilding from the evidence; avoid asserting specific regulated document classes unless confirmed in conversation.

Personen

• T. K.VP IT Global Services93%
• H. H.VP IT Global Applications89%
• T. Z.Head of Combat Systems & IT Architecture84%

Belege

• Solution Architect Application Management (m/w/d)
• Solution Architect Application Management (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies in S/4-related transformation phases typically have to decide early which legacy ERP data and documents must stay in the active system versus move into a compliant archive. In supply-chain-heavy environments, that decision affects HANA sizing, migration scope and later access to historic purchasing, delivery and inventory records. When transformation work is already framed as global and spans operational to strategic topics, the legacy-data cutover often becomes cross-functional rather than a pure IT task.

Angles

• Global supply chain transformation creates a cross-functional legacy-data decision Because the hiring signal is explicitly for "Global Supply Chain Business Transformation", the archive question is likely not only technical. A relevant angle is who decides which historic purchasing, delivery and inventory documents remain operationally needed in the future template versus archived for lookup only.
• Operational, tactical and strategic scope suggests competing needs for old supply chain records The posting describes work across "operational, tactical and strategic tasks". That is a useful opening to discuss how day-to-day access needs for historic supply chain documents can conflict with strategic goals to reduce migrated data volume and retire legacy environments.

Flags

• Evidence is limited to an internship posting, so the transformation signal is strong but seniority and concrete program stage are unclear.
• The posting points to a global supply chain transformation context, but it does not explicitly mention SAP, ECC or S/4HANA.
• Decision-making may sit at group level and not in the local hiring organization.
• No explicit timeline, rollout wave, template milestone or system landscape is stated in the evidence.

Personen

• C. H.Head of Global Development SAP at ZEISS Group97%
• G. R.SAP Team Head APAC @ ZEISS Group | SAP Development, SAP Basis94%
• H. A.Project Manager & SAP-ERP/S4HANA System Analyst / Solution Architect bei Carl Zeiss AG93%
• M. K.Helping to safeguard Carl Zeiss’s Global and Business Critical SAP Systems88%

Belege

• Internship in Global Supply Chain Business Transformation (f/m/x)
• Internship in Global Supply Chain Business Transformation (f/m/x)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a credible transformation signal because the posting ties SAP S/4HANA directly to Palm's central business processes and central IT. In S/4 programs, legacy data and document scope typically gets settled around sizing, process design, and business-area requirement discussions. That is usually the point where companies decide what stays active in S/4, what moves to compliant archive access, and how much legacy footprint they carry into HANA and beyond.

Angles

• Central-process S/4 scope suggests cross-functional archive decisions The posting says SAP S/4HANA is the standard solution for Palm's "zentralen Geschäftsprozesse". That usually means archive scope cannot be solved in one module alone; finance, procurement, sales, and operational documents may need a common decision on what remains active versus accessible historically.
• Bridge role between IT and business is a cue for legacy-access requirements Palm wants someone who "die Verbindung zwischen IT und Fachbereichen lebt" and advises business units on requirements in the S/4HANA system. That is a natural point to raise whether business users still need day-to-day access to older SAP documents and data after process cutover.
• Central IT hiring at headquarters implies a group-level template discussion The role sits in "der zentralen IT an unserem Stammsitz in Aalen" and supports the digital development of the "Palm Gruppe". That suggests decisions on legacy data handling may be made centrally and then applied across group entities rather than locally.

Flags

• Evidence shows active S/4HANA hiring, but not a named migration phase, timeline, or go-live date.
• The posting is for central IT at headquarters, so buying authority may sit at group level rather than with a local plant or department.
• No explicit mention of ECC, archiving, DMS, or legacy-system retirement in the evidence.
• Only one role is visible in the evidence, so current project scale and module scope are still unknown.

Personen

• M. S.IT Architekt bei Papierfabrik Palm GmbH & Co. KG94%
• T. H.Teamleiter Group Processes (SAP, EDI, BI) in der Palm Gruppe92%
• M. S.Head of Technology (CTO) Palm Packaging84%

Belege

• Business Information Specialist – SAP S/4HANA (m/w/d), Aalen
• Business Information Specialist – SAP S/4HANA (m/w/d), Aalen

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a timely archiving signal because companies in active SAP template rollouts typically have to decide how much legacy ECC data and historical finance documentation should remain in the future core versus move to a compliant archive. That decision often affects HANA sizing, rollout complexity, and how quickly older systems can later be retired, especially when finance standardization and regulatory compliance are explicit program goals.

Angles

• SAP FAST rollout into new markets The posting says the role will steer 'SAP template rollouts in new markets from As-is analysis to the end of the hypercare phase'. That creates a concrete decision point on whether historical finance data and documents are migrated into each rollout scope or accessed via archive from legacy environments.
• Governance and stabilization of already-live markets Daimler Truck is not only rolling out SAP FAST but also 'governing, stabilizing and further developing markets already live'. That suggests a mixed landscape where archive and retention design may need to work across both live-template markets and legacy-country setups.
• Accounting and financial reporting compliance The role centers on 'accounting and financial reporting' and explicitly mentions 'regulatory compliance'. That makes the handling of historical finance records, audit-relevant documents, and retention-proof access a concrete finance-program issue rather than a generic IT optimization topic.
• Global standardization across the DTFS Group Because the template is described as standardized 'across the DTFS Group', a useful angle is whether legacy data access and document retention are being standardized alongside the finance template, or left to each market during rollout.

Flags

• The evidence points to a finance-template program, not necessarily a full company-wide S/4HANA transformation.
• The scope named is 'across the DTFS Group', so the buying center could sit in a group or finance-services organization rather than central Daimler Truck IT.
• The role is fixed-term, which can indicate project intensity but may also mean temporary rollout capacity rather than a broad strategic platform change.

Personen

• C. H.Manager PMO Finance Templates95%
• N. S.Manager IT - SAP S 4HANA Finance Hub EMEA91%
• A. M.Lead Solution Architect für Service Operation und IT-Prozesse SAP77%
• J. R.Manager IT Aftersales SAP Application Management58%

Belege

• Senior SAP finance inhouse consultant (f/m/d) fixed-term
• Senior SAP finance inhouse consultant (f/m/d) fixed-term

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies moving from ECC to S/4HANA typically have to decide early which data stays operational and which historical records can be archived or left behind. That choice affects HANA sizing, migration effort, system-copy scope, and later legacy decommissioning. When an internal SAP role combines ECC operations, project delivery, and support across multiple modules, the legacy-data question often intersects directly with ongoing delivery work.

Angles

• One role spans ECC operations and S/4HANA transformation The posting combines "Betrieb und Weiterentwicklung der SAP ECC-Systemlandschaft" with "Unterstützung der Transformation auf S/4HANA". That suggests the team may be balancing day-to-day ECC stability with transformation design, which is where legacy-data scope can become a practical delivery issue rather than a later cleanup topic.
• Broad module scope means archive scope is likely cross-functional The role supports FI, CO, MM, SD, PP, PS, PM, and PLM. In a manufacturing environment, that can mean historical data and documents are spread across finance, procurement, sales, production, maintenance, and product lifecycle processes, so archive decisions may need alignment beyond a single module owner.
• System copies and release work make historical-data volume visible The posting explicitly mentions "Releasewechseln, Patches und Systemkopien". In S/4 programs, system copies and related landscape work are often where teams feel the operational impact of carrying full ECC history into project and non-production environments.

Flags

• Evidence comes from job-posting snippets only; no named S/4 program scope, phase, or timeline is provided.
• The explicit S/4HANA reference appears in a separate snippet, while the fuller posting text mainly details ECC operations and module support.
• The StepStone entries appear to be duplicates of the same role.

Personen

• T. F.Chief Executive Officer98%
• P. S.Produktionsplaner98%
• S. D.Head of Programs92%

Belege

• SAP Inhouse Consultant (m/w/d)
• SAP Inhouse Consultant (m/w/d)
• SAP Inhouse Consultant (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a strong timing signal because the role sits inside the implementation itself, not after the fact. Companies moving to S/4HANA typically have to decide early which legacy data, documents, and interfaces stay in the active system versus move into an archive, because those choices affect process design, migration effort, and HANA sizing before go-live.

Angles

• Warehouse scope includes both own warehouse and 3PL processes The posting names 'Lagerprozesse (Eigenlager + 3PL)'. That usually means logistics-relevant records and document flows are spread across internal and external warehouse setups, which can complicate what must remain operational in S/4 versus what can be archived.
• Interface and exchange-format work is part of the program The role will 'klären Schnittstellen' and 'prüfen Datenaustauschformate (EDI/API)'. That creates a concrete angle around legacy logistics documents and data dependencies that may otherwise stay tied to old ERP interfaces longer than expected.
• Master data migration is explicitly in flight The posting says the team should 'für eine reibungslose Migration der Stammdaten' sorgen. That is a specific moment to separate master data needed in the target system from historical transactional and document data that does not need to inflate the new footprint.
• Go-live and hypercare are already planned deliverables The role covers 'Tests bis hin zu Go-Live und Hypercare'. Once a program is this concrete, decisions on historical access and old-document retrieval often need to be settled before cutover rather than deferred.

Flags

• Only one posting is provided, so the signal is based on a single role.
• The role is temporary ('befristet auf 1 Jahr'), which may indicate project support rather than strategic ownership.
• The posting is for a logistics key user; enterprise archiving decisions could still sit with group IT or a broader SAP program team.
• Evidence mentions S/4HANA implementation and master data migration, but does not specify current ECC scope, archive setup, or timeline dates.

Personen

• O. K.Head of Operations und Geschäftsführer Susonity Production93%
• V. G.Head of Supply Chain EMEA92%
• R. T.SAP S 4HANA Implementation Streamlead PP91%
• B. Z.Head of IT Transformation89%

Belege

• I2O Logistics Key User (w/m/d) befristet auf 1 Jahr

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a timely archiving conversation because companies in S/4-related transformation programs typically have to decide which legacy ECC data must remain operationally accessible, what should move into compliant archives, and who owns that decision across analytics, ERP, and business teams. When programs include new analytics platforms plus mixed S/4HANA, ECC, and non-SAP integration, the boundary between active data and retained history often affects HANA sizing, migration scope, and later legacy-system shutdown options.

Angles

• Greenfield transformation across the meat and sausage plants The posting ties the role to a 'mehrjährigen Greenfield-Transformation' in the 'Fleisch- und Wurstwerken der REWE Group'. That creates a concrete opening to discuss how historical ERP data and documents from plant operations should be split between new active platforms and long-term retention during the program.
• Coexistence of S/4HANA, ECC, and non-SAP sources The role will design 'Integrationsszenarien (z. B. SAP S/4HANA, ECC und Non-SAP-Quellen)'. That specific mix suggests a practical need to clarify which legacy ECC information must stay connected for reporting versus what can be archived and served outside the transactional core.
• Analytics architecture ownership is being built now They want someone to take a 'zentrale Rolle' in introducing and strategically developing the SAP analytics landscape with SAC, Datasphere, BW/4HANA, or SAP Business Data Cloud. That is a useful angle because ownership for legacy data and old documents often gets decided implicitly by whoever shapes the target data architecture.

Flags

• The posting is for Wilhelm Brandenburg but explicitly references the REWE Group; decision-making may sit partly at group level.
• The evidence is strongest for analytics transformation, not a confirmed core ERP migration timeline.
• The hiring signal is from an analytics role, so the first contact may not be the final owner of archiving or legacy decommissioning decisions.

Personen

• H. D.Leitung ERP-Transformation Wilhelm Brandenburg/REWE98%
• C. H.Director - Head of S4 Reporting and Analytics86%
• S. W.Bereichsleiter SAP bei REWE84%

Belege

• (Senior) Analytics Berater (SAP BDC inkl. SAC & Datasphere) (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This signal suggests active SAP platform change around S/4HANA, BW and AWS. In S/4 programs, companies typically need to decide early which historical SAP data and documents stay in the active footprint versus move to compliant archive or legacy access, because that choice affects HANA sizing, migration scope and later decommissioning options.

Angles

• S/4HANA plus BW in the same operated landscape The posting names an SAP system landscape 'inkl. S/4HANA und BW'. That creates a concrete angle around how VHV wants to separate active operational data from historical reporting-relevant data and documents before sizing the future landscape.
• AWS migration and hybrid architecture The role includes 'Unterstützung bei Cloud-Migrationen (AWS) und Mitgestaltung hybrider Architekturen'. In a hybrid target state, archive and legacy-access placement becomes a practical design decision: what must remain near the active SAP core versus what can be removed from the migration path.
• Basis-owned operational stability mandate The hire is responsible for 'Sicherstellung eines stabilen Betriebs, Monitoring und kontinuierliche Optimierung'. That makes operational load, system footprint and retirement of non-essential legacy data a relevant conversation for the team closest to platform stability.

Flags

• Evidence shows active SAP platform work, but not a named S/4 transformation program or timeline.
• The posting is for a SAP Basis Administrator, so the initiative may currently be infrastructure- or operations-led rather than business-led.
• Decision-making could sit centrally across group IT; the vacancy alone does not prove who owns archive or legacy decommissioning decisions.
• No source evidence confirms current archive tooling, ECC footprint, or decommissioning plans.

Personen

• J. A.Head of Digital Development SAP Insurance96%
• F. D.Leiter IT-Infrastruktur92%
• J. E.SAP Architect90%
• D. S.Leiter Plattformbetrieb und Automation87%
• O. C. v. B.Head of International IT Platform82%

Belege

• SAP Basis Administrator mit Schwerpunkt Linux, AWS & BTP (w/m/d)
• SAP Basis Administrator mit Schwerpunkt Linux, AWS & BTP (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies are actively reshaping SAP/ERP landscapes, legacy-data decisions usually surface earlier than expected: what stays in the live core, what is archived compliantly, and what can later support decommissioning of old environments. In S/4-related or broader ERP transformation programs, these choices affect HANA sizing, migration scope, operating complexity, and the ability to retire legacy systems cleanly after go-live.

Angles

• SAP AmS project suggests an operating-model decision point The posting explicitly names a "SAP AmS-Projekt". That creates a concrete opening around how Mercedes-Benz wants to separate day-to-day SAP support scope from historical data and old documents that users still need to access but do not need in the live core.
• Central sales and production planning applications raise historical access needs The transformation architect role sits in "Planung, Allokation und Kapazitätsmanagement" and covers central sales and production planning applications. For this kind of landscape, SDR can probe whether older planning-related SAP data and documents must remain directly accessible for operations, analysis, or audit without inflating the future productive footprint.
• Integrated, data-driven enterprise steering increases pressure on data boundaries The phrase "Transformation hin zu integrierter, datengetriebener Unternehmenssteuerung" points to cross-functional integration. In such programs, teams often need an explicit rule for which legacy ERP content belongs in the new operating core versus an archive layer, especially when multiple business areas and external partners are involved.

Flags

• The clearest SAP signal is an internship posting; the strategic owner is likely elsewhere.
• "SAP AmS" is referenced, but the snippet does not define scope, target architecture, or whether this is directly tied to S/4HANA.
• One posting references Mercedes-Benz Group AG in the description, so decision-making could sit at group level rather than only within Mercedes-Benz AG.
• The transformation architect posting is broader than SAP and may indicate enterprise transformation adjacent to, not identical with, ERP migration.

Personen

• M. H.Global Lead SAP Strategy, Architecture & Transformation at Mercedes-Benz Group AG98%
• A. H.Project lead Digital Transformation SAP Cloud ALM at Mercedes-Benz AG95%
• M. S.Chief Enterprise Architect & Director of IT Strategy at Mercedes-Benz93%
• D. M.SAP Solutionarchitect and Application Owner at Mercedes-Benz AG90%
• K. L.Chief Information Officer at Mercedes-Benz Group AG78%

Belege

• Business Transformation Architect "Agentic-AI & Simulation" (d/m/w/x)
• Praktikant*in Unterstützung im SAP AmS-Projekt
• Praktikant*in Unterstützung im SAP AmS-Projekt

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies moving to S/4HANA, especially Public Cloud with clean-core rules, typically have less room to carry forward custom legacy data structures into the new core. That makes decisions around what stays operationally accessible in S/4, what should move into a compliant archive, and how legacy documents remain available more time-sensitive because those choices can affect integration scope, data ownership, and the long-term cost of keeping older systems alive.

Angles

• Public Cloud clean-core limits what belongs in the new core The role explicitly calls for 'clean-core compliant extensions' and SAP-supported extensibility. That creates a concrete opening to discuss whether older operational and document-heavy history should stay out of S/4HANA Public Cloud rather than being recreated around the core.
• Manufacturing system landscape raises legacy access questions beyond ERP The posting names integrations with MES, APS, and PLM alongside CRM and reporting platforms. In that kind of landscape, archived ERP documents and historical transactions often still need to be reachable for production, planning, quality, or reporting use cases even after the ERP core changes.
• Architecture is still being shaped, not just maintained The role will 'Contribute to the evolution of the company's SAP architecture and integration landscape' and work with Digital Transformation teams and external implementation partners. That suggests the target architecture and ownership boundaries are still being defined, including where legacy data access should sit.

Flags

• Evidence comes from a single role repeated across multiple listings.
• The posting is in English, so the exact legacy system situation is not stated.
• No explicit mention of ECC, migration phase, or archive strategy in the evidence.
• Decision-making could involve external implementation partners, which may complicate ownership.
• 'Global Germany GmbH' may indicate local execution within a broader group structure.

Personen

• B. T.Enterprise Data Architect92%
• B. G.Manager Business IT86%

Belege

• SAP Public Cloud Extension & Integration Developer
• SAP Public Cloud Extension & Integration Developer
• SAP Public Cloud Extension & Integration Developer

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies modernizing SAP landscapes typically have to decide early what stays as active data in the target core and what can be retained compliantly outside it. In SAP-led transformation programs, that choice often affects HANA sizing, migration scope, and the later ability to decommission legacy environments. In regulated sectors such as insurance, long-retention financial and document history can make that decision more consequential than teams expect.

Angles

• Finance-module scope raises the archive boundary question early The SAP role is explicitly focused on "die SAP-Systemlandschaft im Umfeld der Finanz-Module". That makes the active-versus-archived split especially relevant because finance-related legacy data and documents often carry long retention obligations and can expand scope if left inside the future core by default.
• Application-management leadership may become the practical owner of legacy-data decisions Because SIGNAL IDUNA is hiring a "Chapter Lead (m/w/d) SAP Application Management", the decision on what remains operational in SAP versus what is served from an archive may sit with SAP application management standards, not only with a transformation PMO.
• Transformation analysis work suggests requirements are still being shaped The "(Senior) Business Analyst (m/w/d) digitale Transformationsprojekte" signal suggests requirements are actively being defined. That is usually the window to pin down which historical insurance and finance information must remain day-to-day accessible versus retained compliantly outside the operational system.

Flags

• The evidence shows SAP transformation activity, but does not explicitly mention S/4HANA.
• The postings are broad and may cover group-level or platform-level responsibilities rather than a single named migration program.
• Decision-making could be centralized at group IT level rather than within the hiring teams shown in the postings.

Personen

• J. L.Abteilungsleiterin / Lead SAP Application Management98%
• J. v. L.Chapter Lead für Application Management97%
• S. L.Vorstand und CIO, SIGNAL IDUNA Gruppe86%
• A. N.Tribe Lead IT-Area SIGNAL IDUNA Gruppe82%
• J. T.CIO Office SIGNAL IDUNA | WHU Graduate74%

Belege

• Chapter Lead (m/w/d) SAP Application Management
• (Senior) Business Analyst (m/w/d) digitale Transformationsprojekte

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a strong transformation signal because the posting is for architecture ownership of an S/4HANA landscape, not just support. In S/4 programs, companies typically have to decide early which legacy data and documents remain in the active core, which move to archive access, and how document retrieval works across connected platforms. Those choices can materially affect HANA sizing, migration scope, and post-migration legacy decommissioning.

Angles

• Retail Accounting document scope in the future core Because the role owns the 'Retail Accounting S/4HANA Systemlandschaft', a concrete angle is which retail accounting and finance-related historical documents must stay directly available in S/4 versus be served from an archive layer.
• Archive access design across adjacent platforms The posting stresses 'Weiterentwicklung ... im Zusammenspiel mit angrenzenden Systemen und Plattformen'. That makes cross-system access to older SAP documents a relevant design topic while interfaces and platform boundaries are being defined.
• Integration-heavy landscape raises legacy access dependency risk Their listed stack includes SAP BTP, SAP CPI/PI, REST, OData, IDoc, BAPI, AWS and GCP. In integration-heavy S/4 landscapes, teams often need a clear target design for how legacy SAP data and old documents are accessed once interfaces are modernized.

Flags

• The evidence comes from a single architecture posting, so the exact program phase and timeline are not stated.
• The employer is Otto Group one.O GmbH, which may act as a group-level IT organization rather than a single operating company.
• The posting confirms an active S/4HANA landscape buildout, but it does not explicitly mention ECC legacy handling, archiving, or decommissioning.

Personen

• P. R.Team Lead Architecture Consulting92%
• S. B.Principal SAP Strategy Management & Tech Consulting90%
• P. K.Division Manager SAP HCM88%

Belege

• SAP Solution Architect S/4HANA (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

A company-wide ERP program with template design, rollout and transition into steady-state is typically the phase where data scope decisions materially affect migration effort, HANA sizing and the future handling of legacy documents. In S/4-style transformations, companies often need to decide which historical ERP data stays active, what is archived compliantly, and how old system access is handled after rollout waves or decommissioning.

Angles

• EOS spans template, rollout and running operations The posting says EOS covers "von der Template-Entwicklung über den Rollout bis hin zum laufenden Betrieb." That is a concrete handoff point where archive scope can otherwise get fixed implicitly by the operating model rather than deliberately during program design.
• Multi-year transformation increases legacy coexistence risk The role owns a "mehrjährigen ERP-Transformationsprogramms (EOS)". In multi-year rollouts, legacy ERP data and old documents often remain needed across waves, which makes an explicit target for archive access and old-system retirement more important.
• Building materials trade means high document volumes around order-to-cash and procurement EOS is described as shaping "die digitale Zukunft des Baustoffhandels". For a building materials trade context, the practical archive discussion usually centers on large volumes of commercial documents such as orders, delivery and invoice records across branches and trading processes.
• Large user base raises impact of what stays in the active ERP footprint The posting mentions hagebau IT supports "täglich rund 18.000 Anwenderinnen" with its industry-specific ERP solution. At that scale, decisions on what historical data remains in the live ERP platform versus archive can have broad cost and usability implications.

Flags

• Evidence comes from a single job posting, so the transformation scope is clear but the underlying ERP landscape is not named explicitly.
• hagebau IT is an internal IT unit; final decisions on archiving or legacy decommissioning could sit at group level or with business stakeholders outside the IT entity.
• The posting does not explicitly mention SAP, S/4HANA, ECC, archiving, or decommissioning, so outreach should anchor on the ERP transformation program rather than assume those specifics.

Personen

• T. M.Head of SAP / Abteilungsleiter SAP Systems99%
• S. G.Program Manager ERP98%
• M. R.Geschäftsführer IT97%
• T. K.Abteilungsleiter IT Consulting84%
• S. G.IT Process & Project Manager77%

Belege

• Program Manager (m/w/d) ERP - Transformation & Rollout

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies moving service-related SAP processes toward S/4HANA typically need to decide early what stays as active operational data versus what can move into compliant archive. That matters especially when service, maintenance and adjacent modules are involved, because historical orders, notifications, documents and financial references can expand scope, sizing and later legacy-system dependency if not separated deliberately.

Angles

• Service and maintenance process history in scope The role focuses on "Analyse, Konzeption und Implementierung von Service- und Instandhaltungsprozessen in SAP CS und SAP S/4HANA Service". That makes the treatment of historical service and maintenance records a concrete discussion point, not an abstract archiving topic.
• Cross-module dependency risk across SD, MM and FI/CO The posting calls out integration with "angrenzender Module wie SD, MM und FI/CO". In S/4 programs, those links often determine which legacy service documents still need day-to-day access versus what can be archived without keeping broad ECC dependencies alive.
• Migration and rollout scope suggests repeatable legacy-data decisions Because the hire is meant to support "Migrations-, Transformations- und Rolloutprojekten im SAP-Service-Umfeld", there may be value in a repeatable rule set for service-related legacy data and documents before each rollout wave locks in scope.

Flags

• The posting is for a consultant role; some responsibilities could support customer-facing SAP projects, not only Ratiodata SE’s own internal landscape.
• The evidence shows S/4HANA Service and migration activity, but does not confirm the broader ERP template, timeline or current ECC footprint.
• Decision-making could sit centrally across SAP/platform leadership rather than within the service-process team alone.

Personen

• S. R.Head of SAP Competence Center | Leading Global SAP S/4HANA Public Cloud Transformation98%
• A. F.Head of IT Transition90%
• M. R.IT Service Delivery Manager | IT Sourcing & Vendor Management | Transition Expert | SAP Banking | Ratiodata SE78%

Belege

• SAP Consultant (m/w/d) CS / S/4HANA Service
• SAP Consultant (m/w/d) CS / S/4HANA Service

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies run implementation-led transformation programs through go-live, they typically have to decide early how legacy data, archived documents, and old-system access will be handled. Those decisions often affect scope, sizing, compliance setup, and whether legacy platforms can later be retired cleanly.

Angles

• Go-live ownership angle The advertised role owns projects "from initial concept through to successful go-live," which makes it a logical entry point to ask where ownership for legacy data, archived documents, and post-go-live old-system access sits in MISUMI Europa’s transformation governance.
• Process-plus-system design angle The posting explicitly asks for someone who can consider "both process and system perspectives." That is a concrete opening to discuss whether document retention, historical order records, delivery documents, and other operational records are being designed as part of the target process model or left to the system workstream.
• Implementation portfolio angle The role spans "digital transformation, software development, and implementation projects," suggesting multiple intersecting workstreams. That creates a specific risk that archive and legacy decisions fall between delivery teams unless one role is assigned to own them.

Flags

• The provided evidence shows a broad digital transformation / implementation hire, but does not explicitly mention SAP, ECC, or S/4HANA in the snippet.
• Only one role is provided as evidence, so buying-center mapping is still a hypothesis.
• The posting may describe a cross-functional transformation role rather than an ERP-specific program owner.
• Group-level or regional IT governance could own archive/legacy decisions rather than the local project team.

Personen

• H. A.Director Digital Transformation98%
• N. K.PMO Lead | Digital Transformation & Operations Excellence74%

Belege

• Project Manager Digital Transformation (m/f/d)
• Project Manager Digital Transformation (m/f/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This hiring signal suggests active work around the future analytics/data platform alongside SAP-related source structures. In S/4-related transformation phases, companies typically have to decide which legacy ERP data remains operationally needed, what should stay in compliant archives, and who owns that split across ERP, BW, and downstream platforms. Those decisions often affect HANA footprint, migration scope, and later legacy system retirement.

Angles

• BW on HANA successor design creates a legacy-data ownership gap The role explicitly supports "dem Nachfolgesystem unserer SAP BW on HANA-Landschaft". That usually creates a concrete handoff question between SAP, BW, and the new data platform: which historical ERP data and documents remain accessible where, and who decides that split.
• ECC/S4 data structure knowledge points to source-system scope decisions The posting states "Datenstrukturen SAP ECC/ S4 sind von Vorteil". That makes legacy ERP data scope relevant not just for ERP migration, but also for what must still feed reporting, analytics, or audit access after platform changes.
• Initial platform setup is the window to avoid carrying unnecessary history forward The hire will "führend beim initialen Setup sowie beim kontinuierlichen Ausbau der unternehmensweiten Databricks-Plattform". Initial setup is a concrete program moment when retention, historical access, and archive boundaries can be assigned before they become embedded in the target architecture.

Flags

• The evidence points clearly to a SAP BW on HANA to Databricks transformation, but does not explicitly confirm an S/4 program already underway.
• The posting is for a holding company; ownership decisions could sit at group level rather than in a local operating unit.
• The signal is data-platform-centric, so the first conversation may need to bridge Data & Analytics and SAP ownership rather than assume one buyer.

Personen

• H. F.Director Big Data Solutions95%
• D. E.SAP MM-Berater / SAP MM ARIBA-Berater89%

Belege

• Data Engineer - Data Warehouse (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

When companies move toward S/4, decisions on legacy SAP data and historical documents often get locked in indirectly by finance/reporting scope and HANA sizing. Teams covering FI/CO/PS and BW/4HANA/SAC typically need clarity on what stays operationally accessible in S/4, what can move into a compliant archive, and how old system access is handled after migration.

Angles

• Finance scope inside the S/4HANA landscape The posting explicitly names "FI/CO/PS innerhalb der S/4HANA Landschaft". That makes historical finance and project-system documents a concrete discussion point: what EDAG users need day-to-day in S/4 versus what can be retained compliantly outside the live system.
• Analytics stack alongside S/4 The role spans "Analytics (BW/4HANA, SAC)" as well as finance. In S/4 programs, that combination often creates a practical boundary question between reporting-ready historical data and documents that do not need to sit in the core transactional footprint.
• Inhouse role suggests target-state ownership Because EDAG is hiring an "SAP Inhouse Consultant*" rather than only external project support, the company likely needs internal ownership for process and landscape decisions inside the S/4HANA environment, including how legacy data access is organized after cutover.

Flags

• Evidence is limited to a single job posting snippet; no explicit migration timeline, source system, or project phase is stated.
• The posting is for EDAG Engineering GmbH specifically; ERP decisions could still be made at a broader group or central IT level.
• The ad signals S/4HANA landscape work, but does not explicitly confirm ECC retirement or a named S/4 transformation program.

Personen

• G. Z.Head of Group IT and Group QM96%
• P. L.System Consultant SAP92%
• H. H.VP of Digital Transformation84%
• B. H.IT-Projektmanager83%
• L. R.SAP Developer75%

Belege

• SAP Inhouse Consultant* Analytics oder Finance (S/4HANA)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This hiring signal suggests active change across Getinge’s SAP landscape rather than steady-state support. In S/4-related transformation programs, companies typically have to decide early which legacy data stays in the active HANA footprint, what moves into compliant archives, and how old documents remain accessible after cutover. Those decisions often intersect with test scope, template governance, and landscape simplification, especially in global programs.

Angles

• Global SAP program governance creates a natural decision point for archive scope The role explicitly supports 'the Governance of our global SAP program' including template documentation and project controlling. That is a concrete point where rules for legacy data access, archive scope, and old-document handling can be standardized instead of left to each project wave.
• Transition to SAP Cloud ALM can expose unresolved legacy-document ownership Because the posting names 'transition from to SAP Cloud ALM', there is likely ongoing clarification of what remains in the active application landscape versus what should stay accessible outside it. That can matter for which historical objects must still be reachable during testing and operations.
• Test management and test automation increase the cost of carrying too much historical scope The role is responsible for SAP test management, coordinates test managers within SAP projects, and supports implementation of an SAP testing automation solution. In transformation programs, unresolved legacy scope can expand test data, interfaces, and regression effort across projects.
• IDM replacement and landscape coordination suggest broader cleanup beyond one SAP module The role coordinates 'the integration of SAP IDM replacement, Entra ID, into the Getinge global IT applictions landscape' across on-premise and cloud applications. When identity, governance, and application landscape changes happen together, legacy-system access and historical document access often need a clearer target model.

Flags

• The evidence comes from a single specialist posting, so the exact stage of any S/4 program is not stated.
• The posting references a 'global SAP program', which may mean decisions are made above the German entity level.
• No explicit mention of S/4HANA appears in the provided evidence; the signal is broader SAP transformation and governance work.
• The legal entity is 'Getinge Holding B.V. & Co. KG', so some initiatives could be coordinated centrally for the wider group rather than locally.

Personen

• V. D.Vice President Group IT Applications97%
• O. P.Director Global IT Applications Operations95%
• H. M.Director IT Sales & Service Units Enterprise Application Europe94%

Belege

• Expert IT SAP Authorization and Test Management

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

The strongest signal is direct hiring into finance with responsibility during an S/4HANA Public Cloud transition. In S/4 programs, companies typically have to decide early what remains in the new core versus what should stay in archive or a legacy access layer, because those choices affect data scope, migration effort, and later legacy system retirement. Public Cloud programs can make that separation especially important because teams often aim for a cleaner target footprint and tighter process standardization.

Angles

• Finance-led S/4 Public Cloud change The posting is for a Finanzbuchhalter, and the role includes active participation in the S/4HANA Public Cloud transition. That suggests accounting is directly involved, making retention and day-to-day access to historical finance documents a practical workstream, not just an IT topic.
• Public Cloud target increases pressure to define legacy scope Because the posting names SAP S/4HANA Public Cloud explicitly, a relevant discussion is which historical finance data and documents need to stay operationally accessible versus what can be archived outside the new core.

Flags

• Evidence is from a single job posting only.
• The signal is finance-specific; broader enterprise scope should be validated.
• No timeline, incumbent SAP landscape, or migration phase beyond 'Umstellung' is stated in the evidence.
• Decision-making may sit outside the hiring team, for example with central IT or a group-level SAP program.

Personen

• S. F.IT Manager93%
• C. J.IT Operations Manager88%

Belege

• Finanzbuchhalter (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

A stated future SAP S/4HANA introduction is a strong timing signal. In S/4 programs, companies typically have to decide early how much historical ERP data and document volume should move into HANA versus stay accessible in an archive or legacy layer, because that choice affects sizing, migration scope, compliance handling, and later system decommissioning.

Angles

• Finance-led S/4 trigger The signal comes from the Head of Accounting role, not a generic IT posting. That suggests the accounting organization is directly involved in process redesign ahead of the future SAP S/4HANA introduction.
• Accounting process digitization before S/4 The posting combines "Strategische Weiterentwicklung und Digitalisierung der Buchhaltungsprozesse" with the planned S/4HANA introduction. That creates a concrete angle around which accounting documents and historical finance records need to remain day-to-day accessible without overloading the new core.
• Packaging manufacturer document footprint As a paper and packaging manufacturer, Mondi Schwarzenberg is likely to have substantial operational and commercial document retention needs alongside finance records; in S/4 programs, that often sharpens the boundary between transactional data needed in the new system and legacy documents that should stay audit-accessible elsewhere.

Flags

• Only one posting is provided; the signal is strong but narrow.
• The evidence points specifically to accounting-process transformation, not to the full technical scope of the S/4 program.
• Knowledge of SAP S/4HANA is described as desirable in the role, which may indicate early-stage capability building rather than a fully staffed program.
• Decision-making could sit above the Schwarzenberg entity if SAP strategy is coordinated at a broader Mondi group level.

Personen

• J. K.Head of Accounting at Mondi AG92%
• K. M.Leiter IT bei Mondi Halle GmbH88%

Belege

• Head of Accounting / Leiter Rechnungswesen (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies introducing a new ERP system typically have to decide early how much historical ERP data and legacy documents need to remain available in daily operations, versus what can move into a compliant archive. That decision often affects project scope, cutover complexity, user support after go-live, and the long-term cost of keeping legacy environments or large data volumes online.

Angles

• Project-to-operations handoff creates a clear ownership moment for legacy data The posting explicitly combines 'Einführung eines neuen ERP-Systems' with 'Überführung des ERP-Projekts in den Regelbetrieb'. That handoff is a practical point to ask who owns the decision on old ERP data and historical documents once the project leaves implementation mode.
• Internal user support suggests daily access to old documents may become an operational issue RENZ wants this role to provide 'Helpdesk-Support für die internen ERP-Anwender'. In ERP transitions, user tickets often cluster around access to older orders, invoices, delivery records, and other historical documents after go-live.
• Preferred proALPHA experience points to an ERP-specific retention and access design question The posting says 'idealerweise mit proALPHA'. If proALPHA is part of the target or current landscape, the discussion can be framed around how historical data and documents should stay accessible without overloading the new operational setup.

Flags

• The evidence shows an ERP introduction, but does not explicitly mention SAP or S/4HANA.
• The posting references ERP experience 'idealerweise mit proALPHA', so the active program may be non-SAP.
• The signal comes from a junior role; budget ownership and architectural decisions may sit elsewhere.
• Only the Kirchberg an der Murr site is referenced; decisions could still be made centrally beyond this location.

Personen

• B. R.Geschäftsführer61%

Belege

• Junior ERP-Consultant (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This signal suggests an active transformation phase around data foundations. In S/4 and broader ERP/data-platform programs, companies typically have to decide early which legacy data stays active on the new platform, what can move into compliant archive access, and how old systems or old data structures will be handled after migration. Those decisions can materially affect platform sizing, migration effort, and the path to later legacy decommissioning.

Angles

• Turning point after completed database migrations The posting says they are "nach erfolgreichen Migrationen bestehender Datenbanken" and now moving into the next phase. That is a concrete moment to discuss whether older data remains on the future platform or is separated into archive access.
• Central components and processes are being redesigned They state they are redesigning "zentrale Komponenten und Prozesse". That makes governance for legacy documents and historical data a design choice now, not only an operations issue later.
• Dedicated Enablement & Migration team The role sits in "DIA Enablement & Migration". A named migration team gives a clear entry point to ask who owns the split between active data on the new platform and retained historical data outside it.
• Insurance document retention context As an insurer, historical policy, claims, and correspondence records often have long retention and access needs. In transformation programs, that can make the boundary between operational data and compliant archive especially important.

Flags

• Evidence points to a data platform / migration initiative, not explicitly to an SAP or S/4HANA program.
• The posting is for Allianz Kunde und Markt GmbH; transformation and archive decisions could sit at a broader Allianz group or shared IT level.
• Only one posting is provided, so scope, timeline, and system landscape are not confirmed.

Personen

• M. W.Tribe Managerin - Tribe Data Insights & Analytics (DIA)98%
• S. G.Referatsleiterin Enterprise Architecture & Software Excellence91%
• M. U.Lead Architect88%
• A. H.Department Director60%

Belege

• Werkstudent im Projektmanagement für Data Insights & Analytics Enablement & Migration (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies in a visible transformation phase often lock in scope, sizing, and governance decisions before the legacy-data approach is fully clarified. In S/4-related programs, that can affect HANA footprint, migration effort, compliant retention, and how cleanly old systems can later be decommissioned.

Angles

• Transformation office with direct management visibility The posting places the Digital Transformation Office in Strategy and says it reports directly to management. That makes legacy-data scope a governance topic, not just an IT clean-up task, which can matter if archive and decommissioning decisions need executive alignment.
• Cross-functional transformation communication suggests broad program coordination The role supports communication formats for the digital transformation. Where a program needs active internal communication, decisions on what remains in the future core system versus what moves to archive often cut across business, IT, and compliance stakeholders.
• Commercial vehicle transformation context The posting explicitly references transformation in the commercial vehicle industry. In such programs, long-lived operational and service-related information can complicate what must stay accessible versus what can be removed from the active ERP footprint.

Flags

• Evidence is from an internship posting, so seniority and budget ownership are not proven.
• The posting signals digital transformation broadly; it does not explicitly mention SAP, ERP, ECC, or S/4HANA.
• The signal may reflect a strategy/communications office rather than the core ERP program team.
• Group-level decisions could sit beyond Daimler Buses GmbH.

Personen

• M. D.Head of Digital Transformation Office98%
• L. K.Head of SAP Technologies97%
• J. P.IT Lead Architect95%
• M. S.Head Of Digital Transformation Operations87%

Belege

• Praktikum im Digital Transformation Office bei Daimler Busses ab September 2026

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

An active RISE S/4HANA greenfield program is a strong timing signal because companies in this phase typically have to decide, often per workstream, which legacy ERP data must remain operational in S/4 and which historical documents can stay outside the new core. In sales-focused streams, that usually affects customer, order and document history as well as how legacy access is handled after go-live.

Angles

• Sales workstream inside the live RISE greenfield The hiring signal is not generic SAP hiring: the role is tied to an "aktuell laufenden RISE S/4HANA Private Edition-Greenfield Projekt" and specifically to sales topics. That makes the legacy-data question concrete for the sales workstream rather than a broad future discussion.
• SD + C4C suggests customer and sales-history decisions across systems Because the role covers "Sales (SD+C4C)", a relevant discussion point is which historical customer, quote, order and related sales documents users still need day to day after the greenfield cutover, versus what can remain in an archive-access layer.
• Greenfield raises the 'what moves vs. what stays accessible' decision With a greenfield approach, teams usually avoid carrying everything forward. For Wanzl, the evidence points to sales-specific design work, so an angle is whether the boundary for legacy sales data and old sales documents is already owned within that workstream.

Flags

• The evidence is from a sales-focused SAP role; no posting explicitly mentions archiving, legacy decommissioning or enterprise-wide data strategy.
• The transformation signal is tied to Sales (SD+C4C), so broader ERP decisions may sit with a central program team outside this role.
• Only one provided snippet explicitly references the RISE S/4HANA project.

Personen

• D. M.SVP Global IT / CIO99%
• V. W.SAP Application Manager Logistics95%
• C. S.Senior Director Digital, Access & Roll-Outs82%

Belege

• SAP Application Manager (m/w/d) Sales (SD+C4C)
• SAP Application Manager (m/w/d) Sales (SD+C4C)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies running broad transformation programs often end up touching application landscapes, data ownership, and legacy information flows even when the initial mandate is not framed as ERP. In S/4 programs specifically, the legacy-data decision is usually expensive if left until after sizing and migration design, because cold ECC data and historical documents can inflate the HANA footprint and prolong coexistence. This is worth testing here, but only as a hypothesis because the evidence currently points to KI transformation, not a confirmed SAP migration.

Angles

• Transformation governance entry point The concrete hiring signal is a "Programmleitung KI Transformation (m/w/d)". If this program is coordinating cross-functional system and data changes, it could be the right place to ask who owns legacy-data and document decisions across business applications.
• Early-program timing conversation The posting says "zum nächstmöglichen Zeitpunkt" and "unbefristet", which suggests an active program build-out rather than a short advisory mandate. That makes timing of legacy-data decisions a relevant conversation now, if ERP landscape changes are in scope elsewhere.

Flags

• No direct evidence of SAP, ERP, ECC, or S/4HANA in the provided material.
• The hiring signal is for KI transformation, so ArchivoX relevance is currently a hypothesis rather than a confirmed fit.
• The snippet includes "idealerweise im Gesundheitswesen", which may indicate a templated or syndicated posting; verify context before outreach.
• Use a light qualification approach first, otherwise the outreach may feel mismatched if no ERP program exists.

Personen

• R. W.Director IT bei meinestadt.de GmbH94%
• B. M.Head of IT Operations bei meinestadt.de GmbH88%

Belege

• Programmleitung KI Transformation (m/w/d)
• Programmleitung KI Transformation (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

An ERP introduction with responsibility for how ERP interacts with DMS and adjacent applications is a strong timing signal. In programs like this, companies typically have to decide what operational data must move into the new ERP core, what can stay in compliant archives, and how legacy documents remain accessible without inflating the future platform footprint or keeping old environments alive longer than necessary.

Angles

• ERP introduction touches DMS from day one The posting explicitly says the role is responsible for the interplay of "ERP, CRM, DMS, DATEV und weiteren Fachanwendungen." That makes document access, retention, and handoff between ERP and DMS a concrete design topic inside the ERP introduction, not a later clean-up task.
• Cross-application scope raises legacy boundary decisions Because the role covers both strategic and operational management of the ERP system plus other IT specialist applications and platforms, the program likely needs a clear boundary between records that belong in the future ERP versus documents and historical data that can remain outside the transactional core.
• Real-estate/airport-management context implies document-heavy back-office flows Given the classified context of real estate / airport management and the named system landscape including DMS and DATEV, a relevant angle is where historical finance, contract, and administrative documents should remain accessible if the ERP landscape changes.

Flags

• The evidence shows an ERP introduction, but it does not name S/4HANA or SAP specifically.
• The role may combine project and operational system management, so decision-making could sit across multiple teams.
• The posting references Microsoft Business Central and Microsoft Dynamics as welcome knowledge; avoid SAP-assumptive outreach language.
• Industry classification was provided externally; the posting itself does not state operational document types or regulatory requirements.

Personen

• J. F.Project Manager ERP Impl90%
• B. W.Projektleitungen im ERP Umfeld70%
• P. K.Projektleiter Baumanagement bei Berlin TXL Management GmbH64%

Belege

• Projektmanager*in | Systemmanager*in ERP Einführung (w/m/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

This is a strong transformation signal because the role combines current-state ECC FI process knowledge with target-state S/4HANA template build. In S/4 programs, decisions around what finance data, documents, and interfaces must remain operational versus what can move to compliant archive access often get locked in implicitly during template design, testing, and sizing. Companies migrating to S/4 typically benefit from clarifying legacy data scope before the HANA footprint and post-go-live legacy landscape are cemented.

Angles

• FI template build creates a concrete decision point for finance legacy scope The posting explicitly mentions the build of a new S/4HANA template for SAP FI. That is a specific point where teams usually define which historical FI data and financial documents must stay operational in S/4 versus remain accessible via archive or legacy access.
• Period close and bank accounting make document retention and access operational, not theoretical The role supports optimization of 'Bankbuchhaltung' and 'Periodenabschlussprozesse'. Those finance processes depend on reliable access to older accounting documents and audit-relevant records, which makes archive design and retrieval workflows a practical topic during transformation.
• SAP and non-SAP interfaces raise the risk of carrying legacy complexity into the target template The posting says the role supports interfaces between SAP and non-SAP systems as well as adjacent SAP modules. In FI template programs, interface scope can become harder if historical document access and legacy dependencies are not separated cleanly from the future-state core.
• IFRS focus suggests sensitivity around governed historical finance records The title names 'Schwerpunkt IFRS'. For finance-led SAP transformations, historical accounting records, reconciliations, and supporting documents often need governed long-term access even when they should not all be loaded into the new operational environment.

Flags

• Evidence comes from a single job posting, so program scope beyond FI should not be assumed.
• The posting is for an inhouse FI role; broader group-level ERP or archiving decisions could sit with a central IT or transformation function.
• The evidence confirms ECC FI experience and S/4HANA template build, but does not state migration timeline, rollout scope, or archiving approach.

Personen

• B. M.Head Of SAP Finance98%
• W. M.SAP Applikation Manager78%

Belege

• SAP Consultant FI mit Schwerpunkt IFRS (w/m/d) - inhouse

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich

Why now

Companies in an ERP transformation typically make implicit decisions early about what stays in the active ERP core versus what is retained in an archive or legacy-access layer. That matters because migration sizing, HANA footprint, compliance retention, and later legacy decommissioning are all affected by how historical data and documents are separated before the target design is locked.

Angles

• ERP transformation is being led as a business program, not just an IT upgrade The role sought is a "Senior ERP-Transformationsmanager" and the posting frames the work as "Planung, Steuerung & Umsetzung einer ERP-Transformation". That suggests a transformation office or senior program structure where the active-data vs. archive boundary may need an explicit owner early.
• Growth and efficiency framing creates pressure to keep the future ERP core lean The posting ties the ERP transformation to "Förderung von Wachstum und Effizienz". In programs run on that mandate, a useful discussion is whether older operational documents and legacy records really belong in the future ERP scope or should be accessed separately.
• Digital business model work may complicate historical document access requirements The same posting combines ERP transformation with "weiterer innovativer digitaler Geschäftsmodelle". If new digital processes depend on reference to historical transaction or document history, the team may need a deliberate approach for what remains operationally accessible without carrying all legacy volume into the new core.

Flags

• The evidence shows an ERP transformation, but it does not explicitly mention SAP or S/4HANA.
• The posting may indicate a company-level transformation role, but final decisions on data/archiving could still sit at group level.
• Only one hiring signal is available, so process scope, timeline, and target architecture are not confirmed from the evidence.

Personen

• C. W.CIO Interzero98%
• U. B.Expert EPR Systems and Solutions72%

Belege

• Senior ERP-Transformationsmanager (m/w/d)

Mail-Entwurf Template + Evidence-Slots · Freigabe erforderlich