OHUG 2015 Updated

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |
Fusion HCM REST
Services / Atom Feeds
Kiran Mundy
Fusion HCM Product Management
Jul 1, 2015
Oracle Confidential – Internal/Restricted/Highly Restricted

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 2
Safe Harbor Disclaimer
The following is intended to outline our general product direction. It is
intended for information purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion
of Oracle Corporation.

What’s a Service? What is ATOM? Why do I care..?
Your Applications
FBL/HCM Data Loader
Spreadsheet Loader
Payroll Batch Loader
HCM Extract
BIP
REST Services
ATOM Feeds
Batch
Orchestration Layer handles:
1. Transforming the data
2. Invoking the Plugs
3. Scheduling
4. Monitoring
Real Time

Agenda
• Integration Flow Categories
• Customer Use Cases
• Orchestration of Services
• Fusion HCM Integration Community
• REST/Atom coverage in Release 9/10

HCM Major Integration Flows: Batch vs Real Time
1. If Core HR deployment is On-Premise
a) Co-existence Flow
2. If Core HCM deployment is in the Cloud
a) New Hire Flow - Taleo/3rd Party Recruiting to Fusion
b) HR Master Data to Downstream Systems (with optional updates back)
– LDAP - email/username/role assignments, Other Providers - Stock Plan Details, Loan info etc.
– LMS – certifications [Future]
– Employee info to ADP/Benefit Provider, Time & Absence Accruals to ERP
c) Downstream Systems Triggered Read & updates back into Fusion (Mobile)
– Employee Directory Systems
– PaaS Partner Applications
– Time/Absence Tracking systems [Future]
Oracle Confidential – Internal/Restricted/Highly Restricted 5

Batch Tools vs REST Service/ Atom Feeds
FBL/HDL or HCM Extract
• Heavyweight Integrations, hundreds of transactions going back and
forth.
REST Service/Atom Feeds
• Quick and real time access to resource data within Fusion HCM
• Create a basic resource in Fusion HCM or make specific updates to an
existing resource.

Agenda
• Integration Flow Categories
• Customer REST/ATOM Use Cases
• Orchestration of Services
• Fusion HCM Integration Community
• REST/Atom coverage in Release 9/10

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 8
2a. Hires, Rehires & Global Transfers
ORACLE
Recruiting App
3rd Party or TBE
Candidate to Employee
User Creation (automatic)
Employee Notified
of Account
Current Limitations:
1. 2 tier model supported, not 3 tier.
2. “Employees” can be created, but not “Pending Workers” or
“Contingent Workers” or “Contacts”.

2b. Emp Info to Downstream Apps & Updates back
CUSTOMER ORACLE
Atom/RSS Server
Subscribed to
New Hire
Pension
System
Office
Location
Travel
Management
Broker #
Generation
Update Email address, username
LMS
System
LDAP
New Hire,
Transfers,
Promotions etc
Orchestration Layer

2b. Role Assignments
New Hire,
Transfers,
Promotions etc
CUSTOMER ORACLE
Atom/RSS Server
LDAP
Roles Added
Centrally
New Account
/ Job Updates
Subscribed to New
Hire, Updates
Role Assignments posted
back to Fusion IdM
Role
Assignments

2b. Use Cases – Work Structures to Downstream Apps
CUSTOMER ORACLE
Atom/RSS Server
Subscribed to
Workstructure
Feeds
Pension
System
Office
Location
Travel
Management
Broker #
Generation
LMS
System
LDAP
New Org / Job
Orchestration Layer

2b. Use Cases – Position in Fusion drives Job Req in Recruiting App
ORACLE
Recruiting App
3rd Party or TBE
Position
Status Change
Atom/RSS Server
Subscribed to
Position FeedCreates Job
Requisition in TBE

2b & 2c Use Cases – PaaS Use Cases

2c. Directory Service
ORACLE
GET Employees
Updates own
information
Update Employees
Search for
employee

