Skip to Content

image

The previous blog of this series – SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – 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 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):

Screencam Defining Services

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/302cbcdc-342c-2c10-d19d-a4de4273041c

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:

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. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3)
  2. Defining Services (This Blog)
  3. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Leveraging a wizard to automate Service Creation (Part 5)
  4. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in Java (Part 6)
  5. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in .NET (Part 7 – provided by Nakisa)
  6. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing services in ABAP (Part 8)
  7. SAP Co-Innovation Lab Architecture Series: Custom Development delivered Custom Enterprise Services (Part 9)
  8. The specified item was not found.
To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply