SAP Futures Environments Manager

Ubique Systems UK Limited; East Midlands; On-site; GBP 65,000 - 90,000; Full time

Job summary

Ubique Systems UK Limited is seeking an Environments Manager to govern SAP Futures environments, define ownership, and oversee the transition-state landscape for future S/4HANA conversion. You will coordinate DEV/SIT/UAT/testing environments, manage data refresh, and lead CAB discussions.

The role requires proven SAP environment management experience, strong stakeholder communication, and collaboration with Basis teams, SI partners, and SAP across non-production systems.

Qualifications

• Proven SAP environment management on a major transformation programme.
• Hands-on knowledge of SAP landscapes across ECC and cloud products including SuccessFactors and BTP.
• Track record of writing environment strategies and roadmaps for DEV, SIT, UAT, training, regression and production.
• Experience running environment booking, data refresh and test data processes, including anonymisation.

Responsibilities

• Act as environments lead at Technical Review Board, CAB and design authority sessions.
• Maintain the environment register, booking calendar and refresh schedule, reporting progress.
• Manage environment access requests and periodic access reviews with Security and Basis.
• Ensure readiness of environments in line with programme milestones and testing events.

Skills

SAP environments

SAP landscape knowledge

Stakeholder communication

CAB / change control

Transport & release management

Data refresh & test data

Basis collaboration

Systems integrator coordination

Technical coordination

Education

Higher education

Tools

SAP Cloud ALM

Solution Manager ChaRM

SAP IAS/IPS

SAP Concur

SAP Integration Suite

Job description

Requirements

• Environment baseline and landscape map

• ? Build one current-state map of every SAP Futures environment: ECC, PO, Gateway, SuccessFactors 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.

SAP Futures Environment Strategy & Roadmap

• ? 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/4HANA conversion, including which ECC and PO environments must stay until then.
• ? Take the strategy through the Technical Review Board for sign-off.

Environment operating model

• ? 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, SuccessFactors, Concur and Integration Suite, aligned with CAB.
• ? Define environment entry and exit criteria for each test phase.

Ongoing responsibilities

• ? 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.

Key deliverables

• ? A current-state environment register covering every SAP Futures system, with an owner and purpose for each environment.
• ? A signed-off SAP Futures Environment Strategy & Roadmap, including the S/4HANA transition-state landscape.
• ? An agreed environment operating model: booking and scheduling, data refresh and test data, transport and release management, and entry and exit criteria.
• ? An environment plan aligned with the programme plan, with readiness confirmed before each test phase and training event.
• ? A handover pack so D&T can run the environments in BAU after the programme.

Role boundaries

The Environments Manager owns the environment strategy, plan and operating model. These stay elsewhere:

• ? System builds, client copies and Basis configuration - SAP Basis team. This role sets requirements and schedules the work.
• ? SuccessFactors build and tenant configuration under the SoW - NTT DATA. This role assures environment readiness rather than building it.
• ? Integration design and the integration catalogue - SAP Futures Integration Lead. This role makes sure environments are connected to match that design.
• ? Identity, SSO and Concur IC add-on decisions - SAP Technical Programme Manager.
• ? Test strategy, test scripts and test data content - programme test lead. This role provides the environments and refresh approach that testing depends on.

Essential experience

• ? Proven SAP environment management experience on a major transformation programme.
• ? Hands-on knowledge of SAP landscapes across ECC and cloud products, including SuccessFactors 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.

Desirable experience

• ? Higher education experience.
• ? SAP Concur and S/4HANA environment planning, including ECC to S/4HANA 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 Manager ChaRM or similar.
• ? GDPR-compliant test data management in non-production systems.