Sap Hcm(Om) Configuration Document

transcript

SAP HCM ORGANISATIONAL MANAGEMENT CONFIGUTION DOCUMENT

Before we go to the configuration. It is important that we must have an idea of what is the Business

Model or Requirement is. This configuration implements the Business Requirement of the

Implementation Model.

The focus shall be on the following Organisational Management infotypes:

Objects:

Organisational Unit

Position

Legacy ID

Relationships:

“Reports to” (A002) – Relationships for Org. Units to Org. Units

“Reports to” (A002) – Relationships for Positions to Positions

“Belongs to” (A003) – Relationships for Positions to Org. Units

“Manages “ (A012) – Relationships for Positions to Org. Units

Account Assignment Features

This is where the Company Code, Personnel Area and Personnel Subarea will be stored for

Organisational Units and Positions for reporting purposes.

CONFIGURATION OF PLAN VERSION

This defines which plan version is set to the active plan version, that is, the plan version in which the

current, valid Organisational Structure is maintained.

Configuration Path:

SPRO>>>SAP Reference IMG>>>>Personnel Management>>>Global Settings in Personnel

Management>>>Plan Version Maintenance>>>Set Active Plan Version

CONFIGURATION OF NUMBER RANGES

Setup Number Assignment for all Plan Versions

Our Number Assignment is going to be Plan Version Independent i.e. it will be the same across all

Plan Versions. The benefit of this option is that there is no danger of parallel number intervals

occurring i.e. the same number interval for one object in one plan version and for a different object

in another plan version.

Configuration Path:

SPRO>>>SAP Reference IMG>>>>Personnel Management>>>>Organisational

Management>>>>Basic Settings>>>>Setup Number Assignment for All Plan Versions

Enter X in the Value Abbreviation Field to activate number Assignment for all Plan Versions

Click Save

Maintain Number Ranges for objects

The implementation has approved the following number ranges for Objects:

Organisational Units (O): 10000000 – 19999999

Positions (S): 30000000 – 39999999

Legacy ID (99): 90000000 – 999999999

Configuration Path:

Management>>>>Basic Settings>>>>Maintain number ranges>>> Maintain number ranges

Execute Maintain Number Ranges and On the Subgroup column, select 01O to maintain number

ranges for Organisational Units.

Click on “Number Range Maintenance” Button

Output Screen

Click the “Maintain Intervals” Button

Next Screen

In the “From number” column enter the starting number: 10000000

In the “To number” column enters the ending number: 19999999

Click on Save button

For Positions, Number Ranges are maintained using the same steps as has been done for Org. Units

but making sure to select the record with Subgroup 01S on the Change “View “Number Assignment

“: Overview” table as depicted below.

CONFIGURATION OF OBJECT TYPES

Maintain Object Types

The SAP HCM Implementation uses standard object types but there is a requirement to create a

custom Object Type called “Legacy ID” to support the Interface design.

This Custom Object Type will be created to identify the Legacy Organisational Unit.

The characteristics of the custom object are similar to those of the standard Organisational Unit,

therefore, in creating the config. for the custom object a copy of the standard org unit will be made.

Configuration Path:

Management>>>>Basic Settings>>>>Data Model Enhancement>>>Maintain Object Types

Execute Maintain Object Types

Copy the Object Type “Org. Unit” and change the object type to 99, enter the Object type

description then press enter

Click the “Copy All” Button

Click “Continue Button”

Click “Save” Button

CONFIGURATION OF INFOTYPES

Infotype Maintenance

In this section we define OM infotype Characteristics of the Legacy ID.

Configuration Path:

Management>>>>Basic Settings>>>>Data Model Enhancement>>>>Infotype Maintenance

Execute “Maintain Infotype”

Select the infotypes that you need to be maintained for the newly created object type. In this case

we shall assign Account Assignment Feature (IT1008) to the Legacy ID Object type ”99”.

Under “Infotypes” section, double click Time Constraint.

Maintain Time Constraint if needed to, In this case we shall leave it at Time constraint 2 (with gaps).

Under infotypes section, double click “infotypes per object”

Select Organisational Unit Object Type record

Click “Copy” Button

Under the Object Type (OT) field, replace “O” with “99” and press Enter

Click “Save” button

At this stage, Infotype 1008 can be maintained for the new object type “Legacy ID”.

CONFIGURATION OF RELATIONSHIP IT1001

Maintain Relationships

This section is essentially a subsection of the configuration step “Relationship Maintenance”.

Here, we are creating a relation subtype AZ99 – “Is assigned to (Legacy)” for the object type Legacy

ID to Org. Unit.

Configuration Path:

SPRO>>>SAP Reference IMG>>>>Personnel Management>>>>Organisational Management>>>>Basic

Settings>>>>Data Model Enhancement>>>>Relationship Maintenance>>>>Maintain Relationship

Click Execute Maintain Relationship

Create a new relationship by copying an existing one and changing the Relationship Type and it’s

description.

Click Save button

CONFIGURATION OF ASPECTS

Aspects are used to control which Infotypes the user can see through certain maintenance

transactions. The use of aspects is optional. The benefits are that it simplifies maintenance and

training as only the allowed Infotypes are displayed.

ABJ specific aspect will be created to show only the Infotypes that AJB has decided to use.

Asp. Aspect name OT Object type text IT Infotype Name

Organisational

Management

O Organisational Unit 1000 Object

O Organisational Unit 1001 Relationships

O Organisational Unit 1008 Acct. Assignment Features

S Position 1000 Object

S Position 1001 Relationships

S Position 1002 Description

99 Legacy ID 1000 Object

99 Legacy ID 1001 Relationships

Configuration Path:

SPRO>>>SAP Reference IMG>>>>Personnel Management>>>Global Settings in Personnel

Management>>>>Dialog Control>>>>Maintain Aspects.

Create a new Aspect by copying an existing one and changing the name of the Aspects and press the

“Enter” button.

Click the “Copy all” button

Click the “Continue” or “Enter” button

We are back in the initial screen. However, the name of the Aspects disappears. Re-enter the name of the

Aspects and Click the “Save” button.

Under the “Aspects” section, double click “Plan Version per Aspects”. In this case we require only

two Plan Versions for our Aspects, which is Plan Version 01 (Current plan) and Plan Version 02

(Alternative plan/tech.).

Click “Save” button

Under the “Aspects” section, double click “Object types and Infotypes per Aspects”

On the screen you can see the copied Object Types and Infotypes.

We maintain these Object Types and Infotypes according to AJB business requirement.

Aspects configuration completed, it’s now ready for use.

SAP HCM OM PERSONNEL ACTIONS CONFIGURATION

Actions

An action assists in making sure all the required data is maintained. Any Object (i.e. Organisational

Units, Jobs or Positions) is made up of various sets of information stored in different Infotypes (or

screens). It is important to ensure these are maintained accurately and consistently.

The AJB implementation has approved two Action Types, one to create Organisational units (O)

and one to create Positions (S):

To Create Organisational Unit using Action, the following Infotypes were configured.

No Infotype Object Subtype Mandatory

1 1000 Object N/A N/A Yes

2 1002 Description N/A 0001 General Description No

3 1001 Relationships O 002 “Reports (line) to” or “Is line

supervisor of” Yes

6 1008 Account

Assignment N/A N/A No

Configuration Path:

SPRO>>>SAP Reference IMG>>>>Personnel Management>>>>Organisational Management>>>>Basic

Settings>>>>Maintain Personnel Actions

Execute “Maintain Personnel Actions”

To create a new Action type, we select and copy the existing one. In this case we copied the Action

type “O” (Create Organisational Unit)

Click the Copy button

Change the name of the Action type to 9001 and its description to Create organizational unit (JB)

Click Enter button

Click “Copy all” button

Output Result

Click Enter button

We are back in the initial screen. However, the name of the action disappears.

Re-enter the name of the Action.

Click Save button

Choose the newly created Action and select Actions (individual maintenance) under Actions (overview)

section.

Double click on Actions (individual maintenance) under Actions (overview) section.

On the screen you can see the copied Infotypes and subtypes.

