Showing posts with label Payroll. Show all posts
Showing posts with label Payroll. Show all posts

Sunday, June 10, 2012

Processing class, Evaluation class, Cummulation class


Processing class, Evaluation class, Cummulation class

Processing Class will help the wage type how it should be processed during payroll run. Ex.. U want a particular wage type to be taxed. So u maintain PC 68 & required specification.. Same is the case for other processing classes.... If u want the wage type to be cumulated, u maintain Processing class 30 and required specification...

Cumulations class is for calculation base. Consider following info: • Processing class has specification (maintained at view V_512W_D) • These specification actually defines how the wage type will be processed in a particular Rule. For example: You can query processing class specification in a Rule using operation VWTCL. Based on the return value of this query (based on specification maintained at above view), you can specify one or more operations to be performed in the Rule. These operations will be performed on that particular wage type. • Thus processing class specification actually decides treatment of a wage type during payroll. Please note this is the normal use. It is perfectly possible (but highly improbable in practice) that you write a report that will read processing class from this table and do something on that. •

Cumulation class is slightly different. It specifies that a particular wage type should be part of what "other wage types". • "other wage types" mentioned above have to be one of the cumulation wage types (/1**). • When you select cumulation class "11" for wage type X, you are configuring the system such that during payroll processing wage type X will be added to cumulation wage type /111. • This does not happen automatically. ADDCU operation is responsible to perform this job. Thus, if you perform ADDCU operation on wage type X, you will see wage type /111 increased by amount of wage type X. • As ADDCU is an operation, it needs to be called in a Rule. • As expalined above, Rule performs one or more operations based on processing class specifications. • Thus, to put everything together, you specify processing class of Wage type X such that, in a particular Rule, it will be processed through operation ADDCU. And you mark relevant cumulation class for wage type X. That will ensure that wage type X gets added to those cumulation wage types (relevant for cumulation class).

Evaluation class is completely different. It does not have anything to do with payroll. It is used for reporting purpose. In a report program, system can check for setting of evaluation class specification to decide on how the wage type should be displayed. For example, on Form 16 annexure, system displays various heads of earning (gross salary, perks, IOS and exemptions u/s 10). Here you can specify which particular wage type is perk or exemption based on evaluation class settings. Not only that, even within perks, further break up is possible using evaluation class settings. Processing Class Definition A wage type characteristic that controls processing during Payroll. Use There are different processing classes for the various processing steps that are performed within Payroll. During the payroll run, SAP R/3 processes a wage type in a specific processing step according to its individual specification in the respective processing class Example In the standard system, processing class 15 determines how a wage type is valuated in accordance with the principle of averages. The standard system permits the following specifications, for example, for processing class 15: Specification 1: valuation of averages for 3 months Specification 2: valuation of averages for 6 months Evaluation class Wage type characteristic that controls processing when payroll results are evaluated and displayed. Use There are various evaluation classes for the different processing steps that are performed when payroll results are evaluated and displayed. During an evaluation, SAP R/3 processes a wage type in a specific processing step according to its individual specification in the respective evaluation class. In the standard system, the specifications for evaluation class 02 determine how a wage type is printed on a form. Specification 00: no printing on the form Specification 01: prints personal payments/deductions Specification 02: prints wage types included in the total gross amount Specification 03: prints wage types derived from time-based payments and included in the total gross amount Naming Conventions: The following naming conventions are used for wage types: • /0** – valuation • /1** – cumulation • /2** – averages • /3** – country-specific, usually for social insurance • /4** – country-specific, usually for tax • /5** – legal net • /700 – wage/salary plus ER shares • /8** – period factoring • /84* – cost accounting • /A** – outgoing wage types in retroactive accounting period • /Z** – incoming wage types from the previous period

Another Way of explanation :
Every wagetype has 2 containers in it, 1 container holds the amount and another holds the Number. Processing class are methods to process the 2 fields. Example Employee was on Leave without pay for 5 days, so uwould like to reduce his salary by a prticular factor. Through Pclass 10, u will assign a factor to the wagetype , let's say/801.

U need to attach a formulae to this factor , so in rule INP1 U attach the formulae through which the wagetype get processed. /801 Working Days factor-LWOP RTE=TKSOLL Set RTE-TKAU** Subtraction RTE*KGENAU Multiplication RTE/TKDIVI Division ADDWT * OT Output table. So, you gave a command to the wagetype that whenever there is a LOP the formulae is as said. Similarly you have other processing classes: PClass 30 e.g says Cumulation update that means after the processing of the wagetype, how will the amount get cumulated, or stored, will it get stored as monthly or yearly or fortnightly. If u say pclass 30 specification T- i.e cumulate according to table t54c3 then system will go to t54c3 and find out the type of cumulation and process the wagetype.

Please go through pclasses and wagetypes to see the coomon plclasses that are set for all wagetypes u will get good idea.

