Benefit Record (MED) has an end date that is earlier than begin date...

[mike_mccrary]

Hello All,

I am currently looking for some direction on an issue that came up in our HR system. We have an employee that has an end date that is earlier than her begin date for a Medical Plan.

Not sure how this happenend, but when I try to change the end date using PA30, I receive RUNTIME ERROR " UNCAUGHT_EXCEPTION - CX_HRPA_VIOLATED_PRECONDITION ".

I was wondering if anyone knows of a SAP Utility that I can run to correct this end date?

Thanks,

Mike

ECC 6.0

[jayantvenkata · Accepted solution]

Hello Mike

Thanks for the update. No actually it will not have any negative impact on your system as these entries were actually delivered by mistake and should not have been there in the first place.

personnel assignments versus main personnel assignments comes into picture when you use concurrent employment.

Thanks and Kind Regards

Ramana

[mike_mccrary · Accepted solution]

Hello Ramana,

Thank you for all your help.

Mike

[jayantvenkata]

Hello Mike

Yes ,please follow the process ,and this should work.

Thanks and Kind Regards

Ramana

[mike_mccrary]

Hello Ramana,

This did resolve my issue. I was able to change the end date of the employeeu2019s record successfully.

But, this is what I understand so far; I believe. Since we do not use Concurrent Employment, this table is not useful to us. Per the note, that you mentioned, these entries were probably placed in this table via a Support pack.

So, by removing these entries, is there any impact that I need to be aware of? Also, can you elaborate on what you mean by personnel assignments versus main personnel assignments?

You have been really helpful and I appreciate that.

Thank you,

Mike

[mike_mccrary]

Hello Ramana,

Thank you for your response on the issue we are having. I check table V_T582G and it contains IT 167, 168 and 169 with a grouping reason of XMOL (Country Grouping). Now, I am not sure if these assignments were done by our HR Implementation team or were these assignments done with installation/default?

So, you are saying that if I remove these entries, that I should be able to change/delete the record without receiving the ABAP Runtime error?

Thanks again,

Mike

[jayantvenkata]

Hello Mike

The benefits infotypes should only be maintained for the main personnal assignment.

It should not be shared between the assignments,i.e., the view V_T582G should not contain entries for the infotypes

167,168 and 169.

These entries were added incorrectly due to the note 995270.This could be the reason for the dump being encountered.

I would suggest you to reomove the entries(167,168,169) from the view V_T582G and also delete the infotype records created for personnal assignments other than the main personnal assignment, if any.

Infotype 167, 168 and 169 record ahould exist only for the main personnel assignment.

When main personnel assignment is changed, the benefit infotypes for the old Main pers. assignment gets delimited and new benefits infotype records are created for the new main pers assignment. This is the standard behaviour .

Thanks and Kind Regards

Ramana