image
I am not a HCM expert, but playing around with the Oracle HCM adapter did force me to dig a bit deeper into how HCM works. It all began with a relatively simple file based integration that “imported” a worker into HCM. The integration had a REST trigger and leveraged the Oracle HCM adapter as well as the technical SOAP adapter.

I ran a test from Postman, with, what a colleague told me was, a valid REST payload, one of the attributes being BusinessUnitID.

{ “PersonNumber”:”77012″, “StartDate”:”2014/01/01″, “DateOfBirth”:”1988/05/23″, “LegislationCode”:”US”, “FirstName”:”FirstName0112″, “LastName”:”LastName0112″, “LegalEmployerName”:”US1 Legal Entity”, “BusinessUnitId”:”458“, “JobId”:”300100003260508″ }

I tested the integration and then went into Fusion HCM to validate what I had done. From an OIC perspective, the integration flow had executed successfully. So off I ventured into HCM. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

clip_image003 Blog clip_image005 Twitter clip_image004 LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress