SAP Payroll Accounting

-----Original Message----Subject: Payroll Accounting This is the first time I am setting up system for UK payroll. We are using Citrix (Preconfigured version for UK) To build a demo, an employee was hired effective 01.01.2001, A record for Org Assignment, Planned working time, Payroll Status and Basic Pay are existing (All effective 01.01.2001). In It 0003, earliest pers RA date is 01.01.2001 and PDC recalculation date is 01.01.2001. What sequence of activities should be used if I have to run the payroll till 01.06.2001. Need a guidence on the above -----Reply Message----Subject: Payroll Accounting You do not need to do something more than usual. If you change the control record of the payroll area of the employee (transaction pa03) to 06.2001, and run the payroll afterwards, the payroll automatically calculates all the payrolls from Jan to June. i hope this will help. -----End of Message-----

Posting The Payroll Results To FICO

For posting payroll results to Accounting, in IMG you can follow this : 1 ) First you need to create symbolic accounts. goto PAYROLL INDIA REPORTING FOR POSTING PAYROLL RESULTS TO ACCOUNTING ACTIVITIES IN THE HR SYSTEM - EMP GRP AND SYMBOLIC ACCOUNTS DEFINE SYMBOLIC ACCOUNTS 2) DEFINE POSTING CHARACTERISTICS OF WT ( ASSIGN WT TO SYMBOLIC ACCOUNTS)

3) goto PAYROLL INDIA - REPORTING FOR POSTING PAYROLL RESULTS TO ACCOUNTING - ACTIVITIES IN THE AC SYSTEM - ASSIGNING ACCOUNTS - ASSIGN BALANCE SHEET A/C AND ASSIGN EXPENSE A/C 4) EASY ACCESS - HR - PAYROLL-INDIA - SUBSEQUENT ACTIVITIES - PER PAYROLL PERIOD- EVALUATION - POSTING TO A/C-EXECUTE RUN The prerequisite for posting is -Enter posting information in Master data and run payroll. After doing that follow this posting process:a) Create a document b) release document ( it asks do u want to release for posting-say post immediately) c) post document Though the t.code FB03 you can do completeness check of the document. Now execute the posting run - a posting run can be performed as a test run without documents / a simulation run / a productive run. In a simulation and production run the system checks all HR and FI tables and the posting info in master data to determine whether they exist. In a test run the system checks only the balance of expenses and payables. Now you chose execute run - next select release post run - now post post run - finally it generates index info. Tips by : Aruna Rani I have to create a new wage type for additional payments. This has to look at a payroll constant and calculate the amount to be paid. What I would like to know is when I do this do I have to do anything so that the amount in this Wage Type will be posted to FI like create a G/L ? Or will this be posted automatically along with other wage types? If you are copying wage type xxxx to create your new wage type for additional payment, there is a chance that your posting will take place similar to wage type xxxx. Rest is pure config in payroll. There is a full section for it. Symbolic accounts...... G/Ls....Accrual A/Cs.... pretty involved stuff. Without a FI guru with you ...I won't advise proceeding forward. *-- Bijay

