Time Evaluation Forms

Hi experts,
Could anybody help me on how to change the window width of a Time Evaluation form? The problem is that I want to add extra columns but it doesn't allow.
I tried se71 but it doesn't help in my case.
Thanks in advance

Hi,
You could use Designer to create forms and save them as PDF. But in order for them to be filled up using the free Reader, you'd need to have the PDF reader extended. And for that, you'd require the server.
However, with the LC server on the backend, it opens up a whole lot of other possibilities like submitting the data into a workflow for further processing, or using the same form design and have it rendered into HTML so that the data could be captured using just a browser, across devices.
As regards LC, it is not going anywhere. In fact, in March last year, Adobe had a major release, ES4 out with a lot of innovative technologies built in that further augment the product. Please see http://helpx.adobe.com/livecycle.html for more on that. We may not have upgraded the Infopath filter since sometime now, a fact, I am sure you are well aware!

Similar Messages

Absence Quota creation during Time evaluation - Orgnaisational Assg change

Hello Experts,
I have one emplyee for whom the Transfer action has been run - his personal subarea has been changed from 1633 to 1654
obviously the ps grouping for time quota type changed form 35 to 40.
so function QUOTA is creating different quota for this employee than what there exist right now for infotype 2006.
so during time evaluation below error is comming.
    Error entry no. 83 Error when creating absence quota
    A complex application error has occurred
Kindly let me know how to overcome this error.
Thanks Jay

The reason 'error no. 83' occurs in RPTIME00 is because function QUOTA
is trying to generate a quota type which does not exist for the employee
on a specific day. It must have existed some time before. Normally,
the function QUOTA displays an error message concerning the
non-existing quota types. In this case, the 'error no. 83' can only
occur in the following scenarios:
1. If you deleted a quota type that was to be generated
2. If an employee has an organizational reassignment to a personnel
   subarea or employee subgroup which have different groupings for quota
   types and for these groupings the 'old' quota type does not exist.
Function QUOTA checks to determine if the quota types to be generated
are valid. If the quota type is not valid anymore (see reason 2) then
you will get a warning message.
"the problem in these situations was the following:
RPTIME00 is trying to generate a quota for a validity interval
(defined in table T559D) during which the employee belongs to two
different groupings, due to the transfer.
In your case the quota type should be generated with a validity interval
that begins before the employee's organizational change.
Unfortunately, for the time between the validity begin up to the
transfer of the employee there is no entry in table T556A for this quota
type.
or check the config of this quota running Rptquota_check in se38
Therefore, it is possible to solve the problem by defining a dummy
quota type for the 'old' groupings of the employee (table T556A).

Cross Day work issue in Time Evaluation for positive recording.

Dear Experts,
We would like to know whether anyone else has faced the below described issue before or has any suggestions for the same.
Issue Background: We are uploading time events from the clocking recording system into SAP using an interface program. The clocking events are loaded without indicator 'M' and based on whether they belong to current day then assignment is '=' and '<' for previous day assignment.
Issue Description: Some operational staff have planned daily shifts from 00:00 - 08:30. Hence they can clock-in before 00:00 on the previous day and since there is no 'Next Day Indicator' in SAP, we split the time events so that if the clock-in is at 23:00 previous day then the time pairs are formed as
23:00 - 24:00 Current Day with Day assignment '='
00:00 - 08:30 Next Day with Day assignment '='
When we run the time evaluation, the day assignment for Next day pair 00:00 - 08:30 is automatically changed to '<'. This makes the Next day without any events and the time evaluation throws error in the next day.
Now instead of automatic upload, if we manually upload the same time events, the records are as follows:
23:00 - 24:00 Current Day with Day Assignment '+' and Origin Indicator 'M'
00:00 - 08:30 Next Day with Day Assignment '+' and Origin Indicator 'M'
Now if we execute time evaluation, the behaviour is as per expected and the time evaluation doesn't change the day assignment for any records.
Work Around Proposed: Keep atleast 1 sec difference between the time events say the above records can be uploaded as follows:
23:00 - 23:59 Current Day with Day assignment '='
00:00 - 08:30 Next Day with Day assignment '='
But we would like to avoid this if possible.
Summary: In brief we would like to know whether why time evaluation has different processing for Origin indicator 'M' and SPACE.
Many thanks for your inputs in advance, thanks.
Regards,
Roshan.

Hi,
see thread
Time evaluation -early clockin for shifts starting at midnight ?
maybe of interest
bg
Edited by: bg on Sep 16, 2010 9:26 AM

