Login
Register

Home

Trainings

Fusion Blog

EBS Blog

Authors

CONTACT US

Oracle Fusion HCM
  • Register

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

webinar new

Search Courses

There are different scenarios of coexistence, and each scenario requires integration between Fusion and the other core HR system.
Integration for Co-existence Scenarios
The existing core HR system will be the system of record for employee data. Fusion HCM is leveraged for the following specific modules only:
• Talent Management
• Compensation Management
Talent Management comprises of other modules such as Talent Review, Goal Management and Performance Management.
Compensation Management is a single module with all the embedded analytics.
Co-existence with Talent Management 

• Required employee data is synchronized with Fusion
• Profile Information is migrated to Fusion
• Fusion is utilized for Talent Review and Analytics
• Fusion will be the system of record for talent data 

Co-existence with Compensation Management 

• Required employee data is synchronized with Fusion
• Fusion is utilized for the compensation analysis, planning, and allocation purposes
• Work and compensation changes (Bonus, Promotions etc.) at the end of the compensation review cycle are synchronized back to the source application.
The integration objects that are in scope
FHE 53
When Fusion is implemented in a coexistence model, all the objects in the above screenshot will be synchronized between the core HR system and the Fusion application. If a customer goes with only the Talent Management module, all the objects excluding the workforce compensation will be required. If a customer goes for Compensation Management alone, all of these objects excluding the Talent Management objects will be required. The descriptive flex fields are applicable only for the EBS core HR system.
Configurations on the Fusion side
FHE 54
Most of the entities in the above screen come up with the seeded data. Reference data sets comes up with a seeded value called common, seeded lookups, profile types, content types, assignment statuses, person types comes up with the seeded information. If required, customer can customize as per their needs. Some of the entities like legislative data groups, legal entities, legal addresses, legal jurisdictions, legal entity HCM information are some of the configurations that need to be manually done by the implementation team. These configurations have to be manually done in the Fusion application to make sure that the integration objects can be imported into Fusion application from the core HR system.
For this integration, Oracle product has delivered the following tools : 

  • File Base Loader for Inbound Integration into fusion
  • HCM Extract for Outbound extracts from fusion.

My next article will discuss the features of these tools.


Jayashree Prakash

Add comment


Security code
Refresh

About the Author

Jayashree Prakash

Jayashree Prakash

Jayashree is a Oracle Fusion HCM certified consultant who has over fifteen years' experience with Oracle. She has worked as a consultant with several of Alberta's energy companies. She lives in Edmonton and her interests include staying active in the warmer months and vacationing in the Caribbean in the winter

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Mar 2024  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
      1  2  3
  4  5  6  7  8  910
11121314151617
18192021222324
25262728293031

Enquire For Training

Related Items

Fusion Training Packages

Get Email Updates


Powered by Google FeedBurner