Hierarchy
SAP_HRCBE (Software Component) Sub component SAP_HRCBE of SAP_HR⤷
PY-BE-PS (Application Component) Öffentlicher Dienst⤷
P12P1 (Package) Human Resources Belgium: Public Sector
IMG Activity
| ID | OHIBEPBS046 | Set up integration with personnel administration |
| Transaction Code | S_HR0_07000041 | (empty) |
| Created on | 20011019 | |
| Customizing Attributes | OHIBEPBS046 | Set up integration with personnel administration |
| Customizing Activity | OHIBEPBS046 | Set up integration with personnel administration |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHIBEPBS046 |
In this step, you activate integration between Organizational Management and in Personnel Administration. This guarantees data consistency between the two components.
Example
A person is to be transferred from the position "Controlling administrat or" 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.
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.
We 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.
To activate integration, you must check or make the following settings in addition to those you have already made in the step "Global Settings in Personnel Management":
1. Basic Settings
- Integration switch for organizational assignment (T77S0: PLOGI ORGA)
- Default position (PLOGI PRELI)
- Update file PAnnnn (PLOGI PRELU)
- Department switch (PPABT PPABT)
- Default value for personnel subarea (PPINT BTRTL)
- Default value for personnel area (PPINT PERSA)
- Transfer short or long texts from Organizational Management to
Personnel Administraiton (PLOGI TEXTC, PLOGI TEXTO, PLOGI TEXTS)
2. Participating in integration
The feature "PLOGI" contains criteria with which you can determine the persons in your enterprise or personnel structure for whom integration should apply.
The criteria are:
- Company code
-Personnel subarea
- Employee group
- Employee subgroup
You can combine any of these criteria for integration. You can activate integration for all employeed or just for certain company codes, personnel subareas, employee groups, employee subgroups or for different combinations.
Notes
If integration is active, it is possible to relate persons and positions (relationship B008). For this reason, it may be necessary to define relationship characteristics to control the validity of relationships that are created. The system would then send out a warning or error message if, for example, a position was to be occupied and the working time of the holder exceeded the planned working time or if a person is assigned to one or more positions for more than 100% of their working time.
Carry out the step "".
Activities
Make the following settings in the recommended order:
1. Using the entry "PLOGI ORGA", determine whether integration between Organizational Management and Personnel Administration is active. If you do not want integration to be active, enter ' ' (blank).
2. You should not change the entry "PLOGI PRELI". You can, however,change the name of a position with this number (see Value of semantic abbrevation for the entry "PLOGI PRELI") in Customizing for Personnel Administration.
3. In the entry "PLOGI PRELU", determine whether Master Data is to be updated online or by batch input.
4. In the entry "PPABT PPABT", determine whether only organizational units indicated as infotype 1003 "Department" for a position are to be read.
5. Determine the default value for the the personnel subarea in the entry "PPINT BTRTL".
6. Determine the default for the personnel area in the entry "PPINT PERSA".
7. In the entry "PLOGI TEXTC", determine whether the short texts rather than the long text for jobs created in Organizational Management are to be transferred into Personnel Administration.
8. In the entry "PLOGI TEXTO", determine whether the short texts rather than the long texts for organizational units created in Organizational Management are to be transferred to Personnel Administration.
9. In the entry "PLOGI TEXTS", determine whether the short texts, rather than the long texts for positions created in Organizational Management are to be transferred into Personnel Administration.
10. In the feature "PLOGI", determine for which persons integration should be activated for based on the criteria company code, personnel subarea, employee group and employee subgroup.
Note: In the standard system, the switch &PLOGI is set to "X" (all).
11. If you set the switch PLOGI EVENB to 'X' setzen, you can make organizational changes that include a change of company code.
12. According to the set up in your enterprisee (see Activating integration) , start one of the reports in the step "Tools for Integration".
Further notes
-For detailed specifications, refer to the documentation on the entries in the "Semantic group" und "Semantic" and "Semantic abbreviation" fields.
-You can display specific documentation on the feature in the transaction; you will find a general feature description under Help -> Extended Help.
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHIBEPBS046 | 0 | HLA0009701 | Organizational Management |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| PMKC | L - Logical transport object | OOPT | PLOGI 01 | Participate in integration | ||
| V_T77S0SC | V - View | OOPS | 27 | Basic Settings |
History
| Last changed by/on | SAP | 20011019 |
| SAP Release Created in | 470 |
