Integrations
/ SAP ATTP
Integrations · ERP serialization
TracePharma + SAP ATTP
SAP ATTP is the corporate serialization repository for SAP-centric manufacturers. TracePharma interoperates via SAP ICH HTTPS when EPCIS flows from Integration Suite to your tenant—without replacing ATTP in the ERP core.
Preset:
sap_ich
HTTPS
Pulse ecosystem vendor
SAP is a Pulse-listed enterprise stack vendor. TracePharma rarely displaces ATTP entirely. It handles partner-edge L4 workflows—receive, ship, exceptions, ACK monitoring—while SAP remains the corporate serial number repository.
Inbound interoperability
- ✓ HTTPS webhook preset (sap_ich) for SAP Integration Suite / ICH delivery.
- ✓ EPCIS capture into unified receiving and 3T matching.
- ✓ Commissioning reconcile against L3 allocations when manufacturers bridge SAP to L4.
Outbound & compliance
- ✓ Outbound EPCIS to wholesalers not routed through SAP directly.
- ✓ ACK monitoring and exception investigation at partner edge.
- ✓ REST API for WMS and automation alongside SAP flows.
Typical cutover steps
- 1 Map SAP ICH or Integration Suite endpoints with your SAP SI partner.
- 2 Create sap_ich preset inbound connection in TracePharma.
- 3 Define which partners stay on SAP vs partner-edge TracePharma paths.
- 4 Test sample ICH delivery before production promotion.
Best for
- → SAP S/4HANA manufacturers adding lighter partner-edge L4 UX.
- → Distributors receiving SAP-origin EPCIS via ICH HTTPS.
- → Teams where ATTP remains system of record but operators need scan-first L4.
SAP ATTP interoperability FAQ
- Does TracePharma replace SAP ATTP?
- Usually no. ATTP remains the ERP serialization repository. TracePharma handles partner-facing L4 operations—receiving, outbound to specific partners, exceptions, and compliance exports—alongside SAP.
Connect SAP ATTP in your tenant
We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.