Matching feature LEAVE/ENTRY - company changes

[Former Member]

Hi

I am aware that the value for JUPER should match in feature LEAVE/ENTRY to make sense. (Note 1141482). However - this is not the only option for the feature. In our system, feature ENTRY is set up with datetype (VB). So the date in datetype VB decides when a person is considered entering a company. This was done due to some requirements for reports to authorities. To my understanding, JUPER is then not at all considered in feature ENTRY.

The question then is: What to do with JUPER in feature LEAVE?

Problem at hand:

2 companies merge - and all employees are moved into one company.

This causes change of JUPER. But in my opinion we should not change date VB, as they do not have a new entry date.

If we set up feature LEAVE with blank JUPER and leave VB we get a situation where they are not reported correctly to our official employee register. In this register they should be reported leaving one JUPER and entering another. But conceptually they are not changing their hiring conditions to the company.

Anyone had any experience with personell doing company changes like this (where there is not a real leave/entry).

How did you deal with this?

Any input appreciated.

/Kirsten

[Former Member]

Hi Kirsten,

I suppose VARKY(Key dependent on report category) the JUPER X and REENT X need to be set to meet the requirement.havent explored it albeit.

No Worries

KG

Edited by: SAPenjoy:) on Sep 8, 2010 8:44 AM

[siddharthrajora]

Leave

have all return values as NULL

In ENTRY ensure juper is set as X ie REENT X

o REENT X

Any reentries into the company are taken into account. Previous entries

are no longer taken into account

o JUPER X

Changes in legal are valuated in the same way as an entry

[Former Member]

@siddharth:

When we have set ENTRY to datetype VB, I don't believe we can also play with the REENT and JUPER can we?

we cannot change away from VB unfortunately.

Thanks

Kirsten

[Former Member]

I am marking the question answered.

Apparently the official reports for Norway is written in such a way by SAP that when a change in organizational number happens, we need to mark employees as leavers in old JUPER and entering new JUPER.

In my mind this is conceptually incorrect in a merger - but as we need to make official reports take preference, we need to have the settings JUPER X in LEAVE and datetype VB in ENTRY, and also update VB with the date of transfer.

Gives strange results in some reports, so I think we need to make an OSS to SAP to ask why reports are written this way.

Thanks for input.

/Kirsten

[Sujith_EM]

>In LEAVE feature

> JUPER X

>* Any changes to legal people are valuated as leavers*

This feature determines which data should be evaluated in function module HR_LEAVING_DATE in order to define the leaving date.

Edited by: Sujith Nambiar on Sep 7, 2010 4:53 PM

Edited by: Sujith Nambiar on Sep 7, 2010 4:54 PM