Automated order data sync between SAP and ServiceNow using IntegrationHub

BPM ServiceNow
, , , , , , , ,
1

Sharing our implementation of automated order synchronization between SAP and ServiceNow that eliminated manual data entry and significantly improved our order fulfillment SLAs.

Business Challenge: Our operations team was manually entering order data from SAP into ServiceNow for tracking and approvals, leading to delays (average 4-hour lag), frequent data entry errors, and missed SLAs on order processing. With 200+ daily orders, this was unsustainable.

Solution Approach: We leveraged IntegrationHub’s SAP spoke with Flow Designer to create event-driven bidirectional sync. The focus was on real-time order status updates and accurate delivery date mapping between systems. Key requirements included handling SAP’s order status codes and mapping them to ServiceNow’s workflow states while maintaining data integrity across both platforms.

2

This is exactly what we’ve been planning! A few questions: How did you handle authentication between the systems? Did you use the out-of-box SAP spoke or build custom integrations? And what’s your approach for error handling when SAP is temporarily unavailable?

3

Let me provide the complete implementation details that address all the questions:

IntegrationHub SAP Spoke Usage: We utilized the certified SAP ERP spoke (version 2.3 in Tokyo release) which provides pre-built actions for common SAP operations. The spoke configuration includes:

  • Connection alias pointing to our SAP ERP system
  • OAuth 2.0 credentials with dedicated integration service account
  • Connection timeout set to 30 seconds with retry enabled

Key spoke actions we use:

  • Read Sales Order (BAPI_SALESORDER_GETDETAIL)
  • Update Order Status (BAPI_SALESORDER_CHANGE)
  • Query Delivery Status (custom BAPI we created with SAP team)

The spoke abstracts the RFC complexity - we just map input/output parameters in Flow Designer.

Flow Designer for Event-Driven Sync: We built three primary flows:

  1. SAP to ServiceNow Order Creation Flow:

    • Trigger: REST endpoint receives webhook from SAP
    • Validates order data structure
    • Checks for duplicate orders using order number lookup
    • Creates ServiceNow order record with mapped fields
    • Sends confirmation back to SAP

  2. Order Status Sync Flow (Bidirectional):

    • Trigger: Business rule on ServiceNow order status change OR scheduled job polling SAP every 15 minutes
    • Retrieves current status from both systems
    • Applies transformation rules based on mapping table
    • Updates target system
    • Logs sync activity for audit trail

  3. Delivery Date Reconciliation Flow:

    • Trigger: Daily scheduled run at 2 AM
    • Queries orders with delivery dates in next 14 days
    • Compares dates between systems
    • Flags discrepancies for review
    • Auto-corrects if difference is within 24-hour tolerance

Order Status and Delivery Mapping: This was our most complex piece. We created a custom table ‘u_sap_status_mapping’ with these fields:

  • SAP Status Code (e.g., ‘CRTD’, ‘REL’, ‘PICK’, ‘SHIP’)
  • ServiceNow State (mapped to integer values)
  • Direction (SAP->SNOW, SNOW->SAP, or Both)
  • Transformation Rules (JSON field with conditional logic)

For delivery dates, we established these mapping rules:

  • SAP ‘Requested Delivery Date’ → ServiceNow ‘Due Date’
  • SAP ‘Confirmed Delivery Date’ → ServiceNow ‘Expected Delivery’
  • SAP ‘Actual Goods Issue Date’ → ServiceNow ‘Delivered Date’

The flow includes date validation logic - if dates differ by more than 24 hours between systems, it creates a task for manual review rather than auto-syncing potentially incorrect data.

Results After 6 Months:

  • Order processing time reduced from 4 hours to 12 minutes average
  • Data entry errors eliminated (was 8-12 per week)
  • SLA compliance improved from 73% to 97%
  • 200+ orders synced daily with 99.4% success rate
  • Failed syncs (usually due to network issues) auto-recover within 1 hour

Key Lessons Learned:

  1. Invest time in comprehensive status mapping upfront - it’s critical
  2. Build robust error handling and retry logic from day one
  3. Include data validation steps before syncing to prevent bad data propagation
  4. Maintain audit logs of all sync activities for troubleshooting
  5. Work closely with SAP BASIS team for RFC configuration and performance tuning
  6. Test thoroughly with production-like data volumes before go-live

The IntegrationHub approach gave us a no-code/low-code solution that our business analysts can maintain without deep SAP technical knowledge. Flow Designer’s visual interface makes the logic transparent and easier to troubleshoot than custom scripted integrations.

4

How did you handle the order status mapping? SAP order statuses are pretty granular and don’t always have direct equivalents in ServiceNow. Did you create a custom mapping table, or use some transformation logic in the flow?

5

Really interested in the Flow Designer setup. Did you use scheduled flows or event-triggered? How are you capturing the SAP order creation events in real-time? We’re struggling with the event detection piece - SAP doesn’t naturally push events to external systems, so curious how you solved that trigger mechanism.