GHR Employee History Rebuild and Refresh

Hi,

We need help on how to correctly run the process and build/update employee history. Both Refresh and Rebuild are currently scheduled to run at 12am every day but we are getting 'terminated abnormally' error on action:ValidateUserField for Refresh Employee History.

> Create Employee History (action: RebuildEmployeeHistory)

> Refresh Employee History (action: RefreshUpdatedEmployeeHistory)

Not sure if we are supposed to run rebuild every day and not sure which process should go first, is it refresh or rebuild?

What is the purpose or each process? Is the employee update process depended on the rebuild process?

How can we set up how far back the employee history? Can this be set up like the last 90 days or 6 months?

Our requirement is to extract employee information history i.e. org unit, termination date, rates, etc.

Thank you so much for your help.

Christina

Find more posts tagged with

Accepted answers

All comments

mmacgown

Hi Christina,

Your "Terminated Abnormally" error may come from the fact that you have scheduled both the Rebuild and the Refresh at the same time. Rebuild action purges the entire history data set reloads it (both a rebuild and a refresh with most up-to-date data). The Refresh action, on the other hand, is meant to bring existing data in History up to date when run. The Rebuild action typically takes much longer to complete than the Refresh because it is manipulating the entire data set. I generally advise that organizations run the Rebuild action once weekly (typically in a slow day/time like over a weekend, and set the Refresh to run nightly to update existing data.

As far as look-back date ranges, it depends on what your reporting needs are. Some organizations pull in everything during a Rebuild, while others go back a range of time that is less than "All" but sufficient to address reporting requirements. As you might imagine, the time span to run a Rebuild with a much more recent look-back time would be much smaller.

Hope this helps!

Martin

reaganr

Hi Martin,

My company runs a refresh every night and are experiencing scenarios where all changes are not reflected in the EmployeeFieldHistory business class when a change is made prior to another effective date. I submitted an infor incident for this issue. However, I am curious about your advice to rebuild employee history every weekend. Will you provide more information on that? Have you had similar issues where a refresh doesn't pull in all the data?

Thanks,

mmacgown

Hi Rhonda,

The issues you report sound like they are tied to the History Configuration settings (Administrator > Reports > Employee History > Setup > History Configuration. Do you have all available fields in the Field Selection tab enabled? Also, depending on the volume of your employee data set, you may consider expanding the look-back History Start Date further, and running the Rebuild more frequently.

Martin

reaganr

Hi Martin,

Thanks for your input. I believe our configuration is set properly. It takes several days to run a rebuild in our system because of the amount of data that has to be rebuilt so we have not run the rebuild since a month or 2 after our go live last year. Our main issue is when a change is made prior to an effective date that was already entered the refresh doesn't recognize a change that needs to be refreshed. No need for further brainstorming, I'll continue on with the infor incident and see what support says. Again, appreciate your suggestions.

unknown

Hi Martin,

Sorry for my late reply and thank you so much for answering my inquiries. You helped me a lot. Now I understand how rebuild and update work. I will keep the schedule hour the same but I'm going to schedule rebuild once a week (Sunday) and refresh update every day except Sunday (Mon to Sat).

We have history configuration set up to 18 months History Offset and there was a date below the History Offset field it is currently set to 4/21/2021 and greyed out. I cannot edit the field so not sure what is that date field for.

Thanks,

Christina

unknown

Hi,

After I changed the schedule Refresh/Update employee ran successfully but not Rebuild Employee it didn't give us much details on the error. Here's the error we got from email notification.

Object:    Employee
Action:    CreateAllEmployeeHistoryThread
Keys:      HROrganization=       Employee=0

Error:     Exception ID: null
Remote call failed
1st attempt.

The job finally completed with error after 1 day and 4 hours. Do you have idea what the error below means? I'm thinking to change the Employee History Configuration from 18 months to 6 months. Do you think the error has something to do with how much history we are building?

Request: c9f5f85b-c180-ed86-000bc584634a458c
Trigger: 1
Status: Lost While In Progress Failure Code: Lost While In Progress
Queue: HCMConcurrentActions
Actor: 46834 Submitted As Proxy: No
Authenticated Actor: 46834

Runtime Data: tam-ds-203-9f69-i0a1f38501f0a79f69:Async:MQZ
T-14296
Remote Runtime Data: tam-be-203-1485-i0a44de811a3251485:BG_Lmrk
BLDoc:qdLq-13934

Action
Action Type: LandmarkAction Data Area: NHC_PRD_HCM

Module: hr Class: Employee

Action: CreateAllEmployeeHistoryThread

Parameters: <?xml version="1.0" encoding="utf-8"?><view name="CreateAllEmployeeHistoryThread"
className="Employee" viewName="Employee" dataArea="nhc_prd_hcm"
executor="REMOTE_GRID" layoutType="0" action="CreateAllEmployeeHistoryThread"
isDisplayOnly="false"><action name="CreateAllEmployeeHistoryThread" type="SET"
isRequestAction="false" scheduleType="BACKGROUND"
scheduleChoice="BACKGROUND"></action><fields><field name="PrmHROrganization"
id="PrmHROrganization"><![CDATA[ALL]]></field><field name="PrmEmployee"
id="PrmEmployee"><![CDATA[0]]></field><field name="PrmRelationshipToOrganization"
id="PrmRelationshipToOrganization"><![CDATA[]]></field><field
name="PrmRelationshipStatus" id="PrmRelationshipStatus"><![CDATA[]]></field><field
name="PrmWorkType" id="PrmWorkType"><![CDATA[]]></field><field
name="PrmHistoryStartDate" id="PrmHistoryStartDate"><![CDATA[20210423]]></field><field
name="PrmEligibilityGroup" id="PrmEligibilityGroup"><![CDATA[]]></field><field
name="NumberOfThreads" id="NumberOfThreads"><![CDATA[2]]></field><field
name="Thread" id="Thread"><![CDATA[0]]></field></fields><views></views></view>

Auditing
Requested Start: 10/23/2022 12:21:49 AM Created: 10/23/2022 01:39:35 AM Started: 10/23/2022 01:39:35
AM
Error Message
Stack Trace
Retry Information
Max Retries: 10

Thank you for your help.

Christina

jreese

Based on where the Keys are showing HROrganization = I would first look at the parameters you set for the rebuild job. It appears that no HROrganization was passed to process.

unknown

Hi Jreese,

Thanks for your reply.

Just an update on the issues we were having. After changing the history configuration from 18 months to 6 months the job ran successfully but it took 7 hours to rebuild the employee data.

Thanks,

Christina

unknown

The other job that you should consider if you only want X number of days is the dynamic purge so that you can build the Employee history once, refresh the employee history (periodically) with new data and dynamically purge the older data periodically as well.

Copyright © 2025 Infor. All rights reserved.