What is Attendance & Absences Quota? Absence Quota: An employee's entitlement to a certain absence.

The quota has a limited validity period, and is reduced by each recorded absence. Attendance Quota: Determines an employee's timerestricted entitlement to certain attendances. One such example is overtime approval. Recording an attendance of this type reduces an employee's entitlement What is Substitutions? A substitution is employee working time that deviates from planned working time and/or is paid at a different rate because the employee works at an alternative position. Substitutions allow short-term deviations to personal work schedules, as well as different payment for an employee, to be recorded in the system. Substitutions can be set up regardless of whether the absent person is actually being replaced or substituted for temporarily. What is Availability? Description of when a service employee is or is not available. The resource planner uses availability as background information when scheduling a service employee. What are Attendance & Absence Types? Grouping together of employees' scheduled attendances and actual attendances according to the reason for the attenance. Attendances canalso be grouped for other personnel-related reasons, such as for employee time accounts and for valuation of personnel times. How do we record a Overtime? Overtime approvals can restrict the amount and the exact point in time when working time is recognized as "overtime." The type and amount of overtime compensation also depends upon this criteria. The normal working time of an employee is used to determine overtime. Normal working time can also be calculated according to the specific time periods used to perform weekly or monthly overtime calculation analyses. What is Attendance & Absences Counting Rule? Att Counting Rule: Statement that determines deduction days/hours and payroll days/hours from attendance days/hours. An attendance counting rule is made up of several attendance counting rule items. What is the difference among work schedule, daily work schedule and work schedule rule? Work schedule: The work schedule define an organisation works timetable, and contains information on working and break times for group of employees.

Daily Work Schedule: It defines the start and end of working time of the day. Work Schedule Rule: WSR defines the period work schedule in more details. The Employee Subgroup, Personnel Subarea for workschedules and Public Holiday calener are taken into account. What is counting rules? Counting Rule for Abs/Attn. - Specifies conditions that must be fulfilled for counting rule to be chosen, and specifications that decide how the attendances/absence are counted to determine the payroll days or hour. What is time quotas? Time Quotas. - It is related to absence and attendance.It is required at the time of grouping of 'Employee subgroup for Time quota' and 'Personnel Subarea for Time quota'. Is absence/attendence quotas are part of time quotas? Yes. What is TMW & what are its functions? Time Manager's Workplace is the option for time administrators to enter the time datas, it is mainly for maintaining the time events in decentralized. Using intuitive ID they will enter the time events and also absences, OT. What is Rounding Rule? It is a rule to round the absence and attendance hours which will be attached to Counting Rule and then assign to Deduction Rule. What is Quota deduction? Quota deduction is the deduction of employee's absence from the entitlement for any base period. What is Quota Compensation? Quota Compensation is how the quota is compensated either by off or by encashement. During time evaluation (using PT60) we type in a field called Time Statement Variant. Can any one tell me where should I configure this field? We run time evaluation on biweekly and monthly basis. If the first of month starts on Tuesday and Monday is 31st of the last month, while printing the time statement, its printing 31st of the last month in one page and the remaining 30 days of this month in a new page, its just wasting pages. Can any one tell me how to configure this field so that it prints all days on the same page.

ANS:1 In PT60, you only call a variant of the time statement. I think the change have to be made in the form itself. All the config is in the SPRO Personnel time management/Time evaluation/Evaluation and time management pool/time statement form.... ANS:2 Tcode - SE38 Select variant radio button Program name - RPTEDT00 Give variant name. ANS:3 please note the form name used in the report RPTEDT00. You can modify that form in t-code PE51. as u said I tried to find the variant for reprot RPTIME00 and could see the variant using SE38. But I can see only "values" and "attributes" of a variant, Its very difficult to understand what it is? using PE51, I can't see the variant for the report RPTIME00, but I can see the standard forms. I checked the variant in SE38 has been assigned with any of the forms that are displayed in PE51, but its not. can any one tell how r they related? ANS:4 This is simple to understand, better have some knowledge on "Variants". http://help.sap.com/saphelp_nw04/helpdata/en/c0/980389e58611d194cc00a0c94260a5/fram eset.htm Se38 - RPTEDT00 - just execute... here you will see the form name of Time Statement (Give standard one otherwise give your custom form name and all required information into parameters on selection screen) then click on save. Give Variant name - SAP& Cust (example) and Meaning in Variant Attributes. Finally save this variant. Goto PT60 and give your Time Statement Variant here and again save if you want one more variant based on your evaluation. ANS:5execute directly the report RPTEDT00 (System/Service/Reporting) with the variant you use with RPTIME. Then you'll see what form is used in the variant. Please note that you will probably have to use PE50 instead of PE51 if the form is a TEDT class ur suggestions really helped me to understand about HR forms, I just followed all the above suggestions in creating an form and using in PT61 (RPTEDT00) report, it worked well. But I am still unable to find the option where I can restrict it not to print in a new page (see my above posts). can any one help in finding it or give any suggestion where I can set this option. go to PE50 and modify your form accordingly so that it prints in the same page. I THINK (not sure at all ) that you can't always do what you want. If you have any kind of

cumulation in your form (Time type or wage type) then the system will split by week (or month...) First thing I would do is to check if I have cumulated value and then go into the configuration help in SPRO where you have some details how it works (see the path I wrote a few messages back) Better all the time get the business requirement as you said not required in second page. Get the requirement what client is expecting on the form and copy the standard form then do the changes accordingly. the business requirement is not to print in a new page, I copied the standard form and modified its fields accordingly. But I am still unable to find the option or any customizing steps where I can limit this not to print in a new page. If any know how we can set the option in the form Are you using a TEDT or TELU form? Did you check the parameter for list layout, weeks total : full weeks only, the help talks about divided weeks.. Do you have an example of a period when it happen? I could run it to check if I can re-create the problem I am using a TEDT class form. yes the help talks about only weeks or months. I didn't find any option where I can set this. For example, the current month May starts from tuesday (05/01/2007), so the time statement form is printing like: Page 1: Monday 04/30/2007 Page 2: Tuesday 05/01/2207 ..... ..... I just want to exclude the page 1 when I take a time statement form for the month of May. which original standard form did you copy? When you request the statement, do you execute it from PT61 with button radio "current month" (or a date) or automatic after time evaluation.... (if I do the same and I don't have any problem, it means we can solve the problem) Let me give a brief explanation. I copied the standard form TF02 (belongs to TEDT class) to ZF11 from. When I print the time sheet using PT61 suppose for the dates: 01/30/2006 to 02/12/2006. In the first page its printing the header (HD) with time results for the days 01/30/2006 and 01/31/2006 only. And on the second page its printing header and the remaining days. Is there any way that we can make it to print on a single page, i.e. for all 14 days together? How can we set it to print for weekly or monthly etc? in this example , the report is divided because of the end of the month, and I think we can't avoid it (because of cumulated value.. How would you print Saldo if not?.... ) If you don't use any cumulation, I would check for user exit..... 73. I have a scenario in which I have around 10 different types of overtime. What are the different ways to take care of them? Is time evaluation required for that? I am only

using Time in SAP, payroll is thru a 3rd party system. ANS:1 most of the time, overtime is so complex that you have to deal with it in the time schema. Some basics ways are set in SAP but usually, it is not enough and you have to develop your own rules and way of doing it. You make all the calculation and send the output to payroll via time wage types. You may need to set retrocalculation trigger, and use both ZL and ZML table in conjonction with POVT function. Can you pls tell me how the system will work if we do not have any payroll running in SAP. Well, how are you proceeding now? How do you send information to the 3rd part that calculate your payroll? You must probably upload some kind of converted data? If not what is the purpose of calculating overtime?.. If you are not yet using wage types, then you can send the info in time types.... We will be using an inteface thru which we will be sending the data. The payroll system is external and if we have to set up some wage types in SAP, I think we will go with it. Right now, we have nothing. Everything is on planning stage and we are exploring different kinds of ways thru which we can meet our requirements. Our requirement is very simple, Time management in SAP, capture overtime and have it pais thru the 3rd party system. What do you suggest for such a scenario? ANS:1 I can tell you that Time management is always underestimated: it is the link between anything else in HR (masterdata, shift planning, payroll) and because requirements always ended to be more complex with more exceptions than first thought. If you intend to have payroll one day, then I suggest you use wages types so you won't have to re-do everything. Be sure that every requirements have been defined before you make a decision on how to proceed. for example: What trigger the kind of overtime? is it a simple master data easy to read in time? Or will you need a manual flag (like a category in an infotype) to tell you? Do you have exception like daily overtime upon a period overtime (on sundays or stat holydays etc). Are EE salary or hourly paid? Will you have factoring or nivelling issue? (If employee have regular paiement but ireggular shift on multiple weeks). How dhould it react if the EE moves from one way to another way of calculation in the middle of a payroll period? Anyway, I can't say it all here, but if time evaluation is the best solution, re-think it if the only pupose is calculating overtime, because you open a door to huge unknown world. Be sure you have enough senior support this can't be easily done by a non experimented analyst. ANS:2 after analyzing ur situation all I can suggest is u can use time management in SAP for overtime or normal time calculation. In order to connect it to 3rd party payroll u need to take care of a lot of interface (design) issues, especially what data u will be downloading and

