Error and warning messages

Error Message	Description
No rows were added for Employee {Employee Name} because it is a pending employee. Please use the ION processor to complete the initial employee creation to mark this employee as non-pending	This update was for an employee in pending status. Use the ION processor to complete the initial employee creation to mark the employee as not pending.
No rows were added for Employee {Employee Name} because it is a pending employee with pre-existing rows, existing rows will be updated	Although the ION process was used, the rows were already created for the pending employee. In this instance, only updates are allowed.
Calc Group Mapping not found.	The mapped calculation group was not found.
Error: Calculation group {x} not found).	Calculation group could not be found and a new one could not be created because of HR_LOOKUP settings.
Docket {x} and can not be created based on HR_LOOKUP settings.	Docket could not be found and a new one could not be created because of HR_LOOKUP settings.
Error in inserting default calc group.	Error in inserting the default calculation group.
Error parsing EMP_FLAG: more than 20 chars found.	The EMP_FLAG field is over the allotted 20 characters long.
Error parsing OVR_START/END_DATE. Expected mm/dd/yyyy format while attempting to parse {x}.	Invalid formats for OVR_START_DATE and OVR_END_DATE used.
Error parsing WBU_PWD_CHANGED_DATE. Expected mm/dd/yyyy format while attempting to parse {x}.	Invalid WBU_PWD_CHANGED_DATE format used.
Error: A UDF definition for {x} could not be found and can not be created based on HR_LOOKUP settings.	The UDF definition could not be found and a new one could not be created because of HR_LOOKUP settings.
Error: A Team definition for {x} could not be found.	A team could not be found and a new one could not be created because of HR_LOOKUP settings.
Error: Wrong mode while processing balance update: {x}.	The balance mode in the balance string is not set to ADD or SET.
Error: Could not find balance while processing balance update: {x}.	The balance was not found in the balance string.
Error: Balance {x} set to be cancelled was not found.	The balance for which the override was to be cancelled was not found for the employee.
Warning: Value provided for CANCEL operation	The Cancel operation is meant to cancel any existing balance overrides and does not require a value. Any value provided is not considered.
Error: Employee {x} could not be mapped to a {y}.	The related employee mapping resolved to no value, which created a mapping error.
Error: Entitlement policy {x} does not exist.	The entitlement policy was not found.
Error: Import record (ID for employee {x}) did not load as it was missing key employee data. EMP_NAME field requires data.	The EMP_NAME field was not supplied.
Found blank team name in data: {x}.	The team name cannot be null if team string supplied.
Hour type (no hour type named {x} found) and can not be created based on HR_LOOKUP settings.	The hour type could not be found and a new one could not be created because of HR_LOOKUP settings.
Job (no job named {x} found) and can not be created based on HR_LOOKUP settings.	The job could not be found and a new one could not be created because of HR_LOOKUP settings.
Malformed UDF field number {x}. Expected <name> ~<value> .	The employee UDF parameters are in the wrong format.
Pay Group Mapping not found.	The mapped pay group was not found.
Project (no project named {x} found) and can't be created based on HR_LOOKUP settings.	The project could not be found and a new one could not be created because of HR_LOOKUP settings.
Security Group Mapping not found.	The mapped security group not found.
Error: Shift pattern (no shift pattern named {x} found).	The shift pattern could not be found and a new one could not be created because of HR_LOOKUP settings.
Shift Pattern Mapping not found.	The mapped shift pattern was not found.
SO _FLAG employee map not found with name {x}.	The mapped SO employee was not found. Note: Schedule optimization is not supported in multi-tenant deployments of WFM.
Time code (no time code named {x} found) and can not be created based on HR_LOOKUP settings.	The time code could not be found and a new one could not be created because of HR_LOOKUP settings.
Error getting pluggable processor for class {x}.	The class defined in the processor could not be loaded.
Error: An EDL definition does not have tilde separated strings.	The strings in an EDL definition are not separated by tildes.
Error: The number of Job Names and Job Rate Indice are different.	The number of job names does not match the number of job rate levels.
Error: The number of Job Names and Job Ranks are different.	The number of job names does not match the number of job ranks.
Error: Job (no job named {x} found).	Imported job was not found in the database.
Error: Missing Parameter for UDF Data.	Some UDF data is missing a parameter.
Unsupported type for column: {x}.	The mapping interface does not support the data type for given field.
Could not find column '{x}' in input table.	The column was not defined in the mapping interface.
Field ({x}) size cannot be bigger than {y}.	A given field's character limit was exceeded.
{x} is not defined for employee. Check employee UDF definition set up for employee name: {y}.	A UDF field for an employee was not formatted properly, or is missing.
The following team was not created properly: {x}.	The given team record was not created.
EmpFlag index must be between 1 and 20.	The index number for the EmpFlag does not fall between 1 and 20, inclusively.
EmpVal index must be between 1 and 20.	The index number for the EmpVal does not fall between 1 and 20, inclusively.
Employee first/last name cannot be null.	The employee's last and first names were not supplied.
Employee ID cannot be null.	The employee's ID was not supplied.
No edit can be made before paygroup hands off date: {x}.	The imported employee's OVR_START_DATE occurs prior to the Hands Off date of the employee's pay group.
User name must not contain apostrophes. User name entered: {x}.	The given employee name contains apostrophes, which can not be used in the user name format.
User name already exists. User name entered: {x}.	The given employee name already exists in the database.
Employee Badge Number already exists. Employee Badge Number entered: {x}.	The given employee badge number already exists in the database.
Balance {name} must be between {x} and {y}. Value entered: {z}.	For balance validation, the balance value must fall between pre-defined values.
An error has occurred while processing the batch.	An error was encountered while the Employee Import batch was being processed.
For more details, review the error log using the following reference ID: {x}.	Open the error log file to view detailed information on a error that matches the given reference ID.
Error in cloning SO Employee Data.	An error occurred while attempting to clone schedule optimization employee data. Note: Schedule optimization is not supported in multi-tenant deployments of WFM.
Error in loading SO_EMPLOYEE Data.	An error occurred while attempting to load schedule optimization employee data. Note: Schedule optimization is not supported in multi-tenant deployments of WFM.
Error when moving team: {x}	A team movement, in the team structure, made by the Employee Import causes an error.
Error: Number of elements in {x} is different from the number of elements in {y}.	The number of associated elements does not match.
Error: {x} can not exceed {y} characters.	A given data element's character limit was exceeded.
Error: Number of elements in {x} exceeded the number of elements in {y}.	The number of elements in an employee record exceeds the number of a directly related elements in the same employee record.
Error: {x} definition does not have {y} tilde separated strings.	The strings in a data definition are not separated by the expected number of tildes.
Error: Reader Group (no reader group named {x} found).	The given reader group was not found.
User is already granted ancestor team(s) for input team and role within the given period.	A user already holds a non-virtual role in the team structure in the same time period.
Can not assign non-virtual role: {x} as it is currently assigned to another user for the team.	A non-virtual role cannot be assigned to an imported employee because that role is already taken by an existing employee.
Error: Team {x} does not exist.	The given team does not exist in the database.
Error: Role {x} does not exist.	The given role does not exist in the database.
Warning: User name is blank.	When updating team assignments, the user name for a given employee is missing.
Warning: Team assignment {x} does not exist.	The team assignment is missing from the database when attempting to delete a team assignment..
Employee group name specified in SO_EMPLOYEE column does not exist: {x}. Default employee group is used.	The given employee group name does not exist in the database. The default group is assigned to the employee. Note: Schedule optimization is not supported in multi-tenant deployments of WFM.
Data exists in SO_EMPLOYEE column but registry entry scheduleOptimization/IS_ENABLED is false. Set this registry entry to true to process schedule optimization data.	For the system to accept schedule optimization data, the scheduleOptimization/IS_ENABLED registry parameter must be set to true. Note: Schedule optimization is not supported in multi-tenant deployments of WFM.
Error: User role action must be {x}, {y} or {z}.	The user role action is neither Add, Delete, or Update.
Error: No pluggable processors are loaded	This error occurs when a processor that is part of the Employee Import fails.
Error: Mandatory fields must be included in Layout	One (or all) of the OVR_START_DATE, OVR_END_DATE and EMP_NAME fields were not supplied.
Warning: Team structure changed. Team {x} has been moved from parent ID {y} to {z}. Please confirm.	Team has been moved based on given team string.
Employee Badge UDF value cannot exceed 40 chars	The EMP_BADGE_UDF field has a value more than 40 characters within each tilde (`~`) separator.
EMPBDG_ENABLE_BIO has invalid value ' X', valid values are 'Y' or 'N'	The EMPBDG_ENABLE_BIO field has a value other than Y or N.
EMPBDG_ENFORCE_SKD has invalid value ' X', valid values are 'Y' or 'N'	The EMPBDG_ENFORCE_SKD field has a value other than Y or N.
EMPBDG_SUP_LEVEL has invalid value ' X', valid values are character values less than equal to 3 characters	The EMPBDG_SUP_LEVEL field has a value of more than three characters.
EMP_BADGE_FLAG has invalid value ' X', valid values are 'Y' or 'N'	The EMP_BADGE_FLAG field has a value other than Y or N within each tilde separator.

