SAP Engineer Marketplace Integration

Req. Title

SAP Engineer — Marketplace Integration

Location

Bangalore, Karnataka, India

Req. Description

SAP Engineer — Marketplace Integratio

nTeam: Torry Harris Marketplace Experience: 4–6 years Function: Integration Engineering / SA

P
About the ro

leWe are building deep, productised integrations between the Torry Harris Marketplace and enterprise SAP landscapes, with a sharp focus on the industrial manufacturing vertical — discrete and process manufacturers, their distributor and dealer networks, their spare parts and aftermarket businesses, and their B2B supplier ecosystem

s.We're looking for a SAP Engineer who understands SAP from first principles — the underlying data model, document flow, IDoc/BAPI mechanics, and how master data, transactional data, and configuration interact — rather than someone who only knows screens and transaction

s.You will own the SAP side of how our Marketplace plugs into customer ERP environments across product catalog, procurement (Ariba), billing and invoicing, and shipping and delivery. Your work directly determines whether a manufacturer's catalog, purchase orders, invoices, and shipment events flow cleanly between their SAP system and the Marketplace — or whether they don

t.What you'll

• doDesign and build bi-directional integrations between the Torry Harris Marketplace and customer SAP environments — primarily SAP S/4HANA (Cloud and on-premise), with ECC where it shows up in customer landscapes — across the four core domains belo
• w.Build and evolve a portfolio of productised connectors and SDKs that package these integrations for reuse across customers: language-level SDKs for Marketplace developers, configurable connectors with clean upgrade paths, versioning and backwards-compatibility discipline, and documentation that's good enough to ship to a customer's engineering team without an escor
• t.Own the product catalog sync — material master, pricing conditions, classification, units of measure, variant configuration (VC/AVC), bills of materials, and spare parts hierarchies — and ensure catalog state in the Marketplace stays consistent with SAP as the system of recor
• d.Build procurement integrations against SAP Ariba (and where relevant, SAP MM): catalog publishing (CIF/Punchout), purchase requisitions, purchase orders, order acknowledgements, goods receipts, and three-way match scenario
• s.Implement billing and invoicing flows: SD billing documents, FI postings, invoice generation, credit/debit memos, e-invoicing where applicable, and reconciliation between Marketplace transactions and SAP financial record
• s.Implement shipping and delivery flows: outbound deliveries, picking/packing/PGI, shipment notifications (ASNs), tracking event ingestion, and return
• s.Choose the right integration mechanism per use case — IDoc, BAPI/RFC, OData/SAP Gateway, CPI/Integration Suite, REST APIs, event-based via SAP Event Mesh — and justify the choice on grounds of latency, volume, reliability, and customer landscap
• e.Handle the hard parts: idempotency, ordering, partial failures, retries, reconciliation, and audit trails across systems that have very different consistency model
• s.Work with Marketplace product and engineering teams to shape APIs and data contracts on our side so SAP integration is clean rather than bolted o
• n.Engage directly with customer SAP teams during implementations — read their configuration, understand their customisations, and translate that into integration desig

n.What we need from y

ouExperien

• ce4–6 years working hands-on with SAP, with a track record of integrating SAP capabilities into external systems and workflows — not just internal SAP developmen
• t.Demonstrable delivery across at least three of the four focus areas: product catalog (MM material master, pricing), procurement (Ariba, MM), billing/invoicing (SD billing, FI), shipping/delivery (SD deliveries, LE

).First-principles SAP knowled

• geStrong grasp of the SAP data model and document flow — how a sales order becomes a delivery becomes a billing document becomes an FI posting, and the same for the procurement sid
• e.S/4HANA is core, not optional. Hands-on experience with S/4HANA (Cloud and/or on-premise), including the simplified data model, CDS views, side-by-side extensibility on BTP, and the differences between in-app and on-stack extension paths. ECC familiarity is a plus given that many customer landscapes still run i
• t.Comfortable reading and reasoning about SAP configuration, not just code. You can look at a customer's setup and predict how an integration will behav
• e.Working knowledge of ABAP (including RAP / ABAP for Cloud where relevant) — enough to read, debug, and write user exits, BAdIs, and enhancement points when needed. You don't need to be an ABAP specialist, but you shouldn't be blocked by i

t.Building connectors and SD

• KsTrack record of building reusable connectors or SDKs — not just one-off integrations. You think about API ergonomics, semantic versioning, deprecation, and the experience of the developer who will pick up your SDK two years from no
• w.Comfortable designing the abstraction layer between a messy customer-specific SAP setup and a clean, opinionated connector surfac

e.Integration cra

• ftHands-on with IDocs (definition, processing, monitoring), BAPIs and RFC-enabled function modules, and OData services via SAP Gatewa
• y.Practical experience with SAP Integration Suite / CPI, or comparable middleware (MuleSoft, Boomi, webMethods) wired into SA
• P.Familiar with SAP Ariba integration patterns — cXML, CIF catalog uploads, Punchout, and the Ariba Network message flo
• w.Solid REST/JSON and event-driven integration skills outside the SAP world — this role lives at the boundar

y.Engineering fundamenta

• lsThinks in terms of contracts, idempotency, failure modes, and observability — not just happy-path succes
• s.Comfortable with Git, CI/CD, and modern engineering practice. Writes clear documentation as a default, not an afterthough

t.Nice to ha

• veSAP BTP exposure — Integration Suite, Event Mesh, API Management, Workflo
• w.EDI experience (ANSI X12, EDIFACT) — manufacturers run heavy EDI traffic with OEMs, suppliers, and logistics providers, and Marketplace flows often sit alongside i
• t.Exposure to manufacturing-adjacent SAP modules — SAP DMC (Digital Manufacturing Cloud), SAP ME/MII, PP, PM, or QM — and how they feed into or consume from the order-to-cash and procurement flow
• s.Familiarity with B2B distributor / dealer portal patterns and aftermarket / spare parts commerc
• e.Familiarity with SAP authorisation concepts and how they affect integration user design in customer landscape

s.How you'll wo

• rkYou'll sit between the Marketplace platform and customer SAP environments, so you should be equally comfortable in a product engineering sprint and in a customer SAP review cal
• l.You can push back when a proposed integration design will create operational debt, and you can do it with evidenc
• e.You write things down. Integration designs, decisions, and trade-offs end up in shared docs so the next engineer — internal or customer-side — isn't reverse-engineering them six months late