Ad Blocker Detected
Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker.
SAP HR Organisation Management
Transaction code OOPS takes you to all the org mgt related settings in table T77S0.
When maintaining wage elements to position, you will find that in maintaining the infotype “cost planning” to a position, you are not able to assign more than 7 wage elements. If you are wanting to store more than 7 wage elements you are restrained by the time constraint on the infotype.
The time constraint of infotype 1015 can be changed from 2 to 3 in table T777Z. This allows several infotyperecords to be created at the same time.
- When creating number ranges in PD, you need to ensure the following:
- You can create a unique number range for any PD object. The SAP standard entry will have the notation $$$$ IN EX
- Copy this one and name it 01S to produce a specific number range for positions in the active plan version in this client.
- Change the actual details using the different icons. Click on the icon “number range maintenance” – it will look as follows:
- EX 0000001 500000 EX
- IN 1000000 1500000 0000001 IN(ticked)
- The trick is to enter the plan version if you have the setting NUMRG COMP as a blank in the step before – table T77S0.
- If you have an X in the setting then you need to use the $$ in place of the plan version.
- It is possible that you will at some stage find yourself in the following situation. In a client copy, you copy from Production to QA or UAT client but don’t include infotype data (due to sensitivity). This will leave you with an organisation structure with positions which are related to P objects (people) which don’t actually exist.
- Program ‘RE_RHRHAZ00 – Display DB records’ shows all these A008 relationships, however program ‘RE_RHRHDC00 – Delete with list’ does not, neither does ‘RE_RHRHDL00 – Delete DB records’. The big question is: How can you delete the A008 relationships to objects that don’t exist?
- One solution is to recreate dummy objects (people in this case with the minimum of detail), delete the relationships and then go and delete the people. You could use a CATT procedure to automate the process.
- Another solution is to delete the records from table HRP1001 directly using a small ABAP program. Be very careful when choosing your selection criteria. Instead of writing a piece of ABAP code, you could create a CATT procedure to do the trick.
What options are available for an automatic upload of the organisation structure?
- You can upload Org structure using PD Actions (PP03). You might want to create separate files for Org units, Positions, relationship between Org, Position. etc
- There is a std program for OM data conversion. The transaction code is OOMV and OODT
- This is carried out using the program RHMOVE30.
- NB: You must run the program RHINTE10 after every transport using RHMOVE30. This updates the tables that are common to both PA and PD.
- It is probably best to run it before you transport the objects using RHMOVE30.
- If you would like to check the integration objects, you can do so at any stage by running the report RHINTE20. This gives you the PD objects not in PA etc.
- To run RHMOVE30, you can use the menu path: System > Services > Reports
- The program, like most PD objects, hinges on evaluation paths. Choose the object that you would like to transport. The evaluation path gives you an opportunity to take other objects with the chosen object – the relationships go with it as well.
Transporting: Org Units, Positions and the Cost Center assignment.
- Choose O(org unit) as you chosen object. Use o-s-k (from-via-to) as the evaluation path. From the list of available options, choose “kostos” as the path.
- Click on the execute button. First test it (make sure that the test check-box is ticked)
- The result will only show org units and positions. The relationships to the cost centers are there but the actual cost centers are not in the PD domain, hence the reason why you can’t see them there.
- Run the report again without the “test” on. Make sure that the check-box “objects to be transported” is on.
- The resultant output shows you all the objects again (org units and positions) but this time they have a transport icon next to them, which is ticked.
- Click on the transport icon to transport the objects.
- To check and see what objects and relationships are going to be transported. (once they have been released and are ready to be transported) Using transaction code SE10, click on the transport and use the menu path: Request/task > Object list > Display object list: Double-click on the line and you will see what is going to be transported.
Use the evaluation path QUALCATA which is the complete qualifications catalogue.
Use the evaluation path A* and B* to cover all possible relationships.
Use the following evaluation paths:
All relationships around positions including reporting structures, infotype records etc
Use: A* and B* – put them in the same transport
All Relationships around jobs including the relationships to qualifications and tasks etc
Use: A* and B* – put them in the same transport
Using report RHINTE00, you can create objects in Organizational Management from the Personnel Administration infotype 0001 (“Organizational assignment”). In doing this, the following relationships are created:
Cost center and organizational unit or position
Position and organizational unit, job or person
Using report RHINTE10, you can transfer the objects you created in Organizational Management to tables in Personnel Administration.
Using report RHINTE30, you can update the “Organizational assignment” infotype (0001) for the personnel number you have selected, with the data you created in Organizational Management (by executing report RHINTE10).
Using report RHINTE20, you can check whether the objects relevant for integration are set up both in Personnel Administration as well as in Organizational Management.