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

Question

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!

Answer 1

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