Now Cumulation class: Cumulation class means groups into whic wagetype will be categorized, whether it is: Regular income, irregular income or perk or Ptax or PF and so on. Through Cumulation class all wagetypes marked with the cumulation class will come and get stored in 1 bucket and appear as Regular inc...or irregular... simple. Basic pay Reg inc= 2000 HRA=1000 , Both are ticked as CUMCLASS 24 so Total becomes 3000 as monthly reg inc and 3*12=36000 as annaula regular income.

Next Evaluation class : This deals with Where and how should the wagetype appear after getting processed, should it appear in form 16, payslip..or not to be shown. suppose u want a wagetype to appear in form 12ba i.e PERK Then u have to map it in evaluation class 9 Perk, then in form 16 under 12ba u will se the wagetype as Perk. 1. PCLASS - Takes u to formulae to process wt 2.Cum class- Groups the wagetype into similar income components 3. Eval class : Appearance of wagetype. Coming to your scenario: You need to elaborate a lot on this as how is ur org wanting to process. Please take the respective wagetypes, and assign the factor. Please see the INP1 and copy that and make ur factors to proceed.

Thursday, August 12, 2010

Wage Types

Wage types are used to assign payments and deductions as well as to control the payroll program. You need wage types to pay employees.

In the SAP system there are two main categories:

- Primary or dialog wage types
- Secondary or technical wage types
In the standard delivered SAP HR system you can find many sample wage types both dialog (codes starting with letter eg. Mxxx) and technical ones.
Customer defined dialog wage type codes must start with digit.
You can recognize technical wage types as they have a slash (/) as the first character in the code name.
Technical wage types are not part of the employee's master data. System defines their value during payroll processing.
Wage types characteristics can be set under following SPRO path:
Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type
New wage type
To create new wage type you must copy existing one. SAP HR contains model wage types. If these sample wage types meet some of your company's requirements you can use the wage type copier. You then use these copies as your wage types and can modify them so that they meet your specific requirements.
REMEMBER: Customer defined dialog wage type codes must start with digit. The wage types that you create via the copy method are included in all of the wage type groups and tables as the original wage type from which you copied. You can use the log to check what was copied.

Transaction for wage types coping:  OH11 or use SPRO path:

Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Create Wage Type Catalog
 
Permissibility for infotypes You can set up the system so that only certain wage types are permissible for infotypes. You can do this under following SPRO path or using view V_T512Z (transaction SM30):
Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Check Wage Type Catalog -> Check entry permissibility per infotype
 
When you configure a wage type, you can determine whether it can be entered once or more than once per payroll period.

Groupings
 
Personnel subarea groupings can be used for primary wage types to define wage type permissibility. These groups can be used to determine which wage types can be entered for which employees.

There are two types of groupings:

* employee subgroup groupings
* personnel subarea grouping

Two main values for employees subgroup groupings are:
* 1 – for hourly paid employees
* 3 – for monthly paid employees

You define wage type permissibility for each personnel subarea and employee group under SPRO path or using view V_511_B:

Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Check Wage Type Catalog -> Define Wage Type Permissibility for each PS and ESG
Wage Type Characteristics
These characteristics describe way of entering of wage types, but they do not describe how they behave in payroll.

You can define followings:
  • Validity period
  • Operation indicator
  • Minimum and maximum wage type amount
  • Whether or not the wage type amount should be included in the basic pay total
  • Default units of time/measurement, minimum and maximum number
  • Input combinations for number and amount
  • Indirect valuation and its characteristics
You define this under SPRO path or using view V_T511:
Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Check Wage Type Catalog -> Check Wage Type Characteristics
Default Wage Types
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 need to be defined. Feature LGMST has two return values: firstly, the maximum number of enterable wage types in the Basic Pay infotype (IT0008), and secondly, the wage type model the system is to use, which was defied above.
To access feature LGMST use following SPRO path or transaction
PE03: Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Enterprise Structure for Wage Type Model

Valuation of Wage Types
There are two valuation types:
  • DIRECT - the amount used to valuate the wage type is entered in the infotype manually
  • INDIRECT - system automatically calculates the amount of the wage type amount based on simple configuration and enters it in the infotype. You can use indirect valuation for infotypes Basic Pay (0008), Recurring Payments/Deductions (0014), Additional Payments (0015).
How to set indirect valuation
First you need to make appropriate settings in Wage Type Characteristics:
Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Check Wage Type Catalog -> Check Wage Type Characteristics or view V_T511.
Choose the wage type for which you want to use indirect valuation. In the group box Indirect valuation choose the indirect valuation module, which specifies which valuation table is used for indirect valuation. Then specify module variant, which controls read access to the table. To get information about all modules that could be used, use Help pressing F1 on the field Indirect valuation module.
Following are most popular modules:
  • TARIF - uses pay scale data from the pay scale groups and levels to sets the amount of wage type in Basic Pay (IT0008) infotype
  • PRZNT and SUMME - system calculates certain wage types as a percentage (PRZNT) or sum (SUMME) of other wage types
For some modules you need to set how calculation should go. It can be done by simple configuration:
Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Define Valuation of Base Wage Types




