Changing Org Unit

Hi Experts,
I have created an org unit (say 5001) and a position (say 7001) then I have assigned the position to org unit and finally we hired an employee on position 7001. After the completion of hiring we realized that the org unit is wrong and hence we created to a new org unit (say 5002) and changed the position assignment from org unit 5001 to 5002 through PP02 by clicking on the change button (Pencil Icon). after doing this when I goto infotype 001 it shows the old orgunit (5001) only. Please let me know how to rectify this.
Thanks.
Note: I tried to do the same on development server it worked but it is not working on production server.

Hi,
As you have found out, your process of changing the relationship in PP02 does not directly change the IT0001on the PA side.  RHINTE30 or copying to create a new IT0001will bring in the new organization assignment. 
Next time, use the drag-and-drop functionality in PPOME.  You can drag the position to the new org unit to create the new reporting relationship.  Both IT1001and IT0001will then be changed automatically.  
In all cases above, please pay attention to the dates of the org units and the change. 
Paul

Similar Messages

  • Change Org.unit Hierarchy

    Hi,
    I want to change hierarchy of organization unit X111 immediately after X1.
    Ex:
    Existing
    Root X
            |_X1
                |_X11
                |     |_X111
                |_X12
    Required
    Root X
            |_X1
                |_X11
                |_X111
                |_X12
    Under Org.Unit X111 some employees exist. Live Payroll run at least for 1 year completed.
    Is it preferable to change org. unit report to link from X11 to X1.
    What will be implications ?
    regard,
    Chintan

    Hi Chintan,
    Go to T Code: PPOME
    According to your EX: Select X111, click on it and drag and drop it in X1. So that automatically the link flow over there. Hope there will not be any prob in payroll.
    If found useful awrad points
    Regards,
    Madhu Sudhanan

  • How to assign & changed org. unit to employee Id

    Hi
    We want to move some employees from one organizational unit to newly created one in transaction code PPOM_OLD.
    In PPOM_OLD i created new Org. unit ,assign position then assigned existing employee pernr.
    But when i see in PA30 the organizational unit remains same.
    Even when i observed in PA0001 table i can see two entries for one employee number the old entry is with organizational unit where as new one doesn't have organizational unit at all
    Please guide me how can i do changes.
    Best Regards

    Dear Raza,
    Go to pa30- given the Perner-select infotype action 0000-period- all-click on overview
    Now you can view all records related to infotype action-select the new created records-choose icon delete.
    Now create the new organization unit, Position & their relationships through t-code pp01.
    now transfer of employee from old position to new position through action tcode –pa40- select appropriate personal action (promotion, reorganization, transfer etc.)
    Put the perner and effective date –execute –in next steps change details as per requirement i.e. in second part- organ. Assignment –
    New position details –xxxxxxxx  /Personnel area-xx/Employee group-x/Employee sub group-xx
    Save.
    System goes to next info type  0001-
    In the same way give the require details & save.

  • Organization Staffing - Unable to change org.unit description

    Hi All,
    We are unable to change the short and long descriptions of org.units from the organization and staffing interface. Whereas we are able to change it from the expert mode. If we are changing the descriptions, on pressing 'Enter Key' or on 'Saving' data, system brings back the descriptions as 'New Org Unit' and 'New Organizational Unit' as short and long descriptions. Then we have to go to expert mode for changing it. Any solution ?
    Thanks
    Sreeja

    Try this:
    I presume you have a root Org Unit
    --in Goto menu (on top of the Org Unit etc where you see other icons such as one level up, etc) select Organizational Structure option
    --place your cursor on the root Org Unit and click Create icon - that brings up a small screen which reads "Create Org Unit" -- it should also have validity date as well as Short Text and Long Text
    --Make all the entries and save
    Pl let me know if this has worked for you or if you have a differnet scenario
    As such this is very simple
    remember to reward points

  • Change Org Unit in 0001 Infotype

    Hi Experts,
    Ple guide me how to change the Org Unit in Infotype 0001.
    The scenario is we have not assigned Org Unit to some employees while uploading.  Now we have to change the Org Unit in 0001 for some 50 employees. 
    What is the procedure to be followed?
    Regards
    Venu

    Hi Venu,
    If you had already uploaded the Position for 50 employees in IT 0001 than just maintained the Position to Org unit relationship  and org unit will appear in IT 0001.
    if you had uploaded the master data with Default position, than you need to create position  or assign the existing position with the person and create the relationship with the org unit
    you may use TC PPOME, PP03 OR PP01
    Trust this will help you
    warm rgds
    vishal saxena

  • Employee change Org Unit

    Is it possible to change an employee that was assigned to an Org Unit through migration?
    Organizational Management | Org Structures | End Employment Assignment is greyed out.

    Hi Michael,
    The end employment is grayed out in the WoC Org Management Edit Screen Employee Tab, if HCM is scoped and the employee is an internal employee and not a service agent.
    If HCM is not scoped or if it is a service agent you can do do the transfer in WoC OrgManagement . However do not forget to activate the org unit you transfered the employee to.
    If HCM is not scoped there is also the  lean employee UI for hiring, transfers, terminations, etc.
    Raviprasad nicely described what to do with internal employees in HCM.
    Just a remark on the manager. If there is amanger assigned to the org unit where they are transfered, this will be the new manager of the employee.
    Best regards
    Frank

  • How to change Org Unit for larg number of emplyees

    Dear Guru's,
    My client has uploaded wrong Org Units while hiring, now that has to be changed for larg number of employees.
    Can any one suggest me how can we do this for larg number of employees?
    Thanks in advance for your kind suggestions.
    Regards,
    Srinivas

    Hello Srinivas;
    By saying uploaded wrong organizational units, do you mean that organizational structure in PPOME is wrong or employee - position assignment is wrong?
    If employee - position assignment is wrong then I suggest you to use batch input program or use LSMW as you have to change it via personnel action - PA40
    If organizational structure is wrong, then do you have correct organizational structure in another system like test or qa?
    If you have correct organizational structure then you can directly transport it from one system to other but if you don't then you first need to correct the organizational structure and then run LSMW or batch input.
    Regards;
    Okan

  • Change in Position or Org Unit

    End user reported an issue, when user changes Org Unit or Position,  notifies Benefit.
    Benefits run the action transfer or correct payroll data. The top row should have a user name from the benefits ( since they ran action) but the last changes made shows by the user name who made changes to the Position or Org Unit.
    I tested, worked as it should be, first I made change to the position then ran action to correct payroll data, shows changes made by me.

    You got it. One user changed the position on OM side, the other user ran action on the PA side. The top row after the action has user's stamp or name who changed the position. Strange thing is that benefit is complaining that first grouuping for one EG is defaulted back that they manually changed after the first user made changes to position, and this record has user name who changed position.
    I tested, issue is not replicating.

  • Employee resposnsibles Org unit Determination  (Employee is assigned to Org Unit)

    Hi ,
    We want to determine Org unit based on employee responsible but not on basis of USER.
    Employee responsible will be assigned to a particular position in Organization .
    We want to determine Organization unit where Employee is assigned .
    When in transaction Partner Function employee responsible is selected then Organization unit to which employee is assigned should get determined.
    When employee resposnsible is changed Org unit (Service ) should change .
    Please suggest solution.
    Thanks & Regards,
    Anup Reche

    Hi
    first u need to do the filter settings in object BUPA_MAIN to stop the employee replication to R3.
    When u create the no. ranges in r3 u can remove the filter so that the process will continue.
    Regards
    Manohar

  • Best Practice - Changing description for Org Unit/Position or creating new?

    Hello Freinds,
    I just want to know from your experience what's normally practiced in your implementations for OM :-
    For scenarios where there is a need to change the description of a particular org unit or position, do u
    1. just change the description effective a particular date (to maintain history) or
    2. put an end date to those objects and create new ones ?
    Solution 1 is quick and easy, but in IT0001 the description displayed is as on start date of that infotype which is normally a date prior to the change in desc of those objects. As a result this infotype keeps displaying old description.
    Is there any way to change this display to show the current description instead of the description as on start date of this infotype ???
    Solution 2 calls for a lot of related activities, say if i create a new org unit and delemit the old one - then i have to move all the sub org units and positions into this new one ... which is quite time consuming and doesn't really seem practical.
    How do u manage such scenarios ?
    Thanks
    Allen

    We use option #1, although I am not sure this is best practice.  Using option 1 for positions makes it challenging when it comes to reporting on length of time in position.  We frequently have the scenario where a person is reorged not because they applied for another position, but just because the big wigs want to move around the chess pieces.  In these cases we simply modify the position attributes and then run a PA action.  Then if you run a query and use the standard delivered Length of time in position field, it appears as if the person has been in the same position for years (which they have), but their position has been retitled, re-graded, and re-orged numerous times.  This makes it very difficult to get to an employee's length of time in their role. 
    This is a great discussion question I hope more people respond with what they do and why.

  • Problem with Org Unit Change

    Hello Experts.
    We have a problem here.
    There is an employee say : X in position ABC which belongs to Org Unit XYZ.
    Now, there is a change in the Org Structure. The postion has not changed, the employee belongs to the same position. But the Org Unit has changed to PQR and has a new chief.
    The problem is, in the SAP Portal, the Organization assignment is picking up the Chief of XYZ instead of the new chief.
    What could be the reason for this?
    Regards
    Avik

    Hi Avik,
    Check dates on records for ABCu2019s A|003 relationship to PQR and chiefu2019s A|012 relationship to PQR. Maybe the old records were not delimited and hence they are getting picked up.
    Donnie

  • Org Unit Validity Period change

    Hi Experts,
    Can any you please let me know, is there any option of changing the Org Unit Validity period.
    Ex: By mistake I have created an Org unit with Start Date as 01.01.0091 and End Date 31.12.9999.
    Now I would want to change the Validity period of Start Date from 01.01.0091 to 01.01.1900.
    This would be really helpful for me.
    Thank You,
    KishoreJ

    Hi
    you can do this by date preview  icon or delimit options.
    Regards
    Suresh

  • Update table HRP1001. Change the Position and the Org Unit.

    Hi,
    I am new to SAP HR and have been given a work in this area. The requirement is to update the relationship table HRP1001 replacing the old Manager' Position and the Org Unit with the New Manager's Position and the Org. Unit.
    I have some how found out the way to get the Postion and the Org unit of the old manager. Now I am replacing the same with the new details using the Update HRP1001 Command but this is the old and not recommended method acheiving this task.
    Can anyone please suggest me any Function Module OR the BAPI to update the HRP 1001 table with the New MAnager;s Position and the Org Unit.
    Thanks...!!!
    Regards,
    Deepak.

    Hi Kalpesh,
    I am using the FM: 'BAPI_HRMASTER_SAVE_REPL_MULT'but still not updating. I am trying to change the Position and the Org unit but not successful yet.
    I first used the Operator 'I' withi the table BAPIHROBJ-OPERATOR, it failed then I tried 'U' for update it still failed. Can you please let me know how many such operations possible with their charecter values apart from I & U. the domain value set does not exist as it is char1.
    Now I came to know that I have to terminate the old relationship by changing the ENDDA and create a new one with the new BEGDA as tomorrow's date.
    Can you please suggest something.
    Regards,
    Deepak.

  • Impact of changing positions and Org Unit short text

    Hi All..
    This is regarding the impact  of changing positions and Org Unit short text(SAP name - Object Abbreviation, technical field u2013 hrp1000-short).The new approach we are ging to have is to keep short text same across the business unit.
    Example:
    All position in US will have short text u2013 USS
    Similarly All US Org Unit short text will be COMUS
    I was wondering, from SAP best practices point of view, do you see any downside in this approach?
    Example: Any problem in searching position or org using search term.
    Please pin your thoughts...
    Thanks,
    Kumar

    Hi,
    Normally such change will not have any impact in PA module.
    Only in exceptional cases it will have an impact in following cases:
    1. First and mandatory condition that you use abbreviation as position name in IT 0001. If this is the case parameter PLOGI TEXTC (in table T77S0) should be equal X.
    2. Second condition is that parameter PLOGI SPLIT is equal to X. That means that change of object name will lead to record split in IT 0001 in PA.
    So if in table T77S0 you don't have setting PLOGI TEXTC = X and PLOGI SPLIT = X you can go ahead with change of positions abbreviations. It will have no impact on other modules.
    Cheers!

  • Changing personnel area/subarea (IT1008) from org unit to position

    We are live with PA and Org. Mgmt, but have been advised to change the infotype 1008 data - personnel area and subarea to be stored on the position instead of the org unit (where we have it now).  A big reason for this is we have cases when we need to overwrite the personnel subarea at the position level.  For example, a position belonging to an org unit with subarea ABCD, may really be in subarea WXYZ.  Therefore, even though the org unit is ABCD, it will be overwritten at the position level to WXYZ.  My understanding is that the RHINTE30 program will not work approrpiately if we are maintaining the data this way. 
    In transaction PPOME there is an account assignment tab on the org unit with cost center (filled in) and personnel area/subarea (which will be blank moving forward since that data won't be maintained on the org unit).  Then, there is also an account assignment tab on the position with cost center inherited from the org unit (sometimes needing to be overwritten at the position level), and the personnel area/subarea data.  My question is how should I handle the view of PPOME for this data?  Can I hide the personnel area and subarea on the account assignment tab for the org units only so it is not confusing for the users?  The problem with having it this way is that personnel area and subarea are blank on the org unit and filled on on the position.  They are conflicting and both visable/maintainable to the User.  Any advise please?  Thanks!

    Hi Nish,
    I gave you my input on your other related message and now will go for this one.
    As I commented on the other message, RHINTE30 will not integrate infotypes 1008 and 1013. So you don't have to worry about using this functionality (first part of your message).
    On the second part (personnel area / subarea on position rather than org unit): there are some considerations here that are more functional / process driven than technical. From a technical point of view, everything can be done. You can hide data from infotype 1008 on the tabstrip for your org. unit using dynpro handling, even via customizing. You can even transfer the data from infotype 1008 on the org. units to the positions or delimit it on the org units. There are some quite easy ways of achieving this using the LMSW tool (have you used it? I can forward some documentation).
    But personally, I would not recommend to do this from a process point of view. Everything in SAP HR is about the inheritance concept, and I think this works very well when it comes to org. units and positions. It is normally advisable to record personnel area / subarea on the org. unit level. This will be inherited by positions (even if you cannot see it at position level in PPOME) and thus defaulted for the employee. At position level you should handle only the exceptions, which will be in turn also defaulted for the employee holding the position. In this way, data maintenance is minimized. If you delete (or do not use from now on) information about infotype 1008 on org. unit level, your HR department will have to maintain this every time a position is created, and even in cases in which a position is shifted from one org. unit to another one.
    In my opinion, you should address this with your HR department and explain the concept and the consequences of maintaining all at position level. It would only be advisable to do it if the org. unit structure is very cross-personnel areas and subareas. If it is a matter of handling exceptions, again, I would recommend to continue recording this data at org. unit level. All in all, if the data is not recorded on the position and you need to see which is its personnel area, you just need to double-click on the org. unit above.
    Just wanted to let you know my opinion, of course it's your decision. By the way, I'm of course not aware of other possible implications like home-developed reporting and so on.
    Regards,
    Rodrigo

Maybe you are looking for