ORGANIZATIONAL MANAGEMENT

Organizational Plan : A collection of types of information that provide a view of the structural and human resource environment in an enterprise. An organizational plan includes information about the: Organizational structure in an enterprise Positions and the reporting structure or chain of command between them Different types or classes of job Work centers (physical locations) of jobs and positions Tasks performed for a job or position

Organizational Structure : A hierarchy in which the organizational units in an enterprise are arranged according to tasks and functions.
The organizational structure differs from the administrative enterprise or personnel structure, whose structural elements are relevant to payroll accounting and accounting.

Organizational Unit :
An organizational object used to depict the basic structure of an organization. Organizational units are functional units of an enterprise. Depending on how tasks are distributed in an enterprise, an organizational unit can be a department, group, project team, or other unit.

Various Interfaces Of OM :

Organization n Staffing General Structures Matrix Structures Expert Mode Simple Maintenance

Organization n Staffing : It provides an intuitive interface for creating and editing organizational plans.
When an organizational plan is created, the functions can be use to plan for future developments within a company, for example: Corporate re-organizations Expansions Downsizing These reporting functions can be use to extract information for making decisions.

General Structures : It allows to edit organizational plans with any structure including object types which we have defined ourselves (teams, for example).
Matrix Structures : The Matrix view is for creating and editing matrix structures.

Expert Mode : Expert mode allows you to edit the characteristics of various objects and their relationships via info types. You can use the "Organization and Staffing" interface as an alternative to expert mode.
Simple Maintenance : Simple Maintenance is one method you can use to create and update organizational plans.

Simple Maintenance lets you create a framework for organizational

plans using a tree structure.

 In Simple Maintenance you can:

Build and update organizational structures Create jobs and positions Assign positions to organizational units Build task profiles for jobs and positions Build and update reporting structures Assign cost centers to PD objects

Object :

An individual element of information in the system. All objects are classified according to object type. Objects that belong to the same object type share relationships and possess certain types of characteristics.

Object Types : An object type let us classify objects according to features and types of information and arrange them in categories.
Relationships: Relationships are special subtypes of info type 1001. Each relationship has two relationship types , indicated by A and B. For each relationship created (A or B), the corresponding inverse relationship is automatically set up.

Important object types are:Objects

Organizational Unit Job Position Cost Center Person Budget Task

Object Types
O C S K P BU T

Important Relationships :
Relationships A/B 007 A/B 003 A 001 A/B 002 A/B 008 Objects C-S O-O / O-S O-O / S-K O-O / O-S S-P Relation Name describes / is described by belongs to / incorporate cost center assignment reports to / line supervisor of holder

Mandatory Characteristics Of an Object : Object Name Object Type Object Abbreviation Object Id Plan Version Planning Status Validity date

Plan Version : It is used to differentiates between scenarios in which an organizational plan is created.E.g. Current Plan & Alternative Plan.
Number Assignment : The process by which numbers are allocated to business objects. There are two types of number assignment : Internal number assignment occurs automatically in the R/3 System. External number assignment is performed either by the user or an external system. Number assignment is either plan version- specific or plan version Independent.

Subgroup : It represents all number ranges. The names of the subgroups are set up so that the first characters specify the plan version and the last two specify the object type in detail. The structure of the subgroups depends on whether we are using number assignment valid for all plan versions or not.
The following entries are allowed (when number assignment is not valid for all plan versions). $$$$ (plan version and object type are generic) PV$$ (plan version, object type is generic) PVOT (plan version, object type)

The following entry is not allowed: $$OT (plan version generic, object type)
The following entries are allowed (when number assignment is valid for all plan versions): $$$$ (plan version and object type are generic) $$OT (plan version generic, object type) The following entries are not allowed: PVOT (plan version, object type) PV$$ (plan version, object type is generic)

Planning Status : Each Info type is passed trough various status Planned Status : indicates that an object/info type record is proposed but not currently operable. Submitted Status : indicates that an object / info type record has been submitted for review & subsequent approval or rejection. Approved Status : indicates that an object / info type record which has been submitted for review is approved. Rejected Status : indicates that the above record has been rejected. Active Status : indicates that a particular record or info type is currently operable

Personnel actions : A personnel action is a collection of several logically connected info types in the system which, in an exact sequence, are used for processing and are used for a particular system activity. T Code - PA40
Evaluation Paths : An evaluation path is an instruction to the system which determines which object types and relationship(s) are to be included in an evaluation of an organizational plan.

Info Types : A set of data grouped according to subject matter. It aims to enable the user to process employee data in an effective structure in accordance with business requirements. Info types can be identified by their four-digit keys
Subtypes : The categories of information within an info type. Info type 1009 'Health Examinations', for example, has the following subtypes: Health exclusions Health examinations

Features : The objects in the system that determine certain values by querying different personnel and data structure fields in an enterprise.
The values are "return values" or "results." They are used to determine defaults and control certain system processes. In this way, features improve system flexibility.

GENRAL STRUCTURE : you can create object and relationship along selected evaluation paths based on the root object
The evaluation path you choose represents the relationship that will be displayed in the tree structure with the root object. It will define what relationship can be changed and/or create

MATRIX ORGANISATION

n Above is a product-matrix organization. A position or

department reports not only to their line manager but to the manager of the product line.

A matrix organization is a two-dimensional chain of command, in which positions, for example, report to more than one superior

There are three access options for matrix maintenance:

1) Matrix type If you select this option, you choose a predefined matrix type. Matrix types are defined in Customizing. 2) Variant If you select this option, you can choose a matrix view that you previously saved as a variant. 3User-defined/standard selection If you select this option, you access a standard selection screen on which you can define the matrix view you want to work with. You must specify a root object and an evaluation path for each dimension of the matrix and the relationship that will exist between the objects of the two dimensions.

You can then set your access as either the matrix view or one of the two dimensions

Plan versions enable you to administer several organizational plans parallel in the system. Different plan versions can be used to experiment with different scenarios, for simulations and for comparison purposes.

The current plan version is the plan version that is currently being worked on in the system.
When you request reports, the system can extract information only from one plan version. Note: The plan version .: must not be used or deleted since it is used for the transport of plan versions.

OBJECT MAINTANANCE

n In this step, you make the settings required for changing

standard object types and creating new object types. This includes the following system settings: Essential relationship: Relationship type that must be created when you create an object of a particular object type in order for it to be meaningful. External object types: You define the interface program used for reading external object types. Structure search: You define the evaluation path used in the Matchcode structure search for the various object types. You can create two-digit object types in the customer namespace range of 01 to 99.

Time constraints control how objects are related to one another. Time Constraint 1 - Information must exist for the entire life cycle of the object but can be changed. Time Constraint 2 - Information is optional but can exist only once within a user-defined period. Time Constraint 3 - Information is optional, and many data records can exist simultaneously within a user-defined period. Time Constraint 3 dependent on target object type-- Information is optional, and the number of data records that can exist within a userdefined period is dependent on the type of target object. **

 Example of class 1: An object must have a short name stored for it. This information must exist uninterrupted, but can be changed. Example of class 2: A position can have a number of Vacancy infotype records assigned for different periods. Example of class 3: The Sales department can be related with a number of positions simultaneously. Example of class 3 with additional condition: A position can be described by only one job but by a number of tasks.