How ShipERP connects to SAP ECC
ABAP add-on inside SAP, no middleware
Because it is installed in the SAP system, it works from delivery and outbound processing in SD/LE, calls carrier services from SAP, and stores tracking and package data against the delivery. For ECC this means a transport-based installation and basis involvement. Confirm supported ECC support packs with the vendor.
Carrier accounts and label printing
You supply your own carrier accounts. Labels print through SAP output management to label printers, so printer setup in the spool is part of the project.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP outbound delivery | ShipERP | Ship-to, weight, dimensions, service level | Packing or delivery processing |
| ShipERP | Carrier | Rate and shipment requests | Rate shop or ship confirm |
| Carrier | ShipERP and SAP | Label, tracking number, charges | Shipment created |
| Carrier | SAP delivery | Tracking events and proof of delivery | Carrier updates |
Setting it up
- 1Confirm system compatibilityVerify ECC release, support pack and S/4HANA path with ERP Integrated Solutions.
- 2Install the add-onImport transports through your landscape (development, quality, production) with Basis.
- 3Load carrier accountsConfigure UPS, FedEx, DHL or USPS credentials and service levels.
- 4Set package dataEnsure materials carry weight and dimensions, and define packaging materials.
- 5Configure label outputSet output types and spool devices for thermal printers at each packing station.
- 6Test rate shopCompare rates to carrier portals for domestic, international and hazmat-excluded shipments.
- 7Go live by siteStart with one shipping point, then add others.
What usually breaks
- !Missing material weights or dimensions, causing wrong rates or rejected shipments.
- !Carrier credentials stored per environment and not refreshed after copies of production.
- !Label printers in the spool using the wrong ZPL driver or label size.
- !International shipments lacking commercial invoice or harmonised code data.
- !Dangerous goods not supported in the standard flow and shipped manually.
- !Upgrades or support packs changing delivery user exits the add-on relies on.
A private AI layer across both systems
Shipping cost variance
A private assistant compares billed carrier charges to quoted rates and flags deliveries where the difference is large, with likely causes such as dimensional weight.
Late delivery questions
Ask which orders for a customer are delayed and get tracking status joined to the sales order.
Master data gaps
List materials shipped with missing weight or dimensions and draft corrections for approval.
Try it here, free
ABAP Code Review Checklist
A practical review checklist for ABAP changes: database access, security, error handling, structure and S/4HANA compatibility.
When something else fits better
- Your carriers' own web portals for very low parcel volume.
- A third-party shipping platform via SAP integration if you need many carriers beyond what ShipERP covers.
- SAP's own transportation and carrier integration options if you already run them.
Frequently asked questions
Does ShipERP need middleware?
The vendor describes an ABAP add-on that runs inside SAP with no middleware. You still need Basis support to install it and network access to the carriers from your SAP system.
Does it work with S/4HANA?
The listing covers SAP ECC, S/4HANA private cloud and a public-cloud edition on SAP Store. Check the exact editions and releases with the vendor for your system.
Can AI help without touching SAP?
Yes. A read-only layer can analyse deliveries, charges and tracking data on your own infrastructure. Any change to shipments or master data should go through a person.
Pairing documented at www.sap.com/products/scm/partners/erp-integrated-solutions-llc-shiperp-private-c . ShipERP is a product of ERP Integrated Solutions; Netray is independent and not affiliated with either vendor.