Skip to Content
Author's profile photo Former Member

SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3)

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 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:

Screenshot of the Screencam


The detailed storyboard is outlined in the following:


*Create a Process Component Model = Sales Order Processing</li></ul><p> </p><ul><li>Create a Business Object</li></ul><p>Name:  Sales Order</p><p>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.”</p><p>SAP NW Attribute – BO Type: BPO</p><p>(Properties) Name: Placed Center and Aligned Middle</p><p> </p><ul><li>Create a Service Interface</li></ul><p>Name: Manage Sales Order In</p><p>Description/ Definition: This inbound service interface contains the operations that the sales clerk can use to process sales orders in sales and distribution.</p><p>SAP NW Attribute – Technical Name: SalesOrderProcessingManageSalesOrderIn</p><p>SAP NW Attribute – Direction: In</p><p>(Properties) Name: Placement at the top and aligned centered</p><p> </p><ul><li>*Intermediary Step for creation of SO</li></ul><p>Operation uses/ is realized by <BO></p><p>Operation is positioned within Interface               </p><p>Connection occurrence is checked</p><p> </p><p>[ ||SOA300||||G|%5d%5d|]</p><ul><li>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):

 !|height=1|alt=|width=1|src=|border=0!!|height=411|alt=Example Model|width=667|src=|border=0!</body>

Assigned tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Thanks for the post. I had difficulties in viewing the video. I couldn't really figure out the details in the demo..