Setting Up Integration Switches

Objectives

After completing this lesson, you will be able to:

Set up integration settings
Hire an employee and test the integration between OM and PA

Integration Between OM and PA

OM is integrated with PA so that the Organizational Assignmentinfotype is filled with data from OM when integration is active. Consequently, some of the infotype fields are no longer ready for input in the Maintain HR Master Data transaction.

Personnel Administration (PA)

Persons are objects that hold positions in an organizational structure. PA maintains person-related data. The integration of PA with OM enables you to automate some of the maintenance tasks.

Organizational Assignment

If integration is active and a person is assigned to a position in HR master data, the objects linked with the position in HR master data are written to the Organizational Assignment infotype. If integration is active, the Organizational Unit, Job, and Cost Centerfields are not ready for input, but are filled in the Organizational Management infotype (IT0001) exclusively from OM.

In addition, every organizational change is stored in both the Organizational Assignment infotype in HR master data and the organizational plan in OM. This means that if a change made in OM affects the organizational assignment of a person, then the change in the HR master data is written to the Organizational Assignment infotype. Similarly, a change made to a person’s organizational assignment (for example, as a result of a personnel action) in HR master data is updated in OM.

Basic Integration Settings

The PLOGI feature is used to decide the employees that are taken into account for integration between OM and PA.

You must first set the integration plan version in the PLOGI PLOGI entry in table T77S0. If you do not define an integration plan version, integration is not active. You then specify the employees that need to be involved in integration. To do this, maintain the PLOGI feature.

You can form groupings according to the following criteria:

Country grouping
Company code
Personnel area
Personnel subarea
Employee group
Employee subgroup

Enter X in the Value abbr field of table T77S0 to activate participation in integration. If there is to be no integration, leave the field blank.

If you activate the PLOGI ORGA switch in T77S0 by entering X, you also activate integration between the PA and Personnel Planning components as a whole. PLOGI ORGA is the main integration switch. This switch enables PA and the organizational plan to remain consistent.

Additional Integration Settings

Examples of integration settings for the Group PLOGI include the following settings:

PLOGI EVENB:: If you set the PLOGI EVENB switch to X, you can move a person, position, or organizational unit within an organizational structure, if this change also requires a change in the company code for the affected person(s).
PLOGI PRELI:: If an employee has not been assigned to a position in the integrated system, you can use the default value contained in PLOGI PRELI.
PPABT PPABT:: If you use the department switch PPABT PPABT, you can activate the inclusion of the Department indicator in infotype 1003 for integration.

The following table lists the results received when you enter different values for PLOGI PRELU:

Value	Result
BTCI	The changes in OM are not updated immediately in PA (Organizational Assignment infotype 0001). The personnel numbers affected by the change are collected before the new information is updated by a batch input later.
" " or "0"	The update (between OM and PA) takes place immediately.
A numeric value	The system first determines how many personnel numbers are affected for each action in OM. If this number exceeds the numeric value, the same applies as for entry BTCI, or alternatively, as for entries " " or "0".

Daily Routine Activities

The Organizational plan is a dynamic structure. Occasionally organizational units will need to be moved, divided or merged. In most cases those organizational units will already contain positions and those positions will have holders. This means Personnel Administration records must also be updated.

Moving Organizational Units and Positions

Moving an organizational unit or a position entails creating and delimiting relationships AB002 Reports (line) to/is Line Supervisor of and AB003 Belongs to / Incorporates. When you create a new relationship, time constraints on the relationships of that object force the system to delimit the old relationship(s).

When you move organizational units to a different parent organizational unit, they take positions related by the AB003 Belongs to / Incorporates relationship, and any holders, with them.

The infotypes of moved organizational units or positions remain unchanged unless the new relationships force them to be delimited and new ones created. The best example of this is the inheritance of Cost Centers along the organizational structure. Organizational units automatically inherit the master cost center of the parent organizational unit when they are related, this could be at initial creation or when moved.

If the PPOM INHS switch is enabled (X) in table T77S0, the master cost center of a moved position is updated from the date of the new relationship. As in the creation scenario, the Master cost center can subsequently be manually overwritten or split using the Cost Distribution infotype.

Organization and Staffing Interface

Although relationships and infotypes can be maintained in a variety of interfaces, Organization and Staffing is ideal for these kinds of operations because it allows multiple objects to be maintained at once and provides visual confirmation of new relationships.

Delimiting Positions and Organizational Units

When non-manager positions are moved to another organizational unit there should be no need to move the manager position to the new location. It could be moved if it is to continue without manager responsibilities, approvals, and workflow but the most likely scenario is that the holder is transferred out of the position and the position is delimited.

An organizational unit cannot be delimited if it contains positions because the system would also attempt to delimit the AB003 Belongs to / Incorporates relationship to the position. Once all positions have been delimited, the obsolete organizational unit can be delimited.

Positions and organizational units that are no longer required must still exist historically. This is achieved by delimiting instead of deleting.

