on 03-22-2012 9:17 AM
Hi,
In our organization, 200 absence/attendance applications, on average, are posted through ESS in a month. We face one or two cases where users cannot apply absence through ESS due to the error "No time constraint reaction for infotype 2001". When we try to pass the entry through R/3, it shows the same error but it goes away when we press enter 2-3 times and we can save the absence entry.
I understand the concept of time constraint and why it is used for but cannot find out the root cause or solution of this behavior.
Need your help to solve this.
Regards
Palash Mukherjee
You need to revisist your absences customisaiton let me explain
This message appears if there is no Time Contraint Reaction or Time
Contraint Class entered for the absence type. So, please check the
customizing in the following IMG-Path again:
Time Management
-> Time Data Recording and Administration
-> Specify System Reaction to Overlapping Time Infotypes
Please also check your configuration in table V_554S_O.
The system is trying to perform a collision check on this two records
(checking for overlaps with other time infotypes). To do this it looks
for the time constraint class for the absence type (V_554S_O) and
checks V_554Y_B for a reaction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for your reply.
I checked the configuration as you suggested:
Specify System Reaction to Overlapping Time Infotypes:
For infotype 2001 - Time constraint class 01 to 09 defined and against each combination, reaction indicator is defined in terms of A or E.
V_554S_O:
For the given PSG and absence type:
Time constraint class 2 and att./absence class 1
V_554Y_B:
Infotype and Time constraint class and reaction indicator defined.
Generally, collision check works for all employees. We get proper message in almost all cases barring a few where we get stuck and that goes like random selection. We have not yet unearthed any pattern in this behaviour.
Regards
Palash Mukherjee
In last few days, we had 2 cases where system threw time constraint reaction error message but there were approx. 90 other cases which successfully went through. For the two employees, I checked all the mapping I knew of and all were found to be the same as they had been before. These two employees applied sick leave in the past without any problem.
Not very sure how to approach this problem,
Thanks & Regards
Palash Mukherjee
Hi Palash, standard time constraint classes are from 01 to 09 (per V_554Y_B table), so all absences should have a class between 01 and 09. You can use 02 for example. In T554S you can find the constraint class assigned to each absence/attendance.
In ESS Leave Request usually warning messages are shown but it doesn't avoid to review and save data. Error messages conceptually should avoid to save data, but in my experience some error messages in Leave Request are passed by clicking Review button 2 o 3 times. Anyway you should use this 'behavior' in very particular scenarios (i.e. testing the ESS services while the Time tables are being configured).
Another way to 'jump' the error message is to use the Output of messages configuration (V_HRWEB_TRS_MESS table), where you can convert an error message into a warning or a information message, or even hide it to final users.
But let me tell you that is not advisable to 'jump' or 'ignore' error messages due to lateral effects like inconsistent data.
Regards
I am attaching the snap-shot of T554S for one absence type. To my knowledge, configuration is correct. This error comes for one or two stray cases in a month; frequency is not even one percent of the absence applications passed in the system in a month. I am tracking this issue for my academic interest, want to know as to why this message is coming....
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.