OM Q n As

Q. Difference between Org assignment and Org Plan.

A. Organizational assignment is assigning the persons i.e., employees, to certain positions according to organizational structure and plan.

Org plan is defining the org structure in the system via PPOME, PO10, PPOC_OLD, PP01.

Q. Is it possible to create multiple org plans?

A. It is possible to create more than one root organizational unit, that is, more than one organizational structure in a plan version. However, as a rule, a plan version contains one organizational structure, that is, one root organizational unit. 

Q. How does any company use an organizational plan?
A. The company organization structure and reporting structure is represented through the organization plan. The active plan version is the current plan version and the other plan versions are considered as various planning stages.Used for manpower planning. Normally plan version"01" is always made the active plan version.

Q. What is Reporting Structure?

A. Reporting structure defines the reporting hierarchy in SAP. e.g., which position, that is who is reporting to whom. 

Q. Difference between Job and Position?
A. Job is not concrete, it is general object holding various task to perform.(Eg: Manager, GM).
Position is concrete and specific which are occupied by Persons. (Eg: Manager - HR, GM - HR).

Q. What do you mean by a Task? Where do you assign and how?

A. Tasks are the work to be performed by the employee. We can assign task to job or position which finally inherits to the holder that is employee.  

Q. What is the difference between an organizational unit and a work center?
A.  Organizational Unit: Object type 'O ’

• Organizational units are units of your company that perform a function. According to how tasks are allocated in your company, these can be departments, groups or project teams, for example. 
• Organizational units are not the same as other enterprise units, such as personnel area, company code
  and so on. These are used to model structures in Personnel Administration or Payroll Accounting, for
  example.
• You create the organizational structure of your company by relating organizational units to one another. These relationships may be in the form of a hierarchy or a matrix. 
• This organizational structure is then the basis for the creation of an organizational plan.

Work Center: Object type 'A '

• Work centers are the specific physical locations where tasks are carried out.
• A work center can represent anything as general as a geographical location, such as the Philadelphia branch office, or they can be very precisely defined, such as a particular workstation with specific equipment in a specific building (this may make sense in a factory, or plant, for example). 
• Several positions may share one work center. For example, the reception desk may be shared by a number of different employees during the day working different shifts. 
• When you have created work centers, you describe their attributes, such as certain health requirements or physical restrictions limiting the group of employees that may work there. You may define restrictions or you might specify certain examinations that have to be completed at regular intervals

Q. If we have to create multiple positions, what method or tool we can use to avoid errors due to creating them manually?

A. We can create multiple positions by LSMW or batch programs for the Tcode PP01 or PPOCE

Q. Are cost center assignments hierarchical? Where do you assign these in OM?
A. Cost center assignments are hierarchical. You assign these in the account assignment for OM objects. If your org unit in the lower hierarchy does not have a cost center assignment , than it will be assigned the cost center of the upper hierarchical org unit till one is found. For a position, if the cost center is not assigned, it will be assigned the cost center of the org unit to which the position belongs and if not found here, than it will be assigned the cost centre of the upper hierarchical org unit till one is found. These assignments can be overridden by the cost distribution (IT 0027).

Q. What is Expert Mode used for? 
A. The Expert Mode (PP01) is an interface that is ideal for maintaining details. Individual objects are selected using the Object Manager. Infotypes for that particular object can now be maintained.

Q. Can you create cost centers in Expert Mode?
A. Cost centers are the external objects, which will be created by the Finance person. We are assigning the Cost center either to Org unit or to Position. So, you can't create it in Expert Mode.

Q. Can you assign people to jobs in Expert Mode?
A. No. People (Person object - P) cannot be directly assigned to jobs. Instead persons are holders of a position which is described by job.

Q. What are the main areas of the Organization and Staffing user interfaces?
A. Below are the main areas of Org and staffing interface:

• Search Area
• Selection Area
• Overview Area: View the Organizational Unit Hierarchy or Staffing assignments of an Organizational Unit.
• Detail Area: Maintain object characteristics and attributes.

Q. Can you use the organizational structure to create a matrix organization?
A. Yes. You create the organizational structure of your company by relating organizational units to one another. These relationships may be in the form of a hierarchy or a matrix.