That depends on how you create the wage type. The link is done in some T52E* table, which is for instance copied by PU30. If you create the wage type by creating it directly in T512W (via view V_512W_T), then you will have to do the link additionally. The standard way to create a wagetype is however to find a corresponding wage type, which has the same (or similar) functionality as the one you want to create and then use PU30 to copy this wage type to the new wage type. Thereby a lot of tables (I think in the newest, 4.6C, it's around 95 tables) are checked and if needed the entries are copied. Amongst those tables you will also find the ones establishing the links to FI's G/L. *-- Thomas. Following comments relate specifically to 3.1H. They may or may not apply to your system. Normally a new wage type is created by copying an existing wage type, either a model wage type that has some standard attributes, or an existing actual wage type in production use. Your config changes will need to set up the new wage type so that the amount is derived from your payroll constant. However, the posting to FI will have been copied from the wage type you copied. The posting is represented by processing class 32 and evaluation class 01 (of table T512W) for a payment wage type. Provided the new wage type is similar in its posting requirement to the one you have copied you only need to do two things now: 1. ensure that processing class 32 is the correct option for the type of posting you want. 2. ensure that the value in evaluation class 01, also known as a symbolic account, correctly represents the target account number in FI for this expense. If you have to post to an existing account number, for which there is already a symbolic account allocated, you can set evaluation class 01 to that symbolic account. If the payment is so different from existing payment types, that your accountants want it posted to a new account code, you need to 3. allocate a new symbolic account number (next available number in the range)

4. insert a new entry in table T030, "Posting of HR to FI/CO", linking the new symbolic account to the account number advised by your FI administrator. It's actually easier to do than describe. *-- Andrew

One payroll for two month

An option will be to run the payroll for November in December and then December in December. Then in February run for January and then February payroll. Retro to December can be forced on the payroll run screen. You will find a field called "Forced Retro to" It means you would have two payroll results and two DME files in December and then again in February. You could try exiting November without running and then run December. You should find that it will detect that November has no results and auto retro to November. But need to ensure you have not been in corrections for November, otherwise the system will say employees in error (which you can change the status of the individuals - if not too many). Another option is to delete the control record (if the above option doesn't work) and recreate to have next payroll in December but still with your original retro period. You should test these in your user acceptance system to ensure there are no side effects.

Day types
-----Original Message----Subject: day types Hi, The client organisation works on 1st and 4th Satuarday of every month , and 2nd and 3rd satuarday are off. Please tell me how to create Period work schedule for this . -----Reply Message----Subject: RE: day types

Hi, It's very simple. you should use the week number in period work schedule and declair this work schedule 4 time one for each week. -----End of Message-----

Sunday not being considered as a regular working day

The requirement for work schedules is that there are no Saturdays and Sundays, just a 6th day/Day-off and 7th day/Rest day. My employee's planned working time is from Sunday to Thursday, with Friday and Saturday as 6th and 7th day, respectively. However, when I test my employee for overtime rendered on a Sunday (which should be considered as a regular working day), there is no OT calculated for Sunday. The daily work schedule for Sunday can be seen in the employee's PSP table, but no OT time wage type is generated in the table ZL. Is there something I am missing. Will deeply appreciate any help that can be given to me. You can check Day Type selection rule - perhaps it is ssuch that for Holiday class blank on a sunday, day type 1 is selected. You can either change the day type selection rule, or for this particular employee, you can enter substitution record on a sunday as a day type "blank". Then Time Eval should calcluate OT as if it is a normal working day. Another alternative is in the schema you can include a rule, which checks if employee is at work in Suunday and give the DAYPG as paid working day. Essentially, I think it is because of the day type you are facing problems and there a re a few ways to solve this. But I have configured the day type selection rule for Sunday which is the same for the weekdays and Saturday, that is all 1 for holiday class 1 to 9 and holiday class b is blank. If I fix the problem through the schema, where in the schema and what kind of a condition should I set up? I'm very familiar with PY schemas and rules, but I have to admit that I am not too knowledgeable about Time Mgt. I sure hope that you can help me because this problem has been giving me a big headache for the past few days.

On a re-reading of your problem, I see that you have stated that the Wagetype is not being generated in the table ZL - Maybe you should relook at your wagetype selection rule table t510s. Here also you set the conditions of the day for which the wagetype is applicable - whether you have set that it is ok for wagetype to be generated on sunday? Also check what you have set for the function DAYMO in schema TM00 - DAYMO has 4 parameters - the second and fourth are for Sundays - based on what you put here, schema will read corrsponding rule from table T510S. Is there a correspodning rule for Sunday in T510s???? I am giving below the place where the dws is changed iin the schema, but you can try that as a last resort if the above config is not working out. ---------------BLOCK BEG Provide time data IF NOT SIMF No simulation for future periods PERT TD20 Evaluate errors from pair format P2011 Provide time pairs and daily WS ACTIO TD10 End if daily work schedule still A2003 Process work center substitution ACTIO TD60 AB Convert daily WS if RWH and leav P2001 Provide absence data of the day P2002 Provide attendance data of the d PTIP TD80 GEN Process absence/attendance reaso ACTIO TD90 Process generated locked records P2005 * Provide overtime data of the day PTIP TD40 GEN * Set PTYPE/TTYPE for overtime ACTIO TD30 Dynamic DWS assignment: Clock-in ---------I have pasted the xtract of TM00 above - Just after we have imported the planned working times and actual working times, there is the line ACTIO TD60 - please have a look at rule TD60 You can make a copy of this rule, with your own requirements - Rule TD60 checks if there is a leave and changes the DWS for that day. Pl look up the documentation for the operation DAYPG. You are so good!!!! It was the day grouping settings at the function DAYMO in the schema that did the trick. I copied the line and placed all 01 in the parameters. Finally, overtime wagetypes for Sunday are being generated and can be seen in the ZL table.

Question on Payroll Journal Report for Print Forma

Technical Question on Payroll Journal Report for Print Forma I need to know how and where to find a Print Format Form I'm executing Payroll Journal Report, there is a option of how to display the report which SAP call as Print Format. then you select form to display. it's not SAPSCRIPT ok. Does anyone know where to find that form, and display. Transaction PE51 (Form Editor). ----Payroll Journal - Totals Section I would like to insert new wage types in the payroll journal. Since the forms for the details and totals section are different. I have inserted the new wage types in both the forms using PE51. However, the new wage types are only appearing in the details section and not the totals section. Is there any other configuration that I have to do? You must cumulate yours wgtype in **** in order to have column with this certain wgtype in totals. You must define this wgtype **** as cumuilation wgtype only on detail page level. On total page you just put wgtype that you going to see as normal. Thanks for your help. Now, it's working. The wage type should be added in the cum. ID **** for both the forms namely details and totals. ----Unable to add wage type to the total display of Payroll Journal

I am not able to add a wage type to the total display of the payroll journal. there is a form in which I added this wage type for the display. But, it does not display on that journal. Can you please give me some ideas how to resolve this issue? Have a look at V_512W_D and check the Evaluation Class (2) for your wage type. If the value is blank, it will not be displayed in your form, even if the wage type is specifcally defined in your form. You need a non-blank value for your evaluation class (2) in order to print. The Eval Class for that WT already has the value 3 (Earnings) in it. Can you please tell me what else to look for? The Payroll Journal uses 4 separate forms for the print format (1) Page Header (2) Continuation Excerpt (3) Employee Data Excerpt (4) Totals Block Did you add your new wage type to both (3) and (4) print formats? Be aware that in the totals form, with the cummulation ID's, all wagetypes that you want to have cumulated are: 1) Assigned to a cumulation ID of choice and 2) also assigned to cumulation ID ****

Creating Customer Specific Functions for HR Payroll

During the execution of payroll, 'Personnel Calculation Schema' (created using Transaction: PE01) is used to calculate the employee's salary. The schema comprises of funtions (created using Transaction: PE04), inorder to incorporate cutomer specific calculation routines during execution of payroll, SAP allows you to create payroll functions in customer namspace (Starting from Y or Z). Step by Step creation of SAP Payroll Funcitons:

1) Follow the menu path Human Resources>>Time Management>>Administration>>Tools>>Funtions/Operations or transaction PE04. Enter a four digit name for e.g ZIABC, and press the create button, enter the description. On creation the system proposes the name of the routine use it, or enter a name of your choice by selecting the option 'Selfdefined'. 2) During the execution of payroll some tables are filled with wage types and there amounts to make these tables available to your routine enter the name of the table for e.g (RT or CRT) in the input parameters, and to make the changes done to the data in the tables avaiable to the payroll enter the name of the table in the Output parameters as well. Input Parameters ---------------Ctry Num Object Name ---------------------------------------------------------------99 1 RT 99 2 CRT and same shall be done in the Output Paramters if required. 3) Create an include in the program PCBURZ990 (using Transaction: SE38), in which create a subroutine with the name supplied by SAP or the name selected by you during Funtion creation, in our case, it is FUZIABC. Note: The program PCBURZ990 is in SAP Namespace, so an Access Key will be required before you can proceed. But it will not be overwritten during any upgrade.
*Example of the subroutine *-------------------------

FORM FUZIABC. *enter the code ENDFORM.

4) After this activate the program the Funtion and add it in the schema used for payroll processing.

General Idea About UK, US, Indian Payroll

These are the differences among Indian, U.K and U.S payrolls: Differnce between the US and Indian payroll can be broadly categoried on two basis :-

1. For Contract Employees 2. For Salaried Employees For salaried employees, mostly the norms are same, but most of the employees are on contract basis Therefore their classification is mainly on two grounds W2 and 1099. In W2 company pay the taxes and in 1099 employee pay the taxes. The contract employee fee is mainly based on hourly basis for which they are billed. But the vendor takes care of the contract employee salary. This means the company send a time sheet to the vendor and vendor then makes the payment to employee. SAP has given country specific payrolls for more than 38 countries and periodically SAP is releasing the country versions for new countries Each country specific version is called country version. When sap says country version it includes country specific civil, tax laws, contributory and other tax laws (all these details are populated in the country specific info types). Pay roll driver and Schema: - For each Payroll country version there is a country-specific payroll driver with the technical name RPCALCx0 or HxxCALC0 . - For programs with the technical name RPCALCx0 , the x is replaced with a country indicator, for example, Z for South Africa D for Germany, , or X for "Other countries". - For programs with the technical name HxxCALC0, the xx is replaced with the ISO code of the respective country, for example MX for Mexico, or G.B for U.K. Pay roll schema: - The payroll schema contains calculation rules to be used by the payroll driver during payroll. SAP has developed country-specific schemas which are based on standard schema X000. When it is country specific ,the first character in the name refers to the country indicator (for example, G for U.K, F for France D for Germany etc.). When you run any countrys pay roll in the sap system some common info groups which are part of international pay roll and personnel administration.

Some of them are: - Personnel data ( address-6, bank details97 personal data-2,challenges-4 etc..) - Actions ( 0000 info type) - Organizational data - Contractual and contract agreements (Company Instructions info type 0035 , Corporate Function 0034 ) Etc., So when run a pay for a specific country, besides general information valid for the international pay roll, one needs to enter specific details in the particular info types for example if you are running U.K pay roll you need enter The National Insurance number (NI number) used by the Contributions Agency (CA) to uniquely identify an employee in the info type 0002-personal data and if its U S pay roll there is social security number and if its south Africa it some SARS code etc.. all these are available in personal data-national features. Apart from these they are some country specific info types for each country pay roll. For U.K pay roll there are some specific info types: - Tax Data Info type 0065PAYE (Pay as you earn) details are stored - WFTC/DPTC Info type 0087- employees tax credit details are stored - National Insurance Info type 0069 National Insurance Info type 0069 - Pension Funds Info type -0071 - Court Orders/Student Loans (info type 0070) record for them with the appropriate court order subtype - Court Orders/Student Loans (Info type 0070): to record and deduct student loan repayments as specified by the Inland Revenue. - Company Cars- Info type 0442 - Offshore Tax GB -Info type 0570 This info type allows you to record an employee's tax details for Isle of Man, Jersey, or Guernsey and Alderney Offshore Social Security GB -Info type 0571 to record an employee's social security details for Jersey or Guernsey and Alderney. Then there is SMP SSP details specific to U.K pay roll: - SMP is Statutory Maternity pay. - SMP is Statutory Sickness pay - SAP -Statutory Adoption Pay and - SPP- Statutory Paternity Pay. The rates for SMP,SSP,SPP and SAP vary, so accordingly they need to be updated with the latest changes. Every year like Indian Tax rates , there in U.K also changes take place with regard to Tax slabs ( which needed to be reflected in PAYE.. Pay as you earn), civil and social and tax laws. In fact from Oct 2006 this year, there are going to be many changes in the various laws related to employees in U.K All this

need to be populated in respective info types. Like wise U.S pay roll has got some specific info types which are large in number as it has a complex system in place. This is general idea about U.K pay roll.

What Is The Difference Between PCR and CAP

Personnel Calculation Rule:(PCR) It is the instructions to execute defined tasks in Time Management and Payroll. A Personnel Calculation Rules consist of one or more operations. It also contains one or more subarea. A personnel calculation rule is a frame of work instruction that is checked with the existing conditions and a resulting action is performed. The Personnel Calculation rule allows one wage type to be processed in different ways in payroll accounting. The value of the standard pay wage type should be used as a basis of valuation for hourly wage earners. The value of the standard pay wage type should be divided by the planned working hours before being used as a basis of valuation for salaried employees. 1 Hourly wage earner 2 Monthly wage earner 3 Salaried employee Collective Agreement Provisions: (CAP) A standard agreement designates the same pay scale groups and level for both hourly wage earners and salaried employees, however the user must still be able to enter hourly or monthly values in the pay scale table. 1 Industrial workers / hourly wage 2 Industrial workers / monthly wage 3 Salaried employee 4 Non Pay scale employees 5 Public servant

Explanation on Deduction Rules

Deduction Rules rules according to which attendances and absences are to be deducted from the attendance/absence quotas. EXAMPLE: Total Abscence Quota is 20 , in that 20,

Casual leave -05, Sick Leave-10, Privilege Leave-05 Now when the Employee applies for leave, which of these leave will come to picture FIRST i.e the deduction sequence from abscence quotas is determined through deduction rules.Whether first it will be deducted fromPL , OR CL OR SL Sequence in which attendance and abscence has to be deducted from Attendance and abscence quota is based on the following criteria: 1. Attendance/absence quota types 2. Start and end of validity period of the quotas-Until which date the quota is valid 3. Start or end of quota deduction period PERIOD IN A YEAR IN WHICH QUOTA DEDUCTION IS POSSIBLE Deduction Priority: Here you enter the criteria, according to which sequence the system should sort existing employee quotas to make them available for deduction. You can enter the priority levels 1 to 5 for the criteria quota type, start of validity period, end of validity period, start of deduction period and end of deduction period

Configuration In Generation Of Absence Quota

By : Ravi Kanth Vadla Steps to generate Absence quotas: Absence quota: 1. Group personal sub areas for Attendances and Absences. Time data recording - Time management Menu Path: SPRO --> Group personal sub areas for -->Absence catalog -->Absences -> administration Attendances and Absences. Here, first you need to do PSG grouping for Attendances & Absences. 2. Define Absence Type Menu Path: Time Absence --> Absences --> Time data recording and Administration --> Management Define Absence Type --> catalog Click on New Entries; Create an Absence type with a 4 characters code. 3. Determine Entry Screens and Time Constraint Classes Time data recording Menu Path: Time Management --> Determine Entry Screens and Time --> Absence

Catalog --> Absence --> Administration Constraint Classes. Here find the Absence Type that you have created. Click X on Magnifying glass or Ctrl+Shift_F2. Here, by specifying the screen number for attendance type and absence type, you determine which screen is to be used for entering, displaying and maintaining records. Select screen number field and press F1.Give screen number that suits your requirement. Quota Ex.2001 deduction No quota deduction 2051 4. Define Counting Classes for Period Work Schedule. Time data recording Menu Path: Time Management Define Counting --> Absence Counting --> Absence Catalog --> Absences --> Administration Classes for Period Work Schedule. Here, select your PWS and give counting class range 01-09. Counting classes: Counting classes for PWS are used to evaluate absences& attendances. Use different counting classes for PWS with long DWS &many Dayoffs.When you maintain a counting class you must define a separate rule for each Counting class.) For Employee sub groups 5. Group Employee sub groups for Time Quotas. Time data recording and Administration Menu Path: Time Management --> Rules for absence counting (New) --> Absence Counting --> Absence Catalog --> Absences Group Employee sub groups for Time Quotas. Here select you Employee group & Group Employee sub groups for Time Quotas give number ranging from 1-9. For Personnel sub areas 6. Group Personnel sub areas for Time Quotas Time data recording and Administration Menu Path: Time Management --> Rules for absences counting (New) --> Absence Counting --> Absence Catalog --> Absences Group Personnel sub areas for Time Quotas. Here select your & Group Personnel sub areas for Time Quotas give number ranging from 01-99. 7. Define Absence Quota Time data recording Menu Path: Time Management Time --> Managing Time Accounts using Attendance/Absence Quotas -->Administration --> Define Absence Quota Types.-->

Quota Types Definition of Absence quota: Here we define valid absence quota types with 2 digit code (entitlement to time off & leave types) for your employee group& personal sub areas grouping for time quotas. Why we define Absence quota, because, in this we define unit of time measurement whether you want the entitlement to time off to be maintained in Hours or in Days. 8. Permit Quota Generation without Time evaluation Time data recording and Administration Menu Path: Time Management Calculating Absence --> Managing Time Accounts using Attendance/Absence Quotas --> Permit Quota Generation --> Automatic Accrual of Absence Quotas --> Entitlements without Time evaluation Here we define, to transfer the left absence quota for next year or not. Select the Absence quota and click No generate (Radio button). 9. Specify Rule groups for Quota type selection. Menu Path: Managing Time Accounts --> Time data recording and Administration --> Time Management Rules for Calculating Absence Entitlements using Attendance/Absence Quotas --> Specify Rule groups for Quota type --> Generating Absence Quotas selection. Here we give one 2 digit code (01-99) for quota type selection, that what we mention in QUOMO feature. 10. Set Base Entitlement Time data recording Menu Path: Time Management --> Managing Time Accounts using Attendance/Absence Quotas --> Administration Set --> Rules for Generating Absence Quotas --> Calculating Absence Entitlements Base Entitlement. Select Base Entitlement for Absence Quota Generation and Click on Choose: button Click on --> New Entries --> to enter the data. Base Entitlement: Why we define this is, here we evaluate number of eligibility days for the Absence quota. And we assign this to Absence quota that we created earlier. 11. Determine Validity and Deduction Periods. Menu Path: Time Managing Time Accounts using --> Time data recording and Administration --> Management Rules for Calculating Absence Entitlements --> Attendance/Absence Quotas Determine Validity and Deduction Periods.--> Generating Absence Quotas Click on New Entries to enter the data. We define Validity & deduction periods, as you want to define as per calendar year, Accrual period etc.

12. Define Generating rules for Quota Type Selection. Time Menu Path: Time Management Managing Time Accounts using data recording and Administration Rules for Calculating Absence Entitlements --> Attendance/Absence Quotas --> Define Generating rules for Quota Type --> Generating Absence Quotas Selection. 13. Define Deduction Rules for Absence and Attendance Quotas Time data recording and Administration Menu Path: Time Management Quota Deduction Using Managing Time Accounts using Attendance/Absence Quotas - Define Deduction Rules for Absence and Attendance --> Attendance /Absences Quotas Click on New Entries to enter the data. We define deduction rules according to which attendance & absences are to be deducted from the Attendances & Absence quotas. Actually the quota deduction did not depend on individual Absence/Attendances types, but it is determined by the counting rules for Absences/Attendances that are counting rules assigned to an Attendances &Absences types Select Define deduction Rules for Absence Quotas and Click on Choose button. Go and Click on New Entries and enter the data 14. Define Counting rules Time data Menu Path: Time Management --> Absences Counting --> Absence Catalog --> Absences recording and Administration Define Counting Rules --> Rules for absence counting (New) Click on New Entries; enter the data as of your requirement. Counting rules: We define counting rules for counting Attendances & Absences. The rules are used to determine the payroll days & hours for an Attendance & Absence type. The payroll days and hours that have been counted are used to control the deduction of 15. Assign counting rule to Absence type Menu Path: Time --> Absence Catalog --> Absences --> Time data recording and Administration --> Management Assign Counting rules to Absence Types --> Absences Counting 16. Set Personnel Sub area groupings for Time Recording Menu Path: Time Set Personnel Sub area groupings for Time --> Time Evaluation setting --> Management Recording. Select your personnel sub area and give the 2digit code, for grouping and give the same digit for Personnel Sub area groupings for Time Recording. While creating the

Attendance /Absence type. Run Absence quota: The Transaction code to run Absence quota is SE38.In SE38 we generally use to run the SAP Reports. Give SE38, and give report RPTQTA00, to run Absence quota. Then Execute it....

BSI Communication Failure During Payroll Run

I am facing the problem while running US payroll in processing, the error message shows BSI communication failure. By : Venkat BSI Communication Failure: 1. BSI is a tax interface. You need to disable the tax calculation or configure the BSI interface (In real time configuration BSI is already there). 2. Do transaction code PE01 3. Copy schema U000 to TZ00(Any name) 4. Generate main schema (Press generate button) 5. Copy schema UTX0(Calculate Tax) to UZZ0(Any name) 6. You may Generate subschema 7. Open newly copied subschema (UZZ0). 8. Comment out the USTAX and UTPRI function. (Disable) SAVE 9. In PE01 enter Schema TZ00 press change 10. In TZ00 replace the UTX0 function to your newly copied UZZ0 SAVE it 11. Run the Payroll Driver again by using Schema TZ00 That should do it! By : Mike 1.) Firstly in Tax Factory 8.0 issues check system BAT/CSH file. If the OS is Microsoft Windows then it is a BAT file, in case of UNIX systems it is a CSH file. This "batch program" is called by RFC connection and runs the Tax Factory Engine. 1.a) Windows Scenario: The bat file should be set like the following example: 1.) SET TF80_CONNECT_STRING=DSN=TF80;UID=TF80;PWD=bsi; 2.) SET TF80_SCHEMA_NAME=TF80DB.TF80SCHEMADB

3.) errors.txt in gateway working directory 4.) C: 5.) CD C:\BSI\ 6.) in same directory 7.) tf80server.exe %* DSN = ODBC connection. Example = "TF80". UID = Tax Factory 8.0 Database user. Example: "TF80". PWD = Tax Factory 8.0 Database password. Example: "bsi". (Line 2) "TF80DB" = Database's name. (Line 2) "TF80SCHEMADB" = Database Schema's name. (Line 5) Location of tf80server executable file (same place of bat file). 1.b) Unix Scenario: The Csh file should be set like the following example: #!/bin/csh # set execution environment for TaxFactory 8.0 set oracle environment variables grant database rights to users who invoke this # setenv ORACLE_SID ORCL#Replace with your Oracle SID setenv ORACLE_HOME /usr/sap/oracle/product#Replace with your OracleHome setenv LD_LIBRARY_PATH /usr/sap/oracle/product/lib#Replace with $ORACLE_HOME/lib # set the directory path for BSI setenv BSI_DIR /usr/sap/{SID}/SYS/exe/run/#Replace with appropriate path unsetenv NLS_LANG unsetenv ORA_NLS33 change directory to the TaxFactory server directory cd /usr/sap/{SID}/SYS/exe/run #Replace with appropriate path # #set the TaxFactory default database connection setenv DATABASE tf80/bsi@ORCL #Replace with your Oracle Connect #

for SAP trace debugging, uncomment below & see file error.txt in same directory ./tf80server $1 $2 $3 -o error.txt else for usual operation ./tf80server $1 $2 $3 end file 2.) The Tax Factory database user MUST has access to database and a valid password. You can test this in a lot of different ways: 2.a) Connecting directly to database with the Tax Factory Database User for testing purposes. 2.b) Testing the ODBC connection with the Tax Factory Database User Normally the path is Control Panel - Administrative Tools - Data Sources (ODBC) 2.c) Sometimes the dabatase does not allows database account logon (Only Windows Account logon), so it will not possible to test connecting to database using the Tax Factory Database User. In this case you need to connect on database with an Windows Account Logon (with administration permission) and then check if the Tax Factory Database User exists, password is not wrong, user is not locked, user has all permissions to access the tables, etc. 3.) The database's schema MUST be the same mentioned in the bat file. Normally you can check the database schema in the properties of the database (inside of your database program administration, for example SQL Enterprise Manager is the program for Microsoft SQL 2000 database). 4.) The ODBC connection MUST has set the default database your BSI database. 5.) Tax Factory Program must has created the "Data Set", like the following example: Example: System ER5 Client 110 So the "Data Set" will be 110 More information please check note 1068271 section 17 (Q. What is a dataset in TaxFactory 8.0?).

6.) The RFC Connection must target the BAT file and not the executable file and the RFC's name MUST be "BSI80-US-TAX". 7.) Sometimes the problem/dump persists so it will be necessary to create/analyse the log files. To create a test lof file you need to change the bat file to look like this: SET TF80_CONNECT_STRING=DSN=TF80;UID=TF80;PWD=bsi; SET TF80_SCHEMA_NAME=TF80.TF80 errors.txt in gateway working directory C: CD C:\BSI\ in same directory tf80serverdebug.exe %* <<< CHANGED LINE >>> This executable file will create a log file in the same folder describing his problem, then you will be able to analyse the results, if it is a RFC problem, permission, Data Set not created, etc.

Holiday Calendar Setup For HR In ECC 6

SAP HR Ticket: I have been creating a number of work schedules and when generating them have noticed that the Bank holidays in May and August are not pulling through from the Holiday Calendar however, all other public holidays for Great Britain are e.g. Christmas, New Years and Easter. I have displayed the Holiday calendar in question and viewed the definition and all public holidays are set up from 1990 - 2098. I have also clicked on the 'Display Calendar' icon and the May and August bank holidays are set up for 2008 however, when I view 2009 they are not set up. How can I set the May and August bank holidays up for 2009 and ensure that are available in all work schedules? Please follow the whole configuration of the holiday, then, the creation of the DWS and the PWS. For this, start checking in SPRO -> Time Management -> Work Schedules -> Define Public Holiday Classes

SPRO -> Time Management -> Work Schedules -> Daily Work Schedules -> Define Rules for Variants SPRO -> Time Management -> Work Schedules -> Day Types -> Define Selection Rules SPRO -> Time Management -> Work Schedules -> Work Schedule Rules and Work Schedules -> Set Work Schedule Rules and Work Schedules Those are the main points related with the holiday configuration in a PWS. After this, generate the PWS. --The bank holidays for 2009 may be set up as "moveable holiday" which requires you to enter the date in the public holiday for 2009, if you have 2010 dates you can enter those as well. You can check these via tcode SCAL, after you make changes to the public holiday/s all work schedules that use the calendar/s for the public holiday need to be generated. Remember to transport the calendars once you have changed them, calendars are not automatically added to a transport when you make a change, its a manual processes. If the Bank Holidays are fixed dates, then check the holiday calendar end date and end dates for the public holidays assign to the calendar ( tcode SCAL), end date could be 2008. --To create work schedule, just get in tcode PT01. In there, you create and you can check in PT03 the result. If in there is not appearing the new holiday that you created before, there is a problem in the configuration, you may have to check in SCAL the public holiday class of the holiday, then, check the rule variant in the DWS and PWS. --The following are what have work on my system:
y

Inserted 2009 and 2010 public holiday dates for Easter Monday, May Day, Spring Bank Holiday and Late Summer Bank Holiday into the public holiday Calendar and saved the data.

y y y y y y y y

Assigned the public holidays to the Holiday calendar in question and saved the holiday calendar. Displayed the holiday calendar for 2009 and 2010 to check dates being brought through. Some public holiday's were being displayed twice, so I deleted these assignments. Saved the holiday calendar and rechecked calendar for 2009 and 2010 . I transported the public holiday and holiday calendar. Created a work schedule using PT01 . Checked public holidays were being brought through. Displayed work schedule using PT03

Payroll Questions and Help Required

What is the use of processing class and evaluation class and how it will be applied in payroll? Processing Class: There are different processing classes for the various processing steps that are performed within Payroll. During the payroll run, the system processes a wage type in a specific processing step according to its individual specification in the respective processing class. Evaluation class : Its an Wage type characteristic that controls processing when payroll results are evaluated and displayed. There are various evaluation classes for the different processing steps that are performed when payroll results are evaluated and displayed. During an evaluation, the system processes a wage type in a specific processing step according to its individual specification in the respective evaluation class. How to assign allowances & its amount direct to position so that once employee fill up that particular position automatically he/she will receive the allowances and when he transfer to other position automatically the allowancess delimited? Maintain IT1005 - Planned Compensation to all the positions. Here every position will be assigned to a Payscale area type, grade and level. Accordingly, in IT0008,

relevant wage types will pop up for the person to whom the position is assigned. What is the diffrence between RT table and cluster table? RT Table: The purpose of RT Table is to store the wage types and its various attributes and to update the cluster table PCL2 as per its contents. The function used here is PRT. Cluster Table: A data cluster is a grouping of several data objects. Elementary fields, field strings and internal tables can be grouped in a data cluster. Clusters B1 and B2 in files PCL1 and PCL2 are relevant to time evaluation, as is cluster PS, which stores the generated schema. When we enter the amount in wage type components in IT0008, in which table its going to store? IT0008 - Initially it will sits in the Internal Table PIT. I have to assign a holder to a position 'A'. Then hire a new employee with supervisor as the holder of position A. Later on change the holder of position A. Go to Simple Maintenance in Expert mode of Org Mgmt,there you will find PPOM_OLD change. In that you can assign a holder to a position by clicking the staff assignments tab and then assign holder tab.

Procedure To Design Payslip

How to create custom hr form using PE51 and how to give print option for that form? by: Sai Narayana Procedure to design payslip 1. Goto PE51, Enter the Country grouping for which you wish to design the form and give a name to the form...and press Create button.

Enter the form class as CEDT.....for Remuneration Statement. Give the form name and Save....the Attributes for the payslip will be saved. Next: 2. Design the background how the payslip should look alike... 3. Maintain the Single fields, where the values to appear using table names & fieldnames..... 4. Maintain Windows...this is to group any items to appear within a window...for ex., Earnings to display in a window.... 5. Check Line Layouts....how the field values should appear in the payslip.. 6. Maintain Cumulation IDs... 7. Maintain Text IDs.....for texts to be displayed: for ex., Emp Name, Org. Unit, Position, Company.....etc....you maintain these text names in this Text IDs section & select those as Single fields in Step 3. 8. Maintain rules, if any, to be considered... And to print the payslip, you can view the Print button on the Menu bar. Go to PC00_M99_CEDT - Remuneration Statement, enter the details and press Execute, you will find the Payslips.... On the menu bar, you will find Print Symbol....Press it and select the Printer......You can get the printout for the payslip....

Short Overview of SAP Payroll

By: Raju Schemas and Functions In SAP Payroll, functions provide the high-level logic for payroll calculations. Functions perform general processing such as calculating payroll taxes on a given set of wages, reading wagetypes from specific infotypes, calculating benefits premiums, and storing the results of the payroll calculation. There are dozens of functions in SAP payroll, some are country-specific and others are not. Each function

is defined and documented via transaction PE04; you can also view the function documentation via transaction PDSY in releases 4.5 and greater, or with report RPDSYS00 in earlier versions. In SAP HR terms, a payroll function is not the same as an ABAP function. A payroll function does consist of ABAP code, but it is not executed in the same way an ABAP function would be. Payroll functions are executed within a schema by the payroll driver program (lets assume RPCALCU0). A schema is just a collection of functions executed in a specific order each one passing its results on to the next. Schemas are always created and edited via transaction PE01, but are actually stored as a collection of rows in tables T52C0 (SAP standard schemas) and T52C1 (customer-created schemas and modified SAP-standard schemas). The payroll driver reads the lines in T52C0/T52C1 and executes the functions one by one. So how do we make the leap from a payroll function stored in a table to the execution of ABAP code to get the work done? In transaction PE04 you can see the ABAP code associated with every function. The function name in the schema correlates to an ABAP form for example payroll function WPBP maps to the ABAP form fuwpbp; function USTAX maps to form fuustax. So when the payroll driver is executing the schema, it takes the function name from the current row in schema, puts an fu on the beginning of the name, and then does a perform statement on it. Its a very simple and elegant design. Wage Types In a broad sense, a wagetype simply holds a piece of data a rate, number, and/or amount. But more specifically, a wagetype has dozens of attributes that control how it is manipulated and processed. In the end though, it ends up as an object in the payroll results database that stores a rate, number, and/or amount. The most typical use of a wagetype is to store the amounts of earnings, deductions and taxes in an employees paycheck. A persons base pay is stored in a wagetype, the amount of their United Way deduction is stored in a wagetype, and their taxable wages & taxes are stored in wagetypes. Wagetypes, as the primary data element for employee paychecks, are also mapped to FI/CO accounts to record the debits and credits resulting from the paycheck and reported on the W-2 and other tax forms. Wagetypes can also be used to store statistical data such as the number of hours worked in a pay period, the average weekly wages for the past six months, or the amount of wages eligible for a profit sharing calculation. Wagetype attributes are

stored in several tables, but the central table is T512W. Much more time will be spent on various aspects of T512W. There are three categories of wagetypes model, technical, and user. Model wagetypes are delivered by SAP for customers to use as guidelines for creating their own wagetypes. They always start with a letter and SAP may add, delete or update them in system upgrades or HRSPs. Technical wagetypes always start with the / symbol, and are delivered by SAP. They are intended for very specific standard processing in payroll, and while you can modify them, SAP may also update them during upgrades or HRSPs. So if you ever (I mean EVER) change a technical wagetype, check it after each upgrade or HRSP to make sure it still has the attributes you want. And never delete a technical wagetype. User wagetypes always start with a number and these are wagetypes that SAP does not change during upgrades & HRSPs. OK, SAP rarely changes them in upgrades and HRSPs. User wagetypes are for all the company-specific payroll payments and deductions. Rules and Operations A long-time client of ours once created a screen-saver message that stated Payroll Rules!. Those of us who were experienced SAP Payroll analysts or consultants immediately saw the double meaning, and corny humor, in that message. Rules contain the most basic logic used in SAP Payroll. Where a schema is a collection of functions, a rule is a collection of operations. An operation is a very basic piece of logic that is used, mostly, to manipulate wagetypes. For example, operation MULTI multiplies the number and rate fields of a wagetype to determine the amount to pay an employee. Operation OUTWP retrieves specific data about an employee so that another operation can make a decision on how to process it. For example, if the work contract on infotype 1 is UA then do x, if it is UB then do y, otherwise do z. Operations can also be viewed in transactions PE04 and PDSY, and are edited with transaction PE02. Where a functions ABAP equivalent form starts with fu, an operations ABAP form starts with op. For example, operation MULTI would have an ABAP form opmulti. Rules, like schemas, are stored in a table rules are stored in T52C5. The more senior SAP consultants who have been working with computer systems for many years often find similarities between payroll rules and programming mainframe computers in Assembly language. While there is nothing fancy about operations, when used correctly together they can be very powerful.

Hold Loan Deduction for a Specific Period

If an employee has a loan and he can't pay for a specific month. How can I stop loan deduction for that month? by: Bela Pathak You would do as follows: SPRO->PA->Payroll data->Recurring payments and deductions-> Wage types-> Create wage types catalog Select Delete (don't worry you won't delete). Select your loan under Wage type column, uncheck Test run, and at the bottom of the screen, you would select the radio button: Limit Wage type acc to time until (enter the date you want it to be delimited here). Then highight your loan and press delete (don't worry, it won't delete, but will give an end date). You will see message that it has been updated in all the wage type tables etc such as: T511, T512W, T512Z etc. Now go to check wage type text and you will see loan has an end date of ....what was entered above. Now go to Check entry permissibility per infotype and you will see wage type has an end date. You don't need to do anything, these are just checks. Then go to Check Define wage type permissibility for each PS and ESG you will see: loan has a delimit date. Now go to Check Wage type characteristics, you will see: loan has a delimit date. Now in PA30 if you try to create infotype 14 with a start date later than the delimit date, it will not be available. That will be your test that it is no longer available. When you want to make it available again, I think you would just need to copy it in the first step with start date of what you want and end date of 12/31/9999. I have delimited a loan successfully and it works.

Subsequent Process Of Off-Cycle Process

Subsequent activities means the processes needs to be run after the off cycle payroll executed for someone. Process flow: 1. You run an off-cycle payroll. The system writes the off-cycle payroll data to the indicator table for subsequent batch processing (T52OCG). 2. You start program RPUOCB00 (Subsequent Processes of Off-Cycle Activities) TCODE PUOCBA online or as a background job. On the program selection screen, you select Payroll as the subsequent process and specify the process model (you can create your own by copying SAPXXOC process model) that you use for subsequent activities in off-cycle payroll. 3. Program RPUOCB00 reads off-cycle payroll data from table T52OCG and starts one or more processes in the HR Process Workbench. To do this, it uses the process model that you specified on the program selection screen. 4. As soon as a process is started, the system flags the processed records in indicator table T52OCG with the processor, date, and time. The employee who started program RPUOCB00 is entered as the processor. 5. The system transfers data on the payroll area, personnel number, and off-cycle payroll from the indicator table to program RPCEDTU0 (Remuneration Statements) and executes the program. 6. It then transfers the data to programs RPCIPE00 (Posting to Accounting: Create Posting Run) and RPCDTCU0 (Data Medium Exchange Preliminary Program (USA)) and executes these programs. 7. The system flags the results of program RPCDTCU0 with the program run date and an identification feature that consists of the exact time in hours, minutes, and seconds. The last character is replaced by a P, that is: HHMMSP (HH stands for hours, MM for minutes, S for seconds). 8. The system transfers the program run date and identification feature to main program H99_RFF_FRAME. The main program calls program RFFOUS_C (International Payment Medium - Check (With Check Management)) with different variants, if available. The variants contain information on the paying company code, payment method, house bank, account ID, printer, and check lot number.

Result - The remuneration statements are created. - Payroll results are transferred to Accounting. - Checks are printed for the payroll amounts. Depending on the variant used for program RFFOUS_C, payment summaries or payment advice notes are output with the checks.

Doing Bi-Monthly Payroll Run

How to do bi-monthly payroll run? Payroll periods must be generated for each combination of period parameters and date modifiers assigned to a payroll area. All periods within the specified time interval are defined based on the period parameter. The start date and end date for each period is defined and the payday is calculated using a rule entered as a parameter. The payroll year and period define the exact dates for the payroll period. You must create a control record for every payroll area. This control record controls the individual stages of payroll. A payroll period determines the period for which a payroll result is created. The length of payroll periods can differ, for example, a payroll period can be a month, a week, or fourteen days. Payday rule Number of days: These two fields determine how the period payday is calculated. The following values can be used for the payday rule: 1 : The number of days is added to the start date of the period to calculate the payday. 2 : The number of days is deducted from the end date of the period. 3 : The number of days is added to the end date of the period. 4 : Only applies to monthly periods, the number is used as the exact date.

Create one date modifier and different period parameters and assign that one to one pay roll area

Documenting HR Rules And Schemas