LSO evaluation form workflow

Hi All,
I'm using the LSO evaluation form wizard to create my post-training evaluation form.
Currently, the training center separated 1 lengthy evaluation form into 3 forms. So, each time an evaluation form is assigned to participants, it will trigger workflow to send out an email notification to them.
My question is how can we put the title of the 3 evaluation forms into 1 single email notification????
Cheers,
Jill

Hi Jill!
Can you please provide more details about the LSO Evaluation form wizard you are referring to in your post.
Regards,
Ravi Sekhar

PT40- How to pick customised time statement form

Hi all,
I have created a Z Tiem Statement form, how can i use that while doing Time evaluation in Pt60 as well in PT40.
Suggest me how to do this ?
Regards,
Evani

hi allan,
cud u plz help me how to sort out this problem actually in mu company the same scenario is here need to be display pe51 form instead of standard hrforms.....
plz help me how will i replace this "hrforms with pe51"..

Time Evaluation Schemas

Hi All
Please suggest me regarding Time Evaluation Schemas.
We have schemas like TQTA, TM04, TM00 Etc. when we use PT60.
What are the different uses of these schemas & what are the situations when we need to use these schemas.
Which schema to use when & where?
Please Suggest
Thanks & Regards

Hi,
TQTA: Generate Absence Quotas only, wtih this schema, we can update the IT2006. Time managemetn status is 7.
TM04: Time Evaluation Without Clock Times, Time managemetn status is 9 or 1 in 0007IT
TM00:Time Evaluation with Personnel Time Events/with clock times. Time managemetn status is 1 in 0007.
For both TM04, TM00 schemas we are using the one T,code that is PT60. THis PT60 t.code create through RPTIME00 program.
Schema TM00 processes time events that have been recorded at a time
recording terminal, or the time pairs formed from the time events in
pair formation. Attendances and absences are also imported.
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).
The time worked by the employee is recorded in the Attendances infotype
(2002), and not as clock-in and clock-out times. When processing
clock-in/out times, the emphasis is on the length of time between the
postings and not on the times at which the postings were made.
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).
If negative recording is used, the planned hours are generated on the
basis of the daily work schedule. Recorded absences and some attendance
times are deducted (see schema TP01.)
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.
You can use schema TQTA to accrue absence quotas automatically in time
evaluation. The functionality is limited to the task of generating
quotas, that is, time balances or time wage types are not formed.
The schema is designed for employees who do not normally participate in
the daily time evaluation for the purposes of managing time accounts or
forming wage types. Using schema TQTA to determine absence entitlements
has the following advantages:
o   Quotas can be recalculated flexibly.
o   The need for a recalculation is recognized automatically.
o   Processing is carried out for every day in the period, leaving no
    gaps.
We have schemas like TQTA, TM04, TM00 Etc. when we use PT60.
Regards
Devi.

Time Evaluation Re Run in Mid Month & Mid Mont Initialization !

Hi There,
i was trying to run Time evaluation for the period 01.04.2011 to 31/12/2011.
from April, that is 01.04.4011 to 30.06.2011 Time evaluation was good, now time evaluation has to run from 01.07.2011 but time evaluation has repeated from 12.06.2011 to 11.07.2011 as Initialization period 07/2011, and the same scenario is repeated for the rest of the year..all periods are initiated on 12th of each month from 6th month that is 12.06.2011.
i was been trying to rectify this issue but was not bale to solve it, could any one please look in to it and let me know how to solve it?
your help is appreciated.
Thanks
Kumar

Can you please regenerate Period Parameters for 2011 year in T-Code for OG00 for period parameter 01 and then give the hire date in the field Forced Recalculation as of run in PT60 and run the time evaluation.
Best Regards,

Use of Time Evaluation to generate Absence Quota

Hi,
We are planning to use time evaluation to generate absence quota. At the moment we are using RPTQTA00 report to generate Absence Quota. We have negative time management and since, the project has already gone live i have very limited scope to change the basic settings for example we do not have any employee subgroup to identify part time employees, PT & FT are in one employee sub-groups. We have only one ESG & PSG for time recording, time quota etc. The base entitlement is defined for the FT employees and it is reduced propertionately based on the employement percentage in IT0007. Now we are going to adopt a change in design, and planning to have specific work-schedule for PT employees. In that case, we will not have the scope to maintain %age in IT0007 for part time employees but exact no of working hours will be used. It means that system will treat the PT emploees as FT while generating absence quota and output the FT absence entitlement. As i said earlier we can not differentiate PT employees from FT employees based on ESG or PSG, i can not create a separate quota selection rule for part time employees. Hence, we are moving from running RPTQTA00 report to time evaluation for absence quota generation purpose.
Now can anybody please help finding a alternate solution for the above, if it is possible to do it through report RPTQTA00 or we have to adopt the time evaluation. In case we are going to generate absence quota through time evaluation, can we only generate absence quota and skip anything that is related to payroll.
Any comments/suggestion/advise will be very helpful to us.
Thanks.
Sujit