No rows were added for Employee {Employee Name} because it is a pending employee. Please use the ION processor to complete the initial employee creation to mark this employee as non-pending

This update was for an employee in pending status. Use the ION processor to complete the initial employee creation to mark the employee as not pending.

No rows were added for Employee {Employee Name} because it is a pending employee with pre-existing rows, existing rows will be updated

Although the ION process was used, the rows were already created for the pending employee. In this instance, only updates are allowed.

Calc Group Mapping not found.

The mapped calculation group was not found.

Error: Calculation group {x} not found).

Calculation group could not be found and a new one could not be created because of HR_LOOKUP settings.

Docket {x} and can not be created based on HR_LOOKUP settings.

Docket could not be found and a new one could not be created because of HR_LOOKUP settings.

Error in inserting default calc group.

Error in inserting the default calculation group.

Error parsing EMP_FLAG: more than 20 chars found.

The EMP_FLAG field is over the allotted 20 characters long.

Error parsing OVR_START/END_DATE. Expected mm/dd/yyyy format while attempting to parse {x}.

Invalid formats for OVR_START_DATE and OVR_END_DATE used.

Error parsing WBU_PWD_CHANGED_DATE. Expected mm/dd/yyyy format while attempting to parse {x}.

Invalid WBU_PWD_CHANGED_DATE format used.

