One more point to note is that there is a new Action as “Synchronization From Position” reflecting on assignment record and also the sequence has changed from 1 to 2. Similarly log file will show the details about the assignment record processed:Īs a last step we would navigate to the Employee Record for (William Rodgers) and verify if the changes are reflecting as expected.įrom the above snapshot we can clearly see that the changes are reflected as the Department and Job attributes have been updated with new values. Once the process completes the ESS Job status will be completed and there will be a log file and output file available which will hold details about the ESS Job and the assignment records processed.Ī quick look on the output file will show following details:
(If you want to run the process for only a specific Legal Employer, then set “Run at Enterprise Level” to ‘N’ and pass a valid value for Legal Employer)įor this run we will pass “ Past Period to be considered in days ” as 500, Run at Enterprise Level as ‘ N ’ and Legal Employer as “ US1 Legal Entity ” (You can choose either ‘Y’ or ‘N’, if you choose ‘Y’ it would run for entire enterprise) By default, Past Period to Be Considered in Days is set to 30 days. (if you set this parameter to 60 days, then any assignment records with start dates during the previous 60 days are synchronized from positions. The ESS Jobs requires few parameter values to be entered namely: One would need to run “Synchronize Person Records from Assignment” ESS job to make sure the changes made to Position Metadata reflects on assignment record Running Synchronize Person Records from Assignment ESS Job After making the change we can submit the transaction. The New Value of Department is “ Business Services US ” and Job is “ Analyst ”. In the next step we will change the Department and Job attribute value associated with this position (changes are made in “CORRECTION” mode) We observed that the moment we choose position other attributes are populated automatically. In the next step we would create a new employee ( Hire Date as, Legal Employer as “ US1 Legal Entity ” and assign Position as “ TP_POS01_PSYNC ”). Hiring a New Employee and Assigning Newly Created Position The above details when mapped the UI should appear as below (screenshot) Some details related to the positions are below: In the next step we will create a custom position (TP_POS01_PSYNC). Position Synchronization Setup at Legal Employerįor this example, we would choose a Legal Employer “ US1 Legal Entity ” and the Enable Position Synchronization is set as “ Use Enterprise ” (screenshot below): For the “ Manager ” field we will choose “ Use HCM position hierarchy ”
#Logical position how to#
In this post here we would demonstrate how to enable position synchronization and how does it impacts worker’s assignment records.Įnabling Position Synchronization at Enterprise Levelįor this example, we would enable position synchronization and check all flags. Union, Bargaining Unit and Collective Agreement.When position synchronization is used, these are some of the data fields you can carry over: Since position synchronization is used to save time, you can choose from a list of attributes to synchronize across the board. Synchronization also ensures data is consistent across similar positions and hierarchies.
We would like to use position synchronization so that assignments can inherit details from an associated position, which in turn creates less work when you want to enter new positions. So if a set of values like job title, location, and manager are detailed in an assignment, you can synchronize those values with an associated position. Position synchronization is when assignments inherit the values of a predetermined position.
Oracle Fusion Applications Training Index.
0 kommentar(er)
