The previous blog of this series - Modeling Services (Part 3) - showed the path of creating the model entities (process component model, business object, etc.) for the Read Sales Order scenario. The next step is to derive the actual service definition from the model ultimately receiving a design time WSDL.

The Enterprise Services Builder (ES Builder) tool as part of the Enterprise Services Repository (ESR) remains the working environment for the steps of

• Creating service interface and operation definitions
• Assigning the previously created model entities to the respective definitions
• Creating Message Types and Fault Message Types
• Creating Message Data Types
• Detailing the message structure down to the element level
• Data typing

The attached screencam is targeted to guide you through exactly these steps building upon the ESR content that has been created in the screencam in the previous blog on service modeling.

We recommend reading Dirk Richtsteiger's and Michael Seubert's blog on the SAP Global Data Types Catalog. It gives a great introduction to the concept of Global Data Types (GDTs). Here you will find as well the link to the GDT catalog in PDF format. This PDF document not only provides the actual catalog of Core Data Types (CDT) and GDTs with detailed documentation. In the introduction the overall topic of data typing is very well described. So continue on your PdES journey and have a look at the screencam (please note the corrections below):

Correction note: The intermediate data types (IDT) in the screencam have been erroneously derived from the message data type (MDT), e.g. SlsOrdByIDQryMsg_syncSlsOrdSelByID. This is not correct: The IDT names must be derived from the message type (MT) name. In the example above the IDT name should be SlsOrdByIDQry_syncSlsOrdSelByID. The naming in the storyboard below are correct.

The detailed storyboard is outlined in the following:

• Create a Repository Namespace

Name: http://mycompany.com/

• Create a Service Interface

Name:  SalesOrderProcessingManageSalesOrderIn

Namespace: http://mycompany.com/

Category: Inbound

Interface Pattern: Stateless

Description: "Groups operations that read, create, change, delete, or update an House shipment, or parts of it."

• Delete automatically created default operation

Name:  SalesOrderProcessingManageSalesOrderIn

• Create an Operation

Name "ReadSalesOrder"

Mode: Synchronous

Description: "Reads a unique sales order instance"

• Create model assignments of service interface and operation to corresponding definition entities

• Define Operation Structure and create Message Types

Request Message Type: SalesOrderByIDQuery_sync

Response Message Type: SalesOrderByIDResponse_sync

Fault Message Type: StandardMessageFault

• Create Message Data Types

Request Message Data Type: SalesOrderByIDQueryMessage_sync

Response Message Data Type: SalesOrderByIDResponseMessage_sync

Fault Message Type - Standard Data: ExchangeFaultData

• Define Message Data Type Structure

Request Message Data Type structure: 

Content node: SalesOrderSelectionByID

Typed by: Intermediate Data Type (IDT) SlsOrdByIDQry_syncSlsOrdSelByID
[Type name derived using abbreviation concept based on GDT AbbreviationCode]

Only element: ElementID

Typed by: GDT NOSC_SalesOrderID

Response Message Data Type structure:

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 "Leveraging a wizard to automate Service Creation".

In the following the links to all other blogs from the PdES Architecture Series (Not all blogs are published yet):

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