uploading to 3rd party payroll. Its better u transfer the time data in terms of wagetypes from SAP to 3rd party payroll and also to achieve the 10 different overtime calculations u need to have good experience in writing PCR's and Schemas. PCR's play a vital role in calculating overtime. I do understand that going for time evaluation is a big decision and that PCRs and schemas are not something inexperienced people should go for. My scenario is as follows- Ten locations, ten different rules. Workers get paid differently on weekdays, weekends and holidays. Some get paid after 8 hrs a day, some after 48 hrs a week and so on. Looking at this scenario, I was finding it diffcult to configure without using time evaluation. ANS:1 I Forget to ask you if you have real time data entry? You need it to have accurate calculations and sometimes specific checks (for example what happen if you have overtime after 48h a week but the day it happens the EE is absent ?) You may also have part calculated and part manual overtime (if you use compensation category in presences/abs) ANS:2going with time evaluation is the best decision, I think it can handle your scenerio very well. all u need is write all the scenarios for all the rules for example if an employee is absent or present on a holiday--> what's the process...? Like this u will definitely get all the scenario's and write them in terms of PCR's and schema's. Just do some homework on these things once u r comfortable with the configuration part (this should be ur first priority). We will be entering time through time recording terminals as well as CATS depending on the class of employees. We will be using positive time management u can goto OH11 to copy standard wage type and custmized that wage type and based upon ur 10 different overtime u should write a PCR and assigned to the TW15 sub schema in ur schema, Otherwise u can goto IT2012, based upon ur requirement u create wagetype based upon the overtime percentage and assigned to the IT2012. it automatically calculate in ur payroll time showing in the payslip. we dont have payroll in SAP. So dont think will have to worry about that. How exactly does this 2012 work, No it is not IT2012 but probably IT2010 which is a manual way to enter wage types. (IT2012 is for time types 74. I got error in running time evaluation. we were maintained time management without payroll in my company. we maintained tqta schma for leave updation.with 2013 bdc we upload leave and after run pt60. we successfully run for 2 months. Aafter that the pt60 was not executed from last 10 months. Now the problem is again we execute this month

system shows error u are not authorised 0008 basic infotype. the leave balance is not come properly ANS:1 maintain the Time Mgmt status 7 if its time evaluation without payrol integration.. R u generating it for every month /once for a year...? ANS:2 Since it is time management without payroll , the time Managerment status shud be 7 i.e time evaluation without payroll integration

75. Can anybody tell me what the time evaluation do? it puzzled me for a long time. We use negative time recording, recording absence in 2001 and overtime in 2005. I don't know if i should use time evaluation.In infotype 0007,i set time management status 0,1,7,9, all can run payroll correct.I don't know what is the relationship of payroll and time management, and how time management status influence payroll. can anybody emplain me what the time evaluation do? how time evaluation, time management status and payroll work ? what's the difference recording overtime in 2002 and 2005.ffice:office" /> ANS:1 Time evaluation is used to evaluate the recorded time datas. To run time evaluation, you need three basic information like Master Record, Attendances & Absences, Planned Working Time and there are four possible outputs after the Time evaluation: Time Wage types, Time Accounts, Messages, Updated Absence Quotas. So, we need to run the time evaluation to get these output, which will be processed in the Payroll to get the payments. Time evaluation is based on your Time Schema, which is the step by step sequence of your functions. There are two options to valuate the recorded time, either using Time evaluation driver RPTIME00 or in Payroll driver RPCALCx0. Time Management status, determine the type of time management you are following like Positive TM, Negative TM, Without integration with Payroll. 76. How to maintain the time administrator for a users ANS:1 can be maintained via CATSPROFILES and assigned to a user in the user defaults using the parameter id CVR. CATSPROFILES are maintained in TCATS table. Pl take a look the IMG Path Cross-Application Components-->Time Sheet -->Settings for All User Interfaces-->Authorizations these roles are for time entry in CAT2. ANS:2 You can directly go to transaction CAC1, that is CATS profile, there you can maintain the profile of your CATS. You can maintain the profile in your user parameter that is in SU3, go to parameters and enter the CVR over there and enter your profile name there.

77. Positive Time management is recording all Clock in's and clock out's and Negative Time Management is recording only deviations. My Question is what are the Infotypes maintained in Positive Time Mgt and what are the Infotypes maintained in Negative Time Mgt, what are the main config changes that has to be made to activate either Positive or Negative Time recording for a company using these Schemas and also in SPRO. Also what is the significance of the Time Schemas TM00 and TM04 in this regard, is there any specification that either TM00 or TM04 is used specifically for Positive or else specifically for Negative recording, which schema is used for which type of recording. ANS: 1 Schemas are specific Positive TM00, Negative TM04, Infotypes used 2000, 2001 , 2003, 2050, for time infotype are same for the Positive and negative ANS:2 for positive time management you need to maintain the time pairs/ events and some tables to define your time evaluation, also maintain 1 in the IT0007 Important Tables need to maintain: V_T510S - TIME WT SELECTION RULES V_T510H - PAYROLL CONSTANTS T554S - ATTENDANCE AND ABSENCE TYPES V_T55DH - EVALUATION TYPE FOR ATTENDANCES/ABSENCES V_T554R - DAY RULES V_T555A - TIME TYPES Time Schemas: 1. TM00 - Time Evaluation with Personnel Time Events 2. TM01 - Time Evaluation for Work schedule deviation 3. TM02 - Time Evaluation for External services management 4. TM04 - Time Evaluation with-out clock times ANS:3 For both the negative and positive time management, we need to mainatain infotypes 2001, 2006, 2002, 2007. The configuration that you need to set is, in the infotype 0007, i.e, planned working time, tou need to maintain time management status as '1' for positive time management and '9' for negative time management. The "Time Management status" indicator in the Planned Working Time infotype (0007) shows whether all actual times are recorded for an employee, or only exceptions to the planned specifications. Regarding the schemas :

TM00 : Schema TM00 is based on positive recording of time data, that is, recording all times that count as working time (actual times). Schema TM00 only evaluates time data with clock times (or full-day records). The main task of schema TM00 is to classify the actual times by comparing them to the planned specifications in the daily work schedule (start and end of planned working time, core times, breaks, and so on).

TM04 : You can use schema TM04 to process attendances and absences that specify a number of hours only, rather than concrete start and end times. The times stipulated in the daily work schedule are not relevant. Only specifications such as planned hours and minimum daily working time are evaluated from the daily work schedule. TM04 caters both for negative time recording (recording of exceptions to the work schedule) and positive time recording (recording all attendances or actual times). explain in which scenario or situations the other two schemas TM01 and TM02 are used 2. TM01 - Time Evaluation for Work schedule deviation 3. TM02 - Time Evaluation for External services management TM01 Schema TM01 is a standard schema used to evaluate the time data of employees for whom only deviations from the work schedule are recorded. Schema TM01 is based on the following requirements and objectives: Schema TM01 forms time balances, time wage types and time quotas. It is processed using the time evaluation report RPTIME00. The schema imports and processes time data that has been entered online. It was developed for evaluation of time data which represent only the exceptions to the work schedule. In this case, the times (actual times) which are not part of working time are recorded. Time data must be entered as clock times and must be full-day records. The valuation basis for time evaluation is a planned time pair which is generated according to the specifications in the employees personal work schedule. The planned time pairs generally correspond to the actual working time. Only attendances and absences entered in infotypes 2002 and 2001 respectively can cause the planned and actual values to differ. Schema TM01 automatically generates overtime for all recorded attendance times that are outside of the planned working times specified in the daily work schedule. If overtime is entered in the relevant infotype (2005), overtime hours can be approved taking into account overtime breaks.

TM02

The standard schema TM02 is a minimized version with the required functions to generate wage types for evaluating time data for external service providers. The schema is specifically modified to include the requirements for evaluating external services. The characteristics that differentiate schema TM02 from the other standard schemas are highlighted in the following section. As a result, you should already understand the concept behind the Time Evaluation report (RPTIME00) and schema TM00. For more information, see Time Evaluation.

Evaluate External Employees The CHECK - SRV function ensures that only employees who are assigned to Time Management status 8 (External Services) in the Planned Working Time infotype (0007) are included in accounting process.

Set Up Wage Types No balances are determined in schema TM02. Instead, the focus is on setting up the wage types that are to be transferred to Materials Management (MM-SRV). Integrate the functions for balance formation, if you want to form balances. This makes sense if, for example, you want to set up a compensation account for external employees. Use the standard schemas TM00 or TM01 as your guide.

Evaluate on Hourly Basis If you do not want to record the clock-in and clock-out times for external employees, you only need to record and evaluate the attendance hours for external employees. You can use the new TYPES function to evaluate time data recorded without clock times. Use the standard schema TM04 as a guide for modifying the schema TM02 if you want to record time data without clock times for account assignments of external services.

Determine Actual Times from Attendances Infotype (2002) The Time Evaluation (PA-TIM-EVA) normally requires an entry in the time Recording Information infotype (0050). The CHECK-NOTR (No Time Recording) function specifies that information from the Time Recording Information infotype (0050) is not to be used. This function is required if you do not want to record employees actual times using external time recording terminals or the Time Events infotype (2011), but with the Attendances infotype (2002). When you record times for external employee times using time recording terminals, make sure that you have not yet recorded data for external services using the Time Events infotype

(2011). Determine Overtime As in schema TM00, a number of variants exist for determining overtime. Check the characteristics in processing class 17 by overtime wage types you are using.

Export Data in Table HRMMSRVIF The MMSRV function allows you to evaluate the time wage types determined and their corresponding account assignment data using the MM-SRV table ASMD (Service Master - Basic Data). This will eventually determine a new service number. First, however, the interface table HRMMSRVIF must be updated.

To ensure retroactive accounting capacity: During each payroll run, the time wage types from the last payroll run are compared with the new time wage types determined. The differences are evaluated using table ASMD and then put into the interface table HRMMSRVIF 78. Need help in INDONESIA ,PAYROLL and TIME MANAGEMENT, Can you please tell me what are the info type i have to maintain and fro Personnel administration, PAYROLL and TIME MANAGEMENT. Which schema for time and payroll we have to use.ffice:office" /> ANS:1 You may want to navigate Payroll ffice:smarttags" />Indonesia in SAP help. http://help.sap.com/saphelp_erp2005/helpdata/en/47/161a359303f810e10000009b38f83b/fr ameset.htm use payroll schema ID00 Infotypes used: PY-ID Tax Indonesia Infotype (0241) PY-ID Previous Employment Details Infotype (0694) PY-ID Jamsostek Infotype (0242) PY-ID Private Insurance Indonesia Infotype (0319) ANS:2 Time management is international so if you are in Indonesia or US or Australia or Europe - you use the same infotypes, reports, schemas. (some countries though may have some additional functionality - eg. for public sector).

The standard time management infotypes are: 0007 - Work schedule rule (planned work time)

2001 - Absences 2002 - Attendances 2003 - Substitutions 2004 - Availability (eg. Standby/Oncall) 2005 - Overtime 2006 - Absence quota types 2007 - Attendance quota types (use this also for overtime for positive employees) 2011 - Time Events (viewing of clocking times) 0050 - Time Recording infotype (for employees that you want clock times for) 2012 - Time transfer specifications (can use this for leave uploads) 2013 - Quota corrections Time management and Payroll uses the WPBP infotypes - ie 0000 (Actions), 0001 (Org Assignment), 0007 (WSR), 0008 (basic pay). Time management also uses infotype 0041 for accrual of leave (if you configure as such). Time evaluation is used to accrue leave and calculate times for employees depending on their time management status (defined in i0007). The program used is RPTIME00 (and there is a new program for concurrent employment - RPTIME01). The main standard schemas are: TM00 positive time evaluation, TM04 - negative time evaluation, TQTA - quota accrual. These can be viewed with transaction code PE01. What you use is dependent on the types of employees and how much processing you wish to do. ANS:3 Time Mgmt will be Country Independent except few scenarios... http://help.sap.com/saphelp_47x200/helpdata/en/8a/9868bc46c411d189470000e829fbbd/fr ameset.htm Payrolll: http://help.sap.com/saphelp_47x200/helpdata/en/47/161a359303f810e10000009b38f83b/fr ameset.htm 79. please provide me the Time reports available for Russia. ANS:1 Check these: RFHABU10 RFRUBLS0 RFRUDOP0 RFRUKOP0 RFRUKRL0 RFUMSV40 ANS:2 Time management is an international module so reports that are available under the Time management node can be run at your company (provided that the relevant details have

been configured - ie. absences, quotas, time types etc). ANS:3 Time Leveling (Report RPTCMP00) The Time Statement (Report RPTEDT00) Cumulated Time Evaluation Results: Time Balances and Time Wage T Time Accounts (Report RPTDOW00) Displaying Absence Quota Information (Report RPTQTA10) Displaying Time Evaluation Messages (Report RPTERL00) Attendance/Absence Data: Overview (Report RPTABS20) Attendance/Absence Data: Calendar View (Report RPTABS50) Attendance/Absence Data: Multiple Employee View (Report RPTABS60 Attendance Check (Report RPTEAB00) Attendances/Absences Overview Graphic (Report RPTLEA40) Attendance/Absence Data: Overview (Report RPTABS20) Attendance/Absence Data: Calendar View (Report RPTABS50) Attendance/Absence Data: Multiple Employee View (Report RPTABS60 Attendances/Absences Overview Graphic (Report RPTLEA40) 79. How can i remove a wage type (House Allowance) in infotype 14 from the amount calculated for for time quota compensation wage type in infotype 0416? ANS:1 IMG path: Time Management - Time Data Recording and Administration - Managing Time Accounts Using Attendance/Absence Quotas - Processing Absence Quotas in Payroll - Time Quota Compensation In the node 'Define Time Quota Compensation Methods', i have checked against our key {ESG PSG Comp. method} and surprisingly, the rule field is blank. How is it being valuated then?? Wonder if it's defined in payroll rules? i got that in view V_T554C wage type /841 is entered for 'Valuation using constants or averages'. Where do i specify that in /841, transport allowance is excluded? Check in the rule XPPF. This is where partial period factoring is done. Factoring is not what i need. I need to exclude some wage types from the calculation of 'time quota compensation'. Check the Processing Class 1 for House Allowance Wage type. Give '0' in the specification 80. Is there any SAP standard function module to convert user system date into server date based on the time zone?

ANS:1 In Se37 , Use F4 and find the convert * time * input. *convert*time. convert * date * internal ANS:2 Instead of std FM you can write your own FM. 81. The client I am working for has a Thursday Off However Maintenance workers have a staggering off,i.e they work on Thursdays & take some other day as weekly off. My first issue is that if by some chance he takes an off on Thursday,we are unable to mark him as Absent ass the system shows that the person can't be marked absent on a day off. Secondly i need to configure the system in such a way that only for maintenance workers provision is there to remain absent on thursday & take a weekly off anytime else.

ANS:1 Have created different PWS for your maintenance workers(MW) .Assign the OFF day on the exact Off day for your MW. I have created a different worjk schedule rule for these workers as they have no fixed weekly off Now they are able to apply for off on Thursdays. But one more issue is that their weekly off is not paid so number of month days should appear as 26 or 25,but it appears as 30 or 31. How do I go about for this one ANS:2 The weekly off is fixed on Thursday or not, i think u want to use shift plan for this one it wil be more effective ANS:3 Have you checked your Day type assignment 1. Checout DWS - Rules for varient - or create for Thursday 2. Assign this to ur Spl Thursday off If these two were not working you can try with define spl days every week.

ANS:4 Assign the appropriate daytypes so that the person is not paid for those days. The current scenario is that in Maintenance department has a staggering off & he can take off on any day. He is thus paid for 26 or 27 days depending on the number of weekly offs he takes that month Thus if he works for 26/27 days,he gets an attendance bonus of Rs. 100. If he is absent for 1 day,he gets Rs. 75,& rs. 50 for 2 days absenteeism & nothing if absent for more

than two days The work schedule rule attached to them is All day General Shift since they can take weekly off whenever they want. Now the problem which is happeing is that the payslip shows Total month days as 30/31 instead of 26(due to workschedule rule All Day genaral Shift attached). We cannot change the work schedule rule else if he is absent on Thursday,we are not able to mark him absent as system throws error message. So we have kept All day General shift as work schedule. Moreover the system also considers the weekly offs as absent days & so he does not get attendance bonus i.e it shows total days 30 absent days 4(these are the weekly offs) So no attendance bonus gets paid Alternatively the situation should be that the system should show his total days as 26/27 instead of 30/31 & if he doesn't take an off for more than two days,he should get attendance bonus.Also the system should be able to mark him absent on Thursday which is weekly off for others This has to be done only for Maintenance Department 83. I have a Vacation quota 40 which has a balance of 32 hrs. Employee takes a deduction from the Quota 16 hrs this week and I am writing the balance of the Quota into wagetype 4610. Here is the rule I have written HRS=FR40F, ADDDB 4610. The result in 4610 still shows 32 hrs instead of balance 16 hrs. try HRS=FR40C

90. I am working on 6.0. The company has decided to implement only Organizational Management, Time management and Training and Event Management modules. Can any one please tell me if its possible to do this without implementing personnel management??? And how would it be useful???ffice:office" /> ANS:1 Assuming that for instance a nameand a prenameare considered as "Personnel Management" (or personnel administration PA) data, the use of only organizational management ffice:smarttags" />OMwill quite limit the advantages. You could use OM to maintain the organizational chart, but without names on it... might be a bit boring. But if you use Personnel Time Management PTand Training and Event Management TEM, I assume, that you use PA as well. Or how should this work if you are not able to assign the reported time to one person's ID? can you tell me if there is any other way??? Or if there is any other way of uploading emp master data? ANS:2 In brief: use PA. If you want to store employee personnel data (like namesand so on), then you will need the

infotypes from personnel administration PA. Of course you could do it by creating customer specific tables (but with this solution you just create an easy version of what SAP already provides; meaning a lot of effort that is already covered if you use PA). I have read the issue about implementing OM without PA. This can be possible, but if you are going to implement also times and event, you should need PA. If you dont have PA, you wont have times or event. For Times and Events, is requierement PA and OM. ANS: 3 As long as u dont process any employees in SAP, PA module may be left... But if u want to process an emp u should hav hired him and that happens in PA... so check the pros & cons and then go for implementing 91. Could you please explain me where we use time constraint clsses with respect to differend modules (PA,Time Mgt...etc.) ANS:1 time constraints are used to define the storage of data for an infotype there three major time constraints tc-1 tc-2 tc-3 like if a infotype has TC-1 then for that infotype there should be a continuous record, there should be no over laps, last record cannot be deleted like this the TC charecterics are defined. you can go through F1 there everything is explained ANS:2 Time constraint classes are assigned to the time infotypes and subtypes in the HR Time Management component, and define the collision rules which apply to each. http://help.sap.com/erp2005_ehp_02/helpdata/en/8a/9847f246c411d189470000e829fbbd/fr ameset.htm ANS:3 w.r.t to OM module: Time constraints are a tool used internally by the system to protect the integrity of information. You use time constraints to prevent you from creating records that contradict each other. For example, a position can belong to only one organizational unit at one time. If the system allowed you to assign the position to another organizational unit during the same timeframe, there will be two contradictory records. Then, if you try to report on the data, the information will be useless. There are four classes of time constraints:

Time constraint 0 This allows for: * A maximum of one infotype record of the same type and for the same object,

to exist at the same period of time * No changes to be made to the record at all

Time constraint 1 This allows for: * A maximum of one infotype record of the same type and for the same object, to exist at the same period of time * No gaps to exist between the records * Some changes to be made to the attributes of the record

Time constraint 2 This allows for: * A maximum of one infotype record of the same type and for the same object, to exist at the same period of time * Gaps to exist between valid records

Time constraint 3 This allows for: * Multiple infotype records of the same type and for the same object, to exist at the same period of time * Gaps to exist between valid records. For example, there could be a three-year gap between the validity periods of two infotype records that exist for the same object.

ANS: 4 Time constraint Class is used to determine, whether the record is allowed for overlapping or not and how many times it has to occur during the execution. TCC 1 : NoGap, No overlapping at any one time ( Mandatory Record ) TCC 2 : Gap, No overlapping at any one time. ( Optional, but if maintain, only one record is allowed) TCC 3 : Any number of Records.

ANS:5 The few remaining ones are:Time constraint A :- Infotype exists just once from Jan.1 1800 to Dec.12 9999 Time constraint B :- IT exists for maximum of once from Jan.1 1800 to Dec.12 9999 Time constraint T :- Time constraint is based on subtype or subtype table Time constraint Z :- Time constraint for time management infotypes -----> T554Y 92. I want to configure for overtime. The scenario is as below :-

On Weekday = Basic Pay/208 * 1.25 On Sundays = Basic Pay/208 * 1.50 On Public Holiday = Basic Pay/208 * 2.00 ANS:1 Just write a PCR for your algorithm. SAP has delivered with sub-schema's namely TW15 and TW30 for overtime after 8hrs/day and overtime after 40hrs/week. Place your rule in one of the above 2 sub-schema's as per your company needs. My requirement is overtime is applicable after completion of 48 hours in a week. As told earlier three calculations for three types of days. Can you brief me how I should modify schema to meet the requirement with any example as I am unable to read the coding. For your info I use negative time management. Time status - 0, only absence is recorded. When I go to TW15 schema i can findT001 and T002 where and how I should mention the calculation. ANS:2 TW15 is the sub-schema for overtime more than 8hrs/day. In TO01 if you notice carefully, you will see the HRS operation which compares whether the employee has completed 8hrs in a day or not. For a test run, try changing that 8 to 10, save as a different name and run and see whether it works for overtime more than 10hrs/day. Read the help on HRS. It is a very important operation in Time Management module.

93. Difference between skeleton time type and flex time type ANS:1 A time account in the standard SAP System in which you manage an employee's payment-related times. Skeleton time is determined in time evaluation.

Example: Skeleton time in the standard SAP System consists of: Attendance, absence, and off-site work in an agreed period (defined by start and end of working time) Overtime hours that exceed approved overtime Paid break times

FLEX Time: Personnel Time Management (PT)

A working time pattern in which employees determine their start and end times, and employees must work a certain number of hours within a defined period of each day.