SAP Environments Manager

SAP Environments Manager

Initial 3 month contract

Outside IR35

Hybrid - 3 days per week working from home, 2 days per week in the office

The Environments Manager gives SAP Futures a single owner for its non-production and production landscape. Today environment decisions are spread across the programme, Basis, NTT DATA and BAU teams, with no agreed strategy, booking process or refresh plan.

The programme is moving DMU from ECC and SAP Process Orchestration (PO) to Success Factors, Concur and S/4

HANA, with SAP Integration Suite on BTP as the target middleware and SAP IAS/IPS for identity. Programme build, testing, training and BAU support all need the same environments at the same time.

The role defines the SAP Futures Environment Strategy & Roadmap, runs the environments day to day, and makes sure every test phase, training event and release has a ready, connected and correctly configured environment when it needs one.

• Build one current-state map of every SAP Futures environment: ECC, PO, Gateway, Success Factors instances, Concur, BTP and Integration Suite tenants, IAS/IPS and Content Server.
• Record for each environment: purpose, system and client, version, owner, users, connected systems, data currency and current usage (programme, BAU or both).
• Identify gaps, conflicts and single points of failure, including environments shared between programme and BAU.

• Define the target environment landscape across DEV, SIT, UAT, training, regression and production for each product.
• Set out how environments connect: integration and connectivity paths, identity and authentication (IAS/IPS, SSO), and which non-production systems talk to each other.
• Define ownership, BAU versus programme usage, provisioning lead times and the Concur Phase 2 environment needs.
• Plan the transition-state landscape for the future S/4
  
  HANA conversion, including which ECC and PO environments must stay until then.
• Take the strategy through the Technical Review Board for sign-off.

• Set up an environment booking and scheduling process so test phases, training and BAU fixes do not clash.
• Define the data refresh and test data approach for each environment, covering refresh frequency, anonymisation and GDPR requirements.
• Agree transport and release management rules across ECC, Success Factors, Concur and Integration Suite, aligned with CAB.
• Define environment entry and exit criteria for each test phase.

• Produce and maintain an environment plan aligned with the programme plan, showing when each environment is needed, by whom, and in what state.
• Coordinate builds, refreshes and configuration changes with Basis, NTT DATA and SAP so environments are ready before each test phase and training event.
• Run environment readiness checks before SIT, UAT, regression and training, and track defects caused by environment issues.

• Act as environments lead at Technical Review Board, CAB and design authority sessions.
• Keep environment risks, issues and dependencies current in the programme RAID log, and report progress weekly to the SAP Technical Programme Manager.
• Maintain the environment register, booking calendar and refresh schedule.
• Manage environment access requests and periodic access reviews with Security and Basis.

• Proven SAP environment management experience on a major transformation programme.
• Hands-on knowledge of SAP landscapes across ECC and cloud products, including Success Factors and BTP.
• Track record of writing environment strategies and roadmaps covering DEV, SIT, UAT, training, regression and production.
• Experience running environment booking, data refresh and test data processes, including data anonymisation.
• Strong understanding of SAP transport and release management, and of change control through CAB.
• Confident working with Basis teams, a systems integrator (SI) and SAP, and holding them to agreed timelines.
• Clear communicator with technical teams, testers, trainers and business stakeholders.

• Higher education experience.
• SAP Concur and S/4
  
  HANA environment planning, including ECC to S/4
  
  HANA conversion landscapes.
• SAP Integration Suite and PO environments and connectivity.
• Identity environments (SAP IAS/IPS or similar) and SSO across non-production systems.
• Release and transport tools such as SAP Cloud ALM, Solution…