Академический Документы
Профессиональный Документы
Культура Документы
Best Practices 5
Examples 7
Overview
This document provides information about the Synchronize Person Records ESS job.
In day to day business, Oracle Cloud Human Capital Management performs many transactions on different types
of persons. Examples of such transactions are hiring, change in name, addition or modification of work phone,
promotion, supervisor change, job change, position change, and so on. Modules like Lightweight Directory Access
Protocol (LDAP), Customer Relationship Management (CRM), and so on, which closely monitor these changes
want to automatically synchronize these changes into their own systems. This is done through the HCM data
OUTSIDE HCM
3 The composite analyzes 4 5
In SOA server, the HCM Changes
the changes
consuming module synchronized
in HCM data &
composite LISTENS to with other modules.
synchronizes the same
the event.
into their module.
1 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT - SYNCHRONIZE PERSON RECORDS ESS JOB
What is the Synchronize Person Records ESS Job?
The Synchronize Person Records ESS job notifies about the changes (in step 2 above) in person and
assignment data. Firstly, the job identifies all person records with changes in person or assignment
data during a specified period. Secondly, it raises the ChangedPersonDetails event for all those
persons. Finally, the job is terminated after events are raised for all person records. The ESS job logic
is shown in the diagram below.
START
STOP
Only when events are being suppressed (case of batch loads) and or or whenever future changes become effective.
Refer to Best Practices section.
2 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
How to Execute the Synchronize Person Records ESS Job
You must have access to the Scheduled Processes task to execute the Synchronize Person Records ESS job. The
steps to execute the job are provided below. With each step, there is a screenshot to understand it better.
Steps Screenshot
Click the Scheduled Process button. This displays the Process Name
LOV.
Select the job and click OK. Click OK in the new page to display the
Parameter page.
Specify the required parameters and click Submit. See the next section for
an explanation on the parameters.
Note the process ID and then click OK. It shows the Process Running
Information page. Click the Refresh button to see the Running status of
the job.
3 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Parameters and Purpose
This job has 3 parameters. The table below provides information about these parameters.
4 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Best Practices
Batch loads are getting processed
Run this job only once a day. This job must be run on a daily basis to synchronize all active changes.
In this case, the parameters must be set to Today's DATE (From Date), Today's DATE (To Date), No
(After Batch Load).
Run this job immediately after loading the data using FBL, HDL, Spreadsheet loader or any other
loaders. However, if loading has to be done many times a day, it is recommended to run the job after
the execution of the final load.
Run this job with From Date and To Date parameters as start date of data load and completion date of
data load respectively.
The After Batch Load parameter must be set to Yes, if the job is run after a data upload using HR2HR
or FBL or any other data loader that suppresses the events. Otherwise, set the parameter to No.
5 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
When to Execute the Person Synchronization Job
This job can be executed on a daily basis, or after loading of person or assignment data using data
loaders like FBL, SDL or HDL.
Daily(To handle From Date: Null 1. When you specify the Date When future dated
future dated parameters as NULL, it is hires or /work
To Date : Null
changes) assumed that the changes that relationships
After Batch Load : No happened on the system date becomes effective.
(t
When pending
up by the job.
workers are being
converted as
employees or
contingent workers.
After loading From Date: Date when 1. Data load of person and or or When data load
data the data load started assignment happens in 1 or 2 contains active
days. Hence, the date range employees or
To Date: Date when
between loads is 1-2 days. contingent workers.
the data load
completed 2. When you provide the date
range, ensure it is less than 7
After Batch Load: Yes
days. If it is more than 7 days,
the job terminates with a
warning message.
6 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Examples
This section provides example of parameters based on different scenarios to execute the job. Assume the System
Date -Apr-2015 in the examples below.
Mode of Data Count, Type Effective Date Data Data When to From Date To Date After
Entry of Persons of Person Entry/Load Entry/Load run the Batch
Start Date End Date job? Load
Loader 300 Pending 07-Apr-2015 OR 07-Apr-2015 07-Apr-2015 Job N/A N/A N/A
FBL,SDL,HDL Workers any date before Execution
07-Apr-2015 not required
Loader 300 Pending 07-Apr-2015 OR 07-Apr-2015 07-Apr-2015 On or after 07-Apr-2015 07-Apr-2015 Yes
FBL,SDL,HDL Worker any date before 07-Apr-2015
CONVERSI 07-Apr-2015
ON to
EMPLOYEE
S
Loader 300 Pending 07-Apr-2015 OR 07-Apr-2015 07-Apr-2015 On or after 07-Apr-2015 07-Apr-2015 Yes
FBL,SDL,HDL Worker any date before 07-Apr-2015
CONVERSI 07-Apr-2015
ON to
Contingent
Workers
Loader 300 Non 07-Apr-2015 OR 07-Apr-2015 07-Apr-2015 Job N/A N/A N/A
FBL,SDL,HDL Workers any date before Execution
07-Apr-2015 not required
7 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Mode of Data Count, Type Effective Date Data Data When to From Date To Date After
Entry of Persons of Person Entry/Load Entry/Load run the Batch
Start Date End Date job? Load
Loader - 300 Future Dated 07-Apr-2015 07-Apr-2015 Job N/A N/A N/A
Execution
FBL,SDL,HDL Employees (date later than not required
or system date)
Contingent
Workers
UI Hire a 1 Pending Any Date 07-Apr-2015 07-Apr-2015 Job N/A N/A N/A
Pending Worker Execution
worker not required
8 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Mode of Data Count, Type Effective Date Data Data When to From Date To Date After
Entry of Persons of Person Entry/Load Entry/Load run the Batch
Start Date End Date job? Load
UI Hire a 1 Non Any Date 07-Apr-2015 07-Apr-2015 Job N/A N/A N/A
Non worker Worker Execution
not required
UI -- Manage
Employment
OR
UI -- Create
Work
Relationship
UI -- Manage
Employment
OR
UI -- Create
Work
Relationship
9 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Frequently Asked Questions (FAQs)
1. Does the Synchronize Person Records ESS job create TCA party records?
A. No, this job does not create TCA party records. The TCA Composites listen to the ChangedPersonDetails
event, which is raised by the job. TCA Composites analyze this event and create or update the party
records.
A. If the job is executed more than once a day, it may cause performance issues on the SOA server, which
may cause it to crash. Every time, the job is executed, events are raised for all those persons having a
person or assignment data change. That means if there are 10000 people having person, assignment
changes on a day, running the job 10 times will raise 100,000 (10000 * 10) events in total.
3. I am loading employees into the system using File Based Loader. Do I need to run this job?
A. Yes, you need to run this job after the completion of the data loads for person, work relationships. If you
s the total number of batches)
4. I am loading employees via Spreadsheet Data Loader or HDL. Do I need to run this job?
A. Yes, you must run this job if you load data using any of the data loaders.
5. I am creating employees using the New Hire page. Do I need to run this job?
A. No, this is not required because when you create employees using the New Hire page, records are
automatically synchronized.
6. How do I know if I need to execute the job after loading the person or work relationship data?
A. In general, you need to run this job after loading the data using any of the loaders. However, the job
execution is not needed if the
(i) data load contains only pending workers and nonworkers
(ii) data load contains only terminated employees or contingent workers as of the
date)
(iii) data load contains only future-dated employees or contingent workers.
7. I came across a situation where I tried to create Payroll Personal Payment Methods for terminated
A. There are two ways to create party records for terminated employees.
(i) From release 9.2 onwards, execute the ESS job Maintain Party and Location Current Record
Information. This job creates the party records.
(ii) Raise an SR with the Oracle Cloud HCM Support team. They will execute a script to create party
records for terminated employees.
10 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
8. Can I use the methods mentioned in FAQ #7 to create party records for future hires?
A. Yes, follow the same steps to create party records for future hires.
9. I created an employee effective in the future using the UI. I followed the answer for FAQ 5 and did not
execute the ESS Job. However, I find that the party record is not created for this employee. This stops me
from entering payroll personal payment methods. What do I do now to create a party record?
10. I loaded employees and contingent workers using FBL. I ran the ESS job as mentioned here. Later, I found
that the TCA party records are not created for these employees and contingent workers. Do I rerun the
ESS job?
A. No. You should not rerun the ESS job. Instead, you need to analyze the reason for the party creation
failure. To do this, you must raise an SR against the Oracle Cloud HCM development team to identify the
root cause and provide a solution. In case party creation is critical and you cannot wait until the Oracle
Cloud HCM development team analyzes the issue, you can use the methods suggested in FAQ#7 to
create party records.
11 | ORACLE FUSION HUMAN CAPITAL MANAGEMENT SYNCHRONIZE PERSON RECORDS ESS JOB
Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
C O N N E C T W I TH U S
blogs.oracle.com/oracle Copyright © 2014, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 1015