SAP Integration Best Practices: How We Manage Rs 1.2 Lakh Crore+ of Inventory With Custom Engineering

There is a moment in almost every large Indian manufacturing SAP project when someone in the room says: “SAP should be able to do this natively.” And technically, they are often right. SAP can do almost anything, given enough configuration time, enough implementation consultants, and enough money.

The problem is that Indian manufacturing operations — with their specific workflows, statutory requirements, contractor populations, and infrastructure realities — rarely fit neatly into SAP’s standard process models. The result is either a heavily customised SAP installation that nobody wants to touch for fear of breaking it, or a standard SAP installation that the floor team works around with spreadsheets and WhatsApp messages.

Over eight years of building systems that integrate with SAP at India’s largest manufacturing facilities, our team at Ajinkya Technologies has developed a clear philosophy: SAP is the system of record. Custom engineering is the system of execution. The two need to work together in real time — not as a batch sync at the end of the shift.

Here is what that looks like in practice.

The Scale of What We Manage

Before the detail, some context on what we mean by “at scale”:

At JSW Steel, our systems manage the movement of vendor materials valued at Rs 20,000 crore daily. Every tag scan, every bin transfer, every receipt and return is reconciled with SAP in real time. Across the broader JSW deployment, we track 27 million tons of steel annually with full traceability from raw material receipt to finished goods dispatch.

At Hindalco Industries (Aditya Birla Group), our asset tracking and warehouse automation systems manage Rs 12,000 crore+ in inventory, processing 7,20,000+ individual material movements every day.

These are not pilot projects or proofs-of-concept. These are production systems that Indian industry depends on, running 24/7, with SAP integration that cannot fail.

Why Custom ERP Alongside SAP Makes Sense

SAP’s standard warehouse management and inventory modules — whether WM, EWM, or the newer S/4HANA-embedded functions — are designed for global enterprise workflows. They are excellent at financial valuation, compliance reporting, and cross-plant visibility. They are not designed for:

• RFID portal reader event streams generating thousands of raw scan events per minute
• Offline-capable mobile applications for floor staff in facilities with patchy WiFi
• Contractor workforce tracking integrated with inventory movement
• WhatsApp-based exception alerts for supervisors who do not use SAP
• India-specific GST, e-way bill, and statutory compliance workflows that change with every budget

Our approach is to build a lean custom application layer that handles the operational reality of the shop floor, and then push clean, validated transactions into SAP at the movement type level. SAP sees only validated inventory movements — it does not need to process raw RFID events or manage offline sync queues.

The Architecture That Works

The architecture we have refined across multiple large deployments has four layers:

Layer 1 — Data capture. RFID readers, barcode scanners, or manual entries in our custom mobile apps. All capture is offline-capable — data queues locally and syncs when connectivity is restored, preventing any stoppage of operations during network interruptions.

Layer 2 — Custom operations platform. A web and mobile application (React.js frontend, Node.js backend, MySQL/MariaDB database) that handles the operational logic: bin management, FIFO enforcement, quality hold flags, contractor material tracking, return processing. This is where the floor team works. It is fast, simple, and built around how Indian factory staff actually operate.

Layer 3 — Integration middleware. A dedicated integration service that validates completed transactions in our custom platform and maps them to the correct SAP movement types, storage locations, and valuation classes. This middleware maintains a transaction log with retry logic — if SAP is unavailable for a maintenance window, transactions queue and replay automatically.

Layer 4 — SAP. Receives clean, validated inventory movements. The SAP team and finance team work here. MIS reports, statutory filings, inter-company valuations — all sourced from SAP, which sees a complete and accurate picture because our integration layer never pushes a partial or unvalidated transaction.

The Five SAP Integration Failure Points We Fix

In the course of project work and in conversations with peers, these are the five integration points we see fail most often:

1. Movement type mapping is wrong. SAP has hundreds of movement types. Using the wrong one — goods receipt versus transfer posting versus subcontracting receipt — creates valuation errors and stock inconsistencies that are extremely difficult to unwind. We spend two full weeks with the SAP MM/WM team just on movement type mapping before writing a single line of integration code.