We are not able to generate absence quota for part-time employees as when we do that, system is treating PT employees as FT employees and the FT base entitlement is referred while calculating absence quota. i can not define separate absence entitlement for PT employees as we have only one ESG and PSG, and based on this quota selection group is defined. The QUOMO feature is defined based on work contract - employee sub-group (there is no separate emp sub-group for PT employees) - Pay Scale Group. We are having this problem as we have specific work schedule for PT employees now (Ex. we create 3 days work schedule with 15 hours: 4.5,4.5, 6 hours) and we are not maintaining employement percentage for them. So system is treating PT employee as FT employee with 100% employement percentage. Please let me know if you need any specific info to understand my issue.
Thank you so much for the response.

Quota updation upon accural in no time evalution(TMSTA=0)

Dear Team,
We went go live on one and half year back and using no time evaluation for all employee in info type 7.
At the time of financial year starting we will generate Absence quotas say CL, PL through RPTQTA00,
Entitlement is 12 days,Hence April month it self, record will be created in info type 2006.
In mid of month/year Joining employee, based on prorate base entitlement will be updated in info type 2006.
Now Client/My requirement is:
He does" t want to give total entitlement in april it self. every month 1 leave needs to updated. (12 days entitlement for CL, hence prorate base 1 day in April once we run in Payroll, 2 days (11) in May, 3 days (11+1) in june.. so on and so fourth...
How we can configure this. Please help me on this.
Regards,
MVR

Hi,
Try the following setting.
SPRO -> IMG -> Time Management -> Time Data Recording and Administration -> Managing Time Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements -> Rules for Generating Absence Quotas -> Set Base Entitlements
In this select your Quota type and give ENTITLEMENT CONSTANT as 1.
RELATED TO PERIOD as Accrual Period
SPRO -> IMG -> Time Management -> Time Data Recording and Administration -> Managing Time Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements -> Rules for Generating Absence Quotas -> Define Generation Rules for Quota Type Selection
In this, double click your Quota Type then Goto Accrual Period Tab and select Month
Now, the Program RPTQTA00 has to be run run every month with suitable Data Selection Period
Thanks and Regards
Kiran

Time Evalution & PDC recalculation

Dear Experts!
I have to face an weird problem. My scenario is as below:
1. I create a new Time Type to calculate the working date of employee in every month. My time wage type will replace an existed wage type in system, because it's configuration is not correct.
2. After checking on Dev, QAS, the value of Earn Leave ( generated monthly) is CORRECT, we move this TR to PRD.
And after moving it to PRD, there are a lot of employee re-run PT60 from Go Live Date. I don't know why.
Could you please guide me the way to know which recalculation date in Time Evaluation, and How SAP decide the date to retro Time Evaluation in PT60? I just guess the field PDC recalculation in IT 3 ( I read F1 of this field), but now I'm mixed about this information.
And you know, because we change the Earned Leave in Time ( I run PT60) eg: Earned Leave for Feb-2010 will be modified, of course the value of Time Wage Type will be changed. The date Earliest MD change in IT3 is NOT Changed. But the Payroll for this guy is retro from Mar-2010.
Can you please help me clear the way to re-run Time Evaluation & Payroll.
Regards!
Woody.

Hi Woody,
Please note the below Points carefully, which may help you to solve your issue:
Note -
Retro Runs are based on Infotype, If you change any Infotype related to Time / Payroll, then the system automatically maintain the "Earliest MD Change" date in IT 0003.
For IT 0003
1) When you change employee data that is relevant to payroll, the system stores the earliest date from which the master data change is valid. This date can be a future date after the last payroll run
2) The system deletes the date in the Earliest master data change field after successful completion of the payroll run.
The earliest recalculation date for time evaluation is also queried when master data and time data that is relevant to retroactive accounting is changed.
For Payroll Controll Record
Earliest retroactive accounting period
1) Retroactive accounting in payroll can begin on the start date of this period at the earliest.
2) If changes relevant for retroactive accounting have been made before this date, the system does not take these into account in either current or future retroactive accounting. However, retroactive accounting is initiated up to this period.
3) If the earliest personal retroactive accounting date (from IT 0003) differs from the earliest retroactive accounting period, then it will be backdated to the later date.
Comments:
1) May be the Time Wage Type Change (related to Payroll) might have triggred the Retro Payroll, and once it retro run happens the "the system delets the date in the Earliest Master Data Change Field", that is why you are unable to find that field with values.
2) Check the "Earliest Retroactive Accounting Period" in Control Record (Tcode PA03), so that you will get some idea. why it has happend.
3) While determining the Retro, the system checks the IT0003, Control Record, it will take the date whichever is backdated date.
Hope this helps.
Regards
Venu

