HR Implementation - Clarification on Org. Unit & Personnel Subarea

Hello Experts,
We are implemenating OM in which Company is distribute into Plants(PA),which is further Diveded into Department,which is further divided into Sections,which is furter divided into Gang no.
Company -> Plants -> Department ->Sections ->Gang No.
Gang no is basically used for Payroll & Time Management for identifying EMployees into Groups.
Can anyone help how we can MAP in SAP HR.
THanks,
Viru.

Hi,
Your requirement can be addressed with different structures in SAP: Enterprise structure, Organizational structure and Pay structure:
Enterprise structure:
Company = SAP Company code
Plants = SAP Personnel Area
Organizational structure:
Department = SAP Organizational unit
Sections = SAP Organizational unit under main unit (Department)
Pay structure:
Gang No. = SAP Payroll area
Cheers

Similar Messages

OM Implementation: Re-Number Org Unit Number Ranges.

Hi Experts,
My client wants to implement OM module in SAP HR.
The requirement is : They need defined number ranges for org Units in OM. However the existing number ranges for Org Units in PA module do not fit in the range. How do I satisfy this requirement without any impact ?
FYI: Personnel Administration(PA), US Payroll , Benefits and FI-CO is already implemented.
Regards,
Somdeb.

Sounds like the problem is not maintaining different number ranges per object type (which is standard to do), but to not have these conflict with existing number range in T527 tables.
I am not sure how this transfer from just using PA to using integration will work. You will have to check the different RHINTE-reports to make out a strategy how to do this transfer. When you start using OM, where will correct data regarding org.units be? You will neeed to run some integration to establish a new startingpoint after integration is switched on. If this creates conflict between existing numberranges in PA and wanted ranges in OM, you may have to do some coding in PA0001 first.
Kirsten

Creation org unit and subarea

create a org unit and a sub area

Please describe your issue in detail.
Create org-unit: PPOC_OLD
Create sub-area: IMG--> Enterprise structure --> Definition --> Human Resourece Management --> Create Personnel Area/Subarea.

Organization Unit & Personnel Subarea

Hi Experts,
If we classified PSA according to the departments in organization & we created OM, in that Org Unit is considered as per departments, then why org unit (No. wise) is considered lesser comparative to PSA.
Regards,
Saumya.

There are broadly four basic structures in SAP HCM:
1) The Enterprise structure 2) The Organizational structure 3 ) Personnel structure 4) Payl structure.
The Enterprise structure has a larger purview than the other three including the Org structure of which the Org unit is a part . Personnel area is a part of Enterprise structure. Since Enterprise structure has higher level in structural heirachy than Org structure, the Org unit shall always lie low than Personnel Area.
As stated by Kapil, PSA being a part of Enterprise structure needs to be designed considering dependencies like Payroll, Time Management, whereas Org unit do not have these dependencies.

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

Adding New Org Units to Existing Organization Structure

Hi,
There is a change in the Org Structure, i.e we are adding new Org Units(Personnel Sub areas) to the existing Structure and creating postions to the newly created Org Units using PP01. Now my question is what are all things need to be configured with respect to Payroll, for the newly created PSA.
Rgds
Ram

Hi Ramakrishna,
Please be more clearer. PSAs are not org units. PSA belong to enterprise structure, whereas Org Unit belong to Org Structure. When you create new positions under the Org Units tht have been assigned to a PSA, PA, Company Code, Cost Center and Controlling area combination, you would have to set the following.
Group your PSA for,
Primary Wage Types
Premium
Work Schedule
Time Recording
Absence Attendence Type.
Assign Tax Area to a PSA(If it is US Payroll).
Any more suggestions from experts?
K

Evaluation path to get personnel number all the org unit and subordinates

Dear all,
I have OM issue to ask.This is the scenario:
Staff A belong to org 1. Under Org 1, I have org unit 1-A, 1-B and org unit 1-C.
Issue 1 :
I want to run report(RHSTRU00) to to generate all the staff number in org 1 (Include 1-A, 1-B, and 1-C).
Issue 2 :
I want to run report for 1-A, only staff belongs in org 1-A appear.The others not appear.
I was understanding I have to play around with evaluation path. Until now I can't find the suitable evaluation_path. I need your help.tq

Hi,
Not sure why you want to reinvent the wheel. The standard report RHXSTRU02 will give you people by Org Unit. Just enter the Org Unit ID number and you will get the employees as output.
If you still want to use RHSTRU00, you can use O-P or O-S-P to get the employees and the positions.
Paul

OM/PA Bug - Personnel have different Org Unit in PA.

