Transition sap erp hcm auf sap hcm for s/4hana (h4s4)

The contract timeline includes the following:

• Contract start date: The project is proposed to begin in January 2027 with the preliminary projects. The execution period (Ausführungsfrist) is stated as February 1, 2027.
• Contract end date: The execution period (Ausführungsfrist) is stated as December 31, 2027. The target for the Go-Live of the H4S4 productive system is October 2027, followed by a Hypercare phase.
• Total duration: The execution period spans from February 1, 2027, to December 31, 2027.
• Key milestones/phases:
• Vorprojekte (Preliminary Projects): These include "Ausschreibung & Lizenzen", "Business Partner Konzeption", "Code Anpassungen", "BTP neo Ablösung", "Fiori ESS/MSS Umstellung", "Testkataloge (Vorb - Abgleich)", and "Sandbox-Erstellung".
• Pilotierung & Migration (Piloting & Migration): This phase covers "Pilotmigration", "Entwicklung (DEV)", "Qualität (QAS)", and "Produktiv (PRD)-Cutover".
• Go-Live: The Go-Live of the H4S4 productive system is targeted for October 2027. The productive use of the target architecture must occur by December 31, 2027.
• Hypercare: A three-month Hypercare phase is planned for system stabilization after the Go-Live.

The core scope of work for this tender primarily involves the transition of SAP ERP HCM to SAP HCM for S/4HANA (H4S4) and the replacement of SAP BTP Neo with SAP BTP Cloud Foundry.

The Statement of Work summary includes the following key phases and deliverables:

• Project Start and Initialization: Setting up the project team, defining methodology, creating project structure and milestone plans, communication and resource plans, and conducting a project kickoff. Key deliverables include a Project Structure and Milestone Plan, Communication Plan, Resource Plan, and a Project Handbook.
• Conception: Involves project management, preparation of preliminary projects (such as technical conversion to Business Partner, code adjustments, replacement of BTP Neo with BTP Cloud Foundry, and Fiori ESS/MSS conversion), developing an upgrade concept and system architecture for H4S4, providing SAP H4S4 licenses, conducting workshops for functional and technical specifications, documenting results, defining roles and authorizations, developing a test concept, coordinating with third-party service providers, and creating a Cut-over Scenario concept. Deliverables include workshop presentations, functional and technical specifications, the upgrade concept, test concept, and cut-over scenario concept.
• Preliminary Projects (Vorprojekte): Execution of preliminary projects, including technical conversion to Business Partner, code adjustments, and migration from BTP Neo to BTP Cloud Foundry, along with sandbox provisioning. Deliverables are the results of these preliminary projects and written phase acceptance.
• Pilot Upgrade: Execution of a pilot upgrade, handover and test release, test planning and management, creation of test cases and data, and performing various tests (unit, integration, performance, load). Deliverables include documentation of test results, a decision document for release, and written acceptance.
• Upgrade Phase: Management of upgrades for development, quality assurance, and production systems, quality assurance of these upgrades, user and authorization maintenance for the production environment, planning and execution of end-user training, setup of the production environment, and "Smoketest" execution. This phase requires acceptance from data protection, IT security, auditors, and the MDC. Deliverables include the upgrade and cut-over procedure, Smoketest results documentation, and written acceptance with release for operation.
• Go-Live, Operation including Hypercare: Commissioning the H4S4 system, handover to MDC, conducting HyperCare activities (user support, system stabilization and optimization), advising on process and organizational adjustments, and transitioning to the operational process. A three-month Hypercare phase is planned post-Go-Live, with the contractor providing support, response times, error classification, and regular status reports. Deliverables include cut-over documentation, necessary input for other MDC documentation, and acceptance of the overall system.

The project aims for a Go-Live of the H4S4 production system by October 2027, with the premise that existing functional processes and master data structures will largely be retained and transferred unchanged.