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

PY Q n As Set 1

Q. What are the mandatory modules for HR to implement SAP Payroll ?
A. PA / OM / Time Management (basic) 

Q. What is the personnel subarea grouping for primary wage types used for?
A. You can use these groupings to specify which wage types may be entered for which personnel subareas.

Q.  What is the employee subgroup grouping for primary wage types used for?

A. You can use these groupings to specify which wage types may be entered for which employee subgroups.

Q. Permissible check for wage type is performed for each
A. EE subgroup grouping and PSA grouping

Q. Which criteria determine payroll accounting areas?

A. The payroll accounting area  is determined according to the HR country grouping, the employee group and the employee subgroup.

Q. Is there a way to define default values for the pay scale area and pay scale type?

A. Via TARIF feature. The return value must have the form xx/yy, when xx is the pay scale type, and yy the pay scale area. 

Q. Is there a way to define default values for the pay scale group and pay scale level ?

A. Pay scale group and levels can only be defaulted through ABAP development. There is no standard feature to default payscale group and level.

Q. In which tables Payroll constant will be stored & through which T-Code you are able to view the records?
A. Payroll constants are stored under tables T511K which can be accessed via SM30.

Q. Through which T-Code you are able to create a remuneration statement?
A. PC00_Mxx_CEDT (xx - denotes the molga for a country)

Q. What is the employee subgroup grouping for collective agreement provisions used for?

A. The collective agreement provisions grouping is required for indirect valuation of wage types in the Basic Pay infotype (0008).

Q. Can all wage types be entered into all Infotypes?

A. No. All wage types are not permissible for all infotypes (refer wage type groups concept). Wage types are permitted to be stored in payroll infotypes only if these are added to the wage type groups.  Eg Basic Pay IT0008 has wage type group 0008.

Q. What does the input permissibility of a wage type depend upon?

A. Input permissibility of a wage type depends on  the wage type grouping and wage type characteristics. The wage type characteristics are attributes of the wage type that determine as to what is permissible and not permissible, what are the maximum and minimum value limits , what are the units permissible, whether they are to be valuated directly (values entered) or indirectly (values as a reference to other wage type values).

Q. How can you define default wage types for the Basic Pay Infotype?

A. The system can suggest a default wage type for basic pay (IT0008), to do this appropriate wage type must be included in a wage type model. Here you define the default wage types and the sequence how they should appear in the infotype Basic Pay and whether you can overwrite the defaulted wage type or not. 

Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Revise Default Wage Types

After setting wage type model, LGMST feature needs to be defined. Feature LGMST has two return values: firstly, the maximum number of wage types that can be entered in the Basic Pay infotype (IT0008), and secondly, the wage type model the system is to use, which was defined above.

To access feature LGMST use following SPRO path or transaction PE03.

SPRO: Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Enterprise Structure for Wage Type Model

Q. In which feature, default wage type is defined for Basic Pay Infotype?
A LGMST

Q. How does the system know when to trigger retroactive accounting for a particular employee?

A.Retroactive accounting recognition consists of four steps:

• If you edit an infotype that is relevant to retroactive accounting, the system enters the start date of the changed infotype record in the following fields of infotype 0003 Payroll Status:
• Earliest MD change (earliest master data change since last payroll run)
• MD chng.bonus (earliest payroll-relevant master data change (bonus)). This field is only displayed for specific country groupings, it is not displayed for all personnel numbers.

• During the next regular payroll run or correction run (off-cycle payroll type B), the system determines whether the date in the Earliest MD change and (if applicable) MD chng.bonus fields comes before the date in the Accounted to field.
• If this is the case, the system performs retroactive accounting. It starts with the payroll period in which the date entered in the Earliest MD change and MD chng.bonus fields occurs. The system recalculates all payroll periods that lie between the date in the Earliest MD change and MD chng.bonus fields and the date in the Accounted to field.
• The system deletes the date in the Earliest MD change and MD chng.bonus fields 

Q. How is the earliest retroactive accounting date determined for an employee?

A. The system uses the following values to determine the retroactive accounting limit:

• For each payroll area, the system uses the earliest possible retroactive accounting period that is stored in the corresponding payroll control record
• For each employee, the system uses the earliest personal retroactive accounting date that is stored in the Payroll Status infotype (0003)
• For each employee, the system uses the hiring date of the employee The system uses these values to select the most recent date.

Q. What activities are possible when the payroll control record is set to “Released for Payroll”?

A. If you choose the function Release Payroll from the menu, you are prevented from changing infotype data records if such changes affect the past or present. This lock applies to the personnel numbers included in the payroll area concerned. Changes that affect the future are still permitted. You must execute this function in the menu before starting the payroll. If the status of the payroll control record was previously Exit Payroll, the Release Payroll function also has the effect of increasing the period in the payroll control record by 1.

Q. Can a posting run be deleted?

