SAP Integration with Third-Party Apps

No enterprise runs SAP alone. Every SAP landscape coexists with non-SAP applications — CRM, HR, e-commerce, marketing, logistics, banking, and dozens of specialized tools. These third-party applications hold data that SAP needs, and SAP holds data that they need. Integration bridges the gap. This topic covers the practical approaches, patterns, and considerations for connecting SAP to the most common third-party application categories.

CRM Integration: Salesforce to SAP

Salesforce is the world's leading CRM. Companies that use both Salesforce and SAP need to synchronize customer data, opportunity-to-order flows, and product catalog information.

Common Salesforce-SAP Integration Scenarios

OPPORTUNITY TO ORDER:
[Salesforce Opportunity Won] → [CPI] → [SAP SD Sales Order Created]
  CPI maps Salesforce Account to SAP Customer
  CPI maps Opportunity Products to SAP Materials
  SAP order number written back to Salesforce Opportunity

CUSTOMER SYNC:
[SAP Customer Master Changed] → [CPI] → [Salesforce Account Updated]
  Runs daily via timer trigger
  Value mapping for industry codes, payment terms

INVOICE SYNC:
[SAP FI Invoice Posted] → [CPI] → [Salesforce Invoice Object Updated]
  Partners see invoice status in Salesforce without SAP access

Connection Method

Use the HTTP adapter with OAuth 2.0 to call Salesforce REST APIs, or use Open Connectors' pre-built Salesforce connector. For real-time triggers from Salesforce, configure Salesforce Platform Events or Outbound Messages to call a CPI HTTPS endpoint when records change.

HR Integration: Workday / SuccessFactors to SAP

HR systems hold the master record of employees. Payroll, access management, and organizational structures in SAP must stay synchronized with the HR system.

Common HR Integration Scenarios

NEW HIRE ONBOARDING:
Workday: New employee created
      ↓ (daily batch sync via CPI)
SAP HCM: Employee master record created
      ↓ (event-driven via CPI)
IT Systems: User account created, email provisioned, hardware requested

ORGANIZATIONAL CHANGE:
Workday: Department reorganization
      ↓
SAP: Cost centers updated, reporting hierarchy changed

PAYROLL:
SAP HCM runs payroll calculations
      ↓
Workday: Payroll results written back for central HR reporting

Key Consideration: Data Ownership

Define clearly which system is the master of record for each data field. Employee name, start date, and job title are typically mastered in the HR system. Bank account for payroll is typically mastered in SAP. Conflicts arise when both systems allow updates to the same field — establish the rule and enforce it through validation in your integration.

E-commerce Integration: Shopify / Magento to SAP

Online stores generate orders, update inventory, and collect payments. SAP must reflect these transactions for fulfillment, accounting, and inventory management.

Order-to-Cash via E-commerce

[Shopify: Order placed by customer]
      ↓ webhook fires immediately
[CPI: Receives order payload (JSON)]
      ↓
[CPI: Validates and maps to SAP SD format]
      ↓
[SAP SD: Sales order created]
      ↓
[CPI: Reads back SAP order number and delivery date]
      ↓
[Shopify: Order fulfillment status updated]
      ↓
[SAP WM/EWM: Pick order generated]
      ↓
[Goods shipped → SAP SD delivery confirmed]
      ↓
[Shopify: Order marked as shipped, tracking number added]
      ↓
[SAP FI: Invoice posted and payment collected]

Inventory Sync

Shopify must reflect actual SAP stock levels so customers cannot order products that are out of stock. A scheduled CPI iFlow runs every 15-30 minutes, reads stock levels from SAP MM using the stock availability OData API, and pushes updates to Shopify's inventory API for all products below a threshold.

Banking and Payment Integration

Banks provide statement files, payment confirmations, and fraud detection data that SAP FI must process for accurate financial records.

Bank Statement Processing (MT940 / CAMT.053)

[Bank SFTP server: drops daily statement file at 06:00]
      ↓
[CPI SFTP adapter: polls and picks up file]
      ↓
[CPI: Parses MT940 or CAMT.053 format]
      ↓
[CPI: Maps to SAP electronic bank statement format]
      ↓
[SAP FI: Posts statement, auto-clears open items]
      ↓
[Unmatched items flagged for manual review in SAP]

Logistics and Carrier Integration

Shipping carriers (FedEx, UPS, DHL) provide tracking updates that customers and operations teams need. SAP WM creates shipments; carriers execute them; tracking data flows back.

[SAP: Creates shipment, generates label request]
      ↓
[CPI: Calls carrier API, gets label and tracking number]
      ↓
[SAP: Tracking number stored on delivery document]
      ↓
[Customer: Receives tracking number via email (triggered from SAP)]
      ↓
[Carrier: Provides webhook for delivery events (shipped, out for delivery, delivered)]
      ↓
[CPI: Updates SAP delivery status in real time]

Marketplace Integration (Amazon, eBay)

Companies selling on multiple marketplaces need inventory and order synchronization across all channels while keeping SAP as the financial and inventory system of record.

Challenges Specific to Marketplace Integration

Each marketplace has unique order, inventory, and fulfillment APIs with different data models
Marketplaces generate high order volumes during peak periods (Black Friday) that integration must handle at scale
Inventory must be allocated across multiple channels without overselling
Marketplace fee accounting must reconcile with SAP FI

General Third-Party Integration Checklist

Before building any third-party integration, answer these questions:

API availability: Does the third-party application have an API? What protocols does it support (REST, SOAP, EDI)?
Authentication: What authentication method does it require? Do API keys rotate and how often?
Rate limits: What are the API rate limits? Can they handle your expected message volume?
Webhooks: Does the application support outbound webhooks for real-time triggers?
Data ownership: Which system is the master of record for each shared data field?
Error handling: What happens to data in SAP if the third-party system is unavailable? What is the acceptable lag?
Volume expectations: How many messages per hour/day at average and peak load?
Data residency: Does the third-party application store data in approved regions for your compliance requirements?

Documenting answers to these questions before writing the first line of iFlow configuration prevents 80% of late-stage integration project problems.

Previous lesson

Back to course

Next lesson