Error in time evaluation

Dear All,
time evaluation is throwing an error msg "No entry in table T001P for key" for only one employee in the time evaluation display log.
Its happening in the initialization part in time evaluation. for example,
If i run the time evaluation for the month of 01.01.2009 to 24.02.2009. error message throwing on the initialization of 01.02.2009.
I have checked all the groupings in table V_001P_all. All are correct.
Where should i do the correction. Pls
Br.
Manjula

Hi Sikindar,
I have checked all grouping in V_T001P_All every think is correct,
And how can i check with grouping with dates??
This employee getting error message only in the initilation part in time evaluation log.
example if i run the time evaluation from 01.01.2009 to 01.03.2009 . time evaluation running only from 01.01.2009 to 31.01.2009 . its not moving to next month.
if i run time evaluation from 01.02.2009 to 01.03.2009 then its running only 01.02.2009 to 28.02.2009 its not moving to next month.
In the initialization in the next month im getting error message (no entry in table T001P for key)
Thnaks.
Manju

Time Evaluation Re Run

Hi There,
i was trying to run Time evaluation for the period 01.04.2011 to 31/12/2011.
from April, that is 01.04.4011 to 30.06.2011 Time evaluation was good, now time evaluation has to run from 01.07.2011 but time evaluation has repeated from 12.06.2011 to 11.07.2011 as Initialization period 07/2011, and the same scenario is repeated for the rest of the year..all periods are initiated on 12th of each month from 6th month that is 12.06.2011.
i was been trying to rectify this issue but was not bale to solve it, could any one please look in to it and let me know how to solve it?
your help is appreciated.
Thanks
Kumar

Hi,
thanks for reply but till now i have not yet customized the schema or any pcr, so it is pretty much standard TM04 schema, could you plz elaborate your answer?
Thanks.
Kumar

Time evaluation:Regeneration of leaves for past with new slabs.

Hi Gurus
Find below our requirement and advice accordingly
1.Employees annual leave entitlement slabs are bifurcated based on length of service as below
Tenure with Company      Eligibility/Month
1. Probation        1.5 Days
2. 0-3 Years                           2 Days
3. >3-6 Years     2.08 Days
4. >6-10 Years     2.16 Days
5. >10-20 Years     2.33 Days
6. >20 Years Above     2.50 Days
2.Probationary /regular employee bifurcation is done at employee subgroup level
Emp Subgroups     Employee
1. 01 - 10            Regular
2. 11 - 20                          Probationary
3. We use time evaluation schema ZM01 copy of TM01.
4. On hiring, probationary will be assigned with employee subgroups 01-10 via hire action.
5. On confirmation, probationary will be changed with employee subgroups 11-20.
6. For probationary, system will generate monthly accruals of 1.5/month days till confirmation.
7. After confirmation system will start generate 2 days/month.
8. We have a requirement that after confirmation action system should re generate the leaves from date of joining as per the employee after probation.
Illustration:-
1. Employee joined under probation on 01.06.2011.
2. His monthly annual leave accrual till 31.12.2011 will be 9days i.e. (1.5 days * 6 months)
3. On running confirmation action system should regenerate his annual leave from his date of joining with the new slabs and it should be 12 days i.e. (2 days * 6 months).
Is it feasible in time evaluation. Pls advice.
Thanks in advance, Thanesh