Q.In general structure maintenance, is it possible to represent the legal entity of organizational units?
A. Yes

Q. Which status can Infotypes in the Organizational Management component have?
A. Every infotype is assigned a status:

• Active status indicates that an object or infotype record is currently operable.
• Planned status indicates that an object or infotype record is proposed, but not currently operable.
• Submitted status indicates that an object or infotype record has been submitted for review and subsequent approval/rejection, by a person or group of persons at your firm.
• Approved status indicates that an object or infotype record, which has previously been submitted for review, is accepted or authorized.
• Rejected status indicates that an object or infotype record, which has previously been submitted for review, is rejected or turned down.

Q. What is status feature in OM?
A. The status feature allows the object to go through a status cycle to eventually be accepted or rejected.

• Objects can be created in either planned or active status.
• You must assign a status to every object or infotype record that you create. You do not, however have to use all the statuses. Many users use only the active status.
• The report RHAKTI00 lets you change the status of several objects at the same time.

Q. What is the Relationships Infotype (1001) used for / Where can you maintain relationships between objects ?
A. IT1001 Relationship is used to relate the two objects, for example, Cost Center is assigned to Position.

Q. Is it possible to set up new evaluation paths in Customizing? / Which situations require new evaluation paths?
A. Yes. The standard SAP evaluation paths may not satisfy your data reporting or evaluation requirements. Creation of new evaluation paths may be necessary. For ex, you have defined new objects and want to carry out evaluations for them in conjunction with object types that already exist.

You also need new evaluation paths if you are modifying existing evaluation paths, by selecting a "Skip" field, for example.

Copy the evaluation path into the customer name space (beginning with "Y" or "Z") and enter an evaluation path. These must be alphanumeric and have a- maximum of eight digits. They must begin with the letter "Z".

Q How to access HRP1000 table ?
A. HRP1000 can be accessed through Transaction Code:SE16.

Q. Reports in relation to PA – OM Integration / How do you transfer data from PA to PD?
A. During an SAP implementation, conversion program will occur to load OM and PA data separatedly as their own infotypes / objects. But there is a missing connection between OM / PA through relationships and other tables that might not get loaded via conversion. With that, we have several RHINTE programs to assist in this matter. You can access it via SE38 transaction code.

• RHINTE00 - Transfer data from PA to PD: It creates the HRP1001 between P to S in the OM side of the world. When you view a record via IT0001, you see this person holds the position, however via HRP1001, that relationship isn't so.Thus, it loops through all employees in PA by looking at positions on infotype 0001. It checks the corresponding person to position relationship exists in PD (A008), if not it is created.
  
• RHINTE10 - Generates the required relevant tables. (T513 - Jobs, T513S - Jobs, T528B - Positions, T528T - Work Center, T527X - Org Unit

Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. The main difference with this program as opposed to RHINTE20 is that this one has the option to delete items from the PA tables, which no longer exist in PD.

• RHINTE20 - checks for all objects for integration between PA and OM. This is a big one and will take awhile to run. What it does is look at table T513/T513T - Jobs, T528/T528T - Position, and T528X - Org Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any missing objects, it will create the record. 

This program loops through the PD table HRP1000. For each job, position, work centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also.

• RHINTE30 - Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001 during the inital conversion load. RHINTE30 will find the relationship and push it through IT0001.

This will create an infotype 0001 record with correct entries for org unit, job, position and work centre by looking through the organization structure. It creates a batch job, which must be run via SM35.

Q. What is Managers Desktop used for?
A. SAP Manager´s Desktop meets the daily requirements of managers and supports both the administrative - organizational and planning tasks.

• Manager’s Desktop supports managers in making personnel decisions and devising strategic plans in that it allows them to quickly access direct and indirect subordinate employees’ personal data and to evaluate this data.
• Wide function area, tailored to managerial tasks (e.g. functions from different components, workflow inbox, Internet connection, etc.)
• Easy, intuitive operation 
• Exact tailoring of necessary functions possible with customizing and user-specific settings 
• Possible to include customer-specific reporting