ESWorkplace and ESR adopt different classifications for Services...but why?

[Former Member]

Hi,

While experimenting with ESOA I noticed Services are classified differently in ES Workplace (http://erp.esworkplace.sap.com/) and ESR (http://sr.esworkplace.sap.com/)!

Can someone explain me the reason of it?

Thanks

Pietro

As example, take the EmployeeBenefitsParticipationHealthPlanByEmployeeQueryResponse_In service

In ESWorkplace it is classified as

- Service Operation - Read Health Plan

- Service Interface - Manage Employee Benefits Participation In

- Business Process - Benefits Management

- Software Component - ERP

On the other hand, in ESR, the same service is classified only as

- SoftwareComponentVersion - ECC-SE / 603

[Former Member]

Hi Pietro,

There are no two different classifications.

At ESWorkplace, it shows the description of the Service and how it is bundled in SAP Packages ie. ES Bundles. It contains the metadata of Enterprise Services all at one place.

At SR(Service Registry), classification can be different . SR is used by service consumer to search for different available services and the WSDL information for it.It is used for consumption of services by external/internal entities.

If you have some ES available with ESR, it is not mandatory that the same ES would also be available with Service Registry. It would be available only if it is published with the UDDI registry.

The example u posted contains description for service operation(ist one)

and in second case, merely a Software Component Version in ESR.

Service Interface Manage Employee Benefits Participation In belongs to Software Component ERP and

Service Operation EmployeeBenefitsParticipationHealthPlanByEmployeeQueryResponse_In

belongs to Service Interface Manage Employee Benefits Participation In, Software Component Version -ECC-SE / 603.

1 Software Component----

---

>* SW Component Versions

Regards,

Piyush