Labels

2017 absence absence management Account accounting AIM aliases AME and API application application utilities lookups approval assignments ATO Australia Bank bi publisher budget business business groups CAGR candidates cartisian product case CEMLI Center Stage channels Classification competency concurrent Configuration configuration profile constants contextualization conversion correction cost costing coverage area customization data database date DateTracked deductions define design develop DFF diagnostics document earnings ebs EIT Element employee enhancements erp excel expression extension failure Fastformula FBT Flexfield FND fndload foreign key forms Formula fringe benefit FRM-40654 from FTE Functions fund fusion GL global transfer grade help hierarchy HR HRMS human resource management system implementation income information interfaces internet interview job join key flexfield KFF KPI language learning leave legal employer legislation links lists localization location management New Year obia obiee OLF onboarding oracle oracle applications oracle descriptive flex field oracle descriptive flexfield oracle ebs oracle erp oracle fusion HCM oracle hrms oracle hrms interview questions oracle hrms modules oracle hrms modules list oracle hrms organization oracle hrms table oracle hrms tables oracle hrms tutorial oracle irecruitment oracle legal entities oracle lookups oracle organization hierarchy oracle payroll oracle payroll interview questions oracle payroll tables oracle self service order by Organization organization type otbi package package body package specification patch payg Payment payroll people group perform person personalisation phase pl/sql position primary key process profile programs project qualifier Query question questions Recruiting Center Recruitment regex regular expression reporting tool reports requests requirement requisition resume retropay RICE salary schema security profile select SIT smartorg sql statutory stores STP Super Superannuation system systems Table Taleo taleo 15B Taleo Recruitment tax termination test testing trunc update user group user management user type value set variables View Views Web ADI webadi where work relationship

Sunday 22 November 2015

Fusion HCM - For Starters

Here are few terminologies in Fusion that we need to look at - 
  • Legal Employer - an entity that employs the workers. A legal employer is captured at the work relationship level. And all the employment terms and assignments within that relationship will automatically get assigned to that legal employer.
  • Work Relationship - relationship between person and the legal employer. It exists at the person level and it provides the context in which the person's assignments exist. It must have at least one assignment. It could be that of an employee or a contingent worker or non-employees.
  • Employment Term - refers to label for a group of assignments. The employment terms set the terms and conditions to govern one or more assignments. All assignments that belong to an employment term automatically inherit anything that you have defined at the employment term level.
  • Assignments – set of information that defines the person's role within that legal employer. It could have information about the person's location, position, job, grade, and many other information at assignment level.
  • Action and Action Reasons – Fusion categorizes the action and action reasons to a Work Structure as well as Employee Records. For Example, it could be termination, transfer of locations or new hire. In Fusion, various actions can trigger various different workflows. For example, an action history is created when a person gets hired, then promoted, then the location is changed, and termination occurs.
  • Reference Data Set - This concept is new to Fusion Applications. A set ID is a partitioning data reference, which are known as sets. These sets can either be common, which means that they spread across all the business units, or they could be specific to a single business unit. The various set enabled objects in Fusion applications are the departments, locations, jobs, and grades.
  • Organization - Organizations in Fusion are Date Effective whereas in E-Biz, the organization has enable and disable flag. In fusion, the Legislative Data Group (LDG) is equivalent of a Business Group as country specific data portion within an Enterprise. In Fusion, all the classifications are not available to be associated to the organizations. However, in EBS, you could create an organization and associate various classifications along with that organization. In Fusion HR Organizations are called Departments which are HR classified Organizations in EBS
  • Organization Hierarchy - In Fusion, the org hierarchy is known as Tree. In Fusion Apps, we have four different hierarchy structures, department trees, which only consist of departments. The organization trees are different in the sense that they could have any organization for the top node and the child node, as well. And it can be combination of various organizations. Position trees, as the name suggests, it is for various positions. And we can create multiple versions of each tree to create reporting relationships among different positions. Then there is a different tree available for geographies, which is known as the Geography tree. Except the geography tree, we can create multiple trees for each of the tree type. And each tree type can have multiple versions.
  • Person Employment Model - EBS supports two-tier person model which is Employee and Assignment. We can have a one-to-many many relationship, an employee can have many assignments for each person record. However, only one assignment can be primary at a given time. In Fusion Applications, there is an extended support for two-tier as well as three-tiered models. The two-tier model is Employee and then Assignment In three-tier model, we have an additional tier, which is Employment Term that is associated to an employee.       
  • Global Transfer - In Fusion Apps, in case of global transfers, it means movement of the person from one legal employer to another legal employer, which means the person-level information does not change. The source employment terms and assignments are terminated, and their default status is set to 'Inactive payroll eligible'. In Fusion, there is also support for global temporary transfers. And in case of global temporary transfers, upon end-dating the transfer, the employment term and assignments are automatically activated on return of the person.
  • Person Numbers - In Fusion Apps, there are two different numbers that are available. A person number is a number that can be unique within an enterprise. It can either be generated manually or automatically. Then there is something called worker number, which is to uniquely identify an employee or contingent worker work relationships. This is optional for setup, and may or may not be used. Now this allocation within a legal employer can either be automatic or a manual sequence. There is also availability of assignment number for assignment-level information. And it behaves the same way as E-Business Suite having a suffix of -N for any rehires or secondary assignments.


1 comment:


  1. Thanks for sharing this great information I am impressed by the information that you have on this blog. Same as your blog i found another one Oracle Fusion HCM . Actually, I was looking for the same information on internet for
    Oracle Fusion HCM Interview Questions and Answers and came across your blog. I am impressed by the information that you have on this blog. It shows how well you understand this subject.

    ReplyDelete