Skip to main content
Solved

"Assignment and Employement Period are Inconsistent" - Is the a better way to resolve this?

  • February 5, 2025
  • 2 replies
  • 23 views
H
Sidekick (Customer)
Forum|alt.badge.img+7

Hi,

 

This is related to error when generating absence for people who has change of position/assignment.

 

Context: Take this example - Employee E103111 has change of position multiple times within the company but his employment start date is 15/12/2022. See below screenshot:

 

 

What the HR person normally do to fix this is to temporarily change the latest assignment of a person to match with the person employment start date. Which is super inconvenient for them.

This thing has been an unproductive issue for a long time, but we do not know any better solution exist.

Imagine if there is more than 100 people to generate absence and half of them need to do this temporary change, it is a nightmare.

Please share or propose any better solution for this problem.

 

Best answer by ADDMARIAE

Hi,

Employees need a primary organization assignment for each day they are employed (each day in the employment period). I can see that this employee’s first assignment from 15/12/2022 is not Primary - this could cause problems, have you tested just to correct that?

I agree that it is a bit unnecessary for the system to check the employee’s FULL employment period - the only interesting when generating limits is the employment(s) valid during the earning period… This has been on my todo list for reporting to support for some time:-)

It is very common that you have a full history in employment periods going way back but organization assignments are only updated from the time you started using IFS HCM.

Regards,

Maria

 

View original
Did this topic help you find an answer to your question?

2 replies

ADDMARIAE
Superhero (Partner)
Forum|alt.badge.img+14
  • ADDMARIAE
  • Superhero (Partner)
  • 289 replies
  • Answer
  • February 5, 2025

Hi,

Employees need a primary organization assignment for each day they are employed (each day in the employment period). I can see that this employee’s first assignment from 15/12/2022 is not Primary - this could cause problems, have you tested just to correct that?

I agree that it is a bit unnecessary for the system to check the employee’s FULL employment period - the only interesting when generating limits is the employment(s) valid during the earning period… This has been on my todo list for reporting to support for some time:-)

It is very common that you have a full history in employment periods going way back but organization assignments are only updated from the time you started using IFS HCM.

Regards,

Maria

 

N
1 person likes this
  • N
    nimesh
H
Sidekick (Customer)
Forum|alt.badge.img+7
  • hamiasmai
  • Author
  • Sidekick (Customer)
  • 19 replies
  • February 5, 2025

Thanks Maria,

I just tested it out and your suggestion of ticking the Primary assignment seems to be the solution! This idea didn’t come to me because normally I see only 1 Primary assignment is ticked and I didnt know we can have many lines for primary assignment as long as period are not overlapping.

Thanks again, will bring this solution to my HR team.

Best Regards

Hami

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings