Saturday, 30 April 2016

How SAP HR organization works as a single unit

Relationships

We need to look at two types of Relationships in SAP

1.Relationships with same Object Types

2.Relationships with different Object Types

Lets look into them in detail -
Relationships with Same Object Types
sap organizational management tutorial
  • Organizational units are related with each other to form a hierarchical structure.
  • Each organizational unit is created as an individual object type. Using the example above, the organizational unit of "Region Office" is an object type, as are the organizational units of Finance & Accounting and Human Resources.
  • To create the interrelated hierarchy, a relationship must exist between Regional Office and Finance & Accounting and between Regional Office and Human Resources.
  • Relationships are formed in both directions, therefore Regional Office incorporates Finance & Accounting and Finance & Accounting belongs to the Regional Office.
  • When you create a relationship between objects, SAP automatically creates the corresponding reverse   relationship.
Relationships with Different Object Types
sap organizational management tutorial
  • Any SAP organizational unit will have positions attached to it. The organizational units object would therefore be linked the position object types as a relationship.
  • In the example detailed above, the organizational unit object of Human Resources has a relationship of 'incorporates' with the position object of HR Manager, therefore the position object of HR Manager has a relationship of 'belongs to' with the organizational unit object of Human Resources.
Common relationships
sap organizational management tutorial
  • Objects are linked though relationships.
  • You create relationships between the individual elements in your organizational plan. Several linked objects can represent a structure. There are different types of relationships, as the type of connections between elements varies
sap organizational management tutorial

Thursday, 28 April 2016

Learn Organizational Management (OM) in SAP HR


In this tutorial we will cover the key concepts in the OM module of SAP HR
  • Object Types Entities within OM are maintained as object types (e.g. Org Units, positions,jobs)
  • Relationships Links objects together (e.g. person to position, position to Org Unit)
  • Validity Dates Validates life span of objects
  • Infotypes Data input screens used to record relevant information
Object Types

Each aspect of OM is recorded as an object type, a way of grouping similar data together. For example, organizational unit is an object type, position is another object type.
Relationships
There are many objects within OM, and the creation of relationships is the way that data is linked together. When you build the hierarchical organizational structure, you are creating a relationship between organizational unit objects. If you attach a position to an organizational unit, you are creating a relationship between the position object and the organizational unit object.
Validity Dates

Whenever you create an abject or a relationship between objects, you must enter start and end dates. These validity dates ensure that data entries can only be made within a specified lifespan.
Infotypes

These are the data input screens used to record the OM information. Some infotypes are automatically updated 'behind the scenes'; other infotypes require you to manually input the information.
Lets look into the different OBJECT TYPES in detail 
OM is based upon the use of Object Types and Relationships. Object Types group similar data together. Although an organizational plan can consist of many object types, the five basic building block object types and their 'codes' are as follows:
sap organizational management tutorial 
  • The Personnel Administration (PA) module of the SAP HR system holds the person related data in infotypes in the master data file.
  • The Organization Management (OM) module looks at the organization's departmental structure and holds the data in object types. OM object types are a way of grouping similar data. The system assigns a code for each object type.
  • These objects are created and maintained separately and are then linked together using relationships.
Organizational unit sap organizational management tutorial
  • Object type is used for Organizational Unit.
  • Organizational units are units of your company that perform a function.
  • These units can be departments, groups or project teams, for example.
  • You create the organizational structure of your company by relating organizational units to one another.
  • The organizational structure is the basis for the creation of an organizational plan.
Position sap organizational management tutorial
  • Object type is used for Position.
  • Positions are used to distribute tasks to different positions and to depict the reporting structure in your organizational plan.
  • Positions are concrete and are held by employees in a company.
  • Positions are assigned to organizational units and can inherit characteristics from a job.
Job sap organizational management tutorial
  • Object type (classification) is used for Job.
  • Positions are held by people in the company (e.g. secretary in the marketing department,HR manager). Jobs, in contrast, are classifications of functions in an enterprise (e.g. secretary, manager), which are defined by the assignment of tasks and characteristics.
  • Jobs serve as job descriptions that apply to several positions with similar tasks or characteristics. When you create jobs, they are listed in a job catalog.
  • When you create a new position (e.g. secretary in the marketing department), you can relate it to a job that already exists in the job index (e.g. secretary). The position then automatically inherits the tasks and characteristics of the job. This significantly reduces data entry time, as tasks and characteristics do not have to be assigned to each position separately, instead they are inherited via the descriptive job. Note however, that specific tasks and characteristics can also be assigned directly to positions.
Jobs are also important in the following components:
  • Personnel Cost Planning
  • Career and Succession Planning
  • Compensation Management
When you create jobs, they are listed in a job catalog. A job catalog is a list of jobs maintained for an enterprise.
Cost Center sap organizational management tutorial
  • Object type is used for Cost Center.
  • Cost centers are a Controlling/Finance item that represents the origin of costs. Cost center are external from OM and will be created and maintained in the Controlling module. Cost centers can have relationships with either organizational units or positions.
  • Cost center assignments are inherited along the organizational structure.
Person
  • Object type is used for Employee.
  • A person is generally an employee in the company who holds a position.
  • Additional information for employees is maintained in PA (e.g. address, basic pay, etc.).IT0001 (Organizational Assignment) contains the position assignment, defining job,organizational unit, and cost center assignment.
Other noteworthy Object Type is TASKS
  • Object Type T is used for tasks
  • Tasks are individual duties and responsibilities that must be undertaken by employees
Tasks can be clubbed under two headings
  • As part of workflow
  • As part of personnel management to describe jobs and positions

Wednesday, 27 April 2016

How to Create Position

In the SAP command prompt , Enter transaction PPOME
sap-om-create-organizational-unit
In the next SAP screen, click the sap-om-create-organizational-unit button.

In the next SAP screen, Enter the start date of the new position
 
 
Next , search for the organizational unit to which new position will be added. Enter the name of the organizational unit and click find.

 
sap-om-create-position
In the results window , double click on the desired result.
 
The selected organizational unit will be displayed in the overview section. Select the target org unit and click create.
 
The next SAP pop-up window enables you to choose the relationship between the Organizational unit and Position. Select "Incorporates"
 
In the details section , give information of the new position that  you are creating and Click the save button.
 
In the overview section , you will notice that the new position has been added under the Organizational unit.
 
sap-om-create-position

Structure Maintainence

Prerequisites

The following entries belong to structure maintenance:
  • Structure name for decision fields
  • Structure name for back value
  • Structure name for back value
  • Transfer type
  • Subfeature
  • Valid field names for decisions

Process flow

  • Structure name for decision fields
    Structures are defined in the ABAP Dictionary. Only field names defined in the structure can be used in the decision tree. For further information on the ABAP Dictionary, please refer to the documentation on the ABAP Workbench under BC ABAP Dictionary in the SAP Library.
  • Back value structure name
    If the back value consists of more than one value for field return or of more than one column for table return, you can enter the name of a suitable structure here.
    The system proposes the individual fields of this structure when you choose the create or changefunctions in the decision tree. If the fields have a check table or fixed values, these values are displayed as input help, and the entries are checked against these values.
    Note Note
    For technical reasons, the structure of the back value can have a maximum size of 42 bytes. You can enter either a structure name or field name for the back value.
  • Back value field name
    If the field has a check table or refers to a domain with fixed values, the system will propose the key values of the check table or the fixed values as possible back values. This occurs when you are using the create or change functions in the decision tree.
    Note Note
    You must enter the back value in the form Table name - Field name , for example, P0001-ABKRS . You can enter either a structure name or field name for the back value.
  • Transfer type
    The transfer type determines whether the back value should be a field transfer (1) or a table transfer (2).
  • Subfeature
    If this field is flagged, the feature is created as a subfeature. The subfeature is included in the main feature. You can find further information in Decision Tree for a Feature .
  • Valid field names for decisions
    As the person responsible for the feature, select the fields that can be used in the decision tree for the feature. You select these from the fields defined for the feature structure.

Monday, 25 April 2016

Account assignment features

Definition

Infotype with which you can define account assignment features for organizational units and positions.
·  It plays a role in the assignment of cost centers to objects.
You need cost center assignments if you plan to use the Personnel Cost Planning component.
·  It allows you to enter default settings helpful for the Personnel Administration component.
This ensures more efficient integration between the Organizational Management and Personnel Administration components.

Use

You can maintain this infotype using Infotype Maintenance, by creating infotype records one object at a time. Or, you can work in Simple Maintenance, where procedures are streamlined.

Cost Center Assignments

Using this infotype, you can specify cost center-related default settings for organizational units and positions. These default values ensure that the system suggests the correct cost center assignment for objects. You are advised to set default values in order to prevent incorrect data being entered on persons.
Cost centers are determined according to a combination of different pieces of information, including business areas, company codes, and so on. By setting defaults for these items, you narrow down the number of cost centers that can be assigned to an object.
The principle of inheritance applies to account assignment defaults. For example, the defaults set for an organizational unit are inherited by subordinate organizational units, as well as by positions assigned to the organizational units.
If you do not want to set up defaults using the Account Assignment infotype, you can enter a single default for all organizational units, in Customizing. Refer to the Personnel Management section of the Implementation Guide (IMG).

