SAP Integration Lead

SAP Integration Lead

Initial 3 month contract

Outside IR35 - market rate

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

The Integration Lead gives SAP Futures a single owner for integration. Today nobody has that job: DMU lost its dedicated integration expertise in the restructure, and no one maintains the SAP interface inventory.

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. NTT DATA is delivering the Success Factors build, including 39 People Services interfaces (21 standard, 18 custom).

The role defines the To-Be integration landscape, works out what can be switched off after go-live, builds one integration catalogue across Finance, Student and People Services, and turns that into a full SAP Futures integration strategy aligned to the DMU Integration Strategy.

The first four pieces of work run in this order. Each builds on the one before.

• Create the To-Be integration architecture for Success Factors, covering Employee Central, Payroll (ECP), Recruitment, Onboarding, Learning, Performance & Goals and People Analytics.
• Get to know the current People Services integrations in depth, using the People Services Integration Inventory as the baseline.
• Confirm the integration pattern for each interface: SAP Integration Suite (CPI), point-to-point or Integration Center. Agree where each one should sit.
• Work with NTT DATA to check their designs against the To-Be view. Track the custom interfaces and how the contingency allowance is used.
• Drive open items to closure with People Services, Finance and D&T. These include pension and benefits automation, Worktribe, SWP/timetabling, Key Travel, HESA staff returns and the Open Text IDM identity interfaces DMU will deliver.

• Compare the To-Be landscape with today’s ECC, PO and Gateway interfaces. Identify what can be switched off after Success Factors go-live.
• Produce a decommissioning plan with dependencies, owners, retirement dates and checks, including for manual file transfers and reports that new integrations replace.
• Flag interfaces that must stay until the S/4
  
  HANA conversion, such as Agent Portal and the remaining PO interfaces.

• Build and own one integration catalogue across Finance, Student and People Services. Use the existing SAP interface inventory and the ECC/PO/Gateway extract as the start point.
• Record for each interface: source, target, middleware, direction, data, frequency, owner, standard or custom, and status (current, To-Be, retire).
• Set up a process to keep the catalogue current, so ownership does not lapse again.

• Build the list of Student interfaces with the Student Academic product team and Registry, including SLcM and its links to HR data.
• Using the catalogue, write the SAP Futures integration strategy: principles, target patterns, middleware roadmap from PO to Integration Suite, governance, ownership and support model.
• Align the strategy with the DMU Integration Strategy, which Mark Packham’s team aims to baseline by the end of 2026, and contribute to its review cycles.

• Proven SAP integration lead or architect experience on a major transformation programme.
• Hands-on knowledge of SAP Success Factors integration, especially Employee Central to ECC/ECP, using Integration Center and standard packaged integrations.
• Strong SAP Integration Suite (CPI) and SAP PO/PI experience, including migration from PO to Integration Suite.
• Track…