Hi
I have a couple of queries on this scenario.
We can do it on the base of base entitlement but there is action dependency then its better to write PCR.
First Check action type --> Then give the quota as 1.50 or 2 days as per req the nupdate the quota.
Here before writing the PCR we need to take care of one thing that once employee changes the action it could not check the old action. Say for Ex when i am checking the probation and changed the Probation to permenant then it should not check the Probation again. So we need to put a counter check here.
So i am writing a logic like first will check Probation an
For Ex : We take Probation Action type as 01 and Permenant Action type as 02
ZT05 Personnel Calculation Rule ZT05
      " HRS?1      Decision op.     HRS
        " <
          " OUTWPMASSN Action Type
            " 01
              " OUTWPMASSN Action Type
                " 02
                    HRS=1      Set
                    ADDDB1230 Add to day balance
                    HRS=1.50   Set
                    ADDDB1234 Add to day balance
              " OUTWPMASSN Action Type
                " 02
                    HRS=2      Set
                    ADDDB1234 Add to day balance
Please create Time Type 1230 and 1234 at T555A.
Hope this helps you. All the best. Let me know how it worked.
Reg,
Srini

Time Evaluation quota not transferred

Hi,
For a couple of employees when i run time evaluation, quota type 91 gets generated and transferred but quota type 93 does not. It remains 0.
On analyzing the logs, i found that for these employees, there is an entry in table QTTRANS with the quota amount that was supposed to be transferred.
According to doc on help.sap.com, {Table QTTRANS indicates the status of the transfer pool for each day. The cumulated entitlements are indicated until they have been transferred to the *Absence Quotas *infotype (2006) or until the entitlement has expired.}
This means the quota amount for quota type 93 is being generated, but is not being transferred to infotype 2006. Also, the transfer time in the rule is not being shown on ad-hoc basis for these two employees for this particular Quota type. The other quota type 91 which is evaluated on exactly the same basis is working fine.
I have checked the transfer period in config and it is monthly. Also, for other employees in the same grouping PSG, ESG, quota is being generated and transferred correctly.
Quota of 2.5 should be transferred on the last day of every month.
Further, analysis of QTTRANS over a period of time reveals the following results:
Jan05 Quota transferred : 0 ;Table QTTRANS: 2.5
Feb05 Quota transferred : 2.5 ;Table QTTRANS: 2.5
Mar05 Quota transferred : 2.5 ;Table QTTRANS: 5.0
Apr05 Quota transferred : 7.5 ;Table QTTRANS: 2.5
May05 Quota transferred : 10 ;Table QTTRANS: 2.5
Jun05 Quota transferred : 10 ;Table QTTRANS: 5.0
Jul05 Quota transferred : 10 ;Table QTTRANS: 7.5
Aug05 Quota transferred : 17.5 ;Table QTTRANS: 2.5
Sep05 Quota transferred : 20 ;Table QTTRANS: 2.5
Oct05 Quota transferred : 20 ;Table QTTRANS: 5.0
Nov05 Quota transferred : 25 ;Table QTTRANS: 2.5
Dec05 Quota transferred : 25 ;Table QTTRANS: 5.0
For the entire year, it should have generated and transferred 30 but actually it is 25.
I would be very grateful if anyone can point out the cause of this issue.
Thank you,
Regards,
Zubair

HI,
You can view in IT2006 accumulated Quota means current year Quota + carry over Quota. In Time cluster tables "QTTRANS" you can view Quota transfer value.
Refer T.code: Pt66 for Time cluster tables.

Time evaluation generate check out entry

Dear Gurus,
How can we generate Check out entries thru Time evaluation?
The sales employees come to office in the morning, they punch in and leave for sales activity. They don't get overtime, but pay / absence quota deducted if they don't check in in the system.
While running Time evaluation, I am getting error in TE03 (delimiting error). I hv tried creating second entry using TF00. Its not working. Has anybody any solution for this?
Regards,
Vijay

Hi Gurus,
I am rephrasing my requirements. have 2 queries,
1. Sales Employees make only Clock In entries. System should generate the clock out entry or should not throw any error message. System should consider total working time from daily work schedule.
   - TE30 function is generated the entry in TEVEN table based on planned end time, but we need to create the entry in IT2012 otherwise, while processing next days entry, it generates error.
   - Will TF00 create an entry in Time Events IT2051 ? IF yes, how can I tweak TF00 rule to generate Time out entry.
2. General Staff working hours need to be calculated from Shift Start even if they come early. Max working time is 12 hours with 4hrs from start of end of Shift period
   - If shift start is 7AM, I have defining Start tolerance as 6AM to 7:05AM, but still the system is considering the Clock In time for hours worked.
I have to write this condition. How to write ?
   If Clock-in Time < Start Time
      Then   TIP->From = Start Time
I believe it has to be put in TL10 after rounding the Check in & check outs.. so as to update table TIP,
Please suggest,
Regards,
Vijay

Time Evaluation Forms

Similar Messages

Maybe you are looking for