SAP Shipping Interface: A Guide for IT Managers
For most SAP shipping integrations, the decision is clear: IDoc-Outbound for asynchronous delivery and shipment documents, REST/OData via SAP Cloud Integration (CPI) for modern cloud setups. Both variants follow the clean core principle and avoid modifications to the SAP core. There are three reasons for this:
- Update and migration security: Modification-free integrations significantly simplify S/4HANA upgrades because no ABAP adjustments need to be backported to the core.
- Asynchronous robustness: IDoc-based outbound messages include built-in retry and logging mechanisms, which are critical in the event of network interruptions or carrier failures.
- GTS compatibility: Customs processes such as export declarations and sanctions list checks run via the same asynchronous RFC infrastructure that also handles shipping documents.
Those looking to accelerate their go-to-product launch can integrate Paket International as a multi-carrier platform with seamless integration capabilities. The platform supports API and plugin connections and is designed for clean-core strategies.
Key insights
For SAP shipping integrations, the following applies: Modification-free, asynchronous connections via IDoc or REST/OData via CPI are the most future-proof architecture for S/4HANA environments.
| Theme | Details |
|---|---|
| Interface selection | IDoc outbound for delivery documents, REST/OData via CPI for real-time tracking and cloud setups |
| Clean Core Principle | Modification-free integration via external middleware significantly simplifies S/4HANA upgrades. |
| GTS mandatory data | HS code, Incoterms, recipient address, value of goods and country of origin must be fully transmitted. |
| Monitoring transactions | Check SM58, WE02/WE05, BD87 and SLG1 daily; set up automated alerts for queue backlogs. |
| International Package | Offers REST API integration, automatic customs clearance and multi-carrier connectivity without SAP core modification. |
Table of Contents
- What SAP interface types are available for shipping integration?
- Which middleware is suitable for your SAP shipping integration?
- What do proven integration patterns for carrier processes look like?
- What capabilities must interfaces for SAP GTS and customs clearance provide?
- What does a concrete implementation checklist look like?
- How do you monitor and resolve errors in SAP shipping interfaces?
- Parcel International: Automated Shipping Integration in Practice
- Paket International accelerates your SAP shipping integration
- Sources
What SAP interface types are available for shipping integration?
Common SAP interfaces For third-party systems, RFC/BAPI is used for synchronous function calls, IDoc for robust asynchronous messages, and web services (SOAP, REST/OData) for modern APIs and real-time status. Each technology has specific strengths in the context of data transmission.
| interface type | Typical shipping use case | Power |
|---|---|---|
| RFC / BAPI | Synchronous master data queries, inventory checks | Direct feedback, easy implementation |
| IDoc (Outbound) | Delivery documents, shipment messages to carrier gateway | Asynchronous, retry-capable, GTS-compatible |
| SOAP | Web service integration of older carrier systems | Standardized protocol, well documented |
| REST / OData | Real-time tracking, label printing, CPI flows | Lightweight, JSON-enabled, cloud-native |
For outbound delivery messages, IDoc is the established choice: The message type DESADV Alternatively, customer-specific extensions transfer delivery data to external shipping systems. REST/OData is suitable where real-time feedback is required, such as retrieving tracking numbers or status updates from the carrier.
Pro tip: Choose the interface type based on consistency requirements: If SAP needs to process a response immediately (e.g., label print confirmation), REST/OData is the appropriate choice. If delayed processing is sufficient (e.g., handover to carrier), IDoc is the more robust option. Integrations without modifications via external middleware or cloud APIs avoid core changes and facilitate future S/4HANA migrations.
Which middleware is suitable for your SAP shipping integration?
SAP PI/PO versus SAP Cloud Integration
SAP Process Integration (PI) and Process Orchestration (PO) are the classic on-premise middleware platforms. They support IDoc, RFC, SOAP, and REST, offer sophisticated mapping tools, and are already present in many German SAP landscapes. The disadvantage: operation, patching, and scaling are the responsibility of the in-house IT team. For new projects, SAP recommends switching to Cloud Integration (CPI) within the SAP Integration Suite.
CPI runs on the SAP Business Technology Platform (BTP) and supports the same protocols as PI/PO, along with modern REST adapters and pre-built integration packages. SAP handles maintenance, and updates are automatic. For companies using S/4HANA Cloud or planning a phased migration, CPI is the recommended approach.
Decision criteria for PI/PO:
- Existing on-premise infrastructure with ongoing integrations
- Complex ABAP mappings that cannot be migrated in the short term.
- Regulatory requirements that preclude cloud data storage
Decision criteria for CPI / Integration Suite:
- New projects on S/4HANA or S/4HANA Cloud
- Need for rapid onboarding of new carriers without infrastructure costs
- Multi-client capability and country-specific routing logic for cross-border shipping
When does third-party middleware make sense?
Cloud-based multi-carrier solutions They enable integrated label printing, shipment tracking, and the connection of numerous carriers without requiring changes to the SAP core. They are particularly useful when a company operates many carriers simultaneously, must comply with country-specific labeling regulations, or wants to quickly onboard new parcel services. Integration is achieved via a standardized API that SAP accesses using CPI or PI/PO. These modification-free integrations, implemented as external middleware or cloud connections, reduce risks during S/4HANA updates and simplify migration management.
What do proven integration patterns for carrier processes look like?
The typical data flow in an SAP shipping integration follows a clear sequence:
- Create sales order In SAP SD: Customer data, items, Incoterms and delivery address are recorded.
- Generate delivery (Transaction VL01N/VL10): SAP creates the delivery document with packing suggestion and weight information.
- Trigger IDoc outboundThe delivery triggers an outbound IDoc message (e.g., message type).
SHPMNTfor shipments), which is transmitted to the carrier gateway. - Carrier gateway processesThe external system or multi-carrier platform receives the delivery data, selects the carrier, prints the shipping label and returns the tracking number.
- Feedback to SAP: The tracking number is written to the SAP delivery document and the shipping status is updated via REST call or IDoc inbound.
Asynchronous replication is the standard for delivery handovers. Synchronous calls are useful when SAP needs a tracking number immediately, for example, for automatically sending a shipping confirmation to the end customer. For all other steps, asynchronous calls are more robust because carrier systems can tolerate short outages without blocking the SAP transaction.
The following fields are particularly critical for mapping: recipient address with ISO country code, weight and dimensions per package, value of goods and currency for customs purposes, Incoterms, and the customs tariff number (HS code). Multilingualism is relevant for cross-border shipping in Europe: shipping documents must be issued in the local language or in English, depending on the destination country. Interfaces should therefore support voice control via the ISO 639 language code.
Pro tip: Implement a retry pattern with exponential backoff for failed carrier API calls. Define a dead-letter queue for messages that are not delivered after three attempts and trigger an alert there. This prevents silent failures where deliveries are marked as "sent" in SAP, but no label has been generated.
What capabilities must interfaces for SAP GTS and customs clearance provide?
SAP Global Trade Services (GTS) automates foreign trade activities, including export declarations, sanctions list checks, and shipping procedures, thereby reducing delays at borders. Interfaces must initiate these processes and supply them with accurate data.
Mandatory data for GTS transitions:
- Invoice basic data: Invoice number, date, currency, total value
- Commodity codes (HS code / customs tariff number) per item
- Recipient and sender information with complete addresses
- Incoterms and delivery terms
- Country of origin of the goods
- Packaging type, weight and dimensions
- Export control classification (ECCN or AL number)
The transfer of deliveries and invoices to SAP GTS is asynchronous via RFC.Failed replications are logged and can be restarted once the cause has been resolved. GTS automatically decides whether to apply the standard or simplified export declaration procedure.
Missing or incorrect mapping settings are the most common cause of replication errors in GTS integrations. Logs show the exact cause of the error; after correcting the mapping, the transfer can be manually restarted. A direct link between the shipping document and the customs declaration (e.g., ATLAS) avoids manual duplication of effort.
Pro tip: For GTS replication, set up a separate RFC destination with its own error log. Check the transaction daily. /SAPSLL/EXPORT_TLOG on failed transfers. Automated alerts for queue backlogs prevent shipments without a valid export declaration from leaving the warehouse.
For companies that Customs clearance and export documents For those who want to automate without fully implementing GTS, external platforms offer a lean alternative.
What does a concrete implementation checklist look like?
| Step | Controller | SAP transaction / artifact | Test criterion |
|---|---|---|---|
| Create RFC destination | Base Administrator | SM58 | Connection test successful |
| Configure IDoc partner agreement | SAP-Berater | WE20 | Outbound IDoc is generated |
| Set up message control | SAP-Berater | NACE / V | Message triggers upon delivery |
| Define mapping (fields, language, units) | Integration developer | CPI-Iflow / PI-Mapping | All required fields filled |
| Configure authentication (OAuth / API key) | Security Officer | BTP Cockpit / SM58 | Certificate valid, connection encrypted |
| Create carrier test profile | Logistics Coordinator | Carrier Gateway | Test label is generated |
| Perform integration tests | Test team | WE02 / SM58 | No errors in logs |
| Set up monitoring alerts | Base Administrator | RZ20 / CPI Alerting | Alert triggered upon error |
| Plan parallel operation / cutover | Project Manager | Project plan | Fallback process documented |
For unit tests, the transaction is recommended. WE19This allows IDoc messages to be created and processed manually. Carrier test profiles should cover all relevant shipping scenarios: standard parcel, express shipping, hazardous materials, and oversized goods. The cutover plan must include a documented fallback process in case the interface fails during production.
Pro tip: Implement the shipping interface consistently without modifications. Use Business Add-ins (BAdIs) or Enhancement Spots instead of direct ABAP modifications. This will pay off at the latest during the S/4HANA upgrade, when modified objects have to be manually checked and adjusted.
How do you monitor and resolve errors in SAP shipping interfaces?
Four transactions cover the majority of the daily monitoring work:
- SM58: Error log for asynchronous RFC calls. All transmissions that did not reach the target system are logged here. The built-in retry function restarts failed calls as soon as the cause is resolved.
- WE02 / WE05: IDoc overview and status monitor. WE02 displays all IDocs with their status, while WE05 filters specifically for errors. Both transactions are the first point of contact for notifications about undelivered shipments.
- BD87: Reprocessing of faulty IDocs. After correcting the error (e.g., incorrect mapping, missing partner agreement), IDocs can be directly re-initiated here.
- SLG1: Application log. Many GTS and shipping processes write detailed error messages to SLG1, which SM58 and WE02 do not display.
A robust logging strategy includes proper LUW (Logical Unit of Work) handling, idempotent processing on the receiver side, and dead-letter queues for persistently failing messages. RFC destinations should be regularly checked for availability, ideally via an automated health check.
Pro tip: Configure automated notifications in SAP system monitoring (RZ20) or CPI alerting that immediately trigger an email or a message in the ticketing system when there is an increase in erroneous IDocs in BD87 or a queue backlog in SM58. Daily manual checks are insufficient in production shipping environments.
Parcel International: Automated Shipping Integration in Practice
A typical integration project with Paket International follows a clear pattern: SAP generates a delivery message via IDoc outbound, which is transmitted to the Paket International platform via CPI or a direct REST API. The platform handles carrier selection, label printing, and customs calculation, returns the tracking number, and automatically updates the SAP delivery document.
Advantages for the company:
- Manual data entry during carrier handover is completely eliminated.
- Customs duties and shipping costs are calculated in real time, without full GTS implementation.
- Shipment tracking is handled centrally via the Paket International Dashboard, not via multiple carrier portals.
- New carriers are onboarded on the platform side, without SAP adjustments.
Automated customs clearance without manual intervention is the decisive advantage for companies with regular shipments to third countries. Paket International calculates customs fees and creates Export documents This happens automatically as soon as the delivery data arrives from SAP. This reduces delays at borders and lowers the effort required for customs communication.
The integration is designed for a clean core: no ABAP modifications in the SAP core, no proprietary add-ons that cause problems during S/4HANA upgrades. Companies planning a proof of concept can contact us directly via the Paket International platform.
Paket International accelerates your SAP shipping integration
For those looking to connect SAP with a high-performance shipping system without months of middleware projects, Paket International offers a ready-to-use solution. The platform provides REST API and plugin integrations that can be seamlessly integrated into existing SAP landscapes, whether S/4HANA, ECC, or Cloud.
The specific advantage over a purely in-house development: Carrier connections to DHL, UPS, FedEx, DPD, and DB Schenker are already in place. Automated customs clearance and real-time shipment tracking operate without manual intervention. Multi-carrier shipping software Supports country-specific requirements and multilingualism for cross-border shipping in Europe.
For IT managers seeking a quick start: Paket International provides a proof of concept upon request. Get in touch to discuss which integration option best suits your SAP landscape.
Sources
- SAP Global Trade Services — Documentation (GTS)
- Setting up integration into outbound processes — SAP Learning
- Carrier Cloud Connect — Consolut