Error: A UDF definition for {x} could not be found and can not be created based on HR_LOOKUP settings.

The UDF definition could not be found and a new one could not be created because of HR_LOOKUP settings.

Error: A Team definition for {x} could not be found.

A team could not be found and a new one could not be created because of HR_LOOKUP settings.

Error: Wrong mode while processing balance update: {x}.

The balance mode in the balance string is not set to ADD or SET.

Error: Could not find balance while processing balance update: {x}.

The balance was not found in the balance string.

Error: Balance {x} set to be cancelled was not found.

The balance for which the override was to be cancelled was not found for the employee.

Warning: Value provided for CANCEL operation

The Cancel operation is meant to cancel any existing balance overrides and does not require a value. Any value provided is not considered.

Error: Employee {x} could not be mapped to a {y}.

The related employee mapping resolved to no value, which created a mapping error.

Error: Entitlement policy {x} does not exist.

The entitlement policy was not found.

Error: Import record (ID for employee {x}) did not load as it was missing key employee data. EMP_NAME field requires data.

The EMP_NAME field was not supplied.

Found blank team name in data: {x}.

The team name cannot be null if team string supplied.

Hour type (no hour type named {x} found) and can not be created based on HR_LOOKUP settings.

The hour type could not be found and a new one could not be created because of HR_LOOKUP settings.

Job (no job named {x} found) and can not be created based on HR_LOOKUP settings.

The job could not be found and a new one could not be created because of HR_LOOKUP settings.

Malformed UDF field number {x}. Expected <name> ~<value> .

The employee UDF parameters are in the wrong format.

Pay Group Mapping not found.

The mapped pay group was not found.

Project (no project named {x} found) and can't be created based on HR_LOOKUP settings.

The project could not be found and a new one could not be created because of HR_LOOKUP settings.

Security Group Mapping not found.

The mapped security group not found.

Error: Shift pattern (no shift pattern named {x} found).

The shift pattern could not be found and a new one could not be created because of HR_LOOKUP settings.

Shift Pattern Mapping not found.

The mapped shift pattern was not found.

SO _FLAG employee map not found with name {x}.

The mapped SO employee was not found.

Note: Schedule optimization is not supported in multi-tenant deployments of WFM.

Time code (no time code named {x} found) and can not be created based on HR_LOOKUP settings.

The time code could not be found and a new one could not be created because of HR_LOOKUP settings.

Error getting pluggable processor for class {x}.

The class defined in the processor could not be loaded.

Error: An EDL definition does not have tilde separated strings.

The strings in an EDL definition are not separated by tildes.

Error: The number of Job Names and Job Rate Indice are different.

The number of job names does not match the number of job rate levels.

Error: The number of Job Names and Job Ranks are different.

The number of job names does not match the number of job ranks.

Error: Job (no job named {x} found).

Imported job was not found in the database.

Error: Missing Parameter for UDF Data.

Some UDF data is missing a parameter.

Unsupported type for column: {x}.

The mapping interface does not support the data type for given field.

Could not find column '{x}' in input table.

The column was not defined in the mapping interface.

Field ({x}) size cannot be bigger than {y}.

A given field's character limit was exceeded.

{x} is not defined for employee. Check employee UDF definition set up for employee name: {y}.

A UDF field for an employee was not formatted properly, or is missing.

The following team was not created properly: {x}.

