The posting
About the Team & Role AugerOS reads a customer's operational data, models their supply chain, and recommends decisions on allocation, sourcing, risk, and execution. Then it writes those decisions back into the systems where work gets done. For many of our enterprise manufacturing and distribution customers, that system is SAP. Getting data out and decisions back in, with the right authorization, idempotency, and audit trail, is hard, and it's central to what we deliver. You'll be the person who makes that work.
You're Auger's SAP authority. You walk into a customer's SAP team, figure out how their landscape is really configured (not how the diagram says it is), and design the ingestion and write-back approach for that engagement. When the work requires changes inside the customer's SAP, you scope it, pick and direct the specialist partners, and decide whether what they deliver is good enough to ship. You'll sit between Auger engineering, customer SAP and IT teams, and third-party SAP partners, and you'll be the one who can tell a good design from a risky one, with the standing to say so.
There's no legacy SAP playbook here. The discovery process, reference architectures, and partner bench are yours to build, and the whole company will use them. You'll get customer-facing, architectural, contractual, and educational work in one role, on decisions that change what a customer buys, moves, and ships.
What You'll Do Run discovery that finds the real answer Lead sessions with customer SAP teams to map the landscape: ECC or S/4HANA (on-prem, RISE, private cloud), instances and clients, middleware (PI/PO, Integration Suite/CPI, BTP), and existing extraction tools. Work out how each customer has configured and customized the objects we depend on: materials, BOMs, purchase and sales orders, deliveries, inventory, MRP, vendors, customers. Produce artifacts people use: landscape diagrams, object and field mappings, volume and change-frequency profiles, open-risk logs.
Design ingestion and write-back Choose the right extraction pattern per customer from the full toolbox: ODP/ODQ, SLT, CDS views, OData, IDocs, BAPIs/RFCs, Datasphere and Business Data Cloud, third-party tools, file or event-driven. Design write-backs (POs, stock transport orders, allocations) with real attention to authorization, principal propagation, error handling, idempotency, and auditability. Weigh each option against the customer's licensing, SAP's API and extraction policies, security requirements, and their IT team's preferences, then drive to a design both sides sign off on. Work with our engineers on how SAP data lands in Snowflake, Databricks, or Fabric and maps into our data model.
Manage SAP partners Define the work needed inside customer systems: custom CDS views, function modules, BAdIs, iFlows, authorization roles. Source and evaluate SAP subcontractors, review their SOWs for scope, estimates, and assumptions, and hold them to quality and dates. Review their designs and deliverables, and translate between their work and our architecture.
Help create our SAP playbook Build our SAP integration playbook: discovery templates, reference architectures, object catalogs, decision guides. Coach engineers and engagement leads until routine SAP questions don't need you. Track where SAP is heading (S/4 migrations, BTP, Business Data Cloud, API and licensing changes) and tell us what it means for our strategy.
What You Bring 10+ years with SAP, at least 5 in integration or technical architecture. Bachelor's or Master's degree in Computer Science, Engineering, or related fields. Hands-on depth in IDocs, BAPIs/RFCs, OData, CDS views, ODP/ODQ, and SLT, plus at least one middleware platform (PI/PO, CPI, or BTP). A working grasp of the supply chain data model in ECC and S/4HANA: MM, SD, PP, and WM or EWM, including key tables and document flows. You don't need to be a functional consultant, but you can hold your own with one. Experience getting SAP data into Snowflake, Databricks, Fabric, or a hyperscaler data lake. Solid footing in SAP security: roles, technical users, OAuth, principal propagation, and how they apply to third-party integrations. A record of scoping, contracting, and managing SAP subcontractors or SIs, including picking apart SOWs and estimates. The ability to run a workshop with a customer's SAP CoE, then explain the outcome plainly to engineers and executives who don't know SAP. Comfort with ambiguity. Much of the approach will be yours to work out.
