Employee is not being terminated correctly using the HRPersonnel BOD

When the HR admin doesn't follow the correct termination workflow, for example, not using the Terminate button or completing both Term Pending and Term Final steps, WFM can fail to process the employee termination or inactivate their work assignments.

Causes

  • A lack of clarity on the two-step termination process.
  • Differences in termination handling fields compared to other HRPersonnel fields.

Solution

If tables like employee-job are not being truncated:

  • Review the expectations for Term Pending and Term Final in the two-step termination process. Only the final step inactivates work assignments, while the pending step adds a WFM termination override but leaves assignments active. If only the pending step was completed, work assignments will remain active. Ensure that the final termination step is completed.

    See the information about Terminating resources in the Infor HR Talent User and Administration Library (Cloud and On-premises) and select Administrator > HR Talent Resources Setup and Administration.

    Note: WFM treats inactivation and termination as two unrelated operations. Termination is driven by the presence of termination-related initiating action in the BOD XML. Inactivation is driven by a work assignment’s active field.
  • Check the HRT relationship status used for the Term Final step, and enable the work assignment inactivation checkbox on that status, since this check box controls whether the work assignment is inactivated and treated as a Term Final.

    See the information about Inactivate Work Assignment in the Infor HR Talent User and Administration Library (Cloud and On-premises) and select Administrator > HR Talent Resources Setup and Administration.

If termination is not occurring:

  • Click the Terminate button on HRT. Unlike most HRPersonnel fields, WFM termination handling does not trigger from a change in the termination date alone. WFM expects terminations to be initiated using the Terminate button, specifically when the BOD XML InitiatingAction field equals Terminate.
  • HRT’s Termination Turnover feature has basic support, which means the WFM integration syncs the incoming Termination Date as-is and does not perform any checks or business validations. WFM responds to HRT’s termination turnover when the InitiatingAction XML field equals UpdateTermination.

    See "Corrections for turnover calculations" in Infor HR Talent User and Administration Library and select Administrator > HR Talent Setup and Administration > Organizational structure.

  • Partial terminations are not supported on WFM, where the termination validTo date is not blank. WFM only supports permanent terminations.
Note: 
  • WFM's termination date is the first day on which the employee is not working while HRT's termination date is the last date the employee was working. The default processing logic for the termination field expects HRT to increment the termination date by 1 day, so this is the first date not working. Although the XML field is named WFMLastDayWorked, this means the last day not worked which is what WFM expects. .
  • If multiple terminations are received consecutively on WFM, they become WFM overrides which stack on top of each other.

See the information about Terminations and rehires in the Infor HR Talent Integrations Library (Cloud and On-premises) and select HR Talent to WFM integration.