Академический Документы
Профессиональный Документы
Культура Документы
Home If your browser does not support the SDS Knowledge Base menu, click here for an alternative.
Knowledgebase
Payroll
About SDS
Links
Sitemap
Knowledgebase
Payroll Processing
Search Q
SAP HR Payroll
Query Tools Data Tools Human Resources FI/CO Cross System Miscellaneous BW
SDS Offe rs
SAP HR Se
Tutoria
Your Input
With GRET, the retro processing does not take place as per usual with the normal schema. In addition , whereas the normal schema G000 calculates the tax cumulatively (unless the employee is on a week1/month1 tax bas is), GRET recalculates the tax period by period.
Gene ral
This will be old hat for mos t of you, but for thos e who are learning payroll, it is important to rem ember that there are certain mandatory infotypes which an employee must have, in order for you to run a s ucces sful payroll for them. One of those infotypes is Planned Working Time (0007). If you delete an employee's Basic Pay infotype (0008) record, the payroll will still run, but falls over if you have entered any overtime etc. You can, however, have an infotype 8 record, without any wagetypes.
Use the ID: HR_G which is the one for general messages. Type the message, save it and then attach it to an empl oyee or group of employees on IT 128 - sub-type 1 or 2, so that it can appear on the payslip. You can use the fast entry screen for master data - trans action code PA70. Note that for personal mess ages, you need to create an IT 0128 sub-type 2 for each applicable employee. For general mess ages you have to create an IT 0128 sub-type 1 for each and every employee in the payroll area. This can be a bit of an effort if you ha ve a few thousand employees. Larger customers might wish to use CATT procedures or write an ABAP routine to automate the update. There is a program RPU12800 which is a model report for creating batch input sess ions for infotype 0 128 s ubtype 2, personal notifications. You still have to us e the standard fas t data entry functions to enter records for subtype 1, general notifications, en masse.
The payroll control record allows you to control the state of the payroll run. Control records are not transported acros s clients . They have to be created in each client. The control record only advances to the next payroll period when you move it from a state of "Exit Payroll" to "Released for Payroll". You will be prompted with the warning: Payroll area xx: Do you want to release the period xx.yyyy for payroll?. Clicking yes will advance the payroll control record. If you wis h to change either the payroll period or the earliest retro accounting period, you have to delete the control record and then recreate it with the correct dates. Remember that if you are loading your cumulative values into period 6/2001 (i.e. running XLK0 for 6/2001) then you should s et the earliest retro date to 7/2001. This wi ll s top anyone from entering any data which may caus e the payroll to try and retro into a period in which SAP never crea ted a full set of payroll results. The icons at the top left of the screen show you which employees have a matchcode of W (thos e employees who have had data modifications during the current payroll monthly cycle). The icon showing 2 employees next to one another is used to list all the employees who have been process ed through the payroll for the current month. Th e locked icon indicates which employees have been locked and will therefore not be proces sed through the payroll.
Pre-DME
When running the Pre-DME program, each employee process ed has a specific time and date s tamped in their payroll results in the BT table. This will be the s ame for all employees processed in each report - which is done per payroll area. If for some reason the report is terminated during proces sing, you can re-run the Pre-DME with the relevant time and date in the boxes at the bottom LHS. Fill in the time and date in the field Repeat Run and tick the checkbox "flagged records only". This will pick up all those employees and put them into a clean file. You can then run it again without the date and time - which will pick up all the employees who had not been processed at the time of the i nitial program termination - i.e. they would have no record on their BT table in their payroll results. Take care to enter the payroll area in both the "period" and "selection" options. Failing to enter the payroll area in the selection field will mean that everyone in a payroll area with the same period parameters as the one selected at the top will be processed - which is rather dangerous.
1. Viewing the contents of any of the important tables during the payroll processing is very useful when trying to find the source of an error. In the schema, you can use the function "print" and the name of the internal table in the parameter column - for example it, ot, ort etc. Us e the Operation "print" in the "cycle", to view the head entry of the "it" for every loop of the cycle. 2. Wishing to s top the payroll processing with a break point. You can do so using the conventional m ethod of setting "break points" in the ABAP debugger. Alternatively, you can insert a "BREAK" command in the schema at the point where you wish the program to s top. The corresponding ABAP will break at run-time. You don't have to set up breakpoint in ABAP explicitly. When you reach the break, you can modify the table contents as is the case with the normal ABAP debugger.