Using Fusion Middleware for Service Orchestration
• If you already have a perpetual license for SOA Suite, BPEL or BPM Suite can
be used to execute/orchestrate/manage the service calls.
• Or you may have a competing orchestration layer in place that you can
leverage.
• The next few pages show diagrams for the following patterns:
1. If Core HR deployment is On-Premise
1.1 Co-existence flow
2. If Core HCM deployment is in the Cloud
2.1 New Hire Flow - Taleo/3rd party Recruiting to Fusion HCM.
2.2 HR Master data flow - Fusion Core HCM to Downstream Systems (including ERP).
• Examples in next few slides use BPEL, but same concepts apply for any
orchestration layer.

1.1 Co-existence Flow

Coexistence Flow
1. Create a SOA Composite and schedule it to execute periodically.
2. BPEL's "File Adapter" to read the data in.
3. BPEL's Transform Activity to transform the data.
4. Use BPEL to Invoke the UCM Soap Service to write the File into UCM.
5. Invoke the HCM Loader Programs via a SOAP Service call passing them
the encryption parameter along with other required parameters.
6. Implementation Details available here

General Recommendation - FBL/HDL for co-existence
Reasons:
 REST services only support 2 tier & creation of employee (not
pending/contingent workers/contacts etc).
 REST Services only cover heavily used attributes, so all the attributes you need
for co-existence may not be included in the employee/assignment service.
Attribute level detail can be checked via Fusion HCM Integration Community
[Next Section]
 FBL/HDL have been used successfully by several customers in co-existence
scenarios, so they are validated for coexistence use cases.
 Performance considerations as the REST Services are intended for light usage (15-
20 emps/day or so), as there is currently no bulk load functionality.

2.1 New Hire Flow - Batch

2.1 New Hire - REST

2.2 Master Data Flow - Batch

2.2 Master Data Flow - ATOM

2.2 Master Data Flow – ATOM – with Updates

Downstream Apps Flow
1. Create a SOA Composite and schedule it to execute periodically.
2. The composite will invoke BI Reports or HCM Extract using SOAP Services,
or will poll the Atom URL for new entries.
3. Branch for each destination system & transform the data.
4. Use the File Adapter to append to each file destination.
5. Downstream systems process files at the periodicity they need (which
vary by system).
6. Details available here

Aug/Sep 2015 – BPEL Pilot with REST/Atom
Customers Should:
• Have access to BPEL via a perpetual license or trial
• Have use cases suited to REST/Atom.
• Have no go-live commitments dependent on the prototype.
• Agree that the completed work will be rolled into Oracle Future Development
plans.
• Prototypes will be created on customers stage HCM environment on Release 9,
Patch Bundle 8 or R10/PB8.
• We’ll schedule conference calls to review the customers existing BPEL integration
to validate that REST / Atom will meet their use case requirements.
• Contact me with details of your use cases if interested.

Developer Download & Quick Start for SOA Suite/BPEL
• SOA Suite 12.1.3, which includes BPEL PM and Service Bus, comes with a
development installer called QuickStart.
• It can be downloaded from the SOA Suite OTN downloads page.
• The Installing SOA Suite and Business Process Management Suite Quick
Start for Developers guide explains the installation and also points to a
sample tutorial.

Integration Community – Current Objective
• Ongoing exchange with Field & Customers.
• Customers who have requested “Controlled Availability” for REST will
– Train themselves
– Record & Test their use cases.
– Certify their use cases work, or record issues.
• To join the community, send an email providing your company name/use
cases & requesting to be added.
• To request “Controlled Availability” access, the template available on
Community Site.
• Link to Fusion HCM Integration Community available from www.finapps.com

Fusion HCM Integration Community

Enter use case/payload & any errors/response

Approach to Design of the REST Resources
• Flattened Resources – all commonly used child attributes are flattened
onto the parent.
– This means creates/updates to the many common child resources of employee can be
made in a single call.
• UI defaulting paradigm.
– All defaults happening via the UI, will also happen via the REST call.
• LOV links provided for all LOV’s.
– When creating a resource, client app can follow the LOV link and retrieve valid values.
• Any remaining child resource links (unflattened) are returned with the
parent resource.

REST – Root Resources
http://<host>:<port>/hcmCoreApi/resources/latest/<resource>
Resource Description Methods Supported
/employees Returns all employees with links to all
child resources
GET, POST, PATCH
/locations Returns all locations GET
/organizations Returns all organizations with their
classification
GET
/jobs Returns all jobs GET
/jobFamilies Returns all job families GET
/positions Returns all positions GET
/grades Returns all grades GET
Technical Limitation: When an employee is created via REST, the approvals, even if configured, will be ignored.
Employee will be created & Atom entry triggered as if the approvals were not configured.