Click here to Download SAP HCM - Wage Type PDF material  

Sunday, July 25, 2010

ImportantTransaction Codes - HCM

•    Master Data 


PA10 - Personnel file
PA20 - Display HR Master Data
PA30 - Maintain HR Master Data
PA40 - Personnel Events
PA41 - Change Hiring Data
PA42 - Fast Data Entry for Events
PRMD - Maintain HR Master Data
PRMF - Travel Expenses : Feature TRVFD
PRML - Set Country Grouping via Popup
PRMM - Personnel Events
PRMO - Travel Expenses : Feature TRVCO
PRMP - Travel Expenses : Feature TRVPA
PRMS - Display HR Master Data
PRMT - Update Match code
PS03 - Info type Overview
PS04 - Individual Maintenance of Info types

•    Time Management  

PA51 - Display Time Data
PA53 - Display Time Data
PA61 - Maintain Time Data
PA62 - List Entry of Additional Data
PA63 - Maintain Time Data
PA64 - Calendar Entry
PA70 - Fast Data Entry
PA71 - Fast Entry of Time Data
PBAB - Maintain Vacancy  assignments
PT01 - Create Work Schedule
PT02 - Change Work Schedule
PT03 - Display Work Schedule

•    Payroll 

PC00 - Run Payroll
PC10 - Payroll menu USA
PE00 - Starts Transactions PE01 PE02 PE03
PE01 - Schemas
PE02 - Calculation Rules
PE03 - Features
PE04 - Create functions and Operations
PE51 - HR form editor
PRCA - Payroll Calendar
PRCT - Current Settings
PRCU - Printing checks USA
PRD1 - Create DME
SM31 - Maintain Table
SM12 - Locked Secessions
TSTC - Table Look up
SPRO - IMG
SE16 - Data Browser (Table Reports)
PP03 - PD Tables
PPOM - Change Org Unit
PO13 - Maintain Positions
PO03 - Maintain Jobs
•    Benefits
PA85 - Benefits - Call RPLBEN11
PA86 - Benefits - Call RPLBEN07
PA87 - Benefits - Call RPLBEN09
PA89 - COBRA Administration
PA90 - Benefits Enrollment
PA91 - Benefits - Forms
PA92 - Benefits Tables - Maintain
PA93 - Benefits Tables - Display
PA94 - Benefits - Access Reporting Tree
PA95 - Benefits IMG - Jump to Views
PA96 - Benefits reporting
PA97 - Salary Administration - Matrix
PA98 - Salary Administration
PA99 - Compensation Admin - rel. Changes
PACP - HR-CH : Pension fund, interface

•    General Reporting 
PM00 - Menu for HR Reports
PM01 - Dialogs in HR - Create Custom info types
PRFO - Standard Form
PSVT - Dynamic Tools Menu
PAR1 - Flexible Employee Data
PAR2 - Employee List

•    Organizational Management 

PPOM - Change org Unit
PO03 - Maintain Jobs
P013 - Maintain Position
PO10 - Maintain Organizational Unit
PP01 - Maintain Plan Data (menu-guided)
PP02 - Maintain Plan Data (Open)
PP03 - Maintain Plan Data (Event-guided)
PP05 - Number Ranges
PP06 - Number Ranges Maintenance HR Data
PP07 - Tasks/Descriptions
PP69 - Choose Text for Organizational Unit
PP90 - Setup Organization
PP01 - Change Cost Center Assignment
PP02 - Display Cost Center Assignment
PP03 - Change Reporting Structure
PP04 - Display Reporting Structure
PP05 - Change Object indicators (O/S)
PP06 - Change Object indicators OS
PPOA - Display Menu Interface (with dyn.)
PPOC - Create Organizational Unit
PPOM - Maintain Organizational Plan
PPOS - Display Organizational Plan
PQ01 - Events for Work Center
PQ02 - Events for Training Program
PQ03 - Events for Job
PQ04 - Events for Business Event Type
PQ06 - Local Events
PQ07 - Resource Events
PQ08 - Events for External Person
PQ09 - Events for Business Event Group
PQ10 - Events for Organizational Unit
PQ11 - Events for Qualification
PQ12 - Resource Type Events
PQ13 - Events for Position
PQ14 - Events for Task
PQ15 - Events for Company
PSO5 - PD : Administration Tool
PSOA - Work Center Reporting
PSOC - Job Reporting
PSOG - Org Mgmt General Reporting
PSO1 - Tools Integration PA-PD
PSOO - Organizational Unit Reporting
PSOS - Position Reporting
PSOT - Task Reporting

•    Recruitment

PB10 - Initial Entry of applicant master data
PB20 - Display applicant master data
PB30 - Maintain applicant master data
PB40 - Applicant events
PB50 - Display applicant actions
PB60 - Maintain Applicant Actions
PB80 - Evaluate Vacancies
PBA0 - Evaluate Advertisements
PBA1 - Applicant Index
PBA2 - List of applications
PBA3 - Applicant vacancy assignment list
PBA4 - Receipt of application