We maintain these Infotypes according to AJB business requirement.

Click Save button

Now we are going to link our newly created Action type with the Transaction code (PP03)

Choose the newly created Action and select “Transactions for Actions” option.

Double click on the “Transactions for Actions” option.

To create a new link between the newly created Action and Transaction code (PP03), we select and

copying the existing one. In this case we copied the TCODE: PO10D - Maintain Organizational Unit.

Enter the TCODE: PP03 in the “Sem abbr.” field and the description if required.

Press Enter button twice, “Number of entries copied: 1” message displayed.

Click Save button

Action type is now linked to the Transaction Code (PP03)

Now let’s validate the Action Configuration by executing the newly created Action type: 9001

On SAP Easy Access Menu, in the command field, type TCODE: PP03 and press enter

Please note that IT1002 and IT1008 were skipped due to the lack of Authorisations.

To Create Position using Action, the following Infotypes were configured.

No Infotype Object Subtype Mandatory

1 1000 Object N/A N/A Yes

2 1002 Description N/A 0001 General Description No

3 1001 Relationships O A003 “Belongs to” or “Incorporates” Yes

5 1001 Relationships S A012 “Reports (line) to” or “Is line

supervisor of” No

6 1008

Account

Assignment

Features

N/A Yes

SAP Configuration Path:

Management>>>>Basic Settings>>>>Maintain Personnel Actions

Execute “Maintain Personnel Actions”

To create a new Action type, we select and copy the existing one. In this case we copied the Action

type “S” (Create Position)

Change the Action type to 9002 and it’s description to ” Create Position (JB)”

Click Enter button

Click “Copy all” button

Click Enter button

We are back in the initial screen. However, the name of the action disappears.

Re-enter the name of the Action.

Click Save button

Choose the newly created Action and select Actions (individual maintenance) under Actions (overview)

section.

Double click on Actions (individual maintenance) under Actions (overview) section.

On the screen you can see the copied Infotypes and subtypes.

We maintain these Infotypes according to AJB business requirement.

Click Save button

Now we are going to link our newly created Action type with the Transaction code (PP03)

Choose the newly created Action and select “Transactions for Actions” option.

Double click on the “Transactions for Actions” option.

To create a new link between the newly created Action type and Transaction code (PP03), we select

and copy the existing one. In this case we copied the TCODE: PO13 - Maintain Position.

Enter TCODE: PP03 into “Sem abbr.” field and its name in the description field.

Press Enter button twice, “Number of entries copied: 1” message displayed.

Click Save button

Action type is now linked to the Transaction Code (PP03)

Now let’s validate the Action Configuration by executing the newly created Action type: 9002

On SAP Easy Access Menu, in the command field, type TCODE: PP03 and press enter

Please note that IT1002 and IT1008 were skipped due to the lack of Authorisations.

OM – PA Integration

In the SAP system the integration is controlled using switches. All the integration switches are stored

in table T77S0. PA – OM integration is defined by PLOGI – ORGA in this table.

The feature PLOGI acts as the central switch for integration between Organisational Management

and Personnel Administration. It is recommended the integration must be turned on as indicated in

the table below and the integration version set to 01 Current Plan.

This will integrate the Organisational Unit, Cost Centre, Company Code, Personnel Area and

Personnel Sub Area when the position is entered in the PA Infotype 0001.

Configuration path:

Management>>>>Integration>>>> Integration with Personnel Administration OR use TCODE:

SM30 OR SM31 to change table T77S0.

Activate integration between Organisational Management and HR Master Data in Personnel

Administration PLOGI ORGA. This guarantees data consistency between the two components.

PPOM INHS must contain an X to denote that integration with Account Assignment Feature (for

Company Code, Controlling area and Business Area) is turned on.

PLOGI SPLIT must contain an X to denote that when a Position, Job or Organisational Unit

description changes (when Infotype 1000 is copied and changed) then a new Infotype 0001

for the holder (relationship 008) will be created on the date of the changes. This means the

system will always display the up-to-date descriptions of named objects in PA and related

reports.

THE END

Sap Hcm(Om) Configuration Document

Documents