2. Batch management is ignored. For manufacturers who need FIFO or FEFO discipline — paints, chemicals, pharmaceuticals, food ingredients — SAP batch management must be active and correctly configured. Many RFID integration projects treat inventory as batch-agnostic, which breaks FIFO enforcement at the application layer.

3. Storage location master data is incomplete. Custom storage locations for temporary holds, quarantine, vendor-owned stock, and transit zones need to exist in SAP before integration goes live. We have seen deployments delayed by six weeks because storage location master data had to be created and extended to new plants retroactively.

4. Authorisation objects are not considered until go-live. The SAP RFC user account used by the integration middleware needs precisely scoped authorisations — enough to post movements, not enough to approve financial documents. Getting the security architecture right before go-live prevents both access failures and audit findings. We document the required authorisation objects as part of the technical design document.

5. Error handling is an afterthought. Every integration will encounter exceptions: a material not yet created in SAP, a storage location locked for physical inventory, a batch that does not exist. A production-grade integration has a defined exception queue, an alert mechanism (we use WhatsApp alerts to the SAP support team), and a reprocessing workflow. Without this, exceptions pile up silently and create stock discrepancies that only surface at month-end closing.

The JSW Steel Refractory Vendor Material Story

The most complex SAP integration we have built to date is the vendor material management system at JSW Steel’s refractory operations. Refractory materials — silica bricks, graphite electrodes, castables — are high-value, consume-on-use items that are supplied by vendors who retain ownership until the point of consumption. This means:

• Vendor-owned stock must be tracked separately from company-owned stock in SAP
• GRN (Goods Receipt Note) should only be posted against SAP when material is actually consumed, not when it physically arrives
• Vendor reconciliation runs weekly — every tagged item must have a documented movement history
• Material can be returned to the vendor if not consumed, requiring a reversal of the provisional GRN

We built a custom tracking system on top of SAP Vendor Consignment (movement type 101 for receipt into consignment, 201 for withdrawal from consignment to consumption). Our RFID layer tracks the physical location of every tagged batch of refractory material from vendor truck arrival to consumption in the furnace. SAP is updated at each stage. The result is Rs 20,000 crore of vendor material managed daily with zero end-of-month reconciliation surprises.

What a 12-Week SAP Integration Project Looks Like

For manufacturers evaluating a new custom ERP plus SAP integration project, here is the realistic timeline from our experience:

Weeks 1–2: Discovery and process mapping. We walk every material movement process with the operations team and the SAP consultant simultaneously. Every movement is mapped: what triggers it, which data fields are captured, which SAP movement type it maps to, what the exception cases are.

Weeks 3–4: System design and SAP master data preparation. Technical design document covering architecture, API specifications, movement type mapping, and error handling. Parallel track: SAP team creates or extends storage locations, material types, and batch classification schemas required for integration.

Weeks 5–8: Development and sandbox testing. Custom application and integration middleware built and unit-tested. Integration tested in SAP sandbox environment with real material master data and simulated movement scenarios including all identified exception cases.

Weeks 9–10: User acceptance testing. Floor operations team tests the custom application with real devices on the shop floor. SAP team validates that movements post correctly and that financial valuations are accurate. Exception scenarios are tested to verify error handling and alerting works.

Weeks 11–12: Parallel run and go-live. Both old and new systems run simultaneously for two weeks. Any discrepancy between the two is investigated and resolved. Go-live cutover happens at the beginning of a new accounting period to simplify opening balance management.

The Lesson

SAP is not the enemy of custom engineering, and custom engineering is not a workaround for SAP’s limitations. They are complementary layers. The mistake is trying to make SAP do the job of the operational layer — configuration debt accumulates, upgrades become frightening, and floor teams build shadow systems anyway.

The Indian manufacturing enterprises we have seen get this right treat SAP as the single source of financial truth, invest in a clean custom operational layer designed for their specific processes, and maintain a disciplined integration contract between the two. That is what allows them to run at Rs 1.2 lakh crore+ of inventory without clipboards.

Amey Kadle is Founder and CEO of Kadle Global Pvt Ltd. His team has built SAP-integrated systems managing 27 million tons of steel annually at India’s largest manufacturing complexes. View case studies →