Employees - Child Resources
http://<host>:<port>/hcmCoreApi/resources/latest/employees/{id}/child/<resource>
• Can do a “GET” (read) or “POST” (create) on any of these together with the
parent or separately.
/currentAssignment Returns primary assignment for the specific employee GET, POST, PATCH
/directReports Returns a list of employees that are direct reports of {id} GET
/visas Returns a list of visas for employee {id} GET
/photo Returns the photo for employee {id} GET, POST
/assignments Returns all assignments for the employee {id} GET, POST, PATCH
/roles Returns all job roles assigned to the employee {id} GET, POST, DELETE
/personDFF Returns all DFF’s configured for the employee {id} GET, POST, PATCH

/emps attributes /assignments attributes

Employee Assignments - Child Resources
http://<host>:<port>/hcmCoreApi/resources/latest/employees/{id}/currentAssignment/{id}/<resource>
/assignmentDFF Returns DFF’s for the assignment. GET, POST, PATCH
/empreps Returns representatives (from Areas of
Responsibility) for that employee
GET
/peopleGroupKeyFlexfield Returns the Peoplegroup Key Flexfields for the
assignment.
GET, POST, PATCH

ATOM - Employees
http://<host>:<port>/hcmCoreApi/atomservlet/employee/<collection>
Published to Atom Server when the event under “Collection” takes place.
Employees
Collection Description
/newhire Entry created when an employee is hired. If approvals are configured, will fire after
approvals complete.
/empupdate Returns all the updated employees
/empassignment Returns all the assignments for all the employees
/termination Returns all the terminated employees

ATOM - Workstructures
http://<host>:<port>/hcmCoreApi/atomservlet/workstructures/<collection>
Collection Description
/organizations When an organization (of any classification) is created or any attribute on the resource
is updated and corrected.
/locations When a location is created or any attribute on the resource is updated and corrected.
/jobs When a job is created or any attribute on the resource is updated and corrected.
/grades When a grade is created or any attribute on the resource is updated and corrected.
/positions When a position is created or any attribute on the resource is updated and corrected.

REST / Atom Controlled Availability Plan
• Customers need to test their use cases on a central sandbox & certify that
they work before being approved for “Controlled Availability”.
• “Sandbox availability” target
– July 2015 for “POST” & “GET”, with Patch Bundle 7.
– “PATCH” in Aug with PB8
• If approved, we will provide instructions on how to enable /emps in R9/R10
PB8. [Workstructure Read Services/Atom Feeds are already available]
• Link to Fusion HCM Integration Community, where customers can apply for
CA access & the sandbox details are published. Email me for access.
• CA on customer pods – Starting Aug 2015 [On R9/R10 PB8]

Roadmap Items
• Two Way SSL
• Enhancement to support turning on Feeds for HDL/FBL
• Extend /emps to Pending Worker & Contingent Worker.
• Profiles Certifications & Atom Feed & Document Attachments.
• Timecards & Absence Entries. Atom Feed on Absence Entries (entries
within Fusion).
• Element Entries
• Location & Org Creation
• Creation of Lookups

Key Takeaways
• REST Services / Atom Feeds Real Time Use Cases – mainly when Core HCM in Cloud.
– New Hire Flow
– HR Master Data to Downstream Systems (with optional updates back)
– Downstream Systems Triggered Read & Updates back into Fusion.
• You can leverage your existing orchestration layer. If using BPEL, you can volunteer for
BPEL Pilot in Aug/Sep.
• Target “Sandbox availability” via Community.
– In July 2015 for “POST” & “GET”.
– “PATCH” when sandbox upgraded to R10.
• Apply for CA access via Community.
– Test use cases in sandbox via community, as a pre-condition for CA approval.
– If you lose the community url link, you can always get there from this blog @ www.finapps.com

Any questions, please email kiran.mundy@oracle,com

OHUG 2015 Updated

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie OHUG 2015 Updated

Ähnlich wie OHUG 2015 Updated (20)

OHUG 2015 Updated

Hinweis der Redaktion