Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
SAP integration · Lesson

SOAP

Quick answer

Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it.

Key takeaways

  • SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or…
  • WSDL contracts defining the service.
  • XML payloads and WS-* standards.
  • Watch out: Wrong tool for the integration style.

What SOAP integration does

SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or consumer. Middleware (PI/PO) heavily used SOAP for structured, contract-based integration between enterprise systems.

Key aspects

  • WSDL contracts defining the service.
  • XML payloads and WS-* standards.
  • SOAMANAGER for configuration.
  • WS-Security for message security.

When to use it

Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it. For new lightweight integrations, REST/OData is generally preferred.

Common pitfalls

  • Wrong tool for the integration style.
  • Ignoring monitoring/error handling.
  • Point-to-point instead of governed integration.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. Which statement is true of SOAP?

    • A. SAP implementation projects deliver SAP into a business, from strategy and design through build, test and…
    • B. Middleware (PI/PO) heavily used SOAP for structured, contract-based integration between enterprise systems.
    • C. Configuring Fiori makes apps available and correct for users: activating services, assigning catalogs/groups…
    Show answer

    B. Middleware (PI/PO) heavily used SOAP for structured, contract-based integration between enterprise systems.

    Covered in the “What SOAP integration does” section of this lesson.

  2. Which of these also applies to SOAP?

    • A. Misconfigured RFC destinations (SM59).
    • B. For new lightweight integrations, REST/OData is generally preferred.
    • C. Not setting parameter IDs for constantly-repeated field values.
    Show answer

    B. For new lightweight integrations, REST/OData is generally preferred.

    Covered in the “When to use it” section of this lesson.

  3. Which part of the Learn SAP curriculum covers SOAP?

    • A. SAP fundamentals
    • B. SAP integration
    • C. SAP FI
    Show answer

    B. SAP integration

    This lesson sits in the SAP integration section of the Learn SAP course.

Frequently asked questions

What does SOAP stand for, and how is it used in SAP integration?

SOAP integration connects systems to SAP using XML web services with formal WSDL contracts, the classic service-oriented style, still used in enterprise SOA and via middleware.

What does SOAP exchange data with?

Use SOAP where a formal contract or WS-* capabilities are required, or to integrate with systems/middleware that mandate it.

What is the practical takeaway on SOAP?

SOAP integration exchanges XML messages defined by WSDL contracts, with SAP as provider (exposing services via SOAMANAGER) or consumer.

What tends to go wrong with SOAP in SAP integration?

Wrong tool for the integration style. Ignoring monitoring/error handling. Point-to-point instead of governed integration.
CallWhatsAppEnquire