What are your top tips for documenting your rules and schemas? It is known that the quickest way to find out how a schema works is to run payroll and look at it, but we are required to document our existing schema. Report RPDASC00 can produce a file that contains every schema step and the contents of every rule. And that RPUSCC00 can compare a customer schema to a SAP schema and show the changes. Any better ideas for creating documentation of the contents of your own schema and rules? By Ruth: I do something like this. Every time I create a Z sub schema or rule I document it, rationale etc. The following is taken from my current project (6 weeks till go-live!) - I know its extreme amount of work, but has saved my bacon more than once when I wanted to check something I did at another customer XX years prior... and has left customers with a nice warm feeling. 1.1 Payroll Australia Convert HR-PS Annual Salary to Fortnightly Salary Configuration System Reference IMG Task: Convert HR-PS Annual Salary to Fortnightly Salary IMG Menu Path: N/A SAP Transaction Name and Code: PE01 to maintain schema ZPS0 and ZUP0 , PE02 to maintain payroll rule ZU13, ZU10 Object ID: Schema ZPS0 , ZUP0 , Rule ZU10 Create Fortnightly salary, Rule ZU13 Convert from annual to Fortnightly amount. Modify schema to call custom payroll rules and modify rules to use Post wage types instead of SAP HR-PS model wage types. Schema ZUP0, Rule ZU13, ZU10 1.1 Rationale Configuration / Change Rationale: All <client> paid employees (Casual, Fixed Term, Permanent, Award, Contract Staff) have an annual salary defined which will be recorded on Basic Pay. No employees have hourly rates, weekly wages or

fortnightly/monthly amounts stored. Period salary is derived from the Annual Salary using the calculation Fortnightly Salary = Annual Salary * 12/313. Rule ZU13 performs this calculation and 4 decimals are used to ensure accurate calculations. 1.2 Configuration Steps Schema Changes Schema AUP0 copied to schema ZUP0. Modify schema ZPS0 to call ZUP0 instead of AUP0. COM ************************************ COM Payroll schema: Public Sector Standa COM ************************************ COPY QIN0 * Initialization of payroll COPY ZIN0 <Client>:Initialization of payroll COPY AUBD * AU-PS: Edit basic data COPY ZUBD <Client>:AU-PS: Edit basic data COPY QRET Load up any retro recalc values requ COPY QLR0 Import last payroll result COPY AUHC * AU-PS: Higher Duty Allowance COPY ZUHC <Client>:AU-PS: Higher Duty Allowance COPY AUP0 * Convert annual salary to fortnightly COPY ZUP0 <Client>:Convert annual salary to fort s COPY AUQT * AU-PS: Gross remuneration (time mg) COPY ZUQT <Client>:AU-PS: Gross remuneration (time COPY XTBS Save tables for iteration Rule AU13 copied to ZU13, AU10 to ZU10. SAP Rule SAP HR-PS Rule <Client> Z*** Name Description Changes required AU13 ZU13 Convert annual salary into fortnightly Use <Client> wage types instead of SAP Model wagetypes AU10 ZU10 Create wage type into IT Use <Client> wage types instead of SAP Model wagetypes Modify schema ZUP0 to call Post rule ZU13 instead of AU13 and rule ZU10 instead of AU10. COM *************************************** BLOCK BEG Convert annual salary to fortnightly sal COM *************************************** PIT AURD GEN NOAB * Rounding factor from T511K PIT AU10 GEN NOAB * Create wage type into IT

PIT ZU10 NOAB <Client>:Create wage type into IT PIT AU13 GEN NOAB * Convert annual salary into fortnightly PIT ZU13 P01 <Client>:Convert annual salary into fort PIT ZU14 P01 NOAB <Client>:Part Timers BLOCK END Modify Rule ZU10 to create the fortnightly wage type 1010 from the Annual Salary wage type 1000 and to generate Higher Duty Salary 1210 from standard /3H3. PCR Wage Type Cont. Decision Oper 1 Oper 2 Oper 3 Oper 4 * 1000 D ADDWT 1010 * /3H3 ADDWT 1210 Modify Rule ZU13 to convert the fortnightly salary wage types (which will be on the Basic Pay infotype) from the annual amounts to fortnightly amounts. This rule will also convert all rates and amounts to 4 decimals (AUD4) if they are in AUD. PCL 01 will set which wage types are converted from yearly to fortnightly amounts.

Counting Class And Counting Rules

What is mint by counting class and counting rules? Counting rule: is a rule for counting attendance and absences and they are used to determine payroll days and hours of an attendance and absence of an employee. Counting classes are used in Wage Type Valuation & Absence counting. These are assigned to each period work schedule. Suppose a group of employees are coming in night shifts and another group is coming in general shifts. We can assign counting classes to these groups for differentiating them for any payments. Counting classes are forming buckets to collect paid & unpaid absences separately. Counting classes are used in order to form "buckets" to valuate paid and unpaid absences: 1. For factoring to reduce salaries for unpaid absences In the standard SAP R/3 System, all counting classes that contain unpaid absences are processed together for factoring. A prerequisite of factoring is that you have assigned the paid absences to at least one counting class. This means that you should not collect unpaid absences in more than one counting class if you use standard factoring (schema xAL0), otherwise the absences would be valuated twice.

If you want to form several counting classes for unpaid absences, you must specify explicitly which counting classes should be taken into account in factoring. 2. To generate statistics and for cost accounting You can collect absence times in the counting classes in order to fill wage types and evaluate the cumulated values for cost accounting or statistical purposes. You can access the counting classes using operation NUM. Both paid and unpaid absences are usually collected in one counting class. The following rule applies to the further course of payroll: Paid counting classes are queried in operations APnn, and unpaid counting classes in operations AUnn. Example 1. An employee with a fixed salary takes unpaid leave. The number of unpaid absence hours must be calculated before a reduction in salary can be determined. You therefore specify a counting class which is 100% unpaid for the absence valuation rule unpaid leave. 2. You want to find out what sort of costs are incurred for a paid period of incapacity to work. You therefore assign the absence valuation rule Sickness/Cure a counting class in which the absence times are 100% paid. 3. You want to collect absences on public holidays in one counting class, and absences on workdays in another.

Explain Pay scale Area, Pay scale Type, Allowance group. Pay scale type The collective agreement type defines the sector of industry for which the collective agreement is valid Pay scale Area A pay scale area is a special area in which a collective agreement is valid. Grpg PS Group Level Wage type 1 1055/01 01 MS40 1 1055/01 01 MS41

1 1055/01 02 MMVC Pay scale grouping for allowances Indicates a grouping for a set of employees with similar characteristics regarding compensation and benefits based on the following: Pay scale type Pay scale area Pay scale group Pay scale level Employee subgroup grouping for collective agreement provision. This grouping determines eligibility and amounts for various allowances, reimbursements and perks for an employee as per the company specified rules. IMG Path: Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Check Payscale Type Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Check Payscale Area Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Check Assignment of Pay Scale Structure to Enterprise Structure Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Determine default for pay scale data Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Setup payroll period for collective agreement provision