An employee was hired into an Org Unit A. However, when I check into PA20, the employee's org unit is showing as Org Unit B.
I checked PPOME, and the Employee (Person) and his position and it is shown under Org Unit A.(the correct Org Unit.)
I check PP01 for the employee's position and it belongs to Org Unit A.
And yet when I check into PA20, the employee has Org Unit B.
How do I continue my investigation for this?
Points to those who can help.
Thanks.
Olekan

Hello Anantha and Manu,
Thanks for the prompt reply.
The employee is visible in the Staffing mode. He is placed in only one position and is 100 % for this position.
The relationship validity for the Position to the Org Unit A is valid until 12.31.9999.
Currently we have 6 of this employee that belongs to Org Unit A but is showing in Org Unit B in PA20.
Thier positions are adjacent in the staffing screen. So I think there was a mistake during creation of this positions or assignment of the pos. to employees. Or it could be a product error.
Do you think i should raise an OSS note for this?
Thanks
Regards,
Olekan
Edited by: Clueless Noobie on Dec 18, 2007 5:19 AM

Personnel Cost Planning: creating cost item for Org unit

Hi experts,
I am trying to attach a cost item to an org unit by maintaing feature hcp02 but the somehow the cost item applies itself to both org unit and position. Could anyone please let me know the how this can be done?
Thanks

It is extremely difficult to answer your question without knowing all the details of your scenario.
I can briefly explain the scenario I used:
1. I have maintained IT1005 on job level to further distribute this information along the organization structure.
2. First of all i had to run data collection on job level using method "Infotype planned compensation: 1005" and cost item that was a base for other items, e.g. basic salary. System creates records in infotype 5010 "Planning of Pers. Costs" for evaluated jobs.
3. Then I collected cost items for positions using method "Data from related cost planning objects", calculation type A, basis that I previously set up, evaluation path O_O_S_C (I started from head org.unit) and object type source C. I did it for positions to have possibility to adjust cost items on position level using transaction PHCPDCUI - Edit Data, e.g. you can ask managers to review your defaults on position level before staring consolidation on org.unit level.
4. Then you start data collection on org.unit level using cost items on position level. Process similar to step 3 but with different evaluation path and source object.
5. When it's done you run cost planning (PHCPADMN - Manage) using special plan for planning based on OM data.
There are plenty of other scenarios, so can't really give you exact answer on your question, as I don't which scenario you use.

Personnel subarea inheritance issue

Hi,
not sure if this is an abap or functional question, so I started here.
I have a report using Logical Database PNPCE to find some values from a couple of info types. When I select a unit (from the 'OrgStructure' button at the top of the screen), say 111, and all its sub-units with no selections in the selection screen, I get one person displayed. This is correct and this person is in a sub-unit 3 levels down (unit 333).
I then added a selection to only display people in units with Personnel SubArea 'OTEC'. Now I get no results output. When I look in PPOME, I can see that unit 333 has Personnel SubArea 'OTEC' but it is inherited from '111'.
In PP01, unit 111 has an Account Assignment entry (Info Type 1008) but 333 does not.
Does anyone know how to report on this?
Is there a flag somewhere that tells the LDB to check for inherited units?
If not, any ideas if there is a function out there to find the superior unit for these sub-units?
Thanks.

Hi,
I couldn't find a simple solution so have used the FM RH_CHECK_ACC_INPUT to get the parent org unit details.
Thanks.

HR Report to display headcount up to 10 levels of Org Units

Hi Experts,
Can you please give steps for the following requirement.Is there any standards available.Please explain the procedure to create report.
Points will be awarded fot the suitable solutions.
The report shouldl query SAP for the number of employees based on the personnel area and sub area. The main reporting is based on the sub area. If the employee is in the India Pers Area the total number of employees from each sub area will have to be deducted from the headcount for that sub area and added to the India area for headcount totaling.   For each of the areas/subareas we need to gather the total number of Active Employees, Temp Employees and Contractors. This information can be gathered from the employee group.
i/p filed                         available table
Key Date
Employment Status     PA0000
Personnel Area                PA0001
Personnel Sub Area     PA0001
Employee Group               PA0001
Employee Subgroup     PA0001
C stands for column C2 c3 c4 will be filled by users after running report.
         c1       c2     c3 c4             c5     c6
SEIM     70                    9     4          Pers Sub Area - FIN
NGUYEN     25                    0     1          Pers Sub Area - MKT
LUHR     120                    3     4          Pers Sub Area - SLS
DREW     532                    78     2          Pers Sub Area u2013 OPS
CHOMA     35                    2     6          Pers Sub Area u2013 ODLP
LIPPS     3                    0     0          Pers Sub Area - GAA
INDIA     79                    0     0          Pers Area - IND
TOTAL     864                    92     17     0
Thanks and Regards,
Raj

