SAP Integration Architect / SME S/4HANA Greenfield Programme — Life Sciences (Homecare Division)
The Role
Our client, a leading life sciences organisation, is delivering a global S/4HANA greenfield programme. We are looking for a hands-on, broadly experienced Integration Architect / SME who can move comfortably across S/4HANA, SAP Ariba, OpenText VIM, Salesforce (SFDC), and a range of bespoke applications — many of which directly support patients receiving homecare therapy.
Key Responsibilities
Own the end-to-end integration architecture for the greenfield programme — sync, async, batch, events, and APIs.
Design integration between S/4HANA and Ariba (sourcing, procurement, contracts, suppliers, invoicing).
Design integration between S/4HANA and OpenText VIM (invoice capture, workflow, posting).
Architect S/4HANA ? Salesforce (SFDC) flows across customer, patient, order, service, and pricing.
Lead integration design for custom-built applications in the patient-care ecosystem (portals, scheduling, device telemetry, clinical data).
Govern use of SAP Integration Suite / CPI / BTP and any existing middleware (MuleSoft, Boomi, Azure Integration Services).
Establish standards, patterns, error-handling, monitoring, and API/event strategy.
Partner with the OTC Architect and Master Data SME to keep the target architecture coherent.
Essential Experience
Multiple full-lifecycle integration architecture engagements, including at least one S/4HANA greenfield.
Deep experience integrating S/4HANA with Ariba and OpenText VIM.
Strong experience with Salesforce ? SAP integration (accounts, orders, pricing, service, master data).
Comfortable designing integration with bespoke applications via modern APIs, events, and messaging — not just SAP-to-SAP IDocs.
Strong command of SAP Integration Suite, CPI, BTP eventing, API Management.
Demonstrable life sciences experience with appreciation of regulatory constraints (GxP, validated systems, audit trails).
Desirable
Non-SAP middleware (MuleSoft, Boomi, Azure, Kafka); HL7/FHIR; device telemetry or connected-health platforms; identity/consent patterns for patient-facing integrations; developer background.
