Skip to Content
1      Introduction

This ESOA enablement is intended to show overall guideline how typical Enterprise Service Oriented Architectures (ESOA) Project is planning and moving forward to the actual project scoping. The latest SDN articles and the expert’s webblog give you the detail information for the subject matter, on top of that information, this document update that actual project task management based on the customer’s scenario.

The document mainly focused on the main targets:

  • Lead System Architecture: Understand of SAP ESOA Development Lifecycle and knowing that different technologies for the Service Provider and Service Consuming side.    
  •  Project Management Office (PMO) : Overall project scoping with the subject matters, compare with the purely SAP environment  projects, Also, the steps PMO must define during the project scoping and familiar with the sequence
  •   Technical Consultant : Knowing that different technologies set when it comes to actual implementation stage and recommended to technical setup procedure in case of webservice import and webservice enablement from SAP ERP
  •  Business Process Expert:How to create a new business process and discovering re-usable enterprise scenarios from ES Workplace. 

Throughout this guide, we will take a look how typical ESOA project which runs by SAP Composite Environment (CE7.1) implement by the project team. We will take a look from Enterprise SOA Development Lifecycle point of view. However, this guide is mainly focus on “process flow of the project”, it won’t be touched the deep side of business logic coding which it requires Java EE5 development, ABAP coding and CAF manual java code implementation.

image

Figure 1: Enterprise SOA Development Lifecycle

2      Customer Project Scenario

 People4U is doing outsourcing Human Resources (HR) management. From Call center, Project Implementation outsourcing to temporary staffs servicing, their workplaces are quite various and submission of their expense claim and travel related process are all happened independently.

The most frequent business processes which it need to govern is as below:

  • Different submission date of expense claim and reimbursement date 
  • Expense Payment Inquiry 
  • Business Travel request and deliver of advance travel costs in cash
  • Weekly, bi-weekly salary payment

All the travel related transactions run by the custom developed webservice program. Even though, they are running ECC5, but their main usage is FI/CO. HR master data has been maintained, but a lot of function need to be enhanced. So the team is looking for the enhanced featured from ECC and possibly to use of Global Data Type. It will warp the webservice with a more generic and understandable service. The decision, how many process will be created as a new and discover from ES workplace and apply as enhancement in ESR haven’t make any choice yet.

The project team also looking for the best practice for this project not only implementation phase, also post go-live operation parts. The reason being that the project team is quite new for these topics and SAP Web Application Server (WAS) environment quite difficult to find out the ongoing tuning and all the complex of Java landscape when it come to performance.

Finally, with all the open conditions, the project team chose one scenario as a pilot process

Process Name: Expense Approval

Process description

On-site consultant enter their expense exposed enterprise service, it will be reviewed the line of business (LOB) manager. The Amount of expense such as, the line items for travel, over-time-meal and purchase of stationary items less than SGD200, doesn’t required approval  LOB manager, it will be triggered approval process automatically to the finance controller and the payment will be made the last Friday on the same week.

For the composite application development approach how to publish to service registry need to implement. The final decision from service consuming and creation of webservice still pending, the project team needs to know that all the different options ESOA development for the cases

  • Creation of webservice from outside in development point of view
  • Expose webservice
  • Creation of Visual Composer UI for the case of employee make inquiry payment
  • WebDynpro for Java UI

 Again, this guide will not be going through the complete lifecycle of development. It will be cover the above cases and see how efficiently required the service can create and get the glance of overview.

To report this post you need to login first.

4 Comments

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

  1. Dipankar Saha
    Hi,
    One aspect I feel should be included in ESOA implementation is the Business Process Management (BPM). BPM is one of the differentiators and core aspect of any successful ESOA implementation. Unlike the traditional implementation where the application logic is bundled with the process logic and cannot be easily segregated or changed, in ESOA implementations the process logic is maintained in the BPM layer while the core application logic is provided by the backend services. In this example, the checking of expense claim whether the requester need an approval for the claim amount greater than a certain amount, becomes the process logic where submission of the claim to the payment system is the core application logic. In SAP paradigm the BPM aspect is handled by Guided Procedure or more recently by NetWeaver BPM. I think adding that aspect in your next blog will add great value.

    Thanks,
    Dipankar  

    (0) 
    1. Chan Jin Park Post author
      Thanks for your comment Dipankar. Like you said NWBPM and BRM is on the way. You will see lots of topics already in BPX community. Of course, my coming blog will use some of NWBPM part. But this blog more likely go through the process point of view for ESOA implementation. Composite application is huge and there are many ways to produce the enterprise service. NWBPM also one of ways.
      (0) 
  2. Jett Jiang
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 

Leave a Reply