A pharmaceutical manufacturer in Massachusetts had been running their warehouse the same way for years. It worked \u2014 until it did not.<\/p>\n
Their quarantine zone was physical tape on the floor. QC release happened over email. Batch status lived in people’s heads. Every goods movement was written on paper first and typed into SAP later \u2014 sometimes the next morning.<\/p>\n
Nobody thought it was a crisis. Until a shipment of a critical antibiotic left the building before QC had released the batch. It was still under microbiological testing. The recall that followed cost them somewhere around two million dollars. And that was just the financial part.<\/p>\n
Six months later their internal audit found around a dozen open compliance findings. An FDA inspection was already on the calendar for early 2024. They were not ready. Not even close.<\/p>\n
The recall was painful. But the real fear was what came next.<\/p>\n
An FDA Warning Letter would have frozen shipments. Their international contracts had quality clauses \u2014 one adverse finding and those conversations would get very difficult very fast. And underneath all of it was a simpler truth that nobody said out loud in meetings but everyone understood. An unreleased batch reaching a hospital is not a compliance problem. It is a patient safety problem.<\/p>\n
They needed a fix. A real one. Not another procedure document.<\/p>\n
The VP of Supply Chain called SCM Champs directly in August 2023. Not a formal tender. A phone call. He had heard about SCM Champs from someone at another pharma company who had been through something similar.<\/p>\n
He said something simple. “We have maybe five months. Fix it properly.”<\/em><\/p>\n The SCM Champs team flew out the following week.<\/p>\n Two days walking the warehouse floor. Watching how operators actually worked. Not how the SOPs said they worked. What they found confirmed everything. Four physical storage zones existed. Only two were visible anywhere in SAP. Goods coming in had no system-enforced path to quarantine. Operators were confirming movements by keyboard \u2014 no scanning. And the connection between SAP QM and the warehouse stock status simply did not exist in any meaningful way. A batch could be sitting in active QC testing and still be physically pickable by anyone on the floor.<\/p>\n After the floor walk came structured interviews with the warehouse manager, QC supervisor, IT lead, and regulatory head. That combination \u2014 floor observation plus people conversations \u2014 gave SCM Champs a gap analysis with around 27 documented findings mapped against 21 CFR Part 11, EU GMP Annex 11, and the SAP GMP Compliance Framework.<\/p>\n That document became the agreed foundation for everything that followed.<\/p>\n SAP WM was not suitable for this GMP-regulated environment. It provides limited integration with SAP QM and lacks the granular bin-level stock status control that pharmaceutical warehouse compliance demands. For an operation facing an FDA inspection with batch traceability gaps, it was simply not the right fit.<\/p>\n EWM was.<\/p>\n The warehouse was restructured with four clearly defined Storage Types inside EWM. Ambient released. Cold chain released. Quarantine \u2014 with system-controlled restrictions preventing picking from quarantine stock under standard operations. And rejected stock \u2014 physically and systemically separated. Every incoming delivery now routed to quarantine first. No human decision involved.<\/p>\n Batch management was activated properly. Shelf life fields made mandatory at goods receipt \u2014 no receipt possible without manufacturing date and expiry date entered. FEFO \u2014 First Expired First Out \u2014 set as the default picking strategy. The system selects the earliest expiring batch automatically. Operators cannot choose a different bin without a supervisor authorisation that gets logged.<\/p>\n The most important technical piece was the integration between SAP QM and EWM. Configured integration enables a stock type change in EWM based on the QM Usage Decision. When a QC analyst posts a Usage Decision in QM \u2014 that action triggers the status update in EWM through configured follow-up actions and integration settings. Accepted means the batch moves to unrestricted stock and becomes available for picking. Rejected means it moves to blocked stock and routes to the rejected zone. No phone call. No email. No manual step in between once the configuration is in place.<\/p>\n Audit trails secured across all GMP-relevant objects. Every action \u2014 every movement, every status change, every override \u2014 records who did it, when, what it was before, what it is after. Stored in SAP. Audit trails are secured and cannot be altered by business users.<\/p>\n Electronic signatures configured for critical transactions \u2014 goods receipt, QC release, goods issue, destruction of rejected stock. Each signature captures user authentication and approval context at the point of execution. This configuration supports compliance with 21 CFR Part 11 and EU GMP Annex 11.<\/p>\n Role-based access built through SAP GRC. A warehouse operator cannot release a batch. A QC analyst cannot perform physical goods movements. Those two things cannot exist in the same user profile. The system enforces it. Not a policy. The system.<\/p>\n About three weeks into the configuration phase the warehouse operators pushed back on the RF scanning requirement. Hard.<\/p>\n They had been doing keyboard entry for years. They were fast at it. They did not see why it needed to change. Two senior operators in particular made it very clear they thought the scanning process was slower and added steps they did not need.<\/p>\n The SCM Champs team did not argue with them. Instead they spent a full day on the floor running parallel sessions \u2014 keyboard entry versus RF scanning \u2014 and let the operators see the error rate difference themselves. Keyboard entry was producing around one misconfirmation in every fifteen transactions during that exercise. Scanning produced zero.<\/p>\n That changed the conversation. It did not make everyone happy overnight. But it moved from resistance to reluctant acceptance. And by go-live most of them had quietly admitted the scanning process was actually less stressful once they knew the system was catching things they used to catch manually.<\/p>\n That is a small thing. But it is the kind of small thing that decides whether a go-live actually works or falls apart in the first two weeks.<\/p>\n The full Computer System Validation lifecycle was executed. User Requirements Specification covering around 40 requirements \u2014 signed off by QA before any configuration was finalised. Installation Qualification confirming the system was correctly set up in production. Operational Qualification with around 65 test scripts \u2014 every one with the expected result documented before execution and the actual result signed off by both the tester and a QA reviewer. Performance Qualification under live operating conditions with real batches and real users.<\/p>\n Every failed test generated a deviation report. Investigated. Fixed. Re-tested. Nothing carried forward as an open item.<\/p>\n The Validation Summary Report was signed by the QA Director, the IT Lead, and the Warehouse Manager. Go-live was approved only after that signature page was complete.<\/p>\n Operators learned RF scanning, quarantine procedure, and what to do when the system instruction did not match what they found physically on the shelf. QC team learned Usage Decision posting and what the electronic signature meant in a regulated context. Supervisors learned how to read the audit trail and handle exceptions without breaking the compliance record.<\/p>\nFirst thing they did \u2014 they did not open a laptop.<\/strong><\/h3>\n
The decision was to move from SAP WM to SAP Extended Warehouse Management \u2014 EWM \u2014 embedded inside their existing SAP S\/4HANA system.<\/strong><\/h3>\n
Here is where it got difficult.<\/strong><\/h3>\n
Validation was treated as a quality deliverable. Not a checkbox.<\/strong><\/h3>\n
Training happened before a single live transaction.<\/strong><\/h3>\n