Skip to Content
avatar image
Former Member

employee historical record

Hi,

We encountered below issue, let's talk about it.

our company implement SAP PA&OM only in 2008, with some reason the historical position record of employee has not been recorded into system,  all employee's position before 2008, we assign her/him with 99999999, and all Org.Unit and position starts from 2008, not the exactly start date.

We want to record the historical position now, so have to change the first action's position to actual one's, and have to change all Org.Unit and position's start date to previouly date, but these Org.Unit and position already occupied by person.

For above two action is there any good solution? can we use LSMW to change the action, and can we also use LSMW to change Org.Unit and position? If we really can change the Org.Unit and position?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Oct 22, 2015 at 07:05 AM

    Hi Jiangang,

    How many objects are there (S,O and C)..?

    Regards
    Mohan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 21, 2015 at 07:04 AM

    Could you let me know:

    1) What is the start date of the hiring action you have used for all employees? Is it the original date of hire for employees whose DOJ is prior to 2008?

    2)Has payroll been executed for past periods?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      1)To change the start date of the objects, use the standard SAP transaction RE_RHBEGDA0. If start date of any relationship (O-S and S-P) has to be changed, you can use the same tcode.

      2) To create nay new relationships(O-S and S-P), you can create an LSMW.

      3)You can also create an action type in PA (e.g. Data correction / History update) where position can be assigned to the employee for old periods.

      Create an LSMW for this action as well. You can omit this step if you don't want to capture this in IT0.

      4) After the first 3 steps (or 2 steps if you decide to omit the third), you may need to run RHINTE30 to get IT 1 in sync with the OM relationships.

      The reason I asked if you were already using payroll is that all these backdated changes would probably trigger retro. This will not stop you from implementing payroll in the future.

  • avatar image
    Former Member
    Oct 21, 2015 at 02:23 PM

    As a company, we actually went a different route in regards to recording previous job history.  In our situation, we were migrating to SAP from Peoplesoft.  We decided to create a 5 custom infotypes to record job history, position history, department history, status history and salary history.  This scenario is a little different than yours, obviously, but maybe it gives you another option to think about.

    Add comment
    10|10000 characters needed characters exceeded