A. Yes It can be reversed before the Bank transfer.Once the transfer is done the payments need to be adjusted in the next payments.

Q. Where are payroll results stored?

A. Payroll results are stored in PCL2 cluster, which can be accessed using the transaction pc_payresult.

Q. Account assignment type characteristic used in SAP HR

A. The account assignment type of the symbolic account determines:

-The type of posting (for example, posting to expense accounts, debit posting, credit posting) and the process that the system uses in table T030 (Standard Account Table) to search for the assigned account in Accounting

-Which information the system should transfer to Accounting and from which table in the payroll result this information should be taken

Example: The wage types Basic pay and Overtime both represent personnel costs and should therefore be posted to expense accounts. You also want to assign these wage type amounts to Cost Accounting objects. Both wage types are dealt with in the same way as far as posting is concerned and can therefore be posted to the same symbolic account. You must specify the account assignment type C, since, in Accounting, there should be a posting to expense accounts and Cost Accounting should be provided with information.

Q. Where do you specify whether an employee is paid in cash or whether the money is transferred to a bank account?

A. IT 0009 (Bank Details )

Q. Is it possible to branch directly from the payroll log to master data and time data maintenance?

A. Yes. To some extent.

Q. Difference between PCR and CAP?
A. Difference between PCR and CAP is mentioned below:

PCR - The Personnel Calculation rule allows how one wage type is to be processed in different ways in payroll accounting

CAP - CAP is Collective Agreement Provision based on which the different groups of Employees are eligible for different kinds of pay scale structures and benefits and so on. CAP is based on the following components :
1) Pay scale type
2) Pay scale area
3) Employee subgroup grouping for CAP
4) Pay Scale Group and Pay Scale Level

An employee subgroup grouping for collective agreement provisions combines subgroups which are governed by the same valid collective agreement provisions. A provision is a specific labor law regulation within the collective agreement.

Q. PCRs and Employee Subgroup Grouping
A. A personnel calculation rule can consist of several subareas, each of which is characterized by an employee subgroup grouping for personnel calculation rules, a wage type, and a time type. An index function provides an overview, and enables you to switch from one section to another as well as delete individual subareas.

To facilitate differential processing, each employee subgroup must be assigned to a grouping for a personnel calculation rule. Each grouping is defined by SAP and, in this case, can have its own area depending on the personnel calculation rule.

Q. What are the Characteristics of a wage type?
A. These characteristics describe entering of wage types and not how they behave in payroll.

Example

• · You want to define a maximum wage type amount of $1000 and a minimum of $10.
• · The maximum wage type number may be 100, the minimum 1.
• · The wage type amount should not be included in the totals line of basic pay.
• · You must enter a wage type amount.
• · You should only be able to enter the number for a wage type.
• · You want to set certain units of time and measurement for the number.
• · You want to set certain units of time and measurement for the number.
• · Wage types should be valuated indirectly.

Q. What is the remuneration Infotype used for?
A. The Employee Remuneration Information infotype (2010) describes the possible entries for different wage types. You can enter a variety of information for wage types in this infotype which is then processed accordingly during payroll.

In this infotype you can enter the following in combination with a wage type:

• · a valuation basis entered simultaneously with the wage type
• · extra pay for the valuation basis of the wage type still to be determined in payroll
• · a premium indicator
• · an overtime compensation type. 

Q. Naming convention for wage types
A. The following naming conventions are used for wage types:

• /0** – valuation bases
• /1** – cumulation of gross amount
• /2** – averages 
• /3** – country-specific, usually for social insurance 
• /4** – country-specific, usually for tax 
• /5** – legal net 
• /7** – wage/salary plus ER shares
• /8** –  factoring 
• /84* – cost accounting
• /A** – outgoing wage types in retroactive accounting period
• /Z** – incoming wage types from the previous period 

Q. Briefly explain the two different ways to perform pay increase? In dynamic pay increase what are variants A, G, D, E, T , C and R?
A. The two ways are:
1.Simple pay scale increase using report RPU51000 which increases the wage types in customizing
2. Standard pay scale increase where the wage types entered in IT0008 can be automatically increased and the history of the wage types in IT0008 are also updated.

Only one variant can be defined for a wage type. You need to maintain table V_T510D in the customizing and run the program RPITRF00 to carry out the standard pay scale increase.

Make sure that you test your configuration and the execution of the report RPITRF00 only in the test system, run payroll test cases and take user acceptance before transporting these changes to the Production. It is highly recommended that you always do this in the supervision of a senior consultant with good sap payroll experience.

Variant A	Increases a wage type in IT0008 to an absolute amount
Variant G	Increase total pay in IT0008 to an absolute amount
Variant D	Increase by a difference by value or percentage.
Variant E	Valuate according to another pay scale group
Variant T	Add a new wage type to IT0008
Variant C	Delimit an existing wage type in IT0008
Variant R	Replace one wage type by another in IT0008