Currently Being Moderated

image

Partner-delivered Enterprise Services (PdES) 

Delivering Enterprise Services (ES) forms a crucial element to SAP's SOA strategy. By today, SAP has released roughly 3000 productized services over the course of the last two years. More and more partners and customers now actively seek to learn SAP's best practices on how to built their very own Enterprise Services; services with increased usability and reuse inside and beyond one's organization. For Busy People: Understanding ES Governance + ES Methodology = ES Harmonization is hence experiencing broad momentum.

In early 2008, SAP launched the initiative Partner-delivered Enterprise Services (PdES). The initiative targeted on setting up a framework for partners, providing them everything necessary to model, define, implement and ultimately deliver their own methodology-compliant services. 16 pilot partners from all over the world successfully completed  this journey and are now publicly presenting their offerings similar to the look and feel of the ES Workplace on SDN, along with the offerings from PdES: SAP Custom Enterprise Services.

Provisioning and Consumption

Why build Partner delivered Enterprise Services?

Each one of these 16 partners was driven by either one or both of the following use cases. On the one hand side we have the Software Solution Partners (or Independent Software Vendors) and Technology Partners, who service-enable their existing software solution to achieve harmonization for easier integration with SOA scenarios (and of course SAP) and on the other hand we find System Integrators or Service Partners, who aim at filling gaps in ES Bundles Providing Enterprise Services for SAP ERP to deliver Enterprise Services based on their own or existing SAP implementation as basis for individual customer projects. A core motivation for both is clearly the alignment with SAP, wherever possible. This alignment refers to the consistent reuse of already existing Business Objects from SAP - specifically on a semantic level - to ensure smooth integration and/ or transition to SAP and standard. This does, especially to the partner community, offer a clear value proposition:

  • Harmonized Integration into SOA; for example, through the use of interface patterns to structure content or the use of Global Data Types to achieve data type alignment.
  • New opportunity for consulting services; for example, the gained knowledge can potentially be used as unique differentiator for future customers.
  • New marketing element ‘PdES', .e.g. via dedicated information on the partner services on SDN

If you still wonder "WHY should I build Enterprise Services?" you should definitely watch Hans-Joachim Odlozinski's screencam answering the essential question of "Why should I build Enterprise Services?". He describes the overall value and benefits you can gain from embarking on the journey towards PdES. Check out his screencam!

How to start with Partner delivered Enterprise Services?

This architecture series is now targeted to provide you first hand insights into the entire process of delivering methodology-compliant services following SAP's best practices. Following this screencam you will learn how to model, how to define and how to implement your services to come. As a special goody, we will introduce - for the very first time - an automated wizard with integrated governance that you may use free of charge to swiftly create your methodology compliant services.

Ride in the tube of SOA and learn how to deliver your services based on SAP's modeling and definition methodology. Stay tuned for more information and jumpstart your PdES journey with the next blog on SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service - Outlining the ‘way to deliver' services (Part 2).

 

In the following the links to all blogs and screencams from the PdES Architecture Series:
1.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service - Introduction (Part 1) - Screencam (This Blog)
2.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service - Outlining the ‘way to deliver' services (Part 2)
3.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service - Modeling Services (Part 3) - Screencam
4.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Defining services (Part 4)  - Screencam
5.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Leveraging a wizard to automate Service Creation (Part 5) - Screencam + Wizard
6.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Implementing Services in Java (Part 6) - Screencam
7.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Implementing Services in .NET (Part 7 - provided by Nakisa) - Screencam
8.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Implementing services in ABAP (Part 8) - Screencam
9.      SAP Co-Innovation Lab Architecture Series: Custom Development delivered Custom Enterprise Services (Part 9) - Screencam
10.    SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services - Summary (Final Part) - Certification

Comments

Actions

Filter Blog

By date: