Topic 65: Real Time Questions & Answers: Organizational Management

[welcomewiki]

I had transported my org structure from my Golden Masters to the Production Server.After this, I created positions in OM using PO13. Then, I assigned positions to the employees by running an LSMW using a customised action "Organizational Re-assignment" which modifies IT0001 and inserts positions already created in OM.

But, now when I use transaction PPOME, the position holders are not visible in the org structure.

Could any of you please help me out so that the position holders in PA are reflected in OM (TCODE:PPOME) also.

ANS:1 1.Just check if you have created relationship...between Objects.
2.PLOGI-ORGA switch in T77S0
3.Run RHINTE00, RHINTE10, RHINTE30 Reports...

ANS:2 Kindly please recheck the Integrations settings includes Tables T777D,T777ID.,
also the Feature is activated, and along with the other steps like org reassignment, integration with PA, and the rest.

ANS:3 you run, the report integration between PA and OM... i think its RHINTE00. During batch uploading, creation of relationship will not take place.

[welcomewiki]

What are the different ways to acheive OM to PA integration.? Where can I get the docs/ help for the same?

ANS:1 T70SO, there u find the plogi and activate it
and another way is
IMG – PM – PD - INTEGRATION
SET UP IMTEGRATION WITH PA&RECRUITMENT

ANS:2 GO to table V_T77S0SC and activate Switch is to set PLOGI ORGA --X

For your information:-
Set up Integration with Personnel Administration In this step, you activate integration between Organizational Management and HR Master Data in Personnel Administration. This guarantees data consistency between the two components.
Example
A person is to be transferred from the position "Controlling administrator" to the position "Manager of controlling". As soon as this transfer has taken place in Organizational Management, the corresponding changes are made in the "Organizational assignment" infotype (0001) in Personnel Administration.
A person can also be transferred between positions in Personnel Administration using the personnel action "Organizational Change". The relevant changes will then be made in Organizational Management.

Requirements
Using the entry "PLOGI PLOGI", you specify the active plan version that is to be the integrated plan version for Organizational Management, Personnel Development, Personnel Cost Planning, Shift Planning and Training and
Event Management.

The entry has the function of a main switch:
If this entry has the value ' ' (switch "off"), integration is switched off. If a plan version is determined using the switch, integration in this plan version is active for all persons who correspond to the feature "PLOGI" (see below). The entry "PLOGI ORGA" must contain an 'X'. This activates integration between Organizational Management and Personnel Administration via infotype 0001 ("Organizational Assignment").

Activating integration has the following effects:
Changes to Organizational Management objects (organizational unit, job, position, cost center) relevant to integration are transferred to Personnel Administration
Changes to the organizational assignment of employees (infotype 0001) are transferred from Personnel Administration to Organizational Management.

Activating integration:
The sequence in which you carry out preparations for activating integration depends on which one of the following is true of your enterprise:

You have Personnel Administration set up and want to install Organizational Management for the first time.
You have Organizational Management set up and want to install Personnel Administration for the first time.
You want to install both applications for the first time.
In all three cases, you must ensure that Personnel Administration (infotype 0001) and Organizational Management (organizational assignment of employees) contain consistent data.

If the master data regarding the organizational assignment of the person is available in infotype 0001 (organizational unit, job, position and cost center), you must start report RHINTE00.
If Organizational Management data is available, start report RHINTE10.
This will create the relevant information in the Personnel Administration tables.


If the organizational assignment (position and organizational unit of a person) is also to be transferred from Organizational Management into infotype 0001 in Personnel Administration, you also have to start report RHINTE30.
If you are installing both applications and integration is active, you can only maintain the organizational assignment (infotype 0001) of a person in Personnel Administration using an action. Alternatively, you can assign persons to positions in Organizational Management.

It is recommend that you always make organizational changes using an action in Personnel Administration as by doing this, you will also be able to adjust information on working time and salary for this person. You can build up one of the databases for the two components first without active integration and then proceed as described above. In all three cases, report RHINTE20 can correct any inconsistencies that may occur.

ANS:3 follow the steps in IMG, in OM, Integration Node

Set up Integration with Personnel Administration
Transfer Data from Personnel Administration
Prepare Integration with Personnel Administration
Transfer Data to Personnel Administration
Check Integration Consistency

[welcomewiki]

How to maintain infotypes directly in ORG management. These infotypes when i try to maintain in pa30, they say it is not possible. Suppose what if i want to key in some data manually in OM?

