Modeling services constitutes the creation of a visual representation (read: picture) of all the functionality provided via individual services in one organization (as well as its interactions to the outside world). To this end, the Enterprise Services Builder (ES Builder) offers a modeling environment for creating various perspectives based on a set of predefined methodology-compliant models as part of the Enterprise Services Repository (ESR). This model-driven service development provides a broad set of advantages which are elaborated in the ESR Documentation, along with explanations on SAPs modeling entities. Modeling services is hence the first step in outlining the service's functionality and the first step in creating your own service. Here's how it works:

• Create a Process Component Model
• Create a Business Object
• Create a Service Interface
• Create an Operation

The attached screencam is targeted to guide you through exactly these steps. In order to make it as easy as possible the common example of a "Read Sales Order" service has been chosen. You may therewith directly learn each of the steps necessary to model your service, without worrying about the business context. This is something that you may then easily do afterwards as transfer based on the Sales Order BO + correlated services within the ES Workplace. So get started and have a look at the screencam:

 

The detailed storyboard is outlined in the following:

 

• Create a Process Component Model = Sales Order Processing

 

• Create a Business Object

Name:  Sales Order

Description/ Definition: "An agreement between a seller and a customer concerning the sale and delivery of goods, as well as any services that are associated with these processes, on a specific date, for a specific quantity, and for a specific price."

SAP NW Attribute - BO Type: BPO

(Properties) Name: Placed Center and Aligned Middle

 

• Create a Service Interface

Name: Manage Sales Order In

Description/ Definition: This inbound service interface contains the operations that the sales clerk can use to process sales orders in sales and distribution.

SAP NW Attribute - Technical Name: SalesOrderProcessingManageSalesOrderIn

SAP NW Attribute - Direction: In

(Properties) Name: Placement at the top and aligned centered

 

• *Intermediary Step for creation of SO

Operation uses/ is realized by <BO>

Operation is positioned within Interface              

Connection occurrence is checked

 

• Create an Operation

Name: Read Sales Order

Description/ Definition: Query to and response from Sales Order Processing to read a sales order.

SAP NW Attribute - Technical Name: SalesOrderProcessingManageSalesOrderIn.ReadSalesOrder

SAP NW Attribute - Mode: Synchronous

SAP NW Attribute - Message type request: Sales Order By ID Query

SAP NW Attribute - Message type response: Sales Order By ID Response

(Properties) Message Type Request: Add + Change Placement + Change Alignment

(Properties) Message Type Response: Add + Change Placement + Change Alignment

 

... so that you finally come to the following result (based on the existing Business Object Sales Order and the Read Sales Order operation):

 

 

These steps exhaustively embrace all the steps required within the modeling phase of your PdES journey. In case you would like to learn a little bit more about the surrounding aspects, such as the creation of Software Components, Namespaces etc, you should have a close look at a previous coverage on this topic within "360° View on enterprise SOA: Provide and consume your own enterprise services - Model and define your own Enterprise Services (Part 5)" and especially the therein attached screencam. Please be adviced that only the screencam attached to this blog does constitue the latest and correct perspective on modeling.

 

One aspect that you will have clearly recognized... methodology knowhow is key. The screencam shows you all the steps, the clicks but not which pattern to apply when, which naming to choose according to naming conventions, how to leverage existing SAP assets and entities, etc. This is something that we exclusively offered to our PdES partners from 2008 as face to face trainings. Now, the easiest way for you to embrace this knowledge is to join of the global SOA 300 training courses or wait just a little bit until we set the ES methodology wizard free to the world.

 

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 "Defining Services".

 

In the following the links to all blogs and screencams from the PdES Architecture Series:
1.      Introducing the Story Board - Screencam
2.      Outlining the ‘Way to Deliver' SAP methodology-compliant Services
3.      Modeling Services - Screencam (This Blog)
4.      Defining Services  - Screencam
5.      Leveraging a wizard to automate Service Creation - Screencam + Wizard
6.      Implementing Services in Java - Screencam
7.      Implementing Services in .NET - Screencam
8.      Implementing Services in ABAP - Screencam
9.      Custom Development delivered custom enterprise services - Screencam
10.    Summarizing the PdES Architecture Series - Certification