We are architects, developers and declutterers.
We plan, we build, we clean up.
SAP integration for more than 20 years
We build new interfaces, extend the ones you already run, and know every generation of the SAP platform — from XI 3.0 to the Integration Suite.
We plan and run workshops with the business, IT, and external partners, then turn the outcome into functional specifications and mapping requirements that developers can actually work from.
Designing integration scenarios for hybrid landscapes of cloud and on-premise systems: synchronous and asynchronous patterns, event-based approaches, API strategies. Rolling out the SAP Integration Suite, including an honest account of what the platform can do and what it can't.
Advice on selecting prebuilt SAP integration packages, so you use standard where standard is enough and only build where it pays off.
A full inventory of your PI/PO landscape, an assessment of every interface (1:1 migration or redesign), effort estimates, and a migration roadmap with realistic timeframes. Even when nobody remembers what the interfaces actually do: undocumented landscapes are routine for us, not the exception.
We take on the communication with internal departments and external business partners, from clarifying requirements to coordinating tests in end-to-end scenarios that involve several parties.
Building integration flows in the SAP Integration Suite and Cloud Integration (CPI), from a single iFlow to chained processes spanning several flows.
Built to SAP best practices, with clean exception handling, and written so someone can still make sense of them in three years' time.
New business partners, new fields, new formats: we extend your existing iFlows and mappings while they stay in operation, from a two-day change to change requests out of the ticket system, up to redesigning individual process chains. Analysis, solution design, build in DEV, transport to PROD.
Graphical mappings, XSLT, and Groovy for everything low-code can't cover. The focus is on exception handling, streaming, and performance tuning for high-volume data, six-figure row counts in a CSV don't faze us.
Connecting SAP and non-SAP systems through every common adapter: IDoc, OData V2/V4, SOAP, REST, HTTPS, SFTP, JMS, AMQP, JDBC, FILE, plus product-specific adapters for SuccessFactors, Salesforce, and SAP Sales/Service Cloud.
Connecting S/4HANA on-premise and Public Cloud, greenfield and brownfield alike. We know the integration patterns that have proven themselves in S/4 projects, and the pitfalls you only spot on the second one.
Setting up and running Trading Partner Management (TPM) in the Integration Suite: partner profiles, agreements, communication channels. Implementing all the common EDIFACT message types (ORDERS, DESADV, INVOIC, PRICAT, and others), including custom types, custom mappings, and special formats. Onboarding new EDI partners as readily as migrating existing ones out of the PI B2B Cockpit.
Integrating, securing, and managing APIs in SAP API Management. Event-based architectures with SAP Event Mesh for asynchronous message processing.
We build the other side of the interface too: ABAP proxies, RFC modules, IDoc enhancements, BAdIs, CDS views with OData exposure, RESTful ABAP (RAP). As former SAP developers, we don't need to bring anyone else in for this.
Analysing and reverse-engineering existing, sometimes undocumented interfaces.
Assessing each one: carry it over 1:1 or improve it deliberately? Plus regression tests to confirm functional equivalence, cutover planning with rollback scenarios, and go-live coordination. For us, go-live isn't a handover point but a phase, with active monitoring, fast corrections, and an orderly handover to operations.
Moving EDI partners out of the SAP PI B2B Cockpit into Trading Partner Management, including custom types, custom mappings, and the edge cases that appear in no SAP documentation.
Reviewing existing interfaces for best practices, consistency, maintainability, and performance, with a prioritised list of actions instead of a mountain of paper.
Reworking or rebuilding interfaces that have aged out, have performance problems, or that nobody wants to touch anymore.
Client-specific developer guidelines based on SAP standards, naming conventions, and template iFlows to copy from, so every new interface looks like it came from one hand and not from a string of changing contractors.
Building monitoring and alerting concepts, writing runbooks for support teams, analysing failed messages (including in SAP AIF). We know all three support levels from our own practice, from the ticket to fixing complex errors on our own.
Reverse-engineering existing interfaces to produce documentation you can rely on and structured knowledge bases, e.g. in Confluence. Unloved, but worth its weight in gold and for us not an afterthought but part of the craft.
Hands-on onboarding of your staff into building and running the integration platform, and training SAP developers to work with ABAP proxy objects. Our aim is that one day you won't need us anymore, at least not for everything.
Senior SAP Cloud Integration Consultant
No agreement on technical requirements? Differences over the gold standard? I enjoy mediating in SAP integration projects. Finding and implementing a successful interface solution together feels like reaching the mountain summit together and enjoying the view.
More than 23 years of combined experience in SAP integration10+ Industries120+ interfaces migrated in 202520+ clients, from mid-sized companies to large corporationsRan every SAP integration platform since XI 3.0 in productionDegree in Business Informatics (Bachelor of Science)SAP certifications
SAP Cloud Platform/CPIC_CP_I_12 SAP Certified Development Associate - SAP Cloud Platform
C_CP_11 SAP Certified Application Associate - SAP Cloud Platform Integration
SAP PI/POC_PO_7513 SAP Certified Technology Associate — SAP Process Orchestration 7.50
ABAPC_TAW12_740 SAP Certified Development Associate - ABAP SAP NetWeaver 7.40
We know the full lifecycle of an integration: planning the system landscape, capturing and translating requirements, building new interfaces and APIs, extending what's already running and, at some point, cleaning up, optimising, and rebuilding whatever has grown over the years.
As former SAP developers, we know both sides of every interface. We talk to your ABAP developers as equals, generate proxy objects ourselves when that's the faster route, and know from experience what an S/4HANA backend can take, and what you'd better not ask of it.
Our expertise rests on more than two decades and over 35,000 contracted project hours in SAP integration: from SAP XI 3.0 through PI dual stack and PO 7.5 to Cloud Platform Integration and today's Integration Suite. We didn't just operate each of these platforms; we set them up, ran them, and eventually retired them.
With us, you get exactly the two people named on this page. No rotating teams, no junior rotation, nothing lost in translation between sales and delivery. If we think a requirement is unnecessary, we say so, even when it shrinks our own order volume. In the long run, that's why clients have worked with us for over ten years.
“We have been working with Mr. Gregory Reinke for 10 years and are more than satisfied with the advice and support for SAP topics.
Very competent, responsive and factual. Without his support, we would not have been able to meet our demanding operational process requirements.”
“We hired Gregory as external support for a customer project for six months to help us analyze and document various SAP Integration Suite interfaces. Through his expertise, Gregory has made a significant contribution to improving existing operating processes and significantly reducing the error rate. His ability to quickly grasp complex problems and present effective solutions really impressed us. He was always reliable, flexible and actively passed on his knowledge to our team. We are extremely satisfied with his work and fully recommend him to others.”
Mostly remote. That's how we've worked successfully for years, including on large projects. For workshops, go-lives, or whenever the situation calls for it, we come to you.
No, that's the norm. Reverse-engineering existing landscapes is part of almost every project we take on.
Yes. Our range runs from a two-day change, through ongoing development of your interfaces, to multi-year integration or migration projects.
Four new integration flows for processing flat files from various source systems: scheduled pickup of CSV files with six-figure row counts, then sorting, grouping, and content-based routing to multiple recipients.
Plus 25 undocumented interfaces analysed and consolidated, and internal staff trained to run the platform on their own. Sole responsibility for all middleware topics in the project.
Supporting the enterprise architects on integration patterns for a hybrid landscape of S/4HANA, BizTalk, and Integration Suite, from synchronous and asynchronous patterns through to API strategy.
Set up TPM in the Integration Suite and migrated more than ten EDI partners out of the PI B2B Cockpit. All the common EDIFACT message types, plus the special formats that weren't in any documentation.
Twelve months, sole project coordination. Every interface assessed individually: 1:1 migration or redesign. Plus 15 new integration flows connecting S/4HANA to the surrounding systems, including cutover, go-live, and monitoring setup.
30 minutes, no obligation, with an honest assessment. We don't promise more than that — but we deliver on it.
