Business Impact:
Goods Movement posting failures
Transfer Order confirmation delays
Stock discrepancy in EWM vs. ATTP
Delivery processing blocked
Serialization status mismatch
Warehouse task execution halted
When the Warehouse Stops A True Cost of Ignoring ATTP–EWM Latency
The Challenge
Frankfurt, Germany. A mid-sized pharmaceutical distribution center handling life-critical medicines, serialised shipments, and tight regulatory deadlines every single day.
On paper, everything looked solid. SAP EWM was live. ATTP was integrated. The compliance team had signed off. The go-live was celebrated.
Then three months in things started breaking quietly.
Goods movements began freezing mid-process. Warehouse staff scanning serialised cartons would hit confirm and just wait. The system hung. Transfer orders piled up. Supervisors started printing manual workaround sheets. What was supposed to be a smart, automated warehouse was running partially on paper again.
Nobody panicked immediately. Everyone assumed it was a small configuration issue something the internal IT team could fix over a weekend.
That weekend became six months.
What the business was actually losing during those six months —
- Over €45,000 monthly (as reported by the client) in delayed shipments, emergency courier rerouting and penalty clauses from hospital and pharmacy clients
- Three formal regulatory warnings due to serialisation status mismatches between EWM and ATTP
- Delivery SLA dropping from 98.4% to below 81% — clients were noticing and escalating
- Warehouse teams logging 2 to 3 hours of daily manual intervention just to keep shipments moving
- Stock ledger inconsistencies building up silently — inbound confirmed in EWM but ATTP still showing open serialisation status
- Two senior warehouse coordinators resigned citing operational frustration
This was not a minor system glitch anymore. This was a business bleeding quietly — every single day.
The Call to SCM Champs
By the time the distribution center’s operations director reached out to SCM Champs, the exhaustion in her message was visible. She wrote —
“We have tried everything internally. Our SI partner has escalated three times. Nothing is working. Our warehouse is running on workarounds and our compliance team is nervous. We need someone who has actually seen this before.”
SCM Champs had seen it before. Many times.
The team was on a call within 24 hours. No lengthy proposals. No generic discovery templates. Just direct, focused questions from people who understood exactly where to look.
What SCM Champs Actually Found
This is where it gets technical — but stay with it, because every finding below was directly costing this business money.
Finding 1 — Synchronous calls were choking the entire flow
Every single goods movement was triggering a synchronous RFC call to ATTP — meaning EWM would stop completely and wait for ATTP to validate every serial number before allowing the posting to continue. In a warehouse processing hundreds of serialised units per hour, this created a queue of waiting processes that progressively slowed the entire system down to near standstill.
Finding 2 — RFC destination and gateway settings were never optimised
The RFC connections between EWM and ATTP were running on default configuration — never tuned for the actual transaction volume this warehouse was generating. Gateway parameters were throttling the connection during peak morning dispatch hours precisely when the warehouse needed maximum throughput.
Finding 3 — No PPF framework was in place
ATTP serialisation checks were embedded directly inside core execution transactions. There was no Post Processing Framework action set up to handle ATTP communication separately — which meant any ATTP delay immediately became an EWM delay with zero buffer.
Finding 4 — Number range buffering was inactive
During high-volume periods multiple warehouse lines were simultaneously requesting serial number validations against massive ATTP database tables — with no buffering active. Every request was hitting the database cold, creating locks and compounding the latency.
Finding 5 — No local serial number processing was being leveraged
The distribution center was on S/4HANA 2022 — which supports reduced real-time ATTP dependency within EWM itself — but this capability was completely unused. Every scan was pinging ATTP directly, even for actions that did not require it at that moment.
What SCM Champs Delivered — Step by Step
Step 1 — Switched from Synchronous to Asynchronous RFC Processing
The team reconfigured serialisation checks to run asynchronously using aRFC (asynchronous Remote Function Calls) — removing the hard dependency that forced EWM to wait for every ATTP response before continuing. For scenarios requiring guaranteed processing sequence, qRFC (queued RFC) was additionally configured via transaction SMQR — ensuring background queue processing without locking the warehouse interface or delivery document. Queue health was monitored through SMQS and SM58 to ensure no stuck entries during go-live stabilisation.
Step 2 — Built the Post Processing Framework Actions
PPF actions were configured within EWM to trigger ATTP serialisation checks after warehouse task confirmation or goods issue posting — not during. A Goods Movement Block was implemented on the delivery — the official SAP EWM mechanism tied directly to ATTP document status — which releases automatically once the asynchronous PPF action receives a successful ATTP confirmation callback. This completely removed ATTP communication from the critical execution path.
Step 3 — Optimised RFC Destinations and Gateway Parameters
RFC server group assignments were reviewed and corrected via transaction RZ12 for proper load balancing across dialog work processes. Instance profile parameters were then adjusted through RZ10 to allocate sufficient work processes for peak RFC load. Gateway parameters — specifically gw/max_conn and gw/max_overflow_size — were tuned based on the client’s S/4HANA 2022 kernel version to handle high-volume serialisation spikes during peak dispatch windows without connection throttling.
Step 4 — Number Range Configuration and Database Performance Review
Number range buffering for ATTP serial number processing was reviewed and configured per SAP standard guidelines — preventing database locks when multiple warehouse lines simultaneously validate serial numbers during peak operations. Additionally, database performance analysis was conducted on high-volume ATTP tables and optimisation recommendations were raised through proper SAP support channels — ensuring query response improvements without direct index manipulation outside of SAP-compliant procedures.
Step 5 — Reduced Real-Time ATTP Dependency in S/4HANA EWM
Since the client was on S/4HANA 2022, SCM Champs configured EWM to leverage SAP’s recommended integration model for reducing synchronous ATTP load in high-volume environments. Serial number processing was restructured so that EWM handles execution-level actions locally synchronising with ATTP as the system of record only at defined milestones such as goods issue or delivery confirmation. This approach significantly reduced real-time ATTP dependency without compromising pharma serialisation compliance or ATTP’s role as the central validation authority. The result was a reduction of over 60% in unnecessary real-time ATTP calls during a normal warehouse shift (as reported by the client).
Step 6 — End-to-End Validation Before Go-Live
Before anything went live, SCM Champs ran a full parallel testing cycle — covering inbound deliveries, outbound dispatch, stock transfers and returns. Every scenario. Every edge case. Queue monitoring via SMQR and SM58 was kept live throughout. Nothing was pushed to production until the team was fully satisfied that the flow was clean, compliant and stable.
What Changed — Business Impact After Resolution
The difference was not gradual. It was immediate.
- Goods movements posting in real time — the freezing stopped on day one
- Transfer order confirmation time dropped by 72% (as reported by the client)
- Delivery SLA recovered from 81% back to 99.1% within the first month
- All serialisation status mismatches cleared — full regulatory compliance restored
- Manual workaround hours reduced to zero — staff were doing their actual jobs again
- Stock ledger accuracy in EWM and ATTP fully aligned — clean, auditable, reliable
- The operations director sent a single message after week two — “I haven’t had a single escalation call this week. First time in seven months.”
That message said everything.
Why SCM Champs
Some problems look like technology failures. Most of the time they are configuration gaps that the right team with the right experience can find and fix.
SCM Champs works exclusively with pharmaceutical operations across North America and Europe resolving the exact errors that generic SAP partners struggle to diagnose. ATTP compliance failures, EWM integration breakdowns, serialisation bottlenecks, goods movement blockages this is not new territory for us. It is where we live.
If your warehouse is losing time, missing SLAs, or carrying regulatory risk because of an error your current team cannot crack —
You do not need another escalation. You need SCM Champs.