Skip to Content

image

Delivering your very own SAP methodology-compliant services is a very structured and easy to follow procedure. This procedure starts with looking into the uniqueness of the business requirements and how they can be addressed by means of reusable harmonized service candidates. These services are consequentially modeled, defined, implemented and ultimately published out into the market. The entire journey can hence be distilled into two major activities:

Way to deliver services

Analyzing

… the business context, starts with the specification of the business requirements based on a given scenario description. This information is used to derive a consumer model that depicts the overall process being addressed, broken down into individual fine granular process steps that can then be correlated to one or multiple service candidates. The consumer model is matched with the provider model – a model representing all existing services and their underlying functionality. Suitable services can be ignored for the time being as they can simple be reused at a later point in time for consumption. The missing services are the ones of interest as it is there where your PdES journey starts. These are the services that have not yet been built but are necessary to fulfill the initially stated business requirements. On the one hand side partners with their own solution(s) may find this initial task very easy as their consumer and provider model have nearly no overlap, on the other hand partners with deep integration knowledge might need more time in this initial information gathering process. Further information on consumer model and provider model can be found in the a TechEd 2007 session on “Service Modeling” (From page 24 onwards).

The most important and initially most difficult activity for all partners is the next one: the semantic alignment. Alignment refers to the consistent reuse of existing semantics to ensure smooth integration and/ or transition to SAP, Partner environments based on the same methodology and of course the open standards embraced within the methodology. These semantics can be pinpointed to primarily the Business Objects (BO). The BO is the key ingredient within your methodology-compliant service: Getting this one right, makes the rest of work a rather easy undertaking. Hajo Odlozinski gets into some of the reasons why BOs are so important and how they fit into the entire picture of PdES, so check out his screencam on “WHY should I build Enterprise Services?” mentioned already in SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Introduction (Part 1).

The ultimate goal of ‘analyzing’ is to set the stage for For Busy People: Understanding ES Governance + ES Methodology = ES Harmonization. Alignment is thus an essential prerequisite before the physical creation phase of the service, which starts with…

 

Provisioning

… of the service, describes the procedure to build one or multiple services. It is a generally applicable process that each SAP methodology-compliant service in its creation phase has the pleasure to go through. Providing services forms the prerequisite to consuming services, which depicts the usage of those services being built. The four fold approach on how services are provided is elaborated in details within “For Busy People: Understanding Provisioning versus Consumption“,

The focus of this blog series and attached screencams is exactly to guide you through the different steps of modeling, defining and implementing your services*; so that you may ultimately deliver your own SAP methodology-compliant services. Deliver these complementary to existing SAP Enterprise Services and deliver these as differentiator for your own solution. Keep in mind that the better and more diligent your initial investments of time and effort are in aligning your semantics the easier it gets along the way.

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 move on in your PdES journey with the next blog on “SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3)“.

 

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
2.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Outlining the ‘way to deliver’ services (Part 2) (This Blog)
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.    The specified item was not found.Certification

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Prakash Savla
    I am unable to view any of the screencams uploaded. pls priovide instructions on how to use the wizard uploaded here – is there a latest version available ? Also how is it to be installed ?
    (0) 

Leave a Reply