Reports to check what org units or positions linked

Hi,
I want to run a report for 2000 positions and check
which positions are linked with which other positions
and which positions are linked with what other

hi,
sap provide the two types of relationship for a objects ,
A -
BOTTOM  TOP
B----
TOP  DOWN
for position to position  ( A position reported to another position  A|002 where 'A' is bottom up relation and 002 is infotype ( reports line to ) 
position is the line manager of another position  B| 002 where the 'B' is top down relation and 002 is infotype .
position manages an org unit  A |012
an org unit is managed by position B|012
report is HRP1001,
RupaPrasad

Similar Messages

  • For an Org Unit, how do we get all Reporting Org units (Also employees reporting to the sub org unit) & Employees ?

    Hi Experts,
    I have a very common requirement in SAP HCM ABAP development.
    For an Org Unit, how do we get all Reporting Org units(Also employees reporting to the sub org unit) & Employees ?
    I have tried using RH_STRUC_GET_MULTIPLE_ROOTS and RHPH_STRUCTURE_READ, but the evaluation path is insufficient to get all objects under it. I tried with both O-S-P and O-O-S-P evaluation paths and as per some constraints, I can’t create a customized evaluation path for a reason.
    I am using PNPCE database for user selection screen and user would be advising the Org unit. I even referred the standard transaction ‘S_AHR_61016495’ which is using PCH logical database.
    I would really appreciate if anyone could provide a solution for this. (Rewards guranteed )
    Kindly help.
    Thank you.
    Regards,
    Mahesh Konade

    Hi Alexandre,
    Although I could not respond in time, thank you so much for your prompt reply.
    I had used the same RHPH_STRUCTURE_READ and passed the appropriate values to it, but it did not populate the required results. I cross checked the results manually, may be some relations issue. But later I tried using RH_STRUC_GET_MULTIPLE_ROOTS and it worked fine.
    Meanwhile I had done a workaround with PCH and RH_STRUC_GET and it served the purpose of getting all the Org units, it’s reporting sub-org-units, positions and persons (The deepest structure from the root org unit advised on selection screen).
    The solution I used is, I captured the org-units advised on selection screen by user using PCH logical database and then by looping on sub-org units reporting to the main org-unit I populated related positions and persons holding them and assigned it to the PNPCE logical database.
    Thank you so much for the help.
    Regards,
    Mahesh Konade

  • Org Unit Under Position

    Hi,
    Can we create an org unit under a position (other than chief position)
    Eg: GM will be the top of the Company, under GM different departments, is it possible in OM..?
    I would appreciate your help. Thanks!
    SD.

    Hi SD,
    Functional units are reprseneted in OM.Please check allowed relationship per object type.tcode OOIT..Org units and Position relationship can be assimilated using this.
    please check T778T,T777E(Table  T777E contains all the relationships permitted between organizational objects)
    Table  T7791 contains information about which SAP organizational object types should be linked with positions, which with jobs and which with organizational units.
    objects and relationships are building blocks of OM(1000 and 1001)
    please refer to the below link for more details
    https://cw.sdn.sap.com/cw/docs/DOC-39190
    Hope this helps.
    No Worries
    KG

  • 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

  • Creating countries - Move Org unit its positions to another country code

    Hi Gurus,
    The client used a single production server for all the countries under its one country grouping(10) for different countries (US, Malaysia, Sinagapore, China, India, UK).
    We have only one country code for all the OM.
    One Organizational unit needs to move to another country(39), of which all positions, jobs, and the employees assigned to it also needs to move with the Org unit to new country. We are going to change the PA PSAs as well to new country groupings
    Is it possible, and if possible how to do it?
    thanks in advance....

    Hi Kumar,
    As already stated by you change the PA and PSA's accordingly as per the new country groupings as PA's should be assigned to company code within the same country grouping.
    In my knowledge I dont think you need to change anything with the Org Unit as OM objects don't refer to any country groupings as such. If you are using the account assignment infotype ( IT 1008) then you will have to change the Company code to your new company code as your new company code will have different country grouping ( 39).
    Your FI CO objects like Cost centers can be changed to new cost centers as per your requirement from the date you move your Org Units or Positions to new country groupings.
    We can also wait for other expert comments.
    cheers
    Ajay

  • Can there be Org units under positions?

    Hi guys,
    Please let me know how to create Org units under positions
    Thanks
    Deepali

    Deepali,
    Standard SAP configuration for PPOME transaction does not allow you to create or units under positions.
    If you want to do so, you need to carry out the following configuration settings:
    1. Goto table T777E via SM30, select 003 relationship, double click allowed relationships from the menu on the left hand side.
    2. In the table add the following entry:
    S B 003 Incoporates O
    3. Goto table T778A via SM30, select evaluation path SBESX, double click evaluation path(individual maintenance) from the menu on the left hand side.
    4. In the table add the following entry:
    98 S B003 Incorporates * O
    1. and 2. steps are carried out to allow the relationship "Incorporates" between position - org unit.
    3. and 4. steps are carried out to allow the maintenance of this relationship via PPOME transaction.
    Please before doing these configurations make sure that assigning an org unit under a position is logical for your org structure and "Head of org unit" does not solve your requirement.
    Good luck,
    Dilek

  • Missing Org unit from position ID

    Hi Gurus,
    Could you please provide additional information which I have missed out that would help resolve the issue.
    Problem Statement:
    Position ID XXX originally belongs to O XXXXXXXX [Sample Org 1].  When HR Recruitment administrator performed action to move structure reporting to another O YYYYYYYY [Sample Org 2], the record went missing as the action done was CHANGE instead of COPY.  This had caused two ex-staff showed no Cost Center & Org Unit. Now, user is trying to reinstate S XXX to O XXXXXXXX [Sample Org 1] but is prompted with an error message - Company code cannot be determined for cost center 52222.
    Action Taken:
    1. Checked S 5111111 and found that it is currently under O YYYYYYYY and currently occupied by P 123456 (validity period is from 01.11.2010 to 30.04.2011)
    2. Checked  account assignment of S 5111111 to confirm the company where it is assigned to. It reflects that position inherited attributes O YYYYYYYY [Sample Org 2] to which the position is currently under
    3. Checked account assignment of O YYYYYYYY it only contains the controlling area which is TTTT. I then checked IT0001 of the current employee who is holding the position and company code reflecting is CCC.
    4. Checked account assignment of O XXXXXXXX where they want to reinstate the position and it only contains the controlling area which is TTTT and master cost center is 52222. I checked one employee under the said Org to verify to which company it is currently under and found that it is the same, CAT. At this point, I do not see any issues as to why it is not allowing them to create A003 rel to O XXXXXXXX .
    Note: I was not able to replicate the error since it is working fine in dev given the same scenario.
    Findings:
    The only thing that I can see is on the validity date. If they are to reinstate the position to where it has been originally assigned which is under O XXXXXXXX [Sample Org 1], it should not overlap with current record since there is somebody occupying the post. If it does overlap then it will automatically delete the existing record.
    In addition, I have managed to check transaction S_AHR_61016528 (B011 eval path) and found validity period of cost center to O XXXXXXXX is 01.04.2002. If user is trying to establish A003 rel for S 5111111 and validity period used is 01.01.1997. Would that matter why user is getting the said error. I have tested and was able to create rel successfully.
    Would appreciate if you guys could share how else the position can be reinstated to the old org unit.
    Thank you.

    Hi Gurus,
    Could you please provide additional information which I have missed out that would help resolve the issue.
    Problem Statement:
    Position ID XXX originally belongs to O XXXXXXXX [Sample Org 1].  When HR Recruitment administrator performed action to move structure reporting to another O YYYYYYYY [Sample Org 2], the record went missing as the action done was CHANGE instead of COPY.  This had caused two ex-staff showed no Cost Center & Org Unit. Now, user is trying to reinstate S XXX to O XXXXXXXX [Sample Org 1] but is prompted with an error message - Company code cannot be determined for cost center 52222.
    Action Taken:
    1. Checked S 5111111 and found that it is currently under O YYYYYYYY and currently occupied by P 123456 (validity period is from 01.11.2010 to 30.04.2011)
    2. Checked  account assignment of S 5111111 to confirm the company where it is assigned to. It reflects that position inherited attributes O YYYYYYYY [Sample Org 2] to which the position is currently under
    3. Checked account assignment of O YYYYYYYY it only contains the controlling area which is TTTT. I then checked IT0001 of the current employee who is holding the position and company code reflecting is CCC.
    4. Checked account assignment of O XXXXXXXX where they want to reinstate the position and it only contains the controlling area which is TTTT and master cost center is 52222. I checked one employee under the said Org to verify to which company it is currently under and found that it is the same, CAT. At this point, I do not see any issues as to why it is not allowing them to create A003 rel to O XXXXXXXX .
    Note: I was not able to replicate the error since it is working fine in dev given the same scenario.
    Findings:
    The only thing that I can see is on the validity date. If they are to reinstate the position to where it has been originally assigned which is under O XXXXXXXX [Sample Org 1], it should not overlap with current record since there is somebody occupying the post. If it does overlap then it will automatically delete the existing record.
    In addition, I have managed to check transaction S_AHR_61016528 (B011 eval path) and found validity period of cost center to O XXXXXXXX is 01.04.2002. If user is trying to establish A003 rel for S 5111111 and validity period used is 01.01.1997. Would that matter why user is getting the said error. I have tested and was able to create rel successfully.
    Would appreciate if you guys could share how else the position can be reinstated to the old org unit.
    Thank you.

  • What are the infotypes should i maintain for  org units and positions in om. and how can i see positions under org units.

    can anyone help me

    Hi,
    It is depends on your requirement. compulsory info types are 1000 1001 1002 1003 1008 1018....
    go to pp02 and click on F4 option in IT field and Subtype field.
    Example:
    1000
    Object
    1001
    Relationships
    1002
    Description
    1003
    Department/Staff
    1004
    Character
    1005
    Planned Compensation
    1006
    Restrictions
    1007
    Vacancy
    1008
    Acct. Assignment Features
    1009
    Health Examinations
    1010
    Authorities/Resources
    1011
    Work Schedule
    1013
    Employee Group/Subgroup
    1014
    Obsolete
    1015
    Cost Planning
    1016
    Standard Profiles
    1017
    PD Profiles
    1018
    Cost Distribution

  • Create report to check what software were installed from which BDP

    Hi,
    I need assistance to create a report that shows which software were installed from which BDP. How would one go about doing this?
    Thank you in advance

    The best you can probably do is the opposite of your request. Specifically, using the IIS logs on the DP at the central location (assuming that's you topology), you can determine which systems are using the central DP which essentially also tells you which
    ones are not using it (this assumes you are actually using a BITS enabled DP at the central location also). With BDPs in the mix, I don't think that there's any tracking whatsoever on the BDP itself because that essentially normal SMB traffic.
    A better option is to get the network team involved although that probably won't be definitive either because the clients still need to traverse the WAN to communicate with the MP and WSUS instance.
    Jason | http://blog.configmgrftw.com

  • 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.

  • Org unit is not getting defaulted for the selected position in infotype0001

    Org unit is not getting defaulted for the selected position in infotype 0001 during the hiring action.
    In OM Org. units and positions have been created.
    The Org. unit to Position relationship is also created.
    But inspite of this, In infotype 0001, the after selecting a position, the Org unit is still getting defaulted to "00000000" instead of the Org. unit Id to which the position belongs. (Please note: At the time of selecting the position, I do structure search and the position is shown under the correct Or. unit)
    Have I missed any step?

    Have u run the RHINTE programmes properly ?
    are u able to save the record?
    As some times it may be display probolem, if u r able to save the record then check the relationship in pp10/po13.
    and U have not answered what Mr. Valeri is asking about your Implementation/support because these type we come accress if data is not uploaded properly.
    Regards
    vinmax

  • Extending the End Date of Relationship Org. Unit and Position

    Hi All,
    Please help me below.
    Problem: The end date for the relationship between org. unit and position should be set back to 31.12.9999. It was accidentally been set to 31.03.9999 and results to two records in infotype 0001, which the wrong record should be deleted.
    This can only be deleted by changing the relationship end date in PO13 but unfortunately, the user doesn't have any access to this transaction.
    Request: Can you explain to me on how the end date can be change in transaction PPOME or PPOM_OLD as these are the only transactions the user has an access. I'd already explored these transactions but I can't find on how it should be deleted here.
    Thanks!

    Hi Raju,
    Thanks for this information. This was a very helpful answer. But I only need to extend the end date of a particular infotype 0001 record of a particular employee. I think the report will extend all of the records of all the employees in the system. I can't find any parameter in the report wherein I can set the employee number I wish to extend the end date.
    Thanks!

  • How to extract an employee reporting hierarchy per org unit in spreadsheet

    Hi Guys,
    Can any one advise if there's a standard report I can use to see employee's  reporting hierachy in spreadsheetformat ?
    Report must have per org unit positions with their  related positions :'reports to' A002  relationship between two positions in a specific org unit and person's name/employee number occuping the positions.
    I tried creating joint table but battling to undestand how I can have the two related positions info in the infoset.
    Current standard report give me only positions with reports to relationship but haven't found report showing me positions with reports to relationship and their related position.

    Have you tried using logical database PCH? That gives flexibility to create this kind of report. Create an infoset in SQ02 and an Adhoc Query in SQ01 based on PCH Logical Database. You will need the relationship subtype 'A002' and related object type 'P' on selection screen.
    Edited by: Shafiq Rehman on Feb 6, 2008 4:23 PM

  • MSS - Creating new Position and Org unit in MSS

    Dear Expert,
    Question 1: I want to know that is it possible to create a new Position or Org Unit in MSS. I am aware that manager can create a requisitioin for a position. But I am not aware that how HR manager will create the Org Unit or Position thourgh MSS.
    - will the HR manager have a new HR administrator Role to do this activity, if yes, which service / iview is used.
    Question 2: We are using Management of Global employees (MGE). Now if any employee expariate to a foreign country how does ESS/MSS will pick the new country assignment. Is there any ess/mss switch for this? or any other configuration
    Question 3: I would like to know what are the main differences of EHP4 and EHP5.
    thanks
    honey

    Hello honey - answer to the 1st question.
    MSS- click Organisation - Search Organisational Process - enter the Process HR_PD_CREATE_POSITION and click start , this could be one solution how the managers may be able to create new position through MSS.
    Regards,
    Regi

  • 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.

Maybe you are looking for