Tuesday Jun 25, 2013

Fusion HCM SaaS – Integration

Fusion HCM SaaS – Integration

A typical implementation pattern we’re seeing with Fusion Apps early adopters is implementing a few Fusion HCM applications that bring the most benefit to their company with the least disruption to existing programs and interfaces. Very often this ends up being Fusion Goals & Performance, Talent, Compensation or Benefits, often with Taleo for recruiting. The implementation picture looks like what you see below:


Here, you can see that all the “downstream integrations” from the On-Premise Core HR, are unaffected because the master for employee data is still your On-Premise Core HR system – all updates and new hires are made here (although they may be fed in from Taleo to start with).

As a second phase when customers migrate Core HR to Fusion HCM, they have to come up with a strategy to manage integrations to all their downstream applications that require employee details. For customers coming from EBS HR, a short term strategy that allows for minimal impact, is to extract employee data from Fusion (Via HCM Extract), and load the shared EBS HR tables (which are part of an EBS Financials install anyways), and let your downstream integrations continue to function based on this data as shown below.


If you are not coming from EBS HR and there are license implications, you may want to consider:

  1. Creating an On-Premise warehouse for extracting data from Fusion Apps.
  2. Leveraging Fusion Apps Web Services (available to SaaS customers starting R7) to directly retrieve/write data to Fusion Apps.

Integration Tools

File Based Loader

This is the primary mechanism for loading HCM data (both initial load and incremental updates) into Fusion HCM. Employee & related data can be uploaded into Fusion HCM using File Based Loader.

Note that ability to schedule File Based Loader to run on a pre-defined schedule will be available as a patch on top of Rel 5.

Hr2Hr has been deprecated in favor of File Based Loader, but for existing customers using Hr2Hr, here are some sample scripts that show how to get more informative error messages. They can be run by creating data model sql queries in BI Publisher. The scripts currently have hard coded values for request id and loader batch id, which your developer will need to update to the correct values for you. The BI Publisher Training Session recorded on Apr 18th is available here (under "Recordings"). This will enable a somewhat technical resource to create a data model sql query.

Links to Documentation & Traning
Reference documentation for File Based Loader on docs.oracle.com

FBL 1.1 MOS Doc Id 1533860.1

Sample demo data files for File Based Loader

HCM SaaS Integrations ppt and recording.

EBS api's

Loading Information into EBS Full or Shared HCM

This could be candidate information being loaded from Taleo into EBS or  Employee information being loaded from Fusion HCM into an EBS shared HR install (for downstream applications & EBS Financials).

Oracle HRMS Product Family Publicly Callable Business Process APIs (A Reference Consolidation) [ID 216838.1]
This is a guide to the EBS R12 Integration Repository accessible from an EBS instance.

EBS HRMS Publicly Callable Business Process APIs in Release 11i & 12 [ID 121964.1]

Fusion HCM Extract

Fusion HCM Extract is the primary mechanism used to extract employee information from Fusion HCM.

Refer to the "Configure Identity Sync" doc on MOS  for additional mechanisms.

Additional documentation (you'll need an oracle.com account to access)
HCM Extracts User Guides (Rel 4 & 5)

HCM Extract Entity/Attributes (Rel 5)

HCM Extract User Guide (Rel 5)

If you don’t have an oracle.com account, download the zipped HCM Extract Rel 5 Docs (Click on File --> Download on next screen).

View Training Recordings on Fusion HCM Extract

Benefits Extract

To setup the benefits extract, refer to the following guide.
Page 2-15 of the User Documentation describes how to use the benefits extract.

Benefit enrollments can also be uploaded into Fusion Benefits. Instructions are here along with a sample upload file.

However, if the defined benefits extract does not meet your requirements, you can use BI Publisher (Link to BI Publisher presentation recording from Apr 18th) to create your own version of Benefits extract. You can start with the data model query underlying the benefits extract.

Payroll Interface

Fusion Payroll Interface enables you to capture personal payroll information, such as earnings and deductions, along with other data from Oracle Fusion Human Capital Management, and send that information to a third-party payroll provider.

Documentation:
Payroll interface guide
Sample file
DBI's used for the payroll interface.

Usage Patterns always accessible @ http://www.finapps.com

Wednesday Jun 12, 2013

How to customize the user experience in Fusion Apps - Part 1 Composer Security Expressions



Access to resources such as taskflows, regions, buttons, and menus in Fusion Applications is granted by entitlements stored in a policy store and managed through the Authorization Policy Manager (APM).  Users are assigned roles comprised of  a set of entitlements (Oracle makes this quite easy  by providing you with job based seeded roles) authorizing them to  access  only the data and functions neccessary to perform their jobs and no more. On a more granular level it is also possible to control the rendering of certain UI objects by controlling their display attribute at runtime using Page Composer.

An example illustrating a conditional rendering of a Button is outlined below. The condition used in this example is the Role of the authenticated user.

2 Users and 2 Roles

In this example we have two HR Specialists, we want to prevent one of these users from saving Person records.

Figure1 Roles of Louise Beckham

Figure2. Roles of Megan Davis

Customizing the Object

Using Page Composer, the Administartor creates a security condition in Expression Builder. This condition states that the "Save" field on the "Person Management" page will be displayed if and only if the session authenticated user has the PER_HUMAN_RESOURCE_SPECIALIST_VIEW_ALL_DATA role. This happnes to be a role that our user Megan Davis has but that has not been granted to user Louise Beckham.

The statement, written in Expression Language (EL), used in this example is

#{securityContext.userInRole['PER_HUMAN_RESOURCE_SPECIALIST_VIEW_ALL_DATA']}

NB: It is possible to have a include multiple roles as follows: #{securityContext.userInRole['Role 1'||'Role2']}, it is also possible to exclude a role by include a '!' at the beginning of the expression as follows: #{!securityContext.userInRole['Role 1']}


Figure3. Selecting the ADF Object that we want to customize


Figure4. Creating a dynamically calculated attribute value using Expression Builder

Different Display for Different Users

Below is how each of our two users sees the same UI that has now been conditionally customized. We can see the "Save" button displayed on Morgan's UI but not on Louise's.

Figure 5 - .Louise's UI without the Save Button

Figure 6.Megan's UI with the Save Button


About

This blog shares with the broader Fusion Applications community instructional material in the areas of Enterprise Structures, Extensibility, Integration and Security with the a focus on implementation. This blog is updated by the Fusion Applications Implementation Solutions Task force, part of the Fusion Applications Fusion Architecture organization.

Search

Categories
Archives
« June 2013 »
SunMonTueWedThuFriSat
      
1
2
3
4
5
6
7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
26
27
28
29
30
      
Today