Vous êtes sur la page 1sur 48

PAYROLL CLASS 09.01.2012. RECURRING PAYMENTS AND DEDUCTIONS: 1.

SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>Define Reasons for Recurring Payments and Deduc tions New Entries: Reason Reason text 22 Test Reason 2. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Create Wagetpe Catalogue Here we can find the benefits wage types that are discussed earlier. The benefi ts can also be deducted from 014. New Entries All Model wage types starts with M***. Copy the below wage types. M114 M115 M116 M200 M210 M212 8301 8302 8303 3351 3352 3353

All the wage types configured are copied now. 3. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Check Wage type group recurring p ayments and deductions. Here we need to check whether the specified wage types are available in this tal e or not. If the copied value is not available in this table then we need to go to new entries and create the record. 4. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Check Wage type Catalogue=> Check Wage Text: Table: V_512W_T Here we need to check and if required we can change the wage type text, start da te and end date of the wage type. In this table we can also delimit the wage type and deletion is not usally recom mended. 5. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Check Wage type Catalogue=> Check Entry permissibility per infotype

Table: Here we need to check whether the defined wage types are copied into this table and if not available then we need to create that entry in this table. Wage Type Times 8301 8302 8303 8351 8352 8353 Wagetype Text Start Date 01.01.1900 01.01.1900 01.01.1900 01.01.1900 01.01.1900 01.01.1900 End Date 31.12.9999 31.12.9999 31.12.9999 31.12.9999 31.12.9999 31.12.9999 Once X X X X X X Several

Once = Time constratint is 1. Only one entry for the complete duration, Several = Time Constrating is 2. More than one record could exist with no gaps for the same wage type. 6. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Check Wage type Catalogue=> Defin e Wagetype permissibily for each ES and PSG EE Subgroup Grouping Applicable for which employee subgroup grouping that we configured in basic pay configuration. PSG Grouping Applicable for which Personnel Subarea grouping that we configured in basic pay configuration. 7. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>WAGE TYPES => Check Wage type Catalogue=> Check Wagetype Characteristics Table: T511 Select wage type and double cick on the wage type 8301 (Uniform Allowance). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. If we don't check this box then the value will be added but not shown in 000 8 under payments and deductions tab in 0008 infotype. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination: Amount Number/Unit = + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl

e. Select wage type and double cick on the wage type 8302 (Equippement Allowance). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. If we don't check this box then the value will be added but not shown in 000 8 under payments and deductions tab in 0008 infotype. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination: Amount Number/Unit = + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl e. Select wage type and double cick on the wage type 8303 (Car Allowance). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. If we don't check this box then the value will be added but not shown in 000 8 under payments and deductions tab in 0008 infotype. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination: Amount Number/Unit = + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl e. Select wage type and double cick on the wage type 8351 (Charitable deduction). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. Here if we ceck both add to total and deduction, then system will show this wage type in 0008 and consider this as a deduction by showing an indication A be side the amount. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination:

Amount Number/Unit

= + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl e. Select wage type and double cick on the wage type 8352 (). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. Here if we ceck both add to total and deduction, then system will show this wage type in 0008 and consider this as a deduction by showing an indication A be side the amount. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination: Amount Number/Unit = + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl e. Select wage type and double cick on the wage type 8353 (Cafteria Dedction deduct ion). If we select Add To Total, then amount will be displayed in 0008 as salary amoun t. Here if we ceck both add to total and deduction, then system will show this wage type in 0008 and consider this as a deduction by showing an indication A be side the amount. The check is not mandaory its based on clients requiremnet. Number/Unit: Uniform Allowance so no entry should be there in this field. Input combination: Amount Number/Unit = + = -

Here amount is Mandatory. Indirect Valuation: This is a direct wage type so no indirect evavluation is req uired. Rewriteable: X , When a new record is created this amount should be rewriteabl e. PAYMENT MODELS:

We can use the payment model both for Payments as well deductions. 1. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>PAYMENT MODELS => Define Payment Models => Defi nePeriodicities New Entries: Model Text 1212 Monthy 1313 Weekly Name Name of period parameter Quarterly Payment Model Y (Year) Every Last Week of the Period Y (Year) Date Modifier Name 01 Annually Annually Period Paramater 01 03

only if T549Q is generated for all payroll periods the system can understand the above table entires. 2. SPRO=> PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION => PAYROLL DATA => RE CURRING PAYMENTS AND DEDUCTIONS=>PAYMENT MODELS => Define Deduction Periods select payment model: 1212 Start Date:2007 End Date:2014 New Entries: Payment model Period parameter Payment Period: X-MARCH X-JUNE X-SEPTEMBER X-DECEMBER There will an error populate an error to have entry in T549Z as a prerequisite f or this table. Navigation for T549Z in SAP IMG node is SPRO => PAYROLL => PAYROLL USA => DEDUCTIONS => DEDUCTION FREQUENCIES => GENERAT E CALENDAR FOR PAYMENT MODEL PERIOD PARAMETER DATE MODIFIER INITIAL YEAR END YEAR START DATE OF FISCAL YEAR DETERMINE PEROD NUMBER 01 01 2007 2014 0101 (1ST JANUARY) 1 1212 01 Quarterly payment model Monthly

It is similar to Generate payroll period but only two fields are missing in comp arision.

Select the check box carry out the table change to do the live run of generate p ayroll period for payment model. select payment model: 1313 The number of weeks in every month are not same so we need to select the week on which the payment has to be done in any specific month. Prerequisites: We need to generate Holiday calendar, Work schedules, payroll mo del period, This generation will happen only once every year so every year this activity need to be done. Start Date:2010 End Date:2010 New Entries: Payment model Period parameter 1313 03 Quarterly payment model Weekly

sELECT THE TAB LAST TO ENABLE SYSTEM AUTOMATICALLY PAY IN THE LAST WEEK OF EVER Y MONTH. SELECT THE TABL FIRST TO ENABLE SYSTEM AUTOMATICALLY PAY IN THE FIRST WEEK OF EV ER MONTH. INFO: FOR FSA ALSO WE NEED TO SELECT SIMILAR CONFIGURATION IN BENEFITS CONFIGUR ATION BASED ON THE NUMBER OF WEEKS FOR THE NUMBER OF DEDUCTIONS. Payment Period: MONTH JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC W1 W2 W3 W4 X X X X X X X X X W5

There will an error populate an error to have entry in T549Z as a prerequisite f or this table. Navigation for T549Z in SAP IMG node is SPRO => PAYROLL => PAYROLL USA => DEDUCTIONS => DEDUCTION FREQUENCIES => GENERAT E CALENDAR FOR PAYMENT MODEL PERIOD PARAMETER DATE MODIFIER INITIAL YEAR END YEAR START DATE OF FISCAL YEAR 01 01 2007 2014 0101 (1ST JANUARY)

DETERMINE PEROD NUMBER

It is similar to Generate payroll period but only two fields are missing in comp arision. Select the check box carry out the table change to do the live run of generate p ayroll period for payment model. In 0014 infotype we have field for 1st payment period, here we can define first deduction period. SPRO => PAYROLL => PAYROLL USA => DEDUCTIONS => DEDUCTION FREQUENCIES => DEFINE EMPLOYEE GORUPING FEATURE : MODDE This will default the payment model in 0014 infotype. Select payrol area and provide dummy return value 1111. This feature is a field transfer 1 (Check in Pe03 attributes). So we cannot pro vide return value. SPRO => PAYROLL => PAYROLL USA => DEDUCTIONS => DEDUCTION FREQUENCIES => Default value VAREY WAGE TYPE 1111 8301 MODEL WAGE TYPE TEXT UNIFORM ALLOWNACE PAYMENT MODEL 1212 NAME QUARTERL PAYMENT

This configuration will default the value in payment model as 1212 for the secif ied wage type. New Example: Employee take 401K loan, and employee requests the employer to deduct 500 every month from his salary. The employee can obtain more than one loans taken at dif ferent periods but deduction with in the same payperiod Here once the 5000 is paid, the deduction should stop automatically. Possiblity: We can give the start date and end date for 10 months, if the employee may miss any one deduction. So here we need to extend a period. If we wanto the system to check and deduct till the employee has outstanding. w e should not use payment model. For this solution, we need to create three wage types: 1. Balance Wage type = Maintained in 0015 2. Deduction Wage type = Maintained in 0014 3. Total Wage Type = Available in Results table (Not maintained in any tabl e but created) Go to table: T51P1 to create link between these three wage types.

There is a PCR that will check if there is any balance to be deducted from the e mployee salary then if yes it will deduct and if no the deduction will be stoppe d. If the employee has lesser amount deduction compared to the entry in 0014 then t his pcr will check the balance and deduct which ever is less in the both. CONFIGURATION: SPRO => PERSONNEL MANAGEMENT => PERSONNEL ADMINISTRATION=> PAYROLL DATA=> RECURR ING PAYMENTS AND DEDUCTION => WAGE TYPES => CREATE WAGETYPE CATALOGUE Copy standard wage types: M235 8375 401K LOAN 1

If the employee is permitted upto 3 loans, then we need to create 9 wage types a s above for each loan type in 0014, 0015. Now we need to create a wage type in 0015. Go to Tcode : OH11 cLICK ON WAGE TYPE GROUP: SELECT 0015 copy the below wage type M236 8376 401K Loan 1 Balance

Now we need to create a wage type for Results table. Go to Tcode : OH11 Here the wage type model should be blank. copy the below wage type M237 8377 401K Loan 1 Total.

The remaining 6 steps are common 2. Check Wage type text 3. Check wage type permissibility 4. Ceck wage type characteristics. ADDITIONAL PAYMENTS INFOTYPE: For infotype 0015 only date of origin which is end date of the payperiod. We hav e option to change the date of origin. The system will pay the employee in the s ame month if the date falls in the same payperiod. The records can be for future dated payments or deductions also. The amount will be paid not in the month the payperiod is specified, it will be paid in the next month. Here we ave only one tme payments or one time deductions

SPRO => PERSONNEL MANAGEMENT => PERSONNEL ADMINSTRATION => PAYROLL DATA => ADDIT IONAL PAYMENTS => DEFINE REASONS FOR CHANGE New Entry: Code 22 Description Test Reason

SPRO => PERSONNEL MANAGEMENT => PERSONNEL ADMINSTRATION => PAYROLL DATA => ADDIT IONAL PAYMENTS => WAGE TYPES => CREATE WAGE TYPE CATALOGUE Copy wage types: 8603 8604 SIGNING BONUS (JOINING BONUS) COMMISSION 8304 8405

CHECK WAGE TYPE GROUPING create if any of the copied entry is not available CHECK WAGE TYPE PERMISSIBILITY Give the permissibility for all the groups. CHECK WAGE TYPE CHARACTERISTICS: TABLE: V_T511 Wage type 8304 Signing Bonus Add to total X Input combination: Amount x Number x By doing this, we can enter either amount or number for the wage type for paymen t. We can even have dot and dot here instead of x and x. Time unit: Percentage Rewriteable X We need to check the wage type charateristics for all the wage types created in wage type catalogue. Reqirement: 1. Some employees agreed to take the commision in ever 3 payperiods rather than waiting for the whole period. We need to use the same wage type in 0014 and 0015, then we need to go to 0014 c onfiguration, FORMAT FOR WAGE TYPES WAGE TYPE SHORT TEXT LONG TEXT 0008 0014 0015

Now we configure to make the wage type that is created for 0015 to be visible in

0014. 1. Go to wage type model select 0014 and create this wage type there. 2. Go to 0014 navgation and configure in check entry permissiblity for wage type s and create the record for the same wage type. Tomorrow we are going to discuss on table 512W_D tomorrow: In this table we will discuss: PROCESSING CLASS: 1 -19 CUMLATIN CLASS: EVALUATION CLASS: 10.01.2012 SPRO=> PAYROLL => PAYROLL USA => BASIC SETTINGS => PAYROLL ORGANIZATION WE NEED TO DEFINE AND GENERATE PAYROLL MODIFIER AS DISCUSSED IN PA. SPRO=> PAYROLL => PAYROLL USA => BASIC SETTINGS => PAYROLL ORGANIZATION => ENVIR ORNMENT FOR MAINTAINING WAGE TYPES => PROCESSING CLASSES AND EVALUATION CLASSES All the Processing and evaluation classes are maintained in the table for each a nd every wage type: TABLE: V_512W_D PROCESSING CLASS: Processing class defines how the wage type has to be processed in a payroll. The entire payroll is dependent on process class. In SAP Standard we have 01 - 89 as standard processing classes. 90 - 99 are cust omer specific processing class. The custom processed is created just like a custom infotype but the process is d ifferent.

CUMULATION WAGE TYPES: These are nothing but some kind of bucket where we speci fy which wage types are used for cumulation. All the cummulations are valuated f or Fiscal year. Cumulation wage types are from /101 - /199 i standard. These wage types are use d for cumulating the wage type balances. In V_512W_D we have list of cumulation class, Example: 1 Gross Salary = in payro ll results it will be preceeded with /10 and become /101. /101 is used to check the gross salary in payroll results. /102 is for 401 (K) . If the employee is contributing Basic and HRA as 10% for 401K, then for those two wage types we need to check this check box. This will become the base for 401K calculation.

/103 is for Pension Eligible Earnings: If the emloyee is working for more than 3 years in the company they are eligible pension from the company.In savings pla n if we have a penson plan, then we need select those wage types with this chec k box to calculate the pension. In the confuguation we define how much is the e ligiblity but here we define which wage types should be used to account the spec fic calclation. /104 is for NQP (Non Qualified Plans) Eligibile earnings. In another type of pl an where employee can opt for deduction just like /101 or /102. /109 is for Employer benefits contribution. Here we define which wage types are to be selected for employer benefit contribution. /110 is for Net paymens / Deductions. If there is a wage type that is part of n et payment then we need to select this check box. Example Name P0001-ENAME Earning /101 Deduction /110 Total Tax /5U0 Net pay /559

/5U0 is the wage type very secific to USA to derrive the employee total Tax dedu cted. In time management , we will have TIP entries, similarly we have wage types in p ayroll. Cumulation class wage types are not only used for reporting but also for perform ance tuning. Instead of reading all the wage types every time in payroll, syste m will take the cumulation wage types and increase the performance. What ever the cumulation class we see in the list are based in MOLGA. /101 - Universal /102 - USA /103 - USA /104 - USA /009 - USA /110 - Universal /114 - USA /114 - is for Base wage for BSI. We need to take this cumulation class for BSI c laculation /115 - is for Bonus Wages. We specify the percentage or bonus payments in maste r data. Which wage types need to be used or bonus calculation need to be checke d here. If we have non standard bonus calculation then we need to create a cust omer specific calclation. /900 - is for Vacation YTD - This is for vacation base cumulation for selection of wage type for Vacation computation. /101 - /189 - SAP Standard Cumulation Class /190 - /199 - Customer Specific Cumulation Class.

EVALUATION CLASSES: Evaluation classes is used to define, on which window of the payslip are the wag e type need to be printed.

Practically it aluation class s with similar ew entries for

is difficult to create processing class / cumulation class and ev for every wage type so, we always need to copy standard wage type specification. This is the reason why SAP dosen't come up with N wage type and always its a copy from wage type model.

For Infotype 0008 - We will see 11 tables copied for each wage type. US SPECIFIC TECHINICAL WAGE TYPES: /001 - /099 - Valuation Basis - Valuation Basis wage types are used to define Ho urly rate valuation. Hourly rate = Basic Pay total / Average Hours per period. These technical wage type are used hours rates. We have diferent kinds of hour ly payments based on the nature of work, for example: Over time horly rate, on call hourly rate, production control hourly rate, basic pay hourly rate. For eac h kind of hourly rate individual techinical wage type used from /001 - /099. /101 - /199 - Cumulations - Cumulation wage types as discussed above /201 - /299 - Averages - If the emloyee is going on leave for 6 month approved l eave, then we might have requireme that take last 10 months average salary and p ay to the employee. For such requirement this technical wage types are used. /301 - /399 - Total Gross Earnings - Total earnngs will be stored in Total earni ngs. /401 - /499 - Taxes - Taxes are calculated based on /601 - /699 /501 - /599 - New Payments - The amount paid, reversed, unpaid wage types are st ored in this series. /601 - /699 - Taxable Earnings - Total earning - pre deductions is taxable earni ngs used for tax calculation. /701 - /799 - Reortable Sage types (Subject Wage types) - These series are used for reporting purpose. Example: An employee has cap on Social securit tax as 1 ,10,000. If the employee is earning more than that limit, we only need the maxi mum rate will hold for reporting purpose.These wage types are used for such purp oses. If we have to print on W2 only the tax deducted amount, then we need use this wage types. The same will be used for employee and employer unemployment t ax. /801 - /899 - Time Wage types - If an employee has taken an unpaid absences. If we want to print on payslip that how many unpaid days are there and print on pa yslip, then we use this series of wage types. These techincal wage type are generated by the system after the payroll processi ng. CONFIUGRATION: PROCESSING CLASS: SPRO=> PAYROLL => PAYROLL USA => BASIC SETTINGS => PAYROLL ORGANIZATION => ENVIR ORNMENT FOR MAINTAINING WAGE TYPES => PROCESSING CLASSES AND EVALUATION CLASSES => Maintain Procssing classes and their specifications: 1 - Assignment to Valuation Basis. We maintain this processing class for all the wage types with an appropriate specification to identify or to calculate the ho urly rate. Example: WPBP: This is the first table either in time management and payroll that is going to b e created for running the schema.

This table we have 0008 infotype. Wage types: 7000 7001 7002 7003 Basic Pay Special allowance Project allowance Comission

The way we have a TIP table in Time evaluation, we have IT table in Payroll. Al l the wage types are going to be stored in IT table for schema processing as inp ut. The way we have PTIP in Time evaluation, we have PIT table in payroll. The reason we don't read IT table in time management we will not be able to see payroll wage types in tme evalation. Now we have 4 wage types as specified above, now we need to pick which wage type is required for hourly rate calculation. We need to provide the processing cla ss 1, but to understand how it has to process we need to maintain specification class. Example: For unpaid absence deduction: Basic pay only For oncall support payment: Basic pay + Special allowance. Then we need to check as below: Basic Pay Special allownace - /001 and /002 - /002 only

Why should we calculate hourly rate since begining of the employment: Once we derive the hourly rate, system will prorate the employee tenure in the c ompany and multiple with the hourly rate. Select the processing class 1 and click on processing class specifications: Here we wll find the list of specifications. Create a specification class = B = Add the wage type to /005 (It is just a descr iption) To push it to a wage type we need to do it in payroll. Every processing class has a documentation. Now go to V_512W_D For the processing class 1 = we need to choose B specification class for that wa ge type. In processing calsses 0 is also going to have its own meaing and it is different from blank. Keep 0 as specification for 7001,7002,7003. Go to PE02: PCR: X010

*x010 **1 **2 **3 = ESG for CAP (Salaried) ***VWTCL 01 (Check the processing class 01) * ERROR (It means, if the processing class is spec ified as blank the error should be populated) 0 ADDWT * (Add the wage type to output table) Info: ADDWTI ADDWTE ADDWTL ADDWT ADDWT * = Add to * = Add to * = Add to * = Add to 1234 = Add IT table (Input Table) RT Table (Results Table) LRT Table (Last results table) OT Table (Output Table) to Wage type 1234. 1 (In this subnavigation we are pushing the value to /00 1 wage type) 2 3 4 5 6 7 8 9 A B (We need to add a processing class entry and add /005 wage type) This is how we can create and assign custom procssing process. 11-01-2012 X010 PCR: WPBP SPLIT: Multiple records for the same pay period is called split. If there employee joined in mid of the month there will be WPBP slpit If the employee salary is not the same in the same pariod then there will be bas ic pay split. So in both the above cases the hourly rate for that month is not same. If the employee take unpaid leave in first half of the month wher the salary is different from the second half of the month we need to derrive the exact hourly rate for the split. In Infotype 0008 if there are any changes, then we need to consider for WPBP spl it. There can be change in 0007 then also there will be split.

There can be change in 0027 then also tere will be split. There can be change n 0001 then also there will be split. If the employee goes on leave with inactive status, then there will be split in 0000 infotype. Amount that is entered in 0015 is not subject to proration. WPBP will not have split for this infotype. Amount that is entered in 0014 is not subject to proration. WPBP will not have s plit for this infotype. At a conclusion, what ever the wage types that are available in 0008 are only co nsidered for WPBP split and system will prorate the amounts accordingly Even though it is not a regular practice, we can also bring a wage type that is entered 0014 for WPBP split. When there is a split in the wage type there will be many categories of splits d one by the system after the payroll process. Example: Tax Split, Gross split... We ned to fine the required split wage types for our calculation based upon the calculation that is required by client. In India, all most all the wage types that are required for WPBP split are maint ained in 0008 infotype. There is an operation called ELIMI *. It will eliminate all the indicator for a wage type in case of split. ELIMI R Employee sugroup grouping table T503: All the pcr we are writing based on employee subgroup grouping. Here we can dif ferentiate the split based on emploee subgroup. ELIMI A Work center period WPBP - This is very specific to 0008 infotype only. ELIMI ELIMI ELIMI ELIMI ELIMI ELIMI ELIMI ELIMI ELIMI 1 2 3 T K U X Y Z SV TBALE XS TABLE (Not Used) ALP (Alternative Payment Table) C1 BT VO

if we keep ELIMI * system will remove all the indicators. If we keep any value other than * after ELIMI then system will ignore rest all i ndicators and take that indicator only into consideration. If we want to use any variable after ELIMI * then we need to write RESET Z or an y variable that is required. Both the operations works like the same. The maximum number of char after ELIMI are 3. If keep ELIMI R12 then system will remove all indicators except R,1 and 2.

In every payroll infotype, the employee subgroup grouping will be prefixed for e very wage type. Based on the ESG for PCR the wage type will be processed in eve ry pcr. In infotype 0008 we have 7000 = BASIC PAY = 10000 ADDWT * Bring wage type amount 10000 ELIMI Z = if there are any tme units split consider that, eliminate any other sp lit indicators. ZERO N = (Amount, Number, Rate) - Nullify the number field in the WPBP and consi der the amoutn and rate only. ADDWT /001 = Add the 10,000 derrived after the splits and after nullifying the N umber. Again system checks the second wage type 7001 = 5000 and ere ADDWT * will becom e 10,000 + 5000 and do the similar processing as above. At the end it will take all the wage types in 0008 based on the indicators and add to /001 for gross sa lary. X013 - Division of Valuation Bases. X013 * 1 2 3 (ESG for PCR) VWTCL 01 (Chec the processing class 1) * (Any Specfication other than 5) ADDWT * (Add all wage types to output table - O T) 5 (If the specification class is 5) RTE = TSDIVP (Rate = (Average number of working hours in 0008)) = 175 (Example) DIVID ARR (Division of Amount / Number / Rate) = 10,000 / 175 = 57.14285. ZERO = A (Nullify Amount 10,000) ADDWT * (Add wage types to output table - OT) After this PCR, system will show the split of wage type amount in the output tab le under /001 ad /002 as the spcification class is 3 which is to add the wage ty pe to /001 and /002 PRORAM FOR PAYROLL CALCULATION IS RPCALCU0 Maintain 0210 infotype prior to payroll generation. Generate test run for one employee. In the output table IT: 3 7700 Basic Pay 01 Here 3 is the ESG and 01 is the split number.

If there is a split, system will calculate the amount/ number of days for that w age type into number of splits available in that month. The average working hours in 0008 infotype are based on the payroll area - peri od parameter. We should also define the wage type amount only based on the Payr oll period. Example: If it is a weekly payroll employee the hourly rate is going to be calculated bas ed on the weekly value available in average woring hours. DIVID = Devide ADD = ADD SUBS = Substract 12.01.2012 PCR: X020 (Cumulation of Gross Amounts) PROCESSING CLASS 3:Cummulation and Storage of wage type. Specifications type 0 - Pass on unchanged: Just move it to out put table for futher analysis withou t any process. Example Basic pay wage types. 1 - Storage, cumulation with esg for pcr and ac2 indicator: Storage, cumulate w ith ESG for pcr and ac2 indcator for time wage types. Initally we wll identify the hourly rate, once we get the hourly wage, in time w age type we will only know the nmber of hours. Now we need to get the Amount, so we need to multiple the number with the rate based on this specification class. This process is called time wage types valuation. The table for time valuation is : V_512W_B (Time Wage type Valuation) Sect the time wage type 1205. Time wage type is nothing but an absences or attendance type. Double cick on the wage type 1205. If it s a time wage type we will have only hours. Valuation of Current Wage type: Valuation Basis 01 means it is a technical wage type /001. % Rate is how much percentage of the specified wage type should the time wage ty pe be valuated. The valuation will change between different wage types. We need to identify the rate and store them in /0** series wage type and assign that valuation basis in this field. Statement Wage type: If we want to transfer the amount calculated in this time wage type to another wage type then we need to specify the wage type in statemen t wage type. Example: 6260.

Example scenario: Employee on a public holiday and on a weekend, the employee worked on that speci fic day. According to the company policy, if the employee comes and works on su ch days, he is entitled for holiday allowance, over time and weekend premium. OT = 125% HOL = 25% WEND ALLW = 10% 1400 = Over time on weekend. 1401 = Holiday Allowance 1402 = Weekend allowance. Wage type: 1400 Current Wage type: Valuation Bases:01 Rate:125.00 First derrived wage type: Valuation Bases:01 Statement Wage type:1401 Rate:25.00 Second Derrived wage type: Valuation Bases:01 Statement Wage type: 1402 Rate:10% In the output for 1400 wage type we will have the total value o three wage type. We can create the time wage types in OH11 or under create time wage types naviga tion. Second scenario: Employee on a public holiday and on a weekend, the employee worked on that speci fic day. Pay him 200%. Create tme wage types: 1400 = Over time on weekend. Valuaton Bases : /001 Statement: % Rate = 200 Scanario: Weekend Premium is paid with different rate Holiday Premium is paid with different rate Over time allowance with a different rate

Then we to transfer the rates into diferent valuation bases: 1400 = Over time on weekend. Valuaton Bases : /001 Statement: % Rate = 200 1401 = Over time on weekend. Valuaton Bases : /002 Statement: % Rate = 200 1402 = Over time on weekend. Valuaton Bases : /003 Statement: % Rate = 200 We can also handle this requirement directly in tme schema by creating time wage types in PCR. Scenario: If the company fix an amount of 200 per hour as a constant rate. In the valuation basis we need to take K (for constant) Earlier we have discussed T510K table based on the wage type. Here in the valuation basis K, it is not with reference to wage types. If we need the rate or both hourly and salaried employee same then we maintain t he value in T510K. If the hourly employee and salaried employee rates are different then we need to maintain the values in T510J constant table. Here we need to create the same wage type in two MODIF groupings and use them in TMON or MODT pcr. Same like time management we have TMON or MODT we have a similar PCR in Payroll schema also. Scenario: If the employee have rates diffentiated based on pascale structure, then we need to use the Valuation Basis TS. The classfication will be based on below parameters: ESG for PCR: Payscale type:

Payscale Area: Payscale Groups: Payscale Levels: We will define the rate in T510 Table (Revise Payscale Groups and levels). GRP CUR 3 PSGRP MGR LVL 01 WAGE TYP 1205 START DATE 01.01.1900 END DATE 31.12.9999 AMOUNT 100

SCENARIO: Valuation Basis : TG. It works just like TS. But it wont consider the payscale levels. SCENARIO: Valuation Basis : T. It works just like TS. But it wont consider the payscale Groups and levels. SCENARIO: The consultant some times, keep all the values in time wage type valuation. The y will handle the calculation directly in the pcr. For handling this scanarios: Got to Constant table: T511K. Create: Variable: K1234 - Test constant 1 Variable: K1235 - Test Constant 2 01.01.1900 01.01.1900 31.12.9999 31.12.9999 55 60

We need to define the constats based on employeee groups. every wage type should have either number or amount or rate. x xxxx OUTWPPERSG Y SCOND=T IF X SCOND=F IF in payroll: 3 1206 RTE=KK1234 MULT NRA ADDWT* **** ADDWT*

X020 3 (ESG for PCR) **** (Any Wage type) VWTCL 03 (Processing Class 03) * (Specification class specified other than belo w) ADDWT* (Add wage type 0 (If the specification class ADDWT* (Add wage type 1 (If the specification class ADDWTE* (Add the wage ble ELIMI RK (Exlude processing indicators o ther than R,K). In standard PCR it is wrong. ADDCU (Add t0 cumulation wage type n out put table) For time wage types we alwasy use specification 1. Offset Wagetype: It is neither earning or deduction, these are reference wage t ypes only. 2 ELIMI * ADDWTE* 3 ADDWTe* 4 ADDWT* ELIMI AR ADDCU 5 ADDWTE* ELIMI KTX ADCU ELIMI * ..... PROCESSING CLASS 5: Create Net remmuneration and toatl expenditure: /550 - Net Remuneation /700 - Total Expenditure PCR used for this processing class:X030 Here we derrive how much we need to pay to the employee and what is the total co st to the employee. In the below PCR we will define which wage types should be added to /550 and which wage type should be added to /700. X030 (Cumulation of Net Amount) * (Any ESG for PCR and CAP) **** (Any Payroll Wage Type) VWTCL 05 (Processing Class 05) * (Any specfication which is not mentioned below ) ADDWT* (Add to output table) 0 (If the specification is 0) to output table) is 0) to output table) is 1) type to Results ta

ELIMI * (Elimite all split indicators) ADDWTE* (Add to Results Table) ADDWT/550 (Add to /550 Wage type) ADDWT/700 (Add to /700 wage type) 1 (If the specification is 1) ELIMI * (Elimite all split indicators) ADDWT * (Add to output table) 3 (If the specificaton is 3) ELIMI * (Elimite all split indicators) ADDWT /550 (Add to output table) We maintain indicator 3 for storing the Net remunneration) 4 (If the specificaton is 3) Summarized storage in RT and substratition in Net ELIMI* ADDWTE* SUBWT /550 5 (if te specification is 5) Summarized storage in RT and addition in total expenditure ELIMI* ADDWT /700 class: 13.01.2012 PROCESSING CLASS 6: Enter wage type from old payroll account in LRT. RESULTS OF TABES: The below tables wll be stored after the payroll process: RT : Results Table, It conctains the current results when ever the payroll is e xecuted. LRT: Last results table, this will be previous payroll process results ORT: Original results table, We may not need accumulate all the wage type results in LRT. Example: System should check the balance in 0015 and deducted in 0014 every month till th e balance becomes zero. MAY: BALANCE: 800 TOTAL: 400 DEDUCTION: 200 JUNE: We only need Balance: 800 here as LRT to carry over next period for processing. The PCR behind this processing class is X006.

The specification for processing class are as below: 0 - Wage Type will not be transferred. 1 - Wage type will be taken from PRevious Payroll. 2 - Wage type will be taken from same year. X006: * **** VWTCL 06 (If Processing Class 06) * ERROR (Cancle Processing) 0 1 ADDWTL* (Add to Last results Table) 2 LRTST Y (LRTST = Previous Month is in?, Y = Same Year) ADDWTL* (Add to Last Reslts Table) PAYROLL SCHEMA In time management we have global schema, but in payroll, we will have payroll f or every country. India USA UK = IN00 = U000 = GB00

Program name for payroll driver: RPCALCX0. The last two digits in the program represents the country of the payroll process . India USA UK INTERNATIONAL = = = = RPCALCIN. RPCALCU0. RPCALCGB. RPCALCX0.

SIMMULATION RUN: PCOO_M10_CALC_SMU - Simmulation. In M10, the 10 represents MOLGA. For India it is M40 For International it is M99 For UK it is M08. The Payroll is process is based on the payroll area and payroll period. Current Period: What ever the period is open in control record wll be considere d for payroll processing. When ever the user want to run using the current period, the payroll area need t o be relased. Other period: This is used for current and future payroll periods payroll proce ss. It will be generally used for testing the payroll process. Personnel Number: If we want to run payroll for a specific employee, then we ne

ed to enter the personnel number here without entering the payroll area Schema: U000 - Here we specify the schema we use for payroll processing Forced retro accounting as of: If we want retro to be calcuated from specific d ate irrespective of whether it is available in 0003 or not, then specify the dat e here and it will process the payroll only from the specified date in this peri od. Another example is, if we change the configuration, 0003 will ot be updated. so we need to give the date from when it has to run retro of each and every employ ee. In the below scenario: 0003 earliest master data change date is 1st jan 2010, the date given in forced retro acounting as of is 1st june 2010. System will always consider the earlies t date of both for the processing. Here it will take 1st Jan 2010. Display Log: Show the log in the output table: Display log for time management additionally. In payroll schema we will have time eval schema: Scenario: The employee will leave the company today after work, but today he is going to w ork till midnight or the time evaluation is not executed prior to the employee s hift completion, then this check box will bring the employee time evalauation pr ior to payroll in this field. While running the schema with this cehck, system will show if there are any erro s in time evaluation and populate the error log which we can use for check the e rrors and resolve. Remmuneration statment paameters: Payslip is configred in different methods. 1. HR Forms 2. Smart Forms:In smart forms, we can have logo and other additions features. SCHEMA: U000 In Payroll most of them are subschemas: SUBSCHEMA: UINO = Initialization of US Payroll. PGM ABR = Check which type of payroll program are you using.

The reason for this function is, it will determine whether it is regular payroll or Bonus Payroll or correction payroll or payroll adjustments. We can find the types of payroll in offcycle payroll field in the schems process ing program: Blank Regular paroll A - Bonus Payrol

B - Correction Payroll C - Manual Check (Payroll Results Adjustmnets) S - Additional Payments The types of payroll as above are same as time management status in 0007 infotyp e. UPD OPT OPT YES = Whether the data base is updated properly or not. INFT = Read only processed infotypes. TIME = Read all time Infotype.

OPT DEC = It is going to be commented in realtime systems also. If we activ ate it, the hourly rates will be processed with more than 2 decimals. CHECK ABR = It is going to be commnet it in development and quality sy stem. But it will be activated in production system. If this function is activa ted, the payroll wil not be processed if the payroll area is not released in con trol record. OPT BSI = Check whether all the BSI switches are open. It will be activated in Production system. But testing payroll we can deactivate this function. The BSI will be interfaced using transaction code :SM59 => TCP/IP connection (SOAP in the latest Term)=> BSI-US-UPDATE. SUBSCHEMA: UBD0 = Basic Data Processing ENAME = Go and Read employee name WPBP = Go and Read employee wor place basic pay data. P0002 = Go and Read 0002 infotype data. P0006 = Go and Read 0006 infotype data. P0207 2 = Go and read residence tax area and "2" = whether W4 information in f iling status in 0201 infotype. The informatio that is output of 207 and 210 are stored in TAXR internal table. P014 UW14 GEN NOAB = Split WPBP and set APZNR for P0014. (This UW14 P CR will force system to check 0014 if there is any change in addition to WPBP ta ble) While runnign the test run we can open and maintain data in PA30. But in live r un it will throw error if we do so. In 0014 infotype, if the paymement model should not be considered. then we need to remove the payment model from the 0014. In India we don't have this pcr for 0014 split. We need to copy and customize t o use it in Indian Payroll P0014 = Read Infotype 0014 UW14 = Read if ther are any splits GEN = Generate the data

NOAB = Irrespective of employee. UW14: (Spliting WPBP and assigning the split to IT * **** ELIMI A (Elimiate all except Indicator A) WPVPCW WPBPC = Operation WPBPCA = Amount is distributed according to calendar days. Example: 01.04.2010 - 30.04.2010 the Payment is 3000 for WPBP and 300 for 0014. SPLIT: WPBP 01 - 01.01.2010 - 10.10.2010. 1000 WPBP 02 - 11.01.2010 - 30.10.2010. 2000 0014 01 - 01.01.2010 - 10.10.2010 100 0014 02 - 11.01.2010 - 30.10.2010 200 WPBPCD = Amount will be same and updated for every split. Example: 01.04.2010 - 30.04.2010 the Payment is 3000 for WPBP and 300 for 0014. employee have his payroll areas a1 from 01 - 10 apr and 11 - 20 apr in payroll a rea A2 WPBP 01 - 01.01.2010 - 10.10.2010. 1000 WPBP 02 - 11.01.2010 - 30.10.2010. 2000 0014 01 - 01.01.2010 - 10.10.2010 300 0014 02 - 11.01.2010 - 30.10.2010 300 WPBPCS = If the validty period starts or ends during the preiod , the entry in t able WPBP is split using this date. System will create a split in WPBP table and OT table for further processing. Example: 01.04.2010 - 30.04.2010 the Payment is 3000 for WPBP and 300 for 0014. SPLIT WPBP 01 - 01.01.2010 - 30.10.2010 0014 01 - 01.01.2010 - 10.10.2010 0014 02 - 11.01.2010 - 30.10.2010 WPBPCW = It will create a split but don't transfer the data to IT table. What ever the wage type we have in 0014, we don't need this amount for hourly ra te calculation. This will reduce the payroll processing time by excuding this s plit and it can be take care at later point of time in the schema. PRINT NP NAM = Print employee name.

PRINT = Print NP = In a New Page

NAM = with employee Name PRINT PRINT PRINT IF RFRSH ll WPBP = Print Workplace basic pay TAXR = Print TAXT data received from 207 and 210 PERM = Print data from personal data infotype SPRN = If it is offcycle payroll IT = Delete the IT data as it is not required for offcycle payro

PRINT = Print 17th jan 2012 UPRO: This subscema will process the retro payroll. It will read previous resul ts of current period. IF R

It will check each and every wage type in the previous period in comparision to the current period. It the value is negative then system will deduct and if it is positive it will create payment for the employee salary in that month. LPBEG RC

Lopp at previous results (Still valid) in retuls table IMPRT O

System will download all the tables from ORT table (Old Results table). All ORT, LRT and RT tables have the same table structure. PITAB M OV0

This function is used to merge two different internal tables. M = Merge, IT wil l delete the value in one interna table and merge the value in another internal table. D = Deelete. Example: Variabe pay: 10000 Project special allowance: 10% on Variable pay. Which ever the wage types are processed will go to RT tabe, which are not proces sed will be available in IT table. There is a payment called project special payment. We can modify or change the calculation only as long as the values are in input table. If the results are p osted to the output table then no changes can be done for that period. FILIF = Is an operation will help to reset the original values back to the wage

type. We can write this operation before transfering the wage types to the outp ut tabe. To keep the value secured until next processing. So we need to replicate this in a different internal table. PITAB will create another temporary table and tran sfer the values. once the project allowance as shown in the above example is der rived, it can be posted to results table. FILIF can be used to roll back the current value in the wage type to original va lue. This Operations can be as many numbers as required. Ultimately PITAB function will create a temporary table and copy the values. M = Remove the value in actual table and instert in temporary table. V0 = 5 OV0 = 10 after PITAB = OV0 = 15. A = Copy the value in actual tabe to the temporary table. L = PITBA A PCT

This fucntion is used to add values from one internal table to another internal table. A = Add. LPEND End Loop

SUBSCHEMA: XLRO: Import previous payroll results. Example: Employee is issued a cheque and empltoyee is paid difference in compar ision to the previous payroll. This Subschema wil transfer the results to /564 ( Advances) wage type, it will be from the same payroll period. T569V = Table to check if the payroll is in exit status. This should be used fo r functional specs for defining the logic. Companies like ADP / Deloitte will check the payroll results after payroll proce ss. If we want to send the data, we should send only after payroll is exit. In USA, the employer can deduct the excess tax if there is excess then the exces s amount will be paid back to the employee with in 14 days. If the eployer is pa ying less tax, the employer will attract penalty. to avoid this kind of scenario s, the company will send the data to 3rd party only after the payroll exit. Using an interface the data will be sent to 3rd party with date and time stamp i n the background. Another scenario is in a specific payroll period, certain employees payroll is n ot processed and user need to correct the data and reprocess to exit payroll. So Ultimately the payroll results should be posted to 3rd party only after exit payroll. A test scenario is must for every functional specification. SAS = Statement of Audit Standards will not clear the FSD if the test scenario i s not available in some companies.

XLRO will store the previous results table in LRT table. LRT need not have retro to bring the data from previous results. It is only to check the balances available after last procss to pay the remaining in the curre nt month. Example: Every month there should be a deduction of $500 for 401K every month. APR MAY JUN + 500 = IMPRT PORT X006 $400 $500 - Employee has insufficient funds. $900 - When there is a slary increments effective from april (400 + 500 1400 - 500 = 900) ORT L = iMPORT LAST RESULTS P06 NOAB

If there is any payroll process required from pervious payroll period to current payroll period the PCR used is X006. But the employee dosen't have sufficient funds in th ORT need retro to bring the data from previous results. All the wage types that are required from previous pay period for cauculation in the current month are only brought using this PCR and stored in LRT table. Example: We might not need Basic pay but we need advance balance. SETCU Prepare CRT (Cumuative Results Table) old results. Example: The maximum 401K is 17000 and the employee already paid 16000. so if there are 6 months remaining then the 1000 will be distributed accordingly. The total paid will be available in CRT table. The last balance will be available in LRT to calculate. In USA we have table called TCRT (Tax Cumulative results table). We don't have this in Indian Payroll. The structure of CRT and TCTR is different. The YTD values are available in CRT table except tax wage type. In TRCT table w e can see all the wage types including tax wage type. In TCRT, the tax paid is for different authorities. Here we will find additiona l fields like what is the tax authority and which period is that tax authority t he tax paid for. Every payperiod, system will check the LRT table irrespective whether it is retr o or not. ORT will be checked only if there is a retro SUB SCHEMA: UMO0 = Determine Payroll Modifier. It is as good as TMON PCR in time management.

MOD

UMO1

Determine US Payroll Modifiers. UM01 (PCR) 3 (ESG for PCR) **** (For any wage type) UMODI 5=00 UMODI is same as MODIF in time management. This PCR will be used only for Long term disability employees. Here 5 means, it is an indicator for long term disability. Company will pay upto 13 weeks for a short term disability, if still the employe e don't come to the company, employee will execute an action and convert the eml ployee to inactive status and declare him as long term disablity. During this period the employee will be paid as below: 3 Months = 100% Payment 1 Month = 75% Payment 1 Month = 50% Payment Here the above % split may not be same for salaried employee and hourly employee . Here 5 will be read from configuration, just like time we define in T554C / T554 A Tables. Check the configuration. MOD = Modifiers for Payroll accounting MODIF A = 01. (Absence Valuation) If the employee took an absences, the payment might be different from salaries a nd hourly. This MODIF A will differtiate the payment between hourly and slaried employee using the parameter. This operation will read T554C table. MODIF 2 = 01. This will read T510J table for constant based on wage type table. MODIF B = 01. This will read T51D1 table for Limit Modifiers. Example: There is a parking fees, the maximum deduction is 1000 per year for Salaried Emp loyees. We are deducting 150 for both salaried and hourly. Here if it is salaried employee system will stop at 1000 and for hourly it will deduct 150 for the complete period. This different is set in this table. MODIF C = A. (Accrual Basis) MODIF D = 0. (Delay Basis) MODIF C AND D are not in Use. In the output all the groupings are stored in MODIF output table.

Till now we checked the payroll readiness. SUBSCHEMA = UT00: Gross compensation and time evaluation. In International and other payroll schemas, we will have XT00 instead of UT00. The contents are same or UT00 and XT00. We can use XT00 also in USA instead of UT00. PRINT NP PCI

Personal calendar annual view: It will read and print the infotype 0007 for wor king and holidays for the complete year. It is just for information. PRINT NP PCIP

Personal calendar period view: It will read and print the infotype 0007 in a pay roll period view. It is just for information. GENPPS This function will generate the periodic work schedule of an employee provided i f the employee is active or retiree where we run the payroll. During data migration, it is recommended to run work schedule generation atleast one month before the payroll proces. This is a very important function. Based on this function we can determine: How many Working Hours How many working days How many calendar days CHECK THE SCHEMA TILL THIS STEP TO UNDERSTAND WHAT IS HAPPING IN THE LOG. The output for GENPPS is PSP table (Personnel work schedules) PSP is the same table used in time evaluation to store the data. It will take o ne day before and one day after the generation data. ********************* 18TH JAN 2012 PARTP - PARTIAL MONTHLY (PERIOD) PARAMETER Till now we have identified the partial days available in the period. Here we a re going to identify how may working days, how many calednar days in that partia l perod. This function is going to identify partial period valued in a month. Input for PARTP Function is: 1. WPBP - How many splits are there. 2. PSP - How many number of days the employee supposed to work tat particular pe riod. (PSP - PERSONNEL SHIFT SCHEDULE) During customizing also We need to ensure all the WPBP and PSP splits are determ ined and processed before PARTP Function.

The output of PARTP wil be as below: To know the below, go to PE04. Go to funtion PARTP. Click on documenation. Go through the documentation click on any highlighted link, further check for RTE highligted link and you can find the below documentation. You can even give the Operation RTE in PE04 and find t he complete documentation below. In Payroll schema RTE is same as HRS operation in time management. G T S A K SOLL AU AP AX DM DIVP ** GSSOLL GASOLL GKSOLL GSAU** GAAU** GKAU** s GSAP** GAAP** GKAP** GSAX** GAAX** g classes GKAX** nting classes GSDM GADM = Whole Period = Partial Period = Working Time in Hours = Payroll Days = Calendar Days = = = = = = = Planned Time Unpaid Absence Paid Absence Public Holiday Individual Period Flat Rate Any counting class for the Absences. TSSOLL Planned working hours TASOLL Planned working time in work days TKSOLL Planned working time in calendar days TSAU** Unpaid absences in hours for all counting classes TAAU** Unpaid absences in working days for all counting classes TKAU** Unpaid absences in calendar days for all counting classe TSAP** Paid absences in hours for all counting classes TAAP** Paid absences in working days for all counting classes GKAP** Paid absences in calendar days for all counting classes TSAX** Work on public holidays in hours or all counting classes TAAX** Work on Public holidays on all work days for all countin TKAX** Work on public holidays on all calendar days for all cou TSDIVI Individual period working time in hours TADIVI Individual period working time in work days

SDIVI = How many hours the employee supposed to work according to a specific wor k schedule. ADIVI = How many days the employee supposed to work according to a specific work schedule. Example: Purpose - We need to pay exact amount to the employee. Suppose the employee agr eed to work 8 hours a day and 5 days a week so its 176 hours a month. From 01 - 10 = 176 hours per month pattern.

From 11 - 30 = 208 Hours per month pattern declared by the management. Employee salary = 3000 per month So it will be: 01 - 10 = 3000/176 11 - 30 = 3000/208 So the calculation will be like this: If it is calendar Days TKSOLL(Total Number of Partial period calendar days) - TAAU** (Number of absence s in that partial period)*3000(Monthly Salary) /TKSOLL (Partial Planned calendar days - (01 - 10 = 10 Days) and (11 - 30 = 20 days) or TADIVI (Partial Planned w orking days according to work schedule (01 - 10 = 9 Days) and (11 - 30 = 17 days ) GSDIVP GADIVP GKDIVP TSDIVP Flat Rate period working time in hours TADIVP Flat Rate period working time in working days TKDIVP Flat Rate period working time in calendary Days

In a month we might have 28/29/30/31. To maintain flat rate irrespective number of days in the month DIVP is used. Feb = 28 Days Mar = 31 Days Apr = 30 Days If there are unpaid days as 10 in a month. Then Feb = 28 - 10 * 3000 Mar = 31 - 10 * 3000 Apr = 30 - 10 * 3000 In Indian scenario, the rate is fixed per 30 days. So we see no diference in th e pay irrespective of month. We need to maintain T510H or T511K tables. USA Scenario: FEB = 20 Working days MAY = 23 working days For Hourly employee we should not take flat rate. So we need to take as below: TSSOLL(PARTIAL PLANNED WORKING DAYS IN MONTH) - TAAU** (UNPAID ABSENCES FOR THE PARTIAL PERIOD/ TSDIVI(PARTIAL WORKING DAYS ACCORDING TO WORK SCHEDULE) If company choose to go for Hours: TSSOLL(PARTIAL PLANNED WORKING DAYS IN MONTH) - TAAU** (UNPAID ABSENCES FOR THE PARTIAL PERIOD/ TSDIVP(PARTIAL WORKING HOURS IN ACCORDING TO WORK SCHEDULE) If empoyee join date is 20th of the month, system will check how many working ho urs are there accoding to work schedule using TSDIVI, system will check how many

working days are there accoding to work schedule using TADIVI. GENPS function will generate only if the employement status is Active - STAT2 = 1 (Active) / 2 (Retiree) S and A are going to be on employee work schedule and K is going to be on month always. FUNCTION: P2003 - Import sihift substitution into Periodic workschedle. P2003 s**

It will read if there are any substitutions recorded for that specific employee in the month. PIT U010 P01 Create valuation bases (addtion / substraction)

The output will added to /001 and /002 PIT X013 P01 Create Valuation Bases (Division)

The output will added to /001 and /002 OPERATION: RAB (Import Absences) PAYROLL => PAYROLL USA => DAY PROCESSING OF TIME DATA => DEFINE TIME TYPES (T555 A) PAYROLL => PAYROLL USA => DAY PROCESSING OF TIME DATA => Assign identifiers (T5 55Y) Its just a replication of time Navigation in payroll, no need to do it again her e if we do it in time management. PAYROLL => PAYROLL USA => ABSENCES Till now in time management, we assume that all the absences are paid. But no w here in time manage we specified the paid or unpaid absences. PAB - Processing of the absences in payroll. There is an alternative way of procesing the absences by generating the wage typ e in time evaluation and valuating the wage type in T512W_B table. In time management create 3 wage type: 1234 - PL 1235 - SL 1236 - Unpaid VARSTABTYP PL OUTTYP A ADDZL1234 SL OUTTYP A ADDZL1235 UP OUTTYP A ADDZL1236

Valuation of absences in Payroll: PAYROLL => PAYROLL USA => ABSENCES => Describe Absence valuation rules. The valuation rule is 2 digit code. The best practice is to create individual valuation for each absence type in pay roll New Entries: 77 78 79 Sick Leave PL Paid Unpaid Leave

We need to maintain valuation rule for every absence. PAYROLL => PAYROLL USA => ABSENCES => Assign Absences to Valuation Class. PSG AT/ABS TYP VAL CLASS 30 5001 78 30 5002 77 30 UNPL 79 AT/ABS TYPE TEXT PL SL UNPL START DATE 01.01.1900 01.01.1900 01.01.1900 END DATE 31.12.9999 31.12.9999 31.12.9999

PAYROLL => PAYROLL USA => ABSENCES => Determine Grouping for absence valuation: Feature: UMOD Here we need to define if there is any different between salaried and hourly emp loyee for absence valuation. If we want to modify, we need copy and then modify. Update schema UT00 (It is the schema where this UMOD or copy of UMOD need to be upated. 19th Jan 2012. Payroll => PAYROL USA => ABSENCES=> Create wage type cataogue. Copy the wage types: Wage type model: 0520 is for absence valuation. 8355 = Sick Pay 8356 8357 8358 It is not mandatory to copy but it depends on the requirement. We purpose of th is wage type is to assign to absence type. 1. If we want to print any kind of information on payslip, it is possible only t hrough a wage type. 2. If a company want to show both planned and actual wage types on payslip then we need to create a wage type Absence Valuation => Evaluate absences using AS IF principle:

Table: T554C New Entries: Abs Val Grp 01 (MODIF A = 01 in payroll schema) Valuation Rule 77 (Sick Leave) Start Date: 01.01.1900 End Date: 31.12.9999 A table entry in T554E table is a prerequisite for this table entry CC for absence = Entry in T554E table. Paid X (If this box is checked, it means it is a paid absences. For unpaid abs ences this should not be checked) Percentage = 100%, Percentage of payment for the employee. If there is a rule like, if salaried employee we need to pay 100% and for hourly employee we need to pay 75%. We can diferentiate using Absence Valuation Group ing (MODIF A = 02). This is the significance of MODIF A. Wage type: 8355 Description: Sick Pay Time Unit: I I = Valation in current payroll period. B = Valuation in First Payroll Period. First payroll period generated in payroll periods for that year. Percentage: 100% Time Unit: AH (Absence Hours) KT AT AH RT RH = = = = = Calendar Days Absence Days Absence Hours Payroll Days Payroll Hours

Basic Pay split: X (Valuate the absence according to WPBP Split) Abs Val Grp = 01 Val rule = 79 Start Date =01.01.1900 End Date = 31.12.9999 CC for absences = 79 Description = Unpaid leave Paid: (No check) Percentage 100% Days Rule = Blank Remaining same as previous wage type. Wage type: 8359 description: unpaid leave Time: I

Percentage: 100% Time Unit: AH Basic Paysplit =X After there this coniguration we have to specify Valuation baises in 512W_B. If we want the basic pay directly reduced and shown in payslip then this entry i s not required and we do it in factoring in schema. If we want to show the basic pay and deduction separately, then we need to do th e above entry + configure processing class in the 512W_B. The day rules are used in situations like, if the employee is taking this leave on a specific day then the configuration specified in this wage type should be a pplicable. Valuation Basis table:512W_B Wage type: 8359 Valuation basis 01 % Rate = 100% If sick leave a different process is required then we need to change in valuatio n basis. This is the completion of absence valuation. SHORT TERM DISABILITY AND LONG TERM DISABILITY PLANS: It is country specific so it is maintain under payroll navigation: 1. Setup STD/LTD Plans => Establish and define short/long term disability Plans. New Entries: (Copy an Entry) STD/LTD Plan: 20 STD PLAN USA. STD Quota: Quota per Year Illnes Permission: X (If the employe is applying an STD / LTD, employee need to apply sick leave prior to that. This should remain applicable only if the quota of sick leave is complete. Illness Quota = Quota er year per illness In the same table: STD/LTD Plans => PLAN DEFINITION C Unit 1 Weeks C = STD STD STD CS Unit STD 3rd Unit Year 8 Weeks Start Date 01.01.1900 End Date 31.12.9999 STD 1st Unit 1 Weeks STD 2nd 4

Seniority in CS Unit. 1st = 100% 2nd = 75% 3rd = 50%

The employee should maintain sick leave prior to applying STD which is shown how many days in the last two fields in this table. check the last two fields and u pdate the notes.

STD/LTD Plans => PLAN DEFINITION=> STD ILLNESS DEFINITION PSG = 30 ILL TYPE = 5008 (Employee need to apply this sick leave for 6 days for this wage type in connecto to above config) DESC = SICK LEAVE ABS/ATT TYP = 6700 DESCRIPTION = (STD DISABILITY LEAVE) START DATE: 01.01.1900 END DATE: 31.12.9999 2008 screen in 2001 infotype will have a different screen for STD absence type. Assign STD/LTD Plans for Org Units: If STD/LTD is applicable only for Production employees only, then we can define in this navigation. We can also define which STD is applicable for which departm ent / Enterprise structure. Feature: 07MSP (Determine Sick Pay Modifier) We can not only give this feature for Enterprise structure but also be applied b ased on organizational unit. ASSIGN HIRE DATE TYPE TO ORGANIZATIONAL UNIT: Feature: 07DTY If we want to check the seniority in STD using a date type specified in 0041, If there is no value in this feature 07DTY: Determine Hire date type, then system will check the Hire date as the date for seniority configuration. PREPARE PAYROLL FOR PROCESSING PAY RELATED TO STD/LTD PLANS: In earlier coniguration we can specifiy only one valuation rule for each wage ty pe. So for single valuation rules we cannot give 3 different percentages as req uired for STD. So here we need to create 3 valuation rules. 25 26 27 STD -1 (For first time) STD -2 (For Second time) STD -3 (For Third time) 30 6700 25

PSG abs val rule

3rd step :Define 554C table: In 554c we need to define percentage as below: 1. 100% = Paid 2. 75% = Paid and 25% Unpaid 3. 50% = Paid and 50% Unpaid The second entry is only for statistical calculation purpose and it is not manda

tory but its a best practice to maintain. 4th step PREPARE PAYROLL FOR PROCESSING PAY RELATED TO STD/LTD PLANS => CHECK AB SENCE BREAKUP FOR STD AND LTD. PCR = UMO1 IS FOR STD PLANS => CHECK ABSENCE BREAKDOWN FOR STD ABSENCE VALUATION RULE SICK PAY SUPPLIMENT RULE VALUEATION RULE START DATE END DATE P V1 V2 V3 FMLA: Family Medical Leave Act. Employee can avaiail 12 weeks of unpaid leave with out termination from employme nt 2008 is the screen number for absence type in absence configuration. 1. Employee need work in the company for a minimum of 12 months. 2. In the 12 months, the employee should work atleast 1250 Hours. 3. A valid reason should be from the list of available reasons as declared by th e government. 4. To take care of newly born child can be one reason. 5. Employee should not have any sickleave balance. Te transaction code is : PTFMLA. Only two steps for configuration available here. work Bench: Te reason we create a work bench is: 1. To enroll into 401k plan, the employee need to wait for 90 days. 2. In PA30, the system wll allow to create an entry but in work bench system wil l not allow and show a red symbol. This is the purpose of work bench. Example for work bench in Time evaluation is PT40 (Time managemnet Pool) FMLS GUIDELINES => Create FMLA Reasons: New Entries: REASON TEXT BIRTH FMCAR FOST SICK Brth of Child Car of family member Foster Care Serious Illness :01 :00 :25 :01011900 :311299999 :01 (Payroll modifier always will be 01) :25 :26 :27

DEFINE FMLA RULES: PSG = 30 (PSG for time recording) FMLA RULE = 001 Federal FMLA

From Date: 01.01.1900 End Date: 31.12.9999 Entitlement: 12 Weeks Deduction Interval = Calendar Year Eligibility check: Atleast Calculation Process working hours: atleast in last 12 Months 1SVY 1250 12 Months

X - Calculated from Planned Hours (It takes from 0007 infotype X - Calculated from Hours worked from time type (Actual working time0 Day Balance (the time type from which we need to read for this eligibility) IN THE SAME TABLE: FMLA RULES => ASSIGNMENT OF FMLA REASONS Here we define which reasons are allowed for this specific FMLA Rule type: According to the statutory regulations, we can specify the reasons for which the employee is eligible for the speified FMLA Rule. REASONS BIRTH FMCAR SICK DEFINE VALIDITY OF FMLA RULES FOR EMPLOYEES DEFINE FMLA RULE GROUP: FEATURE : FMLMO (Define FMLA Rule Group) MOLGA => EG => RETURN VALUE 20 IN THE TRAINING EG IS SALARIED AND HORLY (UPDATE THE PRACTICE CONFIGURATION ACCO RDINGLY) DEFINE VALIDITY OF FMLA RULES FOR EMPLOYEES: NEW ENTRIES: PSG FMLR RULE NAME OF THE RULE 10 (PSG For Time Recording) 20 001 FEDERAL FMLA

Here we can define the grouping for which group of employees we can allow this e ligibility. STEPS: 1. Create Reasons: 2. Define Rules:

3. Asssigment of Rules FMLA : T5U1K TABLE => FMLA DEDUCTION AND FMLA ABSENCES =>Define rules for determining weekly workin g time. PS GROUPING: 30 PS Grouping for time recording. Calculation Rule: 100 Weekly working time. Start date: 01.01.1900 End Date: 31.12.9999 x - Constant: 30 Hours (System will multiply 12 weeks * 30 Hours for the employe e FMLA leave calculation Reduction rule: No Reduction Rule or X - Weekly working hours for planned working time or x - Average actual working time (The average of parameters given below) Time type Analysis period in weeks It is weeks analysis will be numeber of weeks (-) applied date. x - Averrage planned workng time (The average of planned workng time from 0007 i nfotype with parameter given below) Analysis period in week. => Determine validity of rules for determining week converter for employees Group employees for week conversion: Feature: WWKMO (Determine employee groups for weekly conversion) SAL - 02 HRLY - 01 Define validity rules for determing week coverter for employees New Entries: PSG = 30 WGP = 02 wCOMP = 900 Desc = Weekly working time FMLARI = 001 Text: Feature FMLA The employee FMLA leave will be applied in 2001, but before applying the user ne ed to check whether he/she is eligible for that leave or not. so all this confi g is required Assign absence types for FMLA Reasons: select any of the below and select the folder permissibilit per absence type.

BIRTH FMCAR FOST SICK PSG A/ATYPE ATT/ABS TEXT FMLA PER CONT PERMITTED WITH AaCTION REASON PER INIT PERMITTE

30 0204 D WITH ACTION REASON

in case when the employer want to apply without reason, then no need to configur e FMLA separately. Just absence configuration is sufficient. This configuraton will restrict the misuse of employee useage. How to check whether an employee is eligibe for this specific leave or not: Transaction code PTFMLA Enter a reason: Select period Select the continuity: Intermittent: Gaps in between. Status: In Process Click on check reqest: if the period is more than 1 year from employee join date then he is eligible. In the result: APPLICABE TAB: Eligibility = x means not eligible and yes check mark means he is eligibile ABSENCES TAB: Click on process Absences: System wll take to PA61 Screen and apply FMLA leave for that employee. If we set approval process, then in the PTFMLA screen and set the status to appr oved from in process to get the absence visible in pa30 If the time admin is going to appove then tcode is PTFMLA_PROF or PT_FMLA_APP Wh ere the admin can see the list of applied absences for approval. Here also the admin should change the status from process to approved to see the record in 2001. For absence valuation of FMLA, We need to create and assign valuation rule for F MLA. In a scenario a future absences is applied in current month and paid in current month then we need to use custom functions in pcr. GO TO RPTM0Z00 Program.

We need tell ABAPer to use this include program. It is not directly executable. This list of custom operations or custom functions shold be written in this pr ogram. IN PE04 FOR A FUNCITON OR OPERATION: STANDARD ROUTINE FOR OPERATIONS STARTS WITH OP* FOR CUSTOM FUNCTION OR OPERATION WE NEED TO SELECT THE STRUCTURE: THE MAXIMUM LENGTH OF OPERATION IS 5 CHAR AND OPPRAND IS 5 CHAR FOR ADDZL THE STRUCTURE IS EB EB = 00000SVVVV 00000 = OPEARTION S = COMPARISION VVVV = WAGE TYPE THIS IS HOW WE HAVE TO DEFINE THE STRUCUTRE EXAMPLE: IN A COMPANY IF THERE IS NO TIME ADMINISTRATOR MAINTAINED AND WE NEED TO QUERY BASED ON SOME OTHER PARAMETER, WE NEED TO CREATE A CUSTOM OPERATION TO FIND THE TIME ADMINISTRATION. IN SUCH SITUATIONS WE USE THE CUSTOM OPERATION OR FUNCTION. THE LIST OF VALUES PERMISSIBLES FOR THE OPERATION ALSO NEED TO BE LISTED UNDER P ARAMETER TABLE IN PE04 => SELECT OPERATION => DISPLAY SCREEN. WHILE DEFINING THE PERMISSIBLE VALUES FOR OPERATION, WE NEED TO DEFINE THE RETUR N VALUE TO DIAGNOSE THE ERRORS IN THE OUTPUT. VARIABLE TYPE : TYPE OF THE OPRAND, WHETHER IT IS NUMBER OR VALUE OR ALL VARIABLE LENGTH: LENGTH OF THE OPRAND, HOW MANY CHARACTER ARE PERMISSIBLE. RPTBU00_OPERATXX (Check the exact program name for each operation) The custom opearations or functions shold start with y or z or special character s. CREATE A CUSTOM OPERATION: _ADMIN CREATE DESRIPTION: CHECK THE ADMINISTRATOR SELECT ALL COUNTRIES STRUCTURE OF THE OPERATION: EY = 00000FFFFF ADD VALUE FIELDS: PTADM MEANING TIME ADMINISTRATOR RETURN VALUE : 0 TYPE: ALL LENGTH: 3

ADD VALUE FIELDS: PYADM MEANING PAYROLL ADMINISTRATOR RETURN VALUE : 0 TYPE: ALL LENGTH: 3 If we use S in the structure we need to difine permisisble comparators in Val.S Now we need to tell the abaper that when we use the opeation _ADMINPTADM OR _ADM INPYADM go and check a spefic field. Once the program logic is written, we need to activate the program. After activating this program we need to go t program called: RPTOIP00 Click on dislpay we will find dummy series. If the custom operation is not avai lable here then it will not work. We need to ensure the structure and operation is available in this program. In payroll every country has it own custom payroll opeartions and Functions. PCBURC* is the program names where we can write custom operations for specific c ountry in payroll. The similar program used for time managemnet which we give f or abaper will be used for payroll also. VALUATE ABSENCES USED QUOTA DEDUTION: For the same absences we have two qutoa types wher ethe valuation is different f rom quota type to quota type, Here we can define an absnece type with 3 different quotas, then we need to crea te three valuation rules and assign the valuation rules in this table. We need to maintaint he values in T511K in current year rate, every year we need to create entris if there is a change. OR PCR * 9191 RTE=KPY123 MULTINRA ZERO=R ADDWT* TILL HERE WE COMPLETED THE PCR UT00 SUBSCHEMA. RAB FUNCTION WILLR EAD ABSENCE WITH VALUATION CLASS UNAB FUNCTION WILL READ THE SHORT TERM DISABILITY WITH VALUATION CLASS ALL THE ABSENCES WILL BE PRINTED ON A NEW PAGE IN AB (ABSENCE TABLE) FLSA: FAIR LABOR STANDARD ACT. In infotype 1 we have a field called Exempt: We have to maintain the status for Job to get this value visible.

It means if the employee exceed certain slary he will be exempt. TC00 : Process Time Evaluation in (Paroll)

Instead of MODT, system will user TMOD PCR in TC00 schema. Here system reads only two MODIF'S frm T555Z table and the next table. P2001 P2002 P2005 12 = Infotype 2001 with pairtype 1 and 2 1 = INFOTYPE 2002 WITH PAIR TYPE 1 1 = INFOTYPE 2005 WITH PAIR TYPE 1

TIMTP = SYSTEM WILL CHECK TABLE T555Z SINCE THIS SCHEMA READS ONLY FOR POSITIVE TIME PBKRS = EVALUATION BREAK END INCLUDING ABSENCE BIFURCATION DAYMO GWT GWT CUMBT IF 01 02 S M 02 02 = SET DWS GROPING FOR T510S

DZL = GENERATE WAGE TYPES FOR PROCESING CLASS S ML = GENERATE WAGE TYPES FOR PROCESS CLASS M

= Store overtime time wage type PDC = IF PLANT DATA COLLECTION

IN PAYROLL SCHEMA IF WE WANT TO SEE THE COMPLETE OUTPUT FOR TC00 THEN WE NEED TO USE THE OPTION TIME EVALUATION LOG IN PAYROLL SCHEMA TO TEST 2005 IN TC00 FIRST CREATE ATTENDANCE IN 2002 AND LATER CREATE OVER TIME IN 2005 IN A COMPANY IF THERE IS ANY ISSUE IN THE OUTPUT, WE SHOULD PREPARE IMPACT ANALY SIS DOCUMENT AND GET CONFIRMATION PRIOR TO CONFIGURATION CHANGES. IN TIME EVALUTION THE WAGE TYEPS ARE GENERATED IN HOURS, THESE WAGE TYPES NEED T O BE CALLED IN PAYROLL FOR PAYMENTS. PAB: Process absence Data with 554C table (Mandatory table) If there is any absences, then we will see the wage type if there is any absence applied in that day along with the basic paysplit of 0008. V_T538A is the table where we can see all the unit table like, hours, days,..... The technical name of this filed used in the configuration is ZEINH. In the output log 001 = hours read fromt he abova table, 16 is the number of ho urs for that specific wage type. The structure of IT table is different from ZL table. If want to process any pa yroll wage type, it should be in IT table. PRINT PRINT NP NP PART = PRINT ON NEW PAGE WITH PARTIAL PARAMETER. PARX = PRINT ON NEW PAGE WITH PARTIAL PARAMATER.

PART AND PARX ARE GENERATED ONLY BASED ON WORKED TIME NOT ON PLANNED TIME.

THIS HAS TO BE GENERATED NOW BECAUSE, RAB FUNCTION IS ALREADY PROCESES BY NOW. The output has both partial period facotring as well full month with comes with addition of partial period factoring. PARTA = Partial period factoring for absences only. P0416 = TIME QUOTA COMPENSATION: In 0416 do not account means do not pay in payroll but reduce quota of the emplo yee. This function is only for payroll and if we try to use it time management schema , it will prompt an error. This wage type will be read only if there is 0416 wage type maintained. P2010: Process employee reumneration info Go and create a wage type in 2010 using PA30 tcode 2010 infotype is alternatie for zl table the data read from this infotype are st ored in IT table. This will be processed based on V_T512W_B table Number hours: We can only enter the number of hours here NUmber/Unit: we can enter both number and UOM Amount: we can calculate amount outside SAP and enter the amount here in situati ons where each and every union has its own rate of calculation. Currency: The currenc of payment can be entered in this field. If the user requirement is to show the over time hours and amount on the payslp: In T511 table we need to enable both the fields as optional. So then we can sho w both number and amount in infotype. Extara Pay evaluation: Any employee who is supporting oncall, we are giving extra hourly rate 50. In Z L table we wil have actual hourly rate for every empoyee. If we use this field + 50

Then system will add 50 to hourly rate determined in payroll for this specific e ntry. 50

Then system will substract to hourly rate determined in payroll for this specifi y entry. Premium indicator: The table for premium is T510P table. This premium is paid for every hour and pay to the employee If we did't hourly rate in T512W_B also this will work

This valuation will take care of 2003 substitutons also Tax area: Work tax area where the employee worked for this specific shift. This field is for 0014, 0015, 2010 and 2002 only. External Document Number: To read each and every field in this infotype, we have a pcr in payroll schema. We have total 9 pcrs to read the functionality of 2010 infotype. In time management, the intermediatory data is stored in utility time type In Payroll, the intermediatory data is stored in variables. Variable is a 4 digit alpha numeric code. In timemanagement we need to define the time type to store the intermediatory da ta but in payroll there is no need to create a variable. We can stright away de fine the in PCR with 4 digit alpha numeric code. Example: ADDWT&1234 IF we want to call the value into that table then we need to write RTE=8, 1234 At the end of the procesing the data will be added to /001 wage type. The PCR for 2010 infotype in payroll starts with X930. Click on documentation o f X930 pcr for complete list of schemas available for this infotype 2010. X930 * **** VALBS?0 (Is there any evaluation basis for this wage typ e in 512W_B. * (If there is no valuation basis for this wage type in 512W_B AMT=BETRG (Is the amount available in am ount field of 2010) * (Means f there is amount maint ained which is great or less value) OPIND (Check the operati on indicator OBKEN) ADDWT* (Pass the amount with OBKEN indicator) = (Means if the amount is not m aintained) NUM=ANZHL (If the number is there) ADDWT* (Just pass the nu mber into the wage type table) x (If there is valuation basis for this wage typ e in 512W_B VALBS?0 0 = CURRENT WAGE TYPE VALUATION

1 = FIRST DERRIVED VALUATION 2 = SECOND DERRIVED VALUATION * = ANY VALUATION OTHER THAN x X = Yes if the value exist. BETRG = Technical Name for Amount ANZHL = Technical Name for Number BETPE = Technical Name for Rate OPIND = It will check OBKEN (Indicatory for A if negative) If we enter negative amount for deduction wage type, it will become a payment to the employee.