Personnel Administration Defaults

Using this infotype, you can assign personnel areas to organizational units or positions. Default values for payroll, authorizations and so on are controlled via personnel areas.
The inheritance principle applies to personnel areas. This means that employees automatically inherit personnel areas assigned to organizational units and positions, unless you specify otherwise.
This presents two advantages for Personnel Administration users:
·  Faster assignment of personnel areas, since you do not have to do this separately for every employee.
·  Fewer entry errors, as the system suggests the values to be inherited.
Entering personnel areas presents an additional advantage to customers who are installing the Organizational Management and Personnel Administration components together. Each personnel area is assigned a company code. Company codes are one of the factors used to determine cost centers. (Personnel Administration may require cost center assignments so that payroll charges can be charged back.)
This means if you specify a personnel area, it is not necessary to make any more entries in this infotype.

Integration

If enterprise organization is active in a controlling area, you can only maintain an organizational unit’s cost center and company code assignments in Controlling. You can only assign a controlling area to one organizational unit.
The system saves these assignments in Account Assignment Features (infotype 1008) in the Controlling Areaand Company Code attributes. However, you can maintain or overwrite the Business Area and Personnel Area attributes of this infotype in Organizational Management, even if enterprise organization is active. If you implement the Controlling component, you can find more information in SAP Library under Financials → Controlling →Controlling Methods → Authorizations → Enterprise Organization.

Sunday, 24 April 2016

Organization Management Info Types

Once you have created different OM Objects , you will need to maintain Infotypes  related to it.

Lets look into SAP-HR OM Infotype Maintenance --

There are two Methods to Maintain SAP - Organizational Management Infotypes
1. Using Organization and Staffing Transaction

2.Using the Expert Mode.

In this tutorial we will look into the Expert Mode

The Expert Mode is an interface that is ideal for maintaining details. Individual objects areselected using the Object Manager. Infotypes for that particular object can now be maintained.

Transaction code PP01 can be used to maintain all object types. Due to authorization restrictions, you may not have access to PP01. Instead, you will have to use one of the following transactions, which restrict access to one particular object type:
  • PO10 Organizational Unit
  • PO03 Job
  • PO13 Position
  • PO01 Work Center
The PP01 screen is shown below. Screens for PO10,PO03,PO13 & PO01 are very similar
sap organizational management tutorial
  1. Plan Version: It is important to ensure that you are working in the correct plan version at all times (for this you can also default the plan version in the user parameter
  2. Object Information:The object type, ID and abbreviation are displayed so the user can ensure that the right object is being edited.
  3. Status: Select the status of the infotype you want to maintain using the tab pages (select Active which has status = 1).
  4. Infotype: Select the infotype you want to maintain.
  5. Validity Period: Start and end dates specify the period during which the object exists in the plan version selected.
Important OM Infotypes
1.IT0001 - Description: It gives an Object's Abbreviation and Name
sap organizational management tutorial
2.IT0002- Relationships:
sap organizational management tutorial
  • There are many different relationship types that you can create between object types
  • Each individual relationship represents a subtype of the Relationships infotype (IT1001).
  • Not all relationships apply to every object.
  • Relationship records can manually be created using the Expert Mode interface, but they are also automatically created when using other interfaces (e.g. Organization and Staffing, Simple Maintenance).
  • When creating a relationship, the inverse relationship is usually automatically created by the system.

Saturday, 23 April 2016

Organizational Objects

Definition

Objects that are used to create an organizational plan in Organizational Management.  The following object types are available:
·  Organizational Unit
·  Position
·  Job
·  Work Center
·  Task
Organizational plans can also include organizational objects that come from components other than Organizational Management (cost center or person (employee or user), for example) or objects defined in customizing.

Use

You can relate organizational objects in two ways to create an organizational plan:
·  you can either relate objects of the same object type in separate hierarchies or list them in separate catalogs.
·  or you can relate objects of different object types and in so doing relate the hierarchies and catalogs.
These relationships enable you to depict multi-dimensional dependency in your enterprise’s organizational plan.
It is not mandatory to use all of these objects in your plan. You do not have to define work centers, for example, if you do not find them applicable. You do not have to assign tasks to your jobs and positions. You must, however, create organizational units.
By determining a validity period for every organizational object, you can display and evaluate situations in the past, present and future.

Structure

An organizational object comprises:
·  an 8 digit ID number and a description
·  relationship, which defines the link between the object and other objects
·  various object characteristics
·  validity period and a time constraint
·  status indicator