Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata




From SRM 7.0 on we have the possibility to transfer documents to ECC using ESOA. This leads to some configurations and requirements that we also will see in this document.


First to explain what is ESOA we need to clarify the SOA (Service Oriented Architecture) concept.

  • SOA is an idea of creating composite applications based on reusable building blocks using open standards like Web Services, WSDL, SOAP, UDDI. Any system that provides web services (which are self-contained and self-describing) can be termed as SOA enabled. The provider of the service registers the service over UDDI in the form of WSDL. The consumer searches the UDDI for the desired service and invokes it. There can be multiple web services (from multiple providers) for the same application (eg. purchase order creation).
  • ESOA (former ESA - Enterprise Service Architecture) is SAP's own version of SOA (more specialized version of SOA). SAP calls the services developed over the Business Process Platform and Enterprise Services. The enterprise services are different that web services in the sense that there will only one generic service (registered at UDDI) for one application. Enterprise Services are web services with business value and are reusable parts of business processes. Enterprise Services Repository - part of SAP NetWeaver is central point of ESOA and starting point for creating applications. ESOA is using xml documents for the data exchange.


On SRM7.0 with ECC 6.0 EHP4 on the ESOA is used within the scenarios.

Backend system ECC 6.0 EHP4  type ERP_4.0 is using adaptor /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP (class interface)


Use SRM 7.0 with ECC 6.0 EHP4 functionalities with XI/PI. In this scenario, you will need to configure PI/XI.

You have the option to configure PI server to handle the xml traffic between Your systems.

Many of the ESOA interfaces of SRM 7.0 can only be used with XI/PI. For these interfaces, you will not be able to use ESOA and the new functionalities of EHP4 without configuring a PI system.

Example is the interface SupplierPortalTradingPartner_CreateOrChange_In (from namespace This interface does only support usage with PI system.
If you do not require service hierarchy for example (one of the new functionalities), you may try to configure the system using backend system ERP_3.0 (that use RFC and will not call XI/PI)


PI-independent Enterprise services

As of SRM701 and ERP6 EHP5 (only for EHP5 and higher) You can use PI independent Enterprise services without need for PI system.

This is only supported for a limited number of xml interfaces. These interfaces do have own Web service definitions, so they do not need PI system for the data exchange.
Some examples:

Contract replication from SRM to ECC:
SRM side: PurchasingContractSRMReplicationRequest_Out (
ECC side: PurchasingContractSRMReplicationRequest_In (, web service definition: PurchasingContractSRMReplicati)

Purchase Requisition replication to SRM:
ECC side: PurchaseRequestERPSourcingRequest_Out (
SRM side: PurchaseRequestERPSourcingRequest_In  (, web service definition: /SAPSRM/PurchaseRequestERPSour)
and the related confirmation xml to set the status of the PR:
SRM side: PurchaseRequestERPSourcingConfirmation_Out (
ECC side: PurchaseRequestERPSourcingConfirmation_In (, web service definition: PurchaseRequestERPSourcingConf)

Contract replication from CLM to SRM:
PurchasingContractSRMCreateRequestConfirmation_In (

Purchase Order creation from SRM Shopping cart in Classic scenario:

outbound SRM side: PurchaseOrderERPRequest_Out_V1 (
inbound ECC MM side: PurchaseOrderERPRequest_In_V1 (, web service definition: PurchaseOrderERPRequest_In_V1)



PurchaseOrderERPContractReleaseNotification_In  ( - MM side: PurchaseOrderERPContractReleaseNotification_Out ( info about this scenario here)


You can configure these Web services using the transaction SOAMANAGER

Please read following SAP Notes and the contained documentation about this topic:

SAP Note: 1268336 - Synchronous peer-to peer Services Configuration

SAP Note: 1672909 - SRM / ECC prerequisite for configuration of PI-Independent


Related Content

Related Documents

Basic Settings for SAP Enhancement Package 1 for SAP SRM 7.0

Related Notes

SAP Note: 1270081 - Trouble shooting SOA Services

SAP Note: 817920 -  XI Readiness Check 3.0/7.0, 7.1, 7.3

SAP Note: 1286936 -  PI configuration for SRM additional information

SAP Note: 1268336 - Synchronous peer-to peer Services Configuration

SAP Note: 1672909 - SRM / ECC prerequisite for configuration of PI-Independent


  1. Hi Melina

    Thanks for all good work from offline approval to e-SOA Material and information. I enjoy to read all your wiki summary.

    I request you to write some wiki on error treatment on e-SOA Purchase order and Contract.

    It indeed helps other.


  2. Guest

    Good One Melina. Really informative.