Integrating PeopleSoft HCM with BPA Suite and SOA Suite
By srikant.subramaniam on February 17, 2009 2:14 PM
We
illustrate the progression of a business process from the initial
modeling to the eventual creation of the executable software using
Oracle BPA Suite, Oracle SOA Suite and PeopleSoft HCM.
Oracle BPA Suite provides a standards based approach for the
modeling, analysis and simulation of business processes. Sharing these
process models with the development team is as easy as clicking a
button that reads “Share Blueprint with IT” which then exports the
process metadata to the Oracle SOA Suite (Oracle BPEL PM, Oracle
JDeveloper). The development team integrates the resulting BPEL model
with the backend PeopleSoft HCM to create the executable software.
The tutorials will showcase these capabilities:
- Modeling a business process and exporting it to the development environment.
- Round trip integration between the modeling and the development environments.
- Creation of executable software and integration with the backend application.
Use Case
Consider a benefits enrollment process where an employee has a
qualifying event (the birth of a child, for instance) and now needs to
enroll this new born child for health benefits and also make changes to
the employee's payroll withholding to account for the new dependent.
While a typical benefits enrollment is often more complex than
the above description, this tutorial focuses on a simplified scenario
to illustrate the principal concepts and for ease of implementation and
demonstration.
The process model is setup to accept all the relevant information (Employee ID, payroll withholding information, dependent's name, birth date, etc) upfront. The appropriate business processes (Insert Dependents, Insert W4) are subsequently invoked using this input data.
Implementation
The figure below summarizes the interaction between the business
analyst and the process developer. The business repository contains the
shared metadata and helps to keep the modeling and the development
environments in sync.
There are three distinct phases in the implementation process (click on the links below for detailed instructions):