When delimiting positions or organizational units, the date requested by the system is the last date on which the object should exist.

To delimit a position or organizational unit, you must delimit all dependent relationships by transferring or terminating the holders of the positions and delimiting or moving the positions. The position or organizational unit is then delimited.

How to Set Up Basic Integration Settings

Steps

Confirm integration is active by accessing the hiring action HR505 for personnel number 50599300 with today's date..
1. On the SAP Easy Access screen in the Command field enter transaction code PA40.
2. In the Personnel Number field enter 50599300. Enter today’s date in the date field.
3. Select Hiring HR505, and enter Personnel AreaCABB, Employee Group1, and Employee SubgroupX0. Choose the Execute pushbutton.
4. Point out the open Position field, and demonstrate that a Structure Search is available by selecting the field and the F4 values. Select the Structure Search tab, and open Org. Units Training Group > Training International > Marketing > 00 Marketing. Note that positions appear, including a vacant 00 Assistant position.
5. Cancel the Structure Search dialog box, and Exit the Personnel Action and return to the SAP Easy Access screen.
Turn off the PLOGI ORGA integration switch.
1. On the SAP Easy Access screen enter transaction code SM30 in the Command field.
2. Enter T77S0 in the Table/View field, and choose Maintain.
3. Use the Position button at the bottom of your screen and enter PLOGI in the Group name field, and enter ORGA in the Semantic abbr.field. Select Continue (Enter).
4. Remove the X in theValue abbr field, and choose Save. Choose Enter to acknowledge the warning.
  Result
  Note
  Integration is now turned off.
Confirm integration is turned off by accessing the hiring action Hiring HR505.
1. On the SAP Easy Access screen enter transaction code PA40 in the Command field and choose Enter.
2. Enter Personnel Number 50599300 and enter today’s date.
3. Select Hiring HR505, and enter Personnel AreaCABB,Employee Group1, and Employee SubgroupX0.
4. Choose Execute.
5. Choose the Position field, and choose F4. Values show that a structure search is not available because integration is now turned off. Cancel the search.
  Result
  Note
  Because integration is turned off, there is no longer a Position field on the screen.
Turn the integration switch PLOGI ORGA back on.
1. Exit the personnel action and return to the SAP Easy Access screen by choosing the Back pushbutton.
2. On the SAP Easy Access screen, enter SM30 in the Command field. Enter T77S0 in the Table/View field, and choose Maintain.
3. Use the Positionbutton and enter PLOGI in the Group name field, and enter ORGA in the Semantic abbr. field. Choose the Continue (Enter) pushbutton.
4. Enter an X in the Value abbr field, and choose Save. Choose Enter to acknowledge the warning.
  Result
  Integration between OM and PA is now turned back on.

Result

Integration Tools

The sequence in which you activate integration depends on one of the following constellations:

You already use PA and want to implement OM. The data in PA already includes information about organizational units and positions.
You already use OM and PA is to be integrated with OM.

If HR master data is available in PA, you can use report RHINTE00 to transfer the data to OM.

The following reports are used to transfer data from OM to PA:

Report RHINTE10:: Generates the required table entries in PA for OM objects that are relevant for integration.
Report RHINTE30:: Allows you to transfer a person’s organizational assignments, such as positions and organizational units, from OM to the Organizational Assignment infotype in PA.
Report RHINTE20:: Checks whether all of the objects relevant for integration exist in both PA and OM.

Report RHINTE00

Report RHINTE00 reads the Organizational Assignment infotype records created in PA. It creates a batch input session that in turn creates the relevant OM objects and relationships, depending on the parameters you set.

Details of the Objects and Relationships to be Created

The following tables provide the details of the objects and relationships created:

Objects Created	Description of Relationship
Work Center	Object type A
Job	Object type C
Organizational Unit	Object type O
Position	Object type S

Relationship Created	Description
S <-> P	Person is holder of position, A/B 008
A<-> P	Person is holder of work center, A/B 008
C <-> S	Job describes position, A/B 007
O <-> S	Organizational unit incorporates position, A/B 003
O <-> K	Master cost center assignment, A 011
S <-> K	Master cost center assignment, A 011, depending on the report parameters

No relationships between organizational units or between positions are created. These relationships must be maintained manually in OM. If you select the Create Holder Relationships Only option, the report transfers only those assignments of persons to positions that have changed to OM.

Report RHINTE10

Report RHINTE10 enables you to transfer the following objects created in OM to HR master data:

Organizational unit
Job
Position
Work center

Only objects that have the status 1 (active) in the integration plan version are transferred.

The integration objects are required for the Organizational Assignment infotype. A program run can take place for one or all object types, or for a selected structure.

You can also use report RHINTE10 to delete objects in the Customizing tables for PA. You need to be particularly careful when you delete objects.

Report RHINTE30

