Skip to end of metadata
Go to start of metadata

Content

 

Overview

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.

WHAT IS ESOA? 

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 x SRM X  ECC

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

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

To use SRM 7.0 with ECC 6.0 EHP4 functionalities it is mandatory to use the XI/PI. In this scenario, you will need to configure PI/XI.

  • If you use SRM 7.0 and don't want to use XI/PI you will not be able to use ESOA and the new functionalities of EHP4. 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)
  • As of SRM701 and ERP6 EHP5 (only for EHP5 and higher) customer can use PI independent Enterprise services without need for PI system.

 

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

  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.

    Muthuraman

  2. Guest

    Good One Melina. Really informative.