SAP Configuration, SAP HANA Training

Organizational Plan: 
An organizational plan consists of organizational structure and the relationships that exist amongst them. Its main elements are Organization Structure, Staff Assignment, Reporting Structure, Job Index, Work Centre Plan and Task Catalogue. 
Note : Organizational Plan represents functional structure of the organization. 
 
Plan Versions: 
Plan versions are scenarios in which organizational plans are created. An organization can have multiple plan versions but only one plan version would be active at one point of time. 
Note : 
Current organizational plan is always created under ‘Active’ plan version. 
Note : 
Report - RHCOPL00 copies objects from one plan version to another. 
Note : 
Report - RHCOPLPT compares one plan version with another. 
 
Organizational Assignment: 
Organizational Assignment (also known as Staff assignment) is assigning the persons to positions according to organizational structure and plan. 
 
Organizational Structure: 
An Organizational Structure means the way various organizational objects/elements are placed in the organization. It is a hierarchy of organizational units. 
 
Note : Organization Structures are created via 5 ways viz. Organizational Staffing, General Structure, Matrix, Expert Mode and Simple Maintenance. 
Organizational Structure consists of various organizational objects/elements viz. Department (Organizational Unit) - O, Jobs - C, Positions - S, Cost Center - K, Person - P, Work Centre - A and Task - T. 
 
Organizational Units - O : 
Organizational units are functional units. Based on the requirement of the company, organizational unit could be ‘Departments’ or ‘Groups’ or ‘Teams’. Organizational Structure of the company is created by relating organizational units to one another. 
Main/Root Organizational Unit - O : Whatever the organization we create for the first time is called Main/Root organizational unit. 
Sub Organizational Units - O : Under Main org. unit whatever we create is called sub organizational units. 
 
Jobs - C : 
Jobs are classifications of functions in an enterprise. E.g. Manager , Engineer , Consultant, Secretary etc. 
Job describes the position i.e. it is the basis for the creation of position. 
 
Positions - S : 
Position is the post held by an employee or user in an enterprise. E.g. HR Manager, Production Engineer etc. 
Positions are created on the basis of jobs. Without a job we can’t create a Position. 
<table border="0" cellpadding="0" cellspacing="0"><tbody>
<tr> <td valign="bottom" width="79">Job</td> <td valign="bottom" width="421">Position</td> </tr>
<tr> <td valign="bottom" width="79">Manager</td> <td valign="bottom" width="143">HR Manager</td> <td valign="bottom" width="131">Sales Manager</td> <td valign="bottom" width="146">Payroll Manager</td> </tr>
<tr> <td valign="bottom" width="79">Engineer</td> <td valign="bottom" width="143">Production Engineer</td> <td valign="bottom" width="131">Software Engineer</td> <td valign="bottom" width="146">Mechanical Engineer</td> </tr>
<tr> <td valign="bottom" width="79">Consultant</td> <td valign="bottom" width="143">HR Consultant</td> <td valign="bottom" width="131">FI Consultant</td> <td valign="bottom" width="146">SD Consultant</td> </tr>
</tbody></table>
 
Note : From one Job we can create multiple Positions. But it is not possible to create multiple Jobs from one Position. 
Note : 
It is always correct to have 1:1 relationship between Position and Person so that relationships work properly. For e.g. For 5 supervisors in production department there should be 5 distinct positions in SAP. 
However, at lower employee levels (Workers/Labors) multiple employees could be hired against one single position. 
Note : 
Positions could be 100% filled, partially filled or kept vacant. 
Note : 
An employee can share two or more than two positions at a time. The sharing is based on percentage. 
Note : 
In the absence of position in the system, hiring action can take place. On performing the hiring action in this case, system hires the employee against default position no. 99999999. Once the actual position gets created into the system the employee gets assigned to this new position through ‘change in position’ action. 
Note : 
On separation the position assigned to employee gets delimited and gets replaced by default position (99999999). 
 
Cost Centers - K : 
Cost Center or Master Cost Center is an area where costs are incurred. It is maintained in financial accounting and further assigned to either Organizational Units (Department) or Positions. 
Note : Only costs are collected in cost center and not company revenues. 
Note : If root department is assigned to a cost center then all the sub-departments inherits the same cost center. 
Note : If primary cost is allocated to different cost centers, then it is known as ‘Distribution of Costs’. It is done by maintaining info type 0027 (Cost Distribution) in PA module. 
 
Persons - P : 
A Person is generally an employee in the company who holds a position. 
 
Task - T: 
Task is a description of activities to be performed under a particular job for a particular position in the organizational structure. 
 
Work centers - A : 
Work centers describe the physical (geographical) locations where tasks are performed. 
Functional Reporting and Line Reporting: 
Functional Reporting means a person reporting to the manager of department where he performs his additional task. 
Line Reporting means a person reporting to his departmental head. 
For e.g. a person belongs to electronics department but can also perform the task related to electricity department. His reporting to the head of electrical department would be termed as Functional Reporting, whereas his reporting to his own departmental head (Electronics) would be termed as Line Reporting. 
 
 
Matrix Structure: 
The matrix organization represents a two-dimensional hierarchy. This is based on positions reporting to more than one superior organizational object. Matrix Organization is used for dual reporting. 
Maintain the relationships in table T779M. To do this mention relationship name along with dimensions. For each dimension you have to give object type and the evaluation path.(e.g. O-O-S , O-O-S-P, O-S-P, O-O-VACS etc depending upon the matrix you want to maintain) 
Through T. Code PPME the relation maintained in table T779M could be viewed. 
 
Relationship and Evaluation Path: 
- Relationship is the logical association between any two objects. 
- Evaluation Path is the chain of multiple relationships. It describes the tree structure created in OM and 
relationship formed amongst different objects involved. 
 
 
Relationships (Table T778V): 
Some of the commonly used relationships are as below. 
<table border="0" cellpadding="0" cellspacing="0"><tbody>
<tr> <td valign="bottom" width="186">Relationship</td> <td valign="bottom" width="350">Example</td> </tr>
<tr> <td valign="bottom" width="49">A002</td> <td valign="bottom" width="137">Reports (line) to</td> <td valign="bottom" width="350">Sub-department reports to Root department.</td> </tr>
<tr> <td valign="bottom" width="49">B002</td> <td valign="bottom" width="137">Is line supervisor of</td> <td valign="bottom" width="350">Root department is line supervisor of Sub-department.</td> </tr>
<tr> <td valign="bottom" width="49">A003</td> <td valign="bottom" width="137">Belongs to</td> <td valign="bottom" width="350">Position belongs to Department.</td> </tr>
<tr> <td valign="bottom" width="49">B003</td> <td valign="bottom" width="137">Incorporates</td> <td valign="bottom" width="350">Department incorporates Position.</td> </tr>
<tr> <td valign="bottom" width="49">A007</td> <td valign="bottom" width="137">Describes</td> <td valign="bottom" width="350">Job describes Position.</td> </tr>
<tr> <td valign="bottom" width="49">B007</td> <td valign="bottom" width="137">Is described by </td> <td valign="bottom" width="350">Position is described by Job.</td> </tr>
<tr> <td valign="bottom" width="49">A008</td> <td valign="bottom" width="137">Holder</td> <td valign="bottom" width="350">Person holds of Position.</td> </tr>
<tr> <td valign="bottom" width="49">B008</td> <td valign="bottom" width="137">Holder</td> <td valign="bottom" width="350">Position is holder of Person.</td> </tr>
<tr> <td valign="bottom" width="49">A012</td> <td valign="bottom" width="137">Manages</td> <td valign="bottom" width="350">Chief manages Position.</td> </tr>
<tr> <td valign="bottom" width="49">B012</td> <td valign="bottom" width="137">Is managed by</td> <td valign="bottom" width="350">Position is managed by Chief.</td> </tr>
</tbody></table>
 
 
Commonly used Info types: (Range of OM info types is 1000 - 1999). Commonly used are stated below: 
1000 - Object 1001 - Relationship 
1002 - Description 1007 - Vacancy 
 
Commonly used Transaction Codes: 
Organization & Staffing: 
PPOCE - Create Organization Structure PPOME - Change Organization Structure 
PPOSE - Display Organization Structure 
Expert Mode: 
PO10 - Create Organizational Unit PO03 - Create Job 
PO13 - Create Position PO01 - Create Work Centre 
PP01 - General 
Simple Maintenance: 
PPOC_OLD - Create Org. Structure PPOM_OLD - Change Org. Structure 
PPOS_OLD - Display Org. Structure 
OM Actions: 
PQ03 - Create Job PQ10 - Create Department 
PQ13 - Create Position

Organizational Management SAP HCM

Organizational Plan: An organizational plan consists of organizational structure and the relationships that exist amongst them. Its main e...

In SAP data is locked by the system while it is being edited by a user. Which prevents other users changing the record at the same time. In some cases the lock entries will exist in the system due to system failure. The lock entries can be removed manually from the system by following transaction code SM12 1) Enter the transaction code SM12 in command field and press enter 2) Enter the relevant parameter provided and click the list button <a href="http://lh3.googleusercontent.com/-Pee8TGadiTE/VVtB9DUQRsI/AAAAAAAAB-k/Bexf4mfBY5I/s1600-h/SM12-%2525201%25255B12%25255D.jpg"><img alt="SM12- 1" border="0" height="217" src="http://lh3.googleusercontent.com/-4lIZO94Ugfk/VVtB-EdMsrI/AAAAAAAAB-s/qPYpaP5BRrU/SM12-%2525201_thumb%25255B7%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12- 1" width="644" /></a> 3) Analyze the lock entries and if any previous date entries exist in the system. It has to be cleared by manually deleting <a href="http://lh3.googleusercontent.com/-YQ30V_7AtZc/VVtB_OQP_8I/AAAAAAAAB-0/E8Ps3geLDj4/s1600-h/SM12-2%25255B3%25255D.jpg"><img alt="SM12-2" border="0" height="196" src="http://lh3.googleusercontent.com/-yJ6cvlLAsQ8/VVtCAa3npFI/AAAAAAAAB-8/v4IgllfUj-Q/SM12-2_thumb%25255B1%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12-2" width="644" /></a> 4) Double click on the lock entry and list the detail view for further details. <a href="http://lh3.googleusercontent.com/-Y86CJq-VjeE/VVtCBC35y2I/AAAAAAAAB_E/MKtObLC7ecc/s1600-h/SM12-3%25255B3%25255D.jpg"><img alt="SM12-3" border="0" height="482" src="http://lh3.googleusercontent.com/-rNn7k4I3Q8o/VVtCCCFbO0I/AAAAAAAAB_M/OpA3sNUVjmM/SM12-3_thumb%25255B1%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12-3" width="631" /></a> 5) To delete the lock entries select the entry and press delete button as shown below. <a href="http://lh3.googleusercontent.com/-wcw0n25fK3g/VVtCC6gBHTI/AAAAAAAAB_U/x7Pd1-muzv8/s1600-h/SM12-4%25255B3%25255D.jpg"><img alt="SM12-4" border="0" height="272" src="http://lh3.googleusercontent.com/-LW6_JJdJacA/VVtCD1aZ92I/AAAAAAAAB_c/1MuD_iOjHCg/SM12-4_thumb%25255B1%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12-4" width="1028" /></a> <a href="http://lh3.googleusercontent.com/-YXFgR7uN_y4/VVtCE0m_pxI/AAAAAAAAB_k/h48X7Z-XAgg/s1600-h/SM12-5%25255B3%25255D.jpg"><img alt="SM12-5" border="0" height="321" src="http://lh3.googleusercontent.com/-_XaJfVN2fSc/VVtCFwNrxCI/AAAAAAAAB_s/PbKd6sw2Hr0/SM12-5_thumb%25255B1%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12-5" width="644" /></a> In the dialog box choose yes to confirm and the lock entry will be released with the following message. <a href="http://lh3.googleusercontent.com/-voujonwqA2k/VVtCG7o-2aI/AAAAAAAAB_0/UvfeFXLSS74/s1600-h/SM12-6%25255B3%25255D.jpg"><img alt="SM12-6" border="0" height="263" src="http://lh3.googleusercontent.com/-YEAthH2l6bw/VVtCHwAbNfI/AAAAAAAAB_8/xakC8gM3Ihs/SM12-6_thumb%25255B1%25255D.jpg?imgmax=800" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" title="SM12-6" width="644" /></a>

Deleting Lock Entries in SAP

In SAP data is locked by the system while it is being edited by a user. Which prevents other users changing the record at the same time....

SAP Configuration, SAP HANA Training

Organizational Management SAP HCM

Deleting Lock Entries in SAP

Blog Archive

Labels

Popular Posts