Skip to Content

Hi community,

Interested in SAP Enterprise Services (ES)? Interested in innovative proof-of-concept solutions drawing the possibilities of SAP ES and 3rd-party services to create a measurable value for customers and users? The SAP TechEd 2008 session SOA 209 “Consuming SAP Enterprise Services for “Order-To-Cash” at the Hasso Plattner Institute” (Las Vegas / Berlin / Bangalore) covers the following topics:

Order-To-Cash Scenario

A joined solution was built upon the integration of the following four individually developed solution parts.

  • Product Catalogue and Order Statusis a sales channel providing a web shop offering the interface between customers and vendors for any kind of interaction, e.g. sales order creation and processing status feedback,
  • Outbound Delivery provides a vendor-site web application integrating mobile devices tracking real-time picking and delivery status,
  • Paymentis a desktop-like web application providing detailed information about open and closed payables with corresponding sales orders and invoices,
  • Customer Fact Sheetis a vendor-site application providing a wide range of analysis, statistic and tracking functions to derive information about individual customers and customer sets.

The resulting composite applications build upon ES exposed by a SAP Business Suite backend system. The used services are summarized in the ES Bundles named Order-To-Cash and Customer Fact Sheet. Business functionalities such as sales order and invoice creation are automatically performed by the backend system. Various third-party enterprise services such as GoogleMaps  and FedEx  are used to enhance the functionality of the O2C scenario.

Technology Aspects

Get an insight into different technologies which were used to develop composite applications for the presented scenario. In this sections language capabilities are compared and pros/cons of the following programming languages and technologies are discussed:

  • J2EE:
    established, having huge tool-support, but requiring extensive development times,
  • Ruby on Rails:
    relatively new programming languages building own patterns like code by convention and code reuse by don’t repeat yourself (DRY),
  • JRuby:
    makes it possible to use existing J2EE code from within your Ruby projects,
  • .NET:
    easy to use drag and drop design environment helps to create rapid prototypes,
  • UI Technologies:
    excessive information about agile web 2.0 user interface technologies, e.g. for web applications, and
  • SOA:
    advantages of using SOA in contrast to proprietary communication protocols.

If you have further questions please don’t hesitate to get in contact with me.

Looking forward to see you at SAP TechEd 2008.

Matthieu-P. Schapranow

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