ANS:1 transaction -PP02 and PP03.

ANS:2 u cannot access OM infotypes in PA30. u have use tcodes for position , job, org unit etc.

ANS:3 Info types 0000 to 0999 for personnel master data, and certain applicant data.
Info types 1000 to 1999 for Human resources planning data.
Info types 2000 to 2999 for time management data.
Info types 4000 to 4999 for applicant –only data.
Info types 9000 to 9999 are reserves for customers.

U cannot access OM ifnotype in PA or vice versa..

ANS:3 You can Maintain OM infotypes (Object wise) with following Tcodes

PP01 - General (menu-guided)
PP02 - General (open)
PFCT - Task Catalog
PO01 - Work center
PO13 - Position
PO03 - Job
PO10 - Organizational Unit

When a manager has 2 positions, it doesn't seems that the manager is caught for both org units. he has 2 positions, 50% each.

eg: when we run variant INDIA in HP1-001. the manager for org unit IT_PLM is blank, but is in reality Chrisanth Jebakumar with pernr 2000031.
when run the report with variant IO INDIA, which is org unit IT_IO_0000IN, he is in the output correctly.
how to output the two positions correctly for all org units they are managing.

ANS; There is one position that is considered primary position. It will also appear on the IT 0001 for the person. The rest are considered secondary and exist as relationship on the OM side.

If the person is a chief of an org unit, then it might be possible to assign the person to one position but make him/her a chief of multiple organizational units.

[welcomewiki]

How to maintain the number ranges for organizational units?

ANS:1 Maintain in SPRO or use OONR.

ANS:2 Enter TC: OONR
Create a SubGroup as 01O O for Orgunit OR my be 01S for Position
after creating subgroup 01O for Orgunits Click on the ****on "Number Range Maintenance"
Click on the ****on with a Change Status
Define your number ranges as Internal or External

[welcomewiki]

Can some one please explain what are Personal Actions in Organizational Management, how are they useful, how are they configured in SAP.


ANS:1 These just like actions in personnel administration

FROM SPRO go to
Personnel Management > Organization management >Basic setting >maintain Personnel Actions
Here you can to create new objects like position, work centre etc

ANS:2 In this step, you make the system settings necessary for setting up a personnel action.

A personnel action is a collection of several logically connected infotypes in the system which, in an exact sequence, is used for processing and is used for a particular system activity (see "Create Organizational Unit", for example).

Personnel actions are identified by a key.
You assign the following to each step of a personnel action:
a plan version
an object type
an infotype or subtype
a status
default values for screen entry

You also control, which Function codes are used by an infotype (within a personnel action).

In a transaction controlled by a personnel action (PQ**) , you must determine the object types for which the action is to be executed. For each transaction related to an object type and controlled by a personnel action, specify which default personnel action(PQ**M) is to be processed by the corresponding transaction.
For each default personnel action within a transaction controlled by personnel actions, you can access a Process description.
Example
Personnel action "Create organizational unit":
Personnel action Plan ver. ObjType Infotype Subtype FCode VarField
O ** O 1000 INSE
O ** O 1002 0001 INSE
O ** O 1003 INSE
O ** O 1001 A011 INSE K


The personnel action "Create organizational unit" includes the following steps:

Creating the "Object" infotype (1000)
Creating the "Description" infotype (1002) with the "General Description" subtype (0001)
Creating the "Department/Staff" infotype (1003)
Creating the "Relationship" infotype (1001) with the "Cost Center Assignment" subtype (A011) for object type "K" (Cost Center).


Activities

1. Create the required personnel actions.
2. For each personnel action, determine the following:
Corresponding object type
Required infotypes and subtypes
Function code (INSERT, COPY)
The plan versions for which the personnel action is to be valid
The planning status in which the objects are to be created.

Entering default values is optional.
3. Enter the object type that is to be processed as well as the key of the personnel action for the transaction to be controlled by a personnel action.
Further notes

Ensure that you arrange infotypes in a logical order when defining a personnel action. The "Object" infotype must always be processed first and must have line number "001".
A personnel action may only be defined for one object type.
You can create three-digit personnel actions between "001" and "999".

As like in Personal Administration to run Personal Actions we use the T Code PA40, in the same way what is the T Coded in OM to run the Personal action which we had configured as above.

ANS:3 t-CODE OOMT