Report RHINTE30 enables you to update the Organizational Assignment infotype (PA) for the selected personnel numbers with data created by previous actions in OM.

Report RHINTE30 creates a batch input session for a particular group of persons. The session updates the Organizational Assignment infotype for the corresponding group of persons. The organizational assignment that was created by previous actions in OM is transferred to the Organizational Assignmentinfotype. A new record is created in the infotype for the start date entered. You must activate integration between OM and PA before starting the report.

Report RHINTE20

Report RHINTE20 enables you to check whether the object types relevant for integration have been created in both PA and OM. Objects in master data tables include jobs, work centers/positions, and organizational units. OM objects include work center, job, organizational unit, and position. You can add objects that are missing in either PA or OM immediately.

Integration: Default Values and Fixed Specifications

OM can support PA by providing default values.

The following table shows the default values in OM with the corresponding specifications in PA:

Organizational Management	Personnel Administration
Assignment to position	Provides entries in Organizational Assignment infotype (IT0001) in organizational plan area
Cost Center Assignment relationship	Provides entry in Cost Center field in Organizational Assignment infotype (IT0001)
Cost Distribution infotype	Is relevant for Payroll and Personnel Cost Planning
Employee Group/Subgroup infotype	Provides the default values in Actions infotype
Planned Compensation infotype	Delivers pay-scale information for basic pay
Work Schedule infotype	Enables comparison of work schedule hours with the working time stored in the Planned Working Time infotype (IT0007)
Account Assignment Features infotype	Provides the default values in Actions and Organizational Assignment infotypes

Hire an employee and test the integration between OM and PA

DemoStart Demo

ExerciseStart Exercise

Business Example

Your company is implementing PA and OM. This will streamline the process of hiring new employees to fill your vacant positions. You need to know the various tools you can use to ensure data consistency between the two components.

Task 1: Hire a new employee and set up integration.

Steps

Use the personnel action Hiring Organizational Management OM to hire an employee for the position ## Head of Personnel Development. Enter a name of your choice as the name of the employee and start date as today’s date. Assign the personnel number 505991##. Fill all other infotypes with data of your choice.
Note
Choose (SAP Menu) before you start this exercise.
1. On the SAP Easy Access screen, choose Human Resources→Personnel Management→Administration→HR Master Data→Personnel Actions.
2. In the Personnel no. field, enter personnel number 505991## and in the From field, enter today’s date as the start date. Choose the personnel action Hiring Organizational Management OM and choose Execute.
3. Assign the new employee to the ## Head of Personnel Development position.
  Choose input help, and in the Search Term field, enter ## Head*, and choose Start Search. From the list of positions displayed, select ## Head of Personnel Development position and choose Copy.
4. Choose ENTER. An information dialog box confirms default values are used by the position. Choose Continue. You can see the following information from the position:
  Field Value
  Personnel Area CABB
  EE Group 1
  EE Subgroup X0
  Note
  The higher-level organizational unit ## Human Resources inherits the personnel area from the Account Assignment Features infotype. You maintained the information for the Employee Group/Subgroup infotype for the position ## Head of Personnel Development.
5. Enter Z5 (New Hiring) in to the field Reason for Action. Choose Save. You are automatically taken to the next infotype, until you have entered the necessary data for all infotypes.
6. For the Personal Data infotype, on the Create Personal Data (0002) screen, enter your first name,last name, any date of birth, and marital status. Choose Save.
  Note
  For Organizational Assignment infotype, observe the fields that are already filled with information from OM. The information originates from the Account Assignment features infotype for organizational unit ## Human Resources, the Cost Center Relationship, the relationships from P to S, S to O, and S to C in the Organizational Plan area.
7. Choose Save. The Delimit Vacancy dialog box is displayed. Accept the values by choosing Yes.
  Result
  Note
  You may or may not receive the dialog box for the vacancy. The display of the dialog box is dependent on the settings for your position in the Organization and Staffing Interface (PPOME) or infotype maintenance.
8. Enter an address of your choice and choose Save. The Planned Working Time infotype is displayed. Accept the default values by pressing Enter and choose Save.
9. For the Basic Pay infotype, the system proposes the values that you have defined for the job ## Manager in infotype 1005 Planned Compensation. Accept the default values by pressing Enter and choose Save.
10. Return to the SAP Easy Access screen.
Which fields in the Actions and Organizational Assignment infotypes already contain information you entered in OM?
1. Actions: Personnel area, employee group, employee subgroup
2. Organizational Assignment: Cost center, personnel subarea, job, organizational unit
Which Customizing activities must be completed to activate integration between OM and PA?
1. The Customizing activities required to activate integration between OM and PA are located under the following path:
  - In Customizing, choose SAP Reference IMG —> Personnel Management→Organizational Management→Integration→Set Up Integration with Personnel Administration. (Alternatively you can also use system table T77S0).

Field	Value
Personnel Area	CABB
EE Group	1
EE Subgroup	X0

Continue to quiz