If you want to read the org unit hierarchy from the org structure, tables HRP1001 and HRP1000 should
have all the information you need. HRP1001 hold the relationships between the org structure objects
and HRP1000 holds information about each object.
If you don't want to do the selects yourself, there is a very useful function module called
RH_STRUC_GET which does the same sort of thing ie reads the relationships between org structure objects
using whatever evaluation path you pass in in parameter ACT_WEGID..

PSA and Org unit

Dear All,
We are in deciding phase of Personnel Subarea and org unit, I need to understand the difference between Org unit and PSA while designing.
Regards,
Kumar

hai
there is not much to do with your org structure
but when creating the personnel areas ans personnel structure we have to take care so that when in later parts the data handling should be easy.
it also depends upon the legal structure of the geographies.
like if u take karnataka and tamilnadu.
may be through out the structure and bussiness process of the company is same.
when considering the taxation of the government it is different ex proffessionsl tax.
if u keep these two personnel sub areas seperately(kar,tam) under PA india
the configueration will be easy.
and also the data retrievel will be easy
regards
nalla

SuccessionPlanning - Add 'Personnel Subarea' Selection in the Employee Grid

Hi experts,
I am currently using Nakisa SuccessionPlanning 3.0 SP1 0701027700.
My question is, for the Potential & Performance grid, is it possible to add a selection for 'Personnel Subarea'?
My client wants to view employees in several org units at one go in the 9-box grid. Current workaround is to insert multiple org units IDs in the selection but this can be daunting if there are a lot of org units to be covered.
Please help to give some insight on this.
Thanks,

Hi Aimey00,
Yes this is possible, but it can only be done through customization. The steps are below. Please remember to copy files that you need to edit to the .delta folder if they do not exist there. Should you not be able to follow the steps then I recommend using an experienced consultant because these steps do require some intermediate knowledge of the application configuration files.
1. Edit the NakisaRFC function SAPEmployeeNineBoxSearch.xml to add Personnel Subarea. Personnel Area is already in the function so by using that as an example you can find how to add this field.
2. Add the field to the following data element configurations (..\<build>\AppResources\dataelementconfiguration\): SAPEmployeeSearch_With_NineBoxTemp.xml and SAPEmployeeSearch_With_NineBox.xml
3. Add the field to the search control configurations (..\<build>\AppResources\searchcontrolconfiguration\): EmployeeSearchControl3.xml and EmployeeFiltersControl3.xml
Good luck!
Luke

How to extract Org.unit Hierarches in BI 7.0

Hi experts,
I am developing HCM BI reports, right now I am into Org management and Personnel Administration,
I am new to HCM.
my doubts are clarified in existing discussions in the forum.
queries:
1) how to create hierarchies of Org. units in BI 7.0 give me steps.
2) I am not able to load data into standard info cubes(0PA_C01 and 0PAOS_C01).
Any procedure I have to fallow for these cubes to load data.
thanks in advance
Vijay

1) how to create hierarchies of Org. units in BI 7.0 give me steps.
   U just have to load hierarchies created in ECC... The standard datasource that loads 0ORGUNIT
   hierarchy is 0ORGUNIT_HR01_HIER... Assign this datasource to 0ORGUNIT (transfer rules) and
   create infopackage (in 'Hierarchy selection' tab, if u click 'available Hierarchies from OLTP' button, it
   will give u all available hierarchies (technical name ORGEH) for 0ORGUNIT)
   To check existing orgunits in ECC
      Use tcode PPOSE
      Expand 'Organizational Unit' Node
      Click on 'Structure Search'
2) I am not able to load data into standard info cubes(0PA_C01 and 0PAOS_C01).
      These infocubes has many fields like Gender,Nationality,Language,Age in Years,Country
      key,County Code,Region (State, Province, County),Postal Code etc..
      All these fields are populated through routines (reads master data of 0EMPLOYEE) and a start
      routine.
      So, u have to be careful when u install standard content, make sure u install routines for above
      objects mapping in transfer rules. Also make sure the "Start Routine" installed properly
      In ECC, also check data exists in infotypes PA0000 & PA0302 (for 0PA_C01) and HRP1000,
      HRP1001, HRP1007 & PA0007 (0PAOS_C01)

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.

HR Implementation - Clarification on Org. Unit & Personnel Subarea

Similar Messages

Maybe you are looking for