> Markdown version of [/jobs/ext/4000128-sap-futures-integration-lead](https://www.wearedevelopers.com/jobs/ext/4000128-sap-futures-integration-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # SAP Futures Integration Lead - **Company:** Ubique Systems UK Limited - **Location:** Leicester, UK - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Microsoft Access, Application Integration Architecture, Enterprise Architecture Framework, Middleware, HR Analytics, SAP ERP, SuccessFactors, SAP Concur, SAP (Applications), SAP Human Resource Management Software, SAP Materials Management, SAP Process Orchestration, OpenText, SAP S/4HANA, Integration Frameworks - **Published:** October 29, 2026 - **Apply:** https://www.careerboard.com/gb/en/find-jobs-in-United-Kingdom/-5294A3F9D9719038A4/ ## About the Role ? Proven SAP integration lead or architect experience on a major transformation programme. ? Hands-on knowledge of SAP SuccessFactors 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 record of producing To-Be integration architectures and decommissioning plans. ? Experience building and maintaining integration catalogues across several business areas. ? Ability to write an integration strategy covering principles, patterns, governance and support model. ? Confident working with a systems integrator (SI), reviewing designs and holding them to scope. ? Clear communicator with HR, Finance, Student and D&T stakeholders. Desirable experience ? Higher education experience, including SAP SLcM or student system integrations. ? HESA data returns and regulatory reporting. ? Identity integrations (SAP IAS/IPS, OpenText IDM or similar). ? SAP Concur and S/4HANA integration. ? Integration with pension, benefits and payroll third parties. ? Knowledge of enterprise architecture frameworks or design authorities. ## Description ? Create the To-Be integration architecture for SuccessFactors, 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 OpenText IDM identity interfaces DMU will deliver. 2. Decommissioning after go-live ? Compare the To-Be landscape with today's ECC, PO and Gateway interfaces. Identify what can be switched off after SuccessFactors 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/4HANA conversion, such as Agent Portal and the remaining PO interfaces. 3. Integration catalogue for Finance, Student and People Services ? 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. 4. Student interfaces, then the full integration strategy ? 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. Ongoing responsibilities ? Act as integration lead at Technical Review Board and design authority sessions. ? Keep integration risks, issues and dependencies current in the programme RAID log, and report progress weekly to the SAP Technical Programme Manager. ? Work with Basis on Integration Suite environments, access and connectivity. Key deliverables ? A signed-off SuccessFactors To-Be integration architecture, with the pattern and owner confirmed for every People Services interface. ? A decommissioning plan for interfaces and manual processes that can be retired after SuccessFactors go-live, plus the list of those that must stay until S/4HANA. ? One maintained integration catalogue covering Finance, Student and People Services, with an agreed process for keeping it current. ? A complete list of Student interfaces. ? A SAP Futures integration strategy aligned to the DMU Integration Strategy, including the PO to Integration Suite roadmap and the integration governance and support model. Role boundaries The Integration Lead owns integration design and the catalogue. These stay elsewhere: ? Build and delivery of SuccessFactors interfaces - NTT DATA under the Statement of Work. This role assures their work rather than building it. ? Concur identity and ICS add-on decisions - SAP Technical Programme Manager. ? Integration Suite tenants, access and Basis configuration - SAP Basis team. This role sets requirements. ? The enterprise DMU Integration Strategy - Mark Packham's team. This role contributes the SAP Futures view.