The given team record was not created.

EmpFlag index must be between 1 and 20.

The index number for the EmpFlag does not fall between 1 and 20, inclusively.

EmpVal index must be between 1 and 20.

The index number for the EmpVal does not fall between 1 and 20, inclusively.

Employee first/last name cannot be null.

The employee's last and first names were not supplied.

Employee ID cannot be null.

The employee's ID was not supplied.

No edit can be made before paygroup hands off date: {x}.

The imported employee's OVR_START_DATE occurs prior to the Hands Off date of the employee's pay group.

User name must not contain apostrophes. User name entered: {x}.

The given employee name contains apostrophes, which can not be used in the user name format.

User name already exists. User name entered: {x}.

The given employee name already exists in the database.

Employee Badge Number already exists. Employee Badge Number entered: {x}.

The given employee badge number already exists in the database.

Balance {name} must be between {x} and {y}. Value entered: {z}.

For balance validation, the balance value must fall between pre-defined values.

An error has occurred while processing the batch.

An error was encountered while the Employee Import batch was being processed.

For more details, review the error log using the following reference ID: {x}.

Open the error log file to view detailed information on a error that matches the given reference ID.

Error in cloning SO Employee Data.

An error occurred while attempting to clone schedule optimization employee data.

Note: Schedule optimization is not supported in multi-tenant deployments of WFM.

Error in loading SO_EMPLOYEE Data.

An error occurred while attempting to load schedule optimization employee data.

Note: Schedule optimization is not supported in multi-tenant deployments of WFM.

Error when moving team: {x}

A team movement, in the team structure, made by the Employee Import causes an error.

Error: Number of elements in {x} is different from the number of elements in {y}.

The number of associated elements does not match.

Error: {x} can not exceed {y} characters.

A given data element's character limit was exceeded.

Error: Number of elements in {x} exceeded the number of elements in {y}.

The number of elements in an employee record exceeds the number of a directly related elements in the same employee record.

Error: {x} definition does not have {y} tilde separated strings.

The strings in a data definition are not separated by the expected number of tildes.

Error: Reader Group (no reader group named {x} found).

The given reader group was not found.

User is already granted ancestor team(s) for input team and role within the given period.

A user already holds a non-virtual role in the team structure in the same time period.

Can not assign non-virtual role: {x} as it is currently assigned to another user for the team.

A non-virtual role cannot be assigned to an imported employee because that role is already taken by an existing employee.

Error: Team {x} does not exist.

The given team does not exist in the database.

Error: Role {x} does not exist.

The given role does not exist in the database.

Warning: User name is blank.

When updating team assignments, the user name for a given employee is missing.

Warning: Team assignment {x} does not exist.

The team assignment is missing from the database when attempting to delete a team assignment..

Employee group name specified in SO_EMPLOYEE column does not exist: {x}. Default employee group is used.

The given employee group name does not exist in the database. The default group is assigned to the employee.

Note: Schedule optimization is not supported in multi-tenant deployments of WFM.

Data exists in SO_EMPLOYEE column but registry entry scheduleOptimization/IS_ENABLED is false. Set this registry entry to true to process schedule optimization data.

For the system to accept schedule optimization data, the scheduleOptimization/IS_ENABLED registry parameter must be set to true.

Note: Schedule optimization is not supported in multi-tenant deployments of WFM.

Error: User role action must be {x}, {y} or {z}.

The user role action is neither Add, Delete, or Update.

Error: No pluggable processors are loaded

This error occurs when a processor that is part of the Employee Import fails.

Error: Mandatory fields must be included in Layout

One (or all) of the OVR_START_DATE, OVR_END_DATE and EMP_NAME fields were not supplied.

Warning: Team structure changed. Team {x} has been moved from parent ID {y} to {z}. Please confirm.

Team has been moved based on given team string.

Employee Badge UDF value cannot exceed 40 chars

The EMP_BADGE_UDF field has a value more than 40 characters within each tilde (~) separator.

EMPBDG_ENABLE_BIO has invalid value ' X', valid values are 'Y' or 'N'

The EMPBDG_ENABLE_BIO field has a value other than Y or N.

EMPBDG_ENFORCE_SKD has invalid value ' X', valid values are 'Y' or 'N'

The EMPBDG_ENFORCE_SKD field has a value other than Y or N.

EMPBDG_SUP_LEVEL has invalid value ' X', valid values are character values less than equal to 3 characters

The EMPBDG_SUP_LEVEL field has a value of more than three characters.

EMP_BADGE_FLAG has invalid value ' X', valid values are 'Y' or 'N'

The EMP_BADGE_FLAG field